[yocto] Flashing Yocto to SOM?

[Alexander Korsos]

Hi Stefano,

Thanks for getting back to me. I just tried flashing u-boot.img instead of
u-boot.bin, using "nandecc sw", and get:

U-Boot SPL 2012.07-dirty
Board: DM37xx Torpedo
Error: Bad compare! failed
Error: Bad compare! failed
...


I flashed it again with "nandecc hw" and got:

U-Boot SPL 2012.07-dirty
Board: DM37xx Torpedo

U-Boot 2012.07-dirty

OMAP3630/3730-GP ES1.2, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz
Logic DM37x/OMAP35x reference board + LPDDR/NAND
I2C:   ready
DRAM:  512 MiB
NAND:  512 MiB
MMC:   OMAP SD/MMC: 0
In:    serial
Out:   serial
Err:   serial
Die ID #511000029ff800000155b2141902501b
nand_unlock: start: 00000000, length: 536870912!
Net:   smc911x-0
Hit any key to stop autoboot:  0
Card did not respond to voltage select!
Booting from nand ...

NAND read: device 0 offset 0x280000, size 0x400000
NAND read from offset 280000 failed -74
 0 bytes read: ERROR
## Booting kernel from Legacy Image at 81000000 ...
   Image Name:   Linux-3.2.0
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2300032 Bytes = 2.2 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... Bad Data CRC
ERROR: can't get kernel image!

Could it have something to do with nand_unlock? Any advice on this issue is
greatly appreciated.

Thank you,
Alex

On Tue, Oct 6, 2015 at 8:20 AM, stefano babic <sbabic at denx.de> wrote:

> Hi Alexander,
>
> Am 05.10.2015 um 20:31 schrieb Alexander Korsos:
> >
> > Hi,
> >
> > I'm trying to flash Yocto Dizzy (core-image-minimal built with
> > BitBake) onto a LogicPD DM3730 / AM3730 Torpedo + Wireless SOM using
> > the following commands at the U-Boot prompt:
> >
> > # nand erase.chip
> > # env default -f
> >
> > # setenv loadaddr 0x81000000
> >
> > # setenv ramdiskaddr 0x82000000
> >
> > # setenv kernel_nand_offset 0x00280000
> >
> > # setenv kernel_nand_size 0x00400000
> >
> > # setenv ramdisk_nand_offset 0x00680000
> >
> > # setenv ramdisk_nand_size 0x00dd8680
> >
> > # setenv kernel_location nand
> >
> > # setenv rootfs_location nand
> >
> > # setenv rootfs_type ramdisk
> >
> > # saveenv
> >
> > # mmc init
> >
> > # mw.l ${loadaddr} 0xFFFFFFFF 0x400000
> >
> > # fatload mmc 0 ${loadaddr} mlo
> >
> > # nandecc hw
> >
> > # nand write ${loadaddr} 0x00000000 0x00020000
> >
> > # nand write ${loadaddr} 0x00020000 0x00020000
> >
> > # nand write ${loadaddr} 0x00040000 0x00020000
> >
> > # nand write ${loadaddr} 0x00060000 0x00020000
> >
> > # mw.l ${loadaddr} 0xFFFFFFFF 0x400000
> >
> > # fatload mmc 0 ${loadaddr} u-boot.bin
> >
> > # nandecc sw
> >
> > # nand write.i ${loadaddr} 0x00080000 0x00080000
> >
> > # mw.l ${loadaddr} 0xffffffff 0x400000
> >
> > # fatload mmc 0 ${loadaddr} uImage
> >
> > # nand write.i ${loadaddr} ${kernel_nand_offset} ${kernel_nand_size}
> >
> > # mw.l ${loadaddr} 0xffffffff 0x400000
> > # fatload mmc 0 ${loadaddr} rootfs.ext2.gz.u-boot
> >
> > # nand write.i ${loadaddr} ${ramdisk_nand_offset} ${ramdisk_nand_size}
> >
> >
> >
> > The source files I'm using in my boot partition are the MLO,
> > u-boot.bin, rootfs.ext2.gz.u-boot, uImage, and u-boot.img. I am able
> > to burn all the necessary files onto the SOM, but when I complete the
> > steps and power cycle, I get:
> >
> >
> >
> > U-Boot SPL 2012.07-dirty (Sep 30 2015 - 17:31:44)
> > Board: DM37xx Torpedo
> > Error: Bad compare! failed
> > Error: Bad compare! failed
> > Error: Bad compare! failed
> >
> > ...
> >
> > mkimage signature not found - ih_magic = ea000014
> >
> > ...
> >
> > Error: Bad compare! failed
> > Error: Bad compare! failed
> >
> > ...
> >
> >
> >
> > I've done a good amount of research online and some people say that
> > it's an issue with the nandecc setting, but my only options in U-Boot
> > are hw (hardware) and sw (software) ecc algorithms. Just curious if
> > anyone could identify my errors or possibly point me in the direction
> > of good documentation?
> >
>
> Why do you flash u-boot.bin ? This is missing the header requested by
> TI's  SOCs. You should flash u-boot.img.
>
> Regards,
> Stefano
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20151006/44c3a34c/attachment.html>