[ELDK] mmap: first byte always wrong

Wolfgang Denk wd at denx.de
Fri Nov 26 08:48:24 CET 2010

Dear Alberto Caballero,

In message <AANLkTikhDLRqWvUx7+APFv5fDj8vQNofRBzoeONyTOFO at mail.gmail.com> you wrote:
> I am developing over an EP440xS board. I have stored a valid U-Boot image
> into the board Flash. Kernel and Ramdisk image is stored at 0xFF000000
> address and the test data image at 0xFD000000 address.

Strictly speaking you are off topic here.  The EP440xS is neither
supported by the mainline Linux kernel tree nor by the DENX tree that
is used in the ELDK. 

> Once the Linux is started, I run my program that tries to copy the image
> from Flash into a Linux file. As first step, I try to read the image magic
> number, but I always get the first byte wrong, usually set to 0xFF. The rest
> of the magic number bytes are correct, as the rest of the image header
> bytes.
> Instead of getting 0x27 0x05 0x19 0x56 I am getting 0xFF 0x05 0x19 0x56.
> Any ideas of what's going on? Any suggestion?

Eventually you start reading at an incorrect address?

> This is an extract of the code I am using:

This doesn't help, as we cannot even see how you call these functions,
i. e. which arguments you pass to them.

Best regards,

Wolfgang Denk

DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
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
Wenn das dann in die Hose geht, nehme ich es auf meine Kappe.
                                         -- Rudi Völler, 15. Nov 2003

More information about the eldk mailing list