Thank you two,
this was the hint i needed.
The Load-Address was wrong.
Anyway, i still don't know how to determine the Load- & Entry-Address,
and i would be thankful if you could clear some things up for me.
I always work on ARM Cortex A9 processors.
The first time i came in touch with U-Boot i booted a Uimage kernel, and
i had to do it the following way:
(Please, notice the offset between Load- & Entry-Address)
uboot> fatload mmc 0 0x00ffffc0 bootstrap.uimage
uboot> go 0x01000000
But, while both kernels (the Uimage and the current mini kernel) are
linked for start address 0x01000000, i cannot use the same load address
on the mini-Kernel. Now, i have to load and jump to the same address to
make it work. Like this:
uboot> fatload mmc 0 0x01000000 miniKernel.bin
uboot> go 0x01000000
Why this? How comes the offset with the Uimage?
Another issue:
I tried to execute the same Uimage on another platform. The platform has
the same processor but another U-Boot.
On this platform i fail to execute with my common way:
uboot> fatload mmc 0 0x00ffffc0 bootstrap.uimage
uboot> go 0x01000000
## Starting application at 0x01000000 ...
undefined instruction
pc : [<010000f4>] lr : [<3ff74bc0>]
This looks to me like a wrong Load- or Entry-Address.
But again, it is the same Uimage with start address 0x01000000.
What's wrong here?
I'm confused...
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
