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.

Problem with nandwrite tool for dm365



I know this had been brought up in a few different threads, but I wanted to ask about it again since I have not seen this addressed by TI.

I am trying to simply update my kernel image (not from u-boot, which works fine) using the following commands:

flash_eraseall /dev/mtd2
nandwrite -p /dev/mtd2 uImage

When I reboot, u-boot reports a  "** Read error"  when trying to read the image from flash into RAM. So just for fun, I tried it with the following command (-n option to write without ecc):

nandwrite -n -p /dev/mtd2 uImage

This time when I reboot, the checksum passes and appears to boot and function no problem. I am using the nand tools from mtd-utils-v1.1.tar.gz from PSP_02_10_00_14.

BTW, my flash is a Micron 256MB. I've also tried this on the DM36 EVM with the 2G flash and I see the same behavoir.

Can someone confirm there or is not any known issue using these tools on a dm365 platform?

What are the dangers of doing this with the "-n" option?

Thanks,

-Craig

  • Hi Craig,

    I work with nandwrite and came into the same problem on DM365, but UBoot (U-Boot 1.3.4) does not want to boot. It reports:

    NAND read: device 0 offset 0x800000, size 0x400000
    NAND read from offset 800000 failed -117
     4194304 bytes read: ERROR

    How did You solved the flashing of uImage?

    Thanx,

    Juraj

  • The flashing of uImage / Ramdisk.gz now works. I dowbloaded git://git.infradead.org/mtd-utils and make the tools.

    Now this store EEC correctly, so u-boot can boot code from NAND ok.

    nandwrite -p /dev/mtd2 uImage