Compile to HEX error

[Ralph]

I was using the EEPROM component and had some compiling errors, so I downloaded your sample read / write eeprom and got the same errors. Please see the compiler text below.

__________________________________________________________
File name: C:\ULGLC3QT\EEPROM%20Example[1].c
Generated by: Flowcode v3.2.2.40
Date: Thursday, March 06, 2008 18:01:52
Licence: Professional
Registered to: xxxxxxxxxxxxxxxx

http://www.matrixmultimedia.com

Launching the compiler...

C:\Program Files\Matrix Multimedia\Flowcode V3\BoostC\boostc.pic16.flowcode.exe -v -t PIC16F88 "EEPROM%20Example[1].c"

BoostC Optimizing C Compiler Version 6.70 (for PIC16 architecture)
http://www.sourceboost.com
Copyright(C) 2004-2007 Pavel Baranov
Copyright(C) 2004-2007 David Hobday

Licensed to FlowCode User under Single user Pro License for 1 node(s)
Limitations: PIC12,PIC16 max code size:Unlimited, max RAM banks:Unlimited

internal error: can't parse input file name 'EEPROM%20Example[1].c'

EEPROM%20Example[1].c
Starting preprocessor: "C:\Program Files\Matrix Multimedia\Flowcode V3\BoostC\pp.exe" EEPROM%20Example[1].c -i "C:\Program Files\Matrix Multimedia\Flowcode V3\BoostC\include" -d _PIC16F88 -la -c2 -o EEPROM%20Example[1].pp -v -d _BOOSTC -d _PIC16

runtime error R6002
- floating point not loaded
Error: preprocessing error

failure
.....
Return code = 1

Flowcode was unable to compile the flowchart's C code due to the following errors:

If your flowchart contains C code, please review this carefully. If your flowchart contains no C-code or you have thoroughly reviewed the code, contact Technical Support.

FINISHED
________________________________________


Any thoughts on the cause?

Thank you,
Ralph

[Ralph]

Disregard the above message. I found that the file name was to long.

Ralph

[Benj]

Hello Ralph

The length of the file name should not effect the compilation process.

However the square brackets in the file name would probably cause problems.

[echase]

What is allowed and not in the filename?

I have had all sorts of file names and they are mostly OK although I thought there was a length limit. But recently its gone pear shaped when I copy a working file to a new filename almost the same and it says ‘hex can not be found’

Filenames that work are:-

Test
Test1
2520V4 10bit3
2520V4 10bit2

But not:-

2520V4 10bit4
2520V4 10bit3a
2520V4 10bt3a
2520V410bit3a
2520V410bit3a
2520V410bit333

Some of those are no longer than ones that do work.

I am using the PICkit 2 programmer with your standards mods to Compiler Options

[echase]

Do you have an answer to this? I guess it's more a PICkit problem than Flowcode so not fair to ask you.

Also do you prefer tagging questions onto very old similar posts or generating new ones?

[Benj]

Hello

Yes the filename problem you are having does indeed seem very strange. I wonder if it is because somewhere along the lines the Dos 8.3 filename is being used instead of the NTFS filename. eg 2520V4~1.hex this may explain why some work and other dont. Eg I dont know what happens if you have more then 9 file names that all start with the same characters.

2520V4~1.hex
2520V4~2.hex
...
2520V4~9.hex
??????

For my money I prefare tagging older posts as it means less searching for related solutions etc. However this can be annoying when you just want to post a quick question so im happy with either method.

[echase]

Have not fully resolved this, but as long as I use short names I have not yet experienced the error.