This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Linux/DM3730: NAND image update over OMAP Flashtool doesn't work

Part Number: DM3730

Tool/software: Linux

Good afternoon.
I'm expereiencing some troubles with your product.
First of all - I had to install Windows XP x86 (THIS IS IMPORTANT!) on separate PC for being able just properly connect to my DM3730. It turned out, your OMAP Flashtool (v 4.2) works only with WinXP x86 (HELLO, IT'S 2018!!!).
But the main issue is that after full chip erase and downloading:

  • MLO (offset 0x0, ECC 1-bit x-loader/u-boot),
  • u-boot.bin (offset 0x8000, NAND ECC),
  • uImage (offset 0x280000, NAND ECC)
  • rootfs.yaffs2 (I was trying different offsets: 0x780000, 0x1b80000 and 1400000, NAND ECC).

So after thouse manipulations I reboted, set some environments (diff my bootargs with bootargs, generated after run makeyaffsboot command):

OMAP Logic # setenv kernel_location nand-part
OMAP Logic # setenv rootfs_location /dev
OMAP Logic # setenv rootfs_type yaffs
OMAP Logic # setenv partition nand0,0
OMAP Logic # setenv mtddevname x-loader
OMAP Logic # setenv mtddevnum 0
OMAP Logic # setenv filesize 8E9BCC0
OMAP Logic # setenv yaffsimage rootfs.yaffs2
OMAP Logic # saveenv

After reboot x-loader starts successfully, u-boot starts successfully, Linux kernel starts successfully, but then I got:

[ 6.520996] devtmpfs: error mounting -2
[ 6.525268] Freeing init memory: 244K
[ 6.529571] Kernel panic - not syncing: No init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.

So what's going on? I tried erase each region instead of entire chip, but it gives me error about wrong ECC in debug terminal at u-boot loading stage.

2 Replies

  • Hi user5237540,

    I'm looking on this. I'll update you here.

    BR
    Tsvetolin Shulev
  • In reply to Cvetolin Shulev-XID:

    During tests I found that rootfs was not copied or copied wrong way because I'm unable to mount rootfs from u-boot - it shows me only empty "lost+found" folder:

    OMAP Logic # ymount /fs
    yaffs: Mounting /fs
    ECC oobavail <= 16; forcing "tags-ecc-off"
    OMAP Logic # yls /fs
    lost+found

    But the most interesting that when I tried to mount from u-boot rootfs which is booting well - it gives me banch of strange errors:

    OMAP Logic # ymount /fs
    yaffs: Mounting /fs
    ECC oobavail <= 16; forcing "tags-ecc-off"
    ERROR: v7_dcache_inval_range - start address is not aligned - 0x8f1a9e90
    ERROR: v7_dcache_inval_range - stop address is not aligned - 0x8f1aa690
    ERROR: v7_dcache_inval_range - start address is not aligned - 0x8f1a9e90
    ERROR: v7_dcache_inval_range - stop address is not aligned - 0x8f1aa690
    ERROR: v7_dcache_inval_range - start address is not aligned - 0x8f1a9688
    ERROR: v7_dcache_inval_range - stop address is not aligned - 0x8f1a9e88
    ERROR: v7_dcache_inval_range - start address is not aligned - 0x8f1a9e90
    ERROR: v7_dcache_inval_range - stop address is not aligned - 0x8f1aa690
    ERROR: v7_dcache_inval_range - start address is not aligned - 0x8f1a9e90
    ERROR: v7_dcache_inval_range - stop address is not aligned - 0x8f1aa690
    ERROR: v7_dcache_inval_range - start address is not aligned - 0x8f1a9688
    ERROR: v7_dcache_inval_range - stop address is not aligned - 0x8f1a9e88
    ERROR: v7_dcache_inval_range - start address is not aligned - 0x8f1a9e90
    ERROR: v7_dcache_inval_range - stop address is not aligned - 0x8f1aa690
    ERROR: v7_dcache_inval_range - start address is not aligned - 0x8f1a9688
    ERROR: v7_dcache_inval_range - stop address is not aligned - 0x8f1a9e88
    yaffs tragedy: Bad object type, -1887050668 != 1, for object 299 at chunk 90936 during scan
    ERROR: v7_dcache_inval_range - start address is not aligned - 0x8f1a9688
    ERROR: v7_dcache_inval_range - stop address is not aligned - 0x8f1a9e88
    yaffs tragedy: Bad object type, -1887050668 != 1, for object 298 at chunk 90934 during scan
    ERROR: v7_dcache_inval_range - start address is not aligned - 0x8f1a9688
    ERROR: v7_dcache_inval_range - stop address is not aligned - 0x8f1a9e88
    yaffs tragedy: Bad object type, -1887050668 != 1, for object 297 at chunk 90932 during scan
    ERROR: v7_dcache_inval_range - start address is not aligned - 0x8f1a9688
    ERROR: v7_dcache_inval_range - stop address is not aligned - 0x8f1a9e88
    yaffs tragedy: Bad object type, -1887050668 != 1, for object 296 at chunk 90930 during scan

    P.S. My u-boot version is 2011.06 from LogicPD's Linux BSP-dm37x-2.4-4 (latest available).

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.