Hello
I've write a application which I will bootload with my software bootloader (on 0x80000). The code of the application starts at 0x90000 so the Keil compiler generate a hex file with this offset. How I can remove this offset in my hex file to load it directly with my bootloader?
Thank and regards
Reto
Sorry, but you're really not making much sense.
starts at 0x90000 so the Keil compiler generate a hex file with this offset
What "this" offset is that? And how does the Keil linker (not the compiler!) know about it in the first place?
How I can remove this offset in my hex file to load it directly with my bootloader?
What on earth makes you think you should remove that offset? What is the input data format for your bootloader, anyway?
Hi
I've solved my prob with a other hex2bin converter...
The Keil linker know the offset because I have defined it in the linker options.
What on earth makes you think.... : My bootloader is on address 0x80000. So my bootloader write the given application data (bin) to the address 0x90000. It make not realy sense to give first 0x90000 zeros to the bootloader.
Thank you anyway
The hex file doesn't contain any 0x90000 zeros. The hex file starts with a special record saying that the following data starts at 0x90000.
It is only tools that converts from hex to bin that may - or may not - add empty data. The HEX file can contain any number of holes, but a bin file must always be continuous.