• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 350 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.

DM8168 FLASH HELP

Rodrigo Rengifo
Intellectual 420 points

Hi I'm currently working with the dm8168 chip with the 5.03.01.15 EZSDK.  We have an external flash connected to it, this being Micron NAND flash memory (MT29F4G16ABADAWP).  It is currently connected through the GPMC_D signals, also using CS2.  I've been trying to figure out a way to write and read from it but i'm having a lot of trouble.  The file system doesn't seem to detect it.  Some of my output from the boot shell is the following:

GPIO NAND driver, © 2004 Simtec Electronics
omap2-nand driver initializing
ONFI flash detected
NAND device: Manufacturer ID: 0xad, Chip ID: 0xda (Hynix ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ)
3 cmdlinepart partitions found on MTD device omap2-nand.0
Creating 3 MTD partitions on "omap2-nand.0":
0x000000000000-0x000000280000 : "UBOOT"
0x000000280000-0x0000006c0000 : "KERNEL"
0x0000006c0000-0x000002c40000 : "FS"

This is showing me that it finds the Hynix flash that is connected but it is not recognizing the Micron flash that is on there.  Forgot to mention we're using the Z3 which includes the hinux flash and the dm8168 so we have an "expansion flash" which is the one i mentioned.  Do I need to somehow edit the board file to look for another flash?  Is there another way for me to find the Micron flash without having to change the kernel?

Thanks,

Rodrigo

  • 0
    TI__Intellectual 1645 points

    Rodrigo,

    If you have added another NAND device to your board you would need at a minimum to modify the board configuration of u-boot to account for the H/W change.
    I would start with u-boot, once you are able to probe/detect and read/write to the 2nd NAND device only then i would move up to Linux.
    You would most likely need to make sure that the MTD Partition scheme is coherent between u-boot and Linux for the new device.

  • 0 in reply to Benoit Parrot
    Intellectual 420 points

    Hi Benoit, thanks for your response.  I thought that was something that i had to do but I've never done that before and don't know how to go about it.

    The external part we added is the MT29F4G16ABADAWP (micron 16bit 4Gb).  I’m not too sure on how to edit the board file to allow the file system to detect this expansion flash.

    In the board-ti8168evm.c file I noticed a section that seems to tell the file system where the flash is, what kind and how to partition it. There are three different structures which are ti816x_spi_partitions[] seems that this tells the kernel how to partition that specific nand flash part.  ti816x_spi_flash which tells the nand driver that it should use a specified part of it, this being the .type in this case it is “w25x32”.  Lastly there is the ti816x_spi_slave_info[] which seems to tell the board what driver to use, this is .modalias = “m25p80”.  I believe this shows me that it is using the m25p80 driver which is under drivers/mtd/devices/m25p80.c

    I’m not sure if I should be copying these three entries and changing them to detect our nand part.  How would I go about adding this new nand part to the board file so when it boots the second nand device is also detected?  It is connected to CS2

    Rodrigo