User forums > Using Code::Blocks

i havn't any HEX file in SDCC

(1/3) > >>

majid.ebru:
Hi
i read this link
http://www.nicolas-sanagustin.fr/index.php/2013/03/27/comment-programmer-un-pic-avec-sdcc-et-codeblocks/

and do every thing
but i havn't any HEX file?
please download and see this clip and help me.
waht is my Wrong ?



I can't post masage in that site?
whyyyyyyyyyyyyyyyyyyy?

stahta01:
What version SDCC did you install?

Edit: What Code::Blocks version are you using?

Post the build log.
http://wiki.codeblocks.org/index.php?title=FAQ-Compiling_%28errors%29#Q:_How_do_I_troubleshoot_a_compiler_problem.3F

Tim S.

majid.ebru:
My version SDCC is 3.4.0??

stahta01:
I will NOT be down loading an exe from you.

I will wait for a build log or consider you to be a troll.

Tim S.

stahta01:
What I get as the Build log following the images on the link you posted.


--- Code: ----------------- Build: Release in pic_test (compiler: Small Device C Compiler)---------------

sdcc.exe  --out-fmt-ihx -mpic16 --opt-code-size --verbose --use-non-free -p18f2550     -c main.c -o obj\Release\main.o
WARNING: The target device seems to support XINST and no #pragma config XINST=OFF was found.
         The code generated by SDCC does probably not work when XINST is enabled (possibly by default).
         Please make sure to disable XINST.
         (If the target does not actually support XINST, please report this as a bug in SDCC.)
obj\Release\main.asm:278:Message[1301] Using default destination of 0 (Access Bank).
obj\Release\main.asm:284:Message[1301] Using default destination of 0 (Access Bank).
obj\Release\main.asm:286:Message[1301] Using default destination of 0 (Access Bank).
obj\Release\main.asm:298:Message[1301] Using default destination of 0 (Access Bank).
obj\Release\main.asm:300:Message[1301] Using default destination of 0 (Access Bank).
Processor: 18f2550
sdcc: Calling preprocessor...
sdcc: Generating code...
sdcc: Calling assembler...
sdcc.exe  -o bin\Release\pic_test.hex  --out-fmt-ihx -mpic16 --opt-code-size --verbose --use-non-free -p18f2550      obj\Release\main.o
message: Using default linker script "C:\Apps32\gputils\lkr\18f2550_g.lkr".
Processor: 18f2550
sdcc: Calling linker...
Output file is bin\Release\pic_test.hex with size 681.00 bytes

--- End code ---

NOTE: I did one step not in the images I added the path of "C:\Apps32\gputils\bin" to the SDCC Additional paths under the compiler toolchain tab.
This is because I never add gputils or compilers to the Windows search PATH it causes to many weird errors when you run many different compilers and other tools.

Tim S.

Navigation

[0] Message Index

[#] Next page