Honored Contributor
Honored ContributorHello ignacio
Thank you very much for your kind answer. I don't have time now to read your tutorial, but at first glimpse it seems very interesting. I'll do it next monday. Regarding the arm-altera-eabi-objcopy command line, I understood this is what I'm supposed to use. But, as I wrote in my post, this generates the full 4GB addressable memory image, and the file is useless. I guess that this happens because my axf file contains both sections in the 0-0x100000 memory range (mainly sdram) and sections in the 0xFFFF0000-0xFFFFFFFF range (I think these are for SoC onchip ram and memory mapped registers, am I right?), then objcopy creates an image from the lowest address 0 to the highest 0xFFFFFFFF, although a miminal part is actually relevant. Infact if I exclude sdram or if I include a single memory section (objcopy options -j or -R) the bin file generates with the correct memory size. I also tried to generate separate files for each memory section and tried to manually load them with the 'fatload' command: using the debugger I can see the memory gets correctly loaded with the bin data, but I really don't know if I'm placing this section where they are supposed to be. Moreover I have no idea where my code must start from: I tried a go 0x00100040, but nothing seems to happen.
