Hi Wolfgang,
Thanks for the reply!
> Why using such an odd address as 0x8055b728?
That is a symptom of the system I'm working on...!
> Just follow the rules and never download the image to an address range
> that overlaps with the area where the image will be unpacked / loaded
> to.
I'd wondered
Hi Mike,
Thanks for the reply.
> if it's uncompressed, why not simply load it to the final address in the first
> place ? then bootm wont have to do any memcpy, it can simply jump to the
> entry point.
In our system we use a software update mechanism where the kernel +
initfs images reside in a
Hi all,
I've got an interesting issue with a MIPS board I'm working on. The
uncompressed uImage has been created with a Load Address of 0x8050
and an Entry Point of 0x80504590. This gets TFTP's into RAM at
0x8055b728. When I run a "bootm 0x8055b728" this image fails to run.
Tracing through the
3 matches
Mail list logo