Hello Raphael, Thanks for the quick and expedite answer.
I read the hex file and there seems to be some code between 000003 to 0000d3 I got this from a single .c file witht the added option -V to the compiler. -------------- Build: Release in SDCC_PIC_test --------------- Compiling: SDCC_PIC_Using.c + C:\PROGRA~1\SDCC\bin\sdcpp.exe -nostdinc -Wall -I"C:\Program Files\SDCC\include" -I"C:\Program Files\SDCC\include" -obj-ext=.o -DSDCC_MODEL_SMALL -DSDCC=290 -DSDCC_REVISION=5416 -DSDCC_pic14 -D__pic14 -DSDCC_PROCESSOR="16f874" -isystem "C:\Program Files\SDCC\bin\..\include\pic14" -isystem "C:\Program Files\SDCC\bin\..\include" -isystem "C:\Program Files\SDCC\bin\..\include\pic" "SDCC_PIC_Using.c" + 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 + 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... Could you comment on the two warnigs about the relocation? Hmm I think I am almost ready to go for the stuff I was intended to put in the PIC. Thanks, Frans. > When calling sdcc -V on a single-file project, you can see the linker > include paths, > linker scripts, and required files, something like the heavily edited: > > + "gplink" -I"%SDCC%/lib/pic" -m -s %GPUTILS%/lkr/16f877.lkr -w -r -o demo > \ > demo.o libsdcc.lib pic16f877.lib > > -I are linker search paths (where to find .lib files), -s points to the > linker > script to use, -w suppresses some useless warnings, -r allows to use > SHAREBANK > for DATABANKs, -o specifies the output file basename. > demo.o was compiled from demo.c (the single source file), > libsdcc.lib and pic16f877.lib are the sdcc and device libraries. > > You basically have to insert all your compiled source files *before* > libsdcc.lib > and should be good to go in no time. > > Best of luck > > > Raphael > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Sdcc-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/sdcc-user > ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Sdcc-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sdcc-user
