From: <fap...@gm...> - 2010-03-22 20:12:01
|
Hello Raphael, Thanks for the answer. Although at this moment I do not get results from adding the options, but I know now at which section of the manual I have to look at. Again it is in those books I never read when using someone elses software. I want to thank you again for the swift and pointed answers. They solved my problems I was struggeling with for several weeks now. With best regards, Frans. On 22-3-2010 19:26, Raphael Neider wrote: > Hi, > > >> I got this from a single .c file witht the added option -V to the >> compiler. >> >> >> >> + C:\PROGRA~1\gputils\bin\gpasm.exe -c "obj\Release\SDCC_PIC_Using.asm" >> Linking native: bin\Release\SDCC_PIC_test >> message: using default linker script "C:\Program >> Files\gputils\lkr\16f874.lkr" >> warning: relocation of section "UDL_idata_0" failed, relocating to a >> shared memory location >> warning: relocation of section "ID_idata_0" failed, relocating to a >> shared memory location >> > This is what I meant with -r: allow the use of SHAREBANKs for DATABANKS. > Your PIC seems to have memory that is accessible in multiple/all data > banks. Such memory regions are declared as SHAREBANKs in the linker > script and are not usually used for regular data -- they are used to > implement software stacks or "access banks" like the pic18f* have. > > The warnings do not imply any problem (maybe your device is described > using only SHAREBANK entries?) and might well be degraded to mere > informational rather than warning. > > >> + C:\PROGRA~1\gputils\bin\gplink.exe -I"C:\Program Files\SDCC\lib" >> -I"C:\Program Files\SDCC\lib" -I"C:\Program Files\SDCC\bin\..\lib" >> -I"C:\Program Files\SDCC\bin\..\lib\pic" -w -r -o >> bin\Release\SDCC_PIC_test obj\Release\SDCC_PIC_Using.rel libsdcc.lib >> pic16f874.lib >> Process terminated with status 0 (0 minutes, 4 seconds) >> 0 errors, 0 warnings >> >> There are a lot of -I in the +gplink, do I have to investigate this or... >> > These paths are generated by sdcc and (after ../ resolution) refer to > the same directory. You need to include only the "actual" path > to the .lib files. > > >> Could you comment on the two warnigs about the relocation? >> > See above -- harmless. > > > Raphael > |