Still UBoot ing...

Hi cybdenw,

> Now I take the elf and do a:

> nios2-elf-objcopy -O binary sample.elf sample.bin

>

> This generates from an approx 1000 byte image file (nios2-elf-size) an

> 8Meg binary file. (Why is this?).

The output sections are probably not contiguous ... you might be getting

large fill areas. Can you post the output of:

nios2-elf-objdump -h sample.elf

> mkimage -A nios2 -O linux -T kernel -C gzip -a 0x01000000

> -e 0x01000000 -n "MyAPP" -d sample.gz sample.img

This is correct if your text base is 0x01000000

> Presumably the execute address ought to be set to _start or something similar?

Correct.

> what about the load address?

The load address is the address where u-boot copies/decompresses the

image. Basically the destination copy address.

In most cases, your load address and entry point will be the same. If your

entry point is not at the start of your binary image, then you must set

the entry point appropriately. For example, if you link a jump table and

exception trampoline at offsets 0x0000 and 0x0020, respectively, but your

actual start offset is at 0x0040, you would use a load address of

0x0100_0000 and an entry point address of 0x0100_0040. The entry

point is the target address of a jump (call) from the bootm command.

> What is up here?

Let's look at the objdump ... an see if anything shows up.

Regards,

--Scott