[U-Boot] ## Application terminated, rc = 0x1

[Wolfgang Denk <wd@denx.de>]

Dear ba_f,

In message <2e2178cf246f80c4f9098dce357e5528@rbg.informatik.tu-darmstadt.de> you wrote:
> 
> 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.

Did you read the FAQ? See es[ecially [1]

[1] http://www.denx.de/wiki/view/DULG/MyStandaloneProgramDoesNotWork


> 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

Any uImage should be booted using the "bootm" command, not "go".

> 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?

The uImage file contains a 64 byte header which is interpreted by
commands like "iminfo" or "bootm".


> Another issue:

Plese do NOT do that.  Do not mix topics in a single posting.  Please
open a new thread instead.


Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Mike's Law: For a lumber company employing two men and a cut-off saw,
the marginal product of labor for any number  of  additional  workers
equals  zero  until the acquisition of another cut-off saw. Let's not
even consider a chainsaw.
- Mike Dennison [You could always  schedule the saw, though - ed.]