[U-Boot-Users] OSK5912 copy flash to mem broken?

Stefan Roese sr at denx.de
Thu May 11 11:12:53 CEST 2006

Hi Hiroki,

On Thursday 11 May 2006 09:29, Hiroki Kaminaga wrote:
> I'm facing a problem, on OSK5912 board, boot loader that is
> copied from 0x00000000 to 0x11080000 at powerup is not exactly copied.
> This can be checked as below:
> (after OSK5912 is powered up and uboot prompt is shown)
> OMAP5912 OSK # cmp.b 0x00000000 0x11080000 0x15dd4
> and I got:
> byte at 0x000150a2 (0xff) != byte at 0x110950a2 (0x0f)

Why do you think that this is a problem? What is you problem exactly, meaning 
what is not working? 

I just checked the top-of-git-tree version and also did this cmp.b. The first 
difference is noted at "1109744c d smc_mac_addr" (from System.map). This data 
is updated with the env variable ethaddr upon startup. So this seems 
perfectly reasonable.

> Memory itself is not broken, since I get:
> OMAP5912 OSK # tftp 10000000 uboot.bin
> TFTP from server; our IP address is
> Filename 'uboot.bin'.
> Load address: 0x10000000
> Loading: ##################
> done
> Bytes transferred = 89556 (15dd4 hex)
> OMAP5912 OSK # cp.b 10000000 11080000 0x15dd4
> OMAP5912 OSK # cmp.b 0x10000000 0x11080000 0x15dd4
> Total of 89556 bytes were the same
> I'm using the updated uboot.bin from
> http://omap.spectrumdigital.com/osk5912/osk5912_faq.html

Please try the omap5912osk version from top-of-git. I just updated it's 
support and it works here fine.

> Anyone have the same problem?
> I tested with OSK5912 Revision C and D, and its the same...

I have to admit, I don't know which board version we have installed.

Best regards,

More information about the U-Boot mailing list