• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 99 subscribers
  • Views 304 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

[dm365] problem to write on NAND

gxk
Intellectual 580 points

i have dm365 working w/ dvsdk 2.10.1.18

till today the project works with rootfs mounted from NFS.

Any chances to boot from NAND not working.

 

The SD burn utility (ver 6) can't create board that loads from NAND.

 

After 3 days of work, the question is

Is there any BUG in davinci NAND driver (montavista 5.0 kernel)?

  • 0
    Expert 1780 points

    I'm booting from nand without any problems. What are you experiencing? Why do you say that it does not work? We need to check your mtd configuration and the procedure you use to flash your board.

    At the moment I've only discovered a problem with yaffs2, but jffs2 seems to work.

  • 0 in reply to Marco Braga
    Intellectual 580 points

    Can you help with procedure how to burn kernel and rootfs on flash (dm365)?

  • 0 in reply to gxk
    Expert 1780 points

    Really nothing special, I'll skip the details.

    First of all you decide how to partition your flash memory then calculate flash addresses and partition sizes. I suggest leaving 4MB for the kernel and a space for root that depends on the size of the data you want to put it in.

    Then you configure the MTD devices in the kernel, have a look in arch/arm/mach-davinci. One file (depending on your platform) describes to the kernel how to configure the MTD devices (position, size, etc).

    Recompile the kernel, and boot it from tftp + nfs.

    Now you simply have to erase each mtd device (one for kernel, one for root) with "flash_eraseall /dev/mtdX". If you want to use jffs2 as root file system, use "-j" option.

    Then use "nandwrite" to write the kernel and the root file system image to the correct MTD device. Remember to use "-p" option if it complains that the file size is not aligned to block size.

    If you do not have a file system image, then you can simply mount the empty mtd device you'll use for root and copy data into it.

    This is all, sadly the details depend on exactly what you want to do, the file system you want to use, the way you want to boot your system, etc.

    Remember that for a complete standalone flash boot, you must also write UBL and U-Boot to the flash (using jtag or one of the utilities you'll find on this forum).

    Good luck!