[yocto] Flashing Yocto to SOM?

[stefano babic]

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