Re: [Sdcc-user] [PIC16] Exporting full memory range in hex

2012-05-08 Thread Diego Herranz
After some time, I discovered gplink option "-f VALUE". How didn't I see it before?? It just does what I needed in a much simpler fashion. sdcc -mpic16 -p18f4550 "-Wl -f 0x" file.c That generates a .hex file with unused program memory filled with 0x. Just in case it is useful for somebod

Re: [Sdcc-user] [PIC16] Exporting full memory range in hex

2012-01-31 Thread Diego Herranz
I don't need fuses in the file because fuses are determined but bootloader and you can't change them later. Fuses are out of the 32K region. That's why I added them because without padding, I couldn't get the full 32K. Adding fuses, which are out of that range, allowed dd to copy 32K. Exactly, con

Re: [Sdcc-user] [PIC16] Exporting full memory range in hex

2012-01-30 Thread Unix Savvy Brian
Diego -- How many bytes is "fuses"? Is it pretty constant? Is "fuses" part of the 32K? If "fuses" is constant, you could append it binary file before feeding back to 'objcopy' to make the intel hex file. E.g. 'fuses.bin' are the last one byte of your download. % dd if=file.bin of=t1.bin

Re: [Sdcc-user] [PIC16] Exporting full memory range in hex

2012-01-29 Thread Diego Herranz
Thanks a lot for your help Finally this is what I did: $ objcopy -I ihex -O binary file.hex file.bin $ dd if=file.bin of=file_full_range.bin count=1 bs=32768 (18f2550 memory size in bytes) $ objcopy -I binary -O ihex file_full_range.bin file_ready_for_bootloader.hex Opening the files with a

[Sdcc-user] [PIC16] Exporting full memory range in hex

2012-01-28 Thread Diego Herranz
Hi! I want to use a bootloader (Scene Double bootloader) for PIC16 and it requires to export the full program memory range of your application (even unused range), with no eeprom nor fuses. This is the exact text present in the bootloader manual: > Exporting a HEX File from MPLAB > Once you h