• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 99 subscribers
  • Views 841 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.

[66K2H]multi boot in NAND boot mode

Sung-IL
Mastermind 30810 points

Dear Champs,

My customer is willing to make multi boot mode, and they want to implement it by changing access address in NAND.

If they can modify the configuration of boot configuration pin, it can be implemented?

When I checked datasheet, I found below description for the First Block, but can not understand it easily.

Could you please explain more details on below?

If these pins will be modified, the access address of NAND will be changed?

Thanks and Best Regards,

SI.

  • 0
    TI__Guru* 81335 points

     

    My customer is willing to make multi boot mode, and they want to implement it by changing access address in NAND.

    If they can modify the configuration of boot configuration pin, it can be implemented?

    When I checked datasheet, I found below description for the First Block, but can not understand it easily.

    Could you please explain more details on below?

    If these pins will be modified, the access address of NAND will be changed?

    Yes. It is possible. Your understanding is correct however I am checking with ROM experts to define the address for block value * 16. 

    Thank you for your patience.

  • 0 in reply to Raja
    TI__Mastermind 30810 points
    Hi Rajasekaran,

    Is there any update?
    Have you get any details on the definition for block value *16?



    Thanks and Best Regards,
    SI.
  • 0 in reply to Sung-IL
    TI__Guru* 81335 points
    No, I did not get any details. I am following up. Thank you for your patience.
  • 0 in reply to Sung-IL
    TI__Guru** 116170 points

    Hi Sung-IL,

    Sorry for the delay in responding to this issue. Yes, this feature is implemented and tested with the bootROM.

    If the MIN pin (DEVSTAT[4]) is not set to 1 then the bootROM will read the first block pins (DEVSTAT[15:13]) to determine the first block that it must read in order to find the boot image on the NAND flash. The value in the field will be multiplied by 16 to find the first block to read the boot image.  Hence if the value is set to 0 then it will start from block0, if the value is set to 0x001 then it will read from block16 and so on.

    so the customer can choose to load the boot image at block0, block16 or block32,.... and read the image successfully by setting the appropriate boot switches.

    Hope this clarifies the implementation.

    Regards,

    Rahul

  • 0 in reply to Rahul Prabhu
    TI__Guru* 81335 points
    Rahul,

    Can I file a litbug report to update the data manual with above information or we have it already on the pending actions list?

    Please let me know.