• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 364 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.

partition names on system with multi flash devices

ranchu
Guru 20755 points

Hello,

I have 2 flash in my board:

1. spi flash (with one partition)

2. nand flash with several partitions

On linux I see that the spi partition is the first /dev/mtd0 and the nand partitions starts from /dev/mtd1 on.
It should not been problematic, but we have issues that some boards have fram HW failure, and so the rootfs from nand failed to be discovered (because when spi is not probed, the partitions starts from 0.. and so the bootargs value for ubifs partition is not correct any more).

I have tried to change the initialization order in boot file by exchanging the spi and nand init, but it didn't help.

Does any one have any idea how can we make it more robust for such failures ?

Thanks,

Ran

  • 0
    TI__Guru** 116100 points

    Hi Ran,

    We need to look into the problem and address that why the SPI is not getting detected on few boards.

    I think, we can't do any thing for this or can't change bootargs in run time ie not able to change bootargs after SPI is not getting detected.

    Are you able to find, whether SPI is working or not in u-boot ?

    If yes, we can change the bootargs for rootfs when SPI is not getting detected.

    Actually this is not good way to fix this unless we find what cause the SPI hw problem.

  • 0 in reply to Titusrathinaraj Stalin
    Guru 20755 points

    Hi Titusrathinaraj Stalin,

     

    Thanks very much for the the quick reply.

    Yes, Some boards have real HW failure. But I thought that if the spi partition will always come after  nand partitions, than it would be better approach against such HW failure. With such a solution I don't need to change bootargs at all becuase the partition in bootargs will be the same the nand with or without spi probed, because if the spi partition /device/mtdY is always after /device/mtdX : Y>X, than the value in bootargs is always correct) .
    Anyhow, if that is not possible, than we will leave it this way.

    Thanks,

    Ran

  • 0 in reply to ranchu
    TI__Guru** 116100 points

    Hi Ran,

    What content did you have in SPI partition ?

    Will you face any problem without SPI partition content ?

    In other words, Is that okay if SPI is not getting detected.

    Did you find any reason behind for the SPI hw failures ?

    Is that issue not rectifiable ?

    But I thought that if the spi partition will always come after  nand partitions, than it would be better approach against such HW failure. With such a solution I don't need to change bootargs at all becuase the partition in bootargs will be the same the nand with or without spi probed, because if the spi partition /device/mtdY is always after /device/mtdX : Y>X, than the value in bootargs is always correct) .


    Yes, you are absolutely right.


    I have tried to change the initialization order in boot file by exchanging the spi and nand init, but it didn't help.

    Hmm, I think, the SPI driver is called before NAND as per Kconfig and Makefile files.