Because of the holidays, TI E2E™ design support forum responses will be delayed from Dec. 25 through Jan. 2. Thank you for your patience.

  • State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 100 subscribers
  • Views 738 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Original question:

[FAQ] PROCESSOR-SDK-AM57X: How to boot from QSPI flash on AM57x.

[FAQ] PROCESSOR-SDK-AM57X: UNIFLASH sequence for different QSPI part number?

ANUBHAV AKASH
Expert 6870 points
Part Number: PROCESSOR-SDK-AM57X
Other Parts Discussed in Thread: UNIFLASH

I have a new QSPI (different part number than TIEVMs) on my customBoard? I have tried flashing MLO using UNIFLASH but its not happening. Can anyone guide me through the process?

  • 0
    TI__Expert 6870 points

    Hi,

    Please follow below steps:

    • Update the pdk_am57xx\packages\ti\board\src\flash folder according to your QSPI specification.
    • Once updated, build the board lib.
    • Then, you can test read/write to your QSPI by building QSPI diagnostic test(pdk_am57xx\packages\ti\board\diag\qspi), QSPI driver example or both. You can verify the vendor id and manufacturer id of your qspi part number. This will tell you that whether your QSPI is up or not.
    • Then, you can build the pdk_am57xx\packages\ti\board\utils\ to get the updated flash programmer according to your QSPI part number in pdk_am57xx\packages\ti\board\utils\uniflash\target\bin\idkAM57Xx\.
    • Now, you can follow this link for writing and erasing sequence for UNIFLASH.
      • Only thing you have to keep in mind is that, you have to use uart_idkAM57Xx_flash_programmer.out from pdk_am57xx\packages\ti\board\utils\uniflash\target\bin\idkAM57Xx\ instead of <path\to\uniflash\root_folder>\processors\FlashWriter\idkAM57Xx\uart_idkAM57Xx_flash_programmer.out (as this is default binary compatible with TIEVMs).
    • Rest steps will remain same, just build the binaries (MLO,etc.) freshly.

    Note - just keep in mind whenever you are using any binary that is prebuilt that may not work with your customBoard as those are compatible with TIEVMs. Therefore, always build the binaries freshly.

    Useful links:

    e2e.ti.com/.../3713470