Honored Contributor
Honored ContributorHere is something else I've discovered.
Regarding the endiannes problem, the data is shown as misplaced only in the disassembly window of the usb-blaster debugger. The data appears to be ok in the memory window of the debugger or if I dump the memory with the md command from the serial port interface. Which is correct? The section gets loaded starting at memory address 0x100040, no matter the address I specify in linker or in mkimage. Instead, if I directly load the bin file generated by objcopy, without using mkimage, it loads correctly (i.e. isr vector table at 0x100000 and cs3_reset at 0x100040) What's the actual difference between objcopy and mkimage ouput? **** discard this part: this was my error; see my following post The last point is not completely true, because between interrupt vector and cs3_reset I always find a stray code 0xEA00024 which shifts all the remaining part to higher addresses. I mean: 0x100000 : interrupt vector 0x100040 : stray data 0xEA00024 ??? 0x100044; cs3_reset + cs3_start_c code which is supposed to be @0x100040 **** I'm very puzzled of this. I hope someone can explain me
