Thread: [Flashforth-devel] FF5.0 compilation problem
Brought to you by:
oh2aun
Menu
▾
▴
flashforth-devel
|
From: Attila H. <att...@gm...> - 2024-05-19 16:25:28
|
Hi Mikael, and the other FF friends, I have downloaded the latest version of the FF5.0 to generate an uptodate hex file instead of my old one for PIC18F26k42. Unfortunately it caused some problem. Two lines in the ff-pic18.S makes error: ../src/ff-pic18.S:877:: error: (876) syntax error ../src/ff-pic18.S:878:: error: (800) undefined symbol "USBDriverService" Without theese lines the compilation seemingly succesful, but the result is unusable. Although the hex file contains the FF code, but it is starting at $DC60 not at zero address, The 0 to DC5F range contains FF. The eeprom also full of FF. Please help me! BR: Attila Herman |
|
From: Mikael N. <mik...@fl...> - 2024-05-19 19:48:25
|
Hi Attila. Those two lines need to surrounded by "#ifdef USB_CDC". I will update the repository. To get a proper hex file you need to give command line parameters to the linker as described in p18f-main.inc PIC-AS does not have any linker scripts. The parameters needs to be supplied on the command line in PIC-AS global options. BR Mikael On 2024-05-19 19:25, Attila Herman wrote: > Hi Mikael, and the other FF friends, > I have downloaded the latest version of the FF5.0 to generate an > uptodate hex file instead of my old one for PIC18F26k42. Unfortunately > it caused some problem. > Two lines in the ff-pic18.S makes error: > ../src/ff-pic18.S:877:: error: (876) syntax error > ../src/ff-pic18.S:878:: error: (800) undefined symbol > "USBDriverService" > Without theese lines the compilation seemingly succesful, but the > result is unusable. Although the hex file contains the FF code, but it > is starting at $DC60 not at zero address, The 0 to DC5F range contains > FF. The eeprom also full of FF. > Please help me! > BR: > Attila Herman |
|
From: Attila H. <att...@gm...> - 2024-05-20 10:06:44
|
Hi Mikael,
Thank you for your reply!
Unfortunately the main problem is not solved.
Indeed, the unusable hex file is generated only without the needed FF
options, but using it makes errors.
I tried to put it into different location in PIC-AS global options, but it
allways gives errors.
Without any modification the linker "Generated command line" field contains:
-mcallgraph=std -Wl,-Map=${FINAL_IMAGE_NAME_MINUS_EXTENSION}.map
-mno-download-hex
After put the needed FF options into "Custom linker options" field, the
"Generated command line" changes:
-Wl,-Wa,-a
-Wl,-pudata_acs=000h,-pudatabig=050h-presetVec=0h,-phi_int=8h,-plo_int=18h
-mcallgraph=std -Wl,-Map=${FINAL_IMAGE_NAME_MINUS_EXTENSION}.map
-mno-download-hex
The result of Build Project:
make[2]: *** [nbproject/Makefile-default.mk:122:
dist/default/production/FF.X.production.hex] Error 1
make[1]: *** [nbproject/Makefile-default.mk:85: .build-conf] Error 2
make: *** [nbproject/Makefile-impl.mk:39: .build-impl] Error 2
If I put the FF option in the Additional Options field, the content of
"Generated command line" field does not change instantly, but the build
errors are same as above.
I don't know what to do.
( The enviroment: Win10, MPLAB X IDE v6.20)
BR
Attila
Mikael Nordman <mik...@fl...> ezt írta (időpont: 2024.
máj. 19., V, 21:49):
> Hi Attila.
>
> Those two lines need to surrounded by "#ifdef USB_CDC".
> I will update the repository.
>
> To get a proper hex file you need to give command line parameters to the
> linker as described in p18f-main.inc
>
> PIC-AS does not have any linker scripts. The parameters needs to be
> supplied on the command line in PIC-AS global options.
>
> BR Mikael
>
>
> On 2024-05-19 19:25, Attila Herman wrote:
>
> Hi Mikael, and the other FF friends,
> I have downloaded the latest version of the FF5.0 to generate an uptodate
> hex file instead of my old one for PIC18F26k42. Unfortunately it caused
> some problem.
> Two lines in the ff-pic18.S makes error:
> ../src/ff-pic18.S:877:: error: (876) syntax error
> ../src/ff-pic18.S:878:: error: (800) undefined symbol "USBDriverService"
> Without theese lines the compilation seemingly succesful, but the result
> is unusable. Although the hex file contains the FF code, but it is
> starting at $DC60 not at zero address, The 0 to DC5F range contains FF. The
> eeprom also full of FF.
> Please help me!
> BR:
> Attila Herman
>
> _______________________________________________
> Flashforth-devel mailing list
> Fla...@li...
> https://lists.sourceforge.net/lists/listinfo/flashforth-devel
>
|
|
From: Mikael N. <mik...@fl...> - 2024-07-05 15:26:02
|
Hi Attila.
Did you solve your problems ?
I get those errors if I use XC8 as the compiler. Are you sure you are
using PIC-AS?
What is the whole output from the compilation.
BR Mikael
On 2024-05-20 13:06, Attila Herman wrote:
> Hi Mikael,
> Thank you for your reply!
> Unfortunately the main problem is not solved.
> Indeed, the unusable hex file is generated only without the needed FF
> options, but using it makes errors.
> I tried to put it into different location in PIC-AS global options, but
> it allways gives errors.
>
> Without any modification the linker "Generated command line" field
> contains:
> -mcallgraph=std -Wl,-Map=${FINAL_IMAGE_NAME_MINUS_EXTENSION}.map
> -mno-download-hex
> After put the needed FF options into "Custom linker options" field, the
> "Generated command line" changes:
> -Wl,-Wa,-a
> -Wl,-pudata_acs=000h,-pudatabig=050h-presetVec=0h,-phi_int=8h,-plo_int=18h
> -mcallgraph=std -Wl,-Map=${FINAL_IMAGE_NAME_MINUS_EXTENSION}.map
> -mno-download-hex
> The result of Build Project:
> make[2]: *** [nbproject/Makefile-default.mk:122:
> dist/default/production/FF.X.production.hex] Error 1
> make[1]: *** [nbproject/Makefile-default.mk:85: .build-conf] Error 2
> make: *** [nbproject/Makefile-impl.mk:39: .build-impl] Error 2
>
> If I put the FF option in the Additional Options field, the content of
> "Generated command line" field does not change instantly, but the build
> errors are same as above.
> I don't know what to do.
> ( The enviroment: Win10, MPLAB X IDE v6.20)
> BR
> Attila
>
> Mikael Nordman <mik...@fl...> ezt írta (időpont: 2024.
> máj. 19., V, 21:49):
>
> Hi Attila.
>
> Those two lines need to surrounded by "#ifdef USB_CDC".
> I will update the repository.
>
> To get a proper hex file you need to give command line parameters to
> the linker as described in p18f-main.inc
>
> PIC-AS does not have any linker scripts. The parameters needs to be
> supplied on the command line in PIC-AS global options.
>
> BR Mikael
>
> On 2024-05-19 19:25, Attila Herman wrote:
>
> Hi Mikael, and the other FF friends,
> I have downloaded the latest version of the FF5.0 to generate an
> uptodate hex file instead of my old one for PIC18F26k42. Unfortunately
> it caused some problem.
> Two lines in the ff-pic18.S makes error:
> ../src/ff-pic18.S:877:: error: (876) syntax error
> ../src/ff-pic18.S:878:: error: (800) undefined symbol
> "USBDriverService"
> Without theese lines the compilation seemingly succesful, but the
> result is unusable. Although the hex file contains the FF code, but it
> is starting at $DC60 not at zero address, The 0 to DC5F range contains
> FF. The eeprom also full of FF.
> Please help me!
> BR:
> Attila Herman _______________________________________________
> Flashforth-devel mailing list
> Fla...@li...
> https://lists.sourceforge.net/lists/listinfo/flashforth-devel
--
--
Mikael |
|
From: Attila H. <att...@gm...> - 2024-07-05 19:35:16
|
Hi Mikael.
Sorry, but I forgot to reply the final result.
Downloaded the updated version of FF5.0 (24.05.25) everithing is solved.
I used previously also the PIC-AS, but didn't succed to build perfect hex
file. I don't know why.
Whatever the last version works well! Thank you very much for your help!
BR Attila
Mikael Nordman <mik...@fl...> ezt írta (időpont: 2024.
júl. 5., P, 16:32):
> Hi Attila.
>
> Did you solve your problems ?
>
> I get those errors if I use XC8 as the compiler. Are you sure you are
> using PIC-AS?
>
> What is the whole output from the compilation.
>
> BR Mikael
>
> On 2024-05-20 13:06, Attila Herman wrote:
>
> Hi Mikael,
> Thank you for your reply!
> Unfortunately the main problem is not solved.
> Indeed, the unusable hex file is generated only without the needed FF
> options, but using it makes errors.
> I tried to put it into different location in PIC-AS global options, but it
> allways gives errors.
>
> Without any modification the linker "Generated command line" field
> contains:
> -mcallgraph=std -Wl,-Map=${FINAL_IMAGE_NAME_MINUS_EXTENSION}.map
> -mno-download-hex
> After put the needed FF options into "Custom linker options" field, the
> "Generated command line" changes:
> -Wl,-Wa,-a
> -Wl,-pudata_acs=000h,-pudatabig=050h-presetVec=0h,-phi_int=8h,-plo_int=18h
> -mcallgraph=std -Wl,-Map=${FINAL_IMAGE_NAME_MINUS_EXTENSION}.map
> -mno-download-hex
> The result of Build Project:
> make[2]: *** [nbproject/Makefile-default.mk:122:
> dist/default/production/FF.X.production.hex] Error 1
> make[1]: *** [nbproject/Makefile-default.mk:85: .build-conf] Error 2
> make: *** [nbproject/Makefile-impl.mk:39: .build-impl] Error 2
>
> If I put the FF option in the Additional Options field, the content of
> "Generated command line" field does not change instantly, but the build
> errors are same as above.
> I don't know what to do.
> ( The enviroment: Win10, MPLAB X IDE v6.20)
> BR
> Attila
>
>
> Mikael Nordman <mik...@fl...> ezt írta (időpont: 2024.
> máj. 19., V, 21:49):
>
> Hi Attila.
>
> Those two lines need to surrounded by "#ifdef USB_CDC".
> I will update the repository.
>
> To get a proper hex file you need to give command line parameters to the
> linker as described in p18f-main.inc
>
> PIC-AS does not have any linker scripts. The parameters needs to be
> supplied on the command line in PIC-AS global options.
>
> BR Mikael
>
>
> On 2024-05-19 19:25, Attila Herman wrote:
>
> Hi Mikael, and the other FF friends,
> I have downloaded the latest version of the FF5.0 to generate an uptodate
> hex file instead of my old one for PIC18F26k42. Unfortunately it caused
> some problem.
> Two lines in the ff-pic18.S makes error:
> ../src/ff-pic18.S:877:: error: (876) syntax error
> ../src/ff-pic18.S:878:: error: (800) undefined symbol "USBDriverService"
> Without theese lines the compilation seemingly succesful, but the result
> is unusable. Although the hex file contains the FF code, but it is
> starting at $DC60 not at zero address, The 0 to DC5F range contains FF. The
> eeprom also full of FF.
> Please help me!
> BR:
> Attila Herman
>
> _______________________________________________
> Flashforth-devel mailing list
> Fla...@li...
> https://lists.sourceforge.net/lists/listinfo/flashforth-devel
>
>
> --
> --
> Mikael
>
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X