patrice,
Okay, I think we can work through this. I have a question about the md5sum though. Are you
sure that it is wrong?
I only ask because it isn't always obvious what is being hashed here. LoLo only hashes the
loaded portion of the file. So, if you just run md5sum on your workstation, on the ELF file, it will look different. To see what LoLo is hashing, do the following:
arm-elf-objcopy -O binary file.elf file.raw
md5sum file.raw
Then compare the two outputs again. The first line strips out all of the ELF headers, debug information, etc. This leaves only the raw binary (.data, .text, .bss) sections left. That is what LoLo does when it loads the file.
I have a simple shell script that lets me do this in one command such as:
arm-md5.sh:
arm-elf-objcopy -O binary $1 $1.raw
md5sum $1.raw
rm -f $1.raw
Also, you know that you have to use the
burn command after you load this file to store it in flash correct? See the LogicLoader's User Manual for more information on the correct sequence needed to store a program in flash and why that is the way it is.
Please let me know if this helps. If not, can you post the entire session and include it in your next post.
Thanks,
--mikee