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.

RTOS/AM4372: How to use "ProcessorSDKSerialFlash.exe" to write QSPI Flash on Pinmux Option 1?

Part Number: AM4372
Other Parts Discussed in Thread: UNIFLASH

Tool/software: TI-RTOS

Hi Team
How to use "ProcessorSDKSerialFlash.exe" to write QSPI Flash on Pinmux Option 1?

Uniflash


From Will Hsu

  • What is the platform that is currently being used by the customer ?  Is it the IDK platform or a custom board. The Uniflash tool that we provide currently supports pinmux option 0 as the CAM peripheral is used on the IDK platform.

    In order for customer to change this, they need to open the TI pinmux tool  and select the correct pin option for QSPI using IOSET 2 instead of IOSET1

    Note: It is important that we recommend the customer to use pinmux tool and not try to do register write to control module to avoid any issue with IO set configuration related issues.

    After the pinmux setting is applied, the customer would need to rebuild the board library  and uniflash tool using following instructions.

    Rebuild Board

    Set SDK build environment

    cd pdk_am437x_x_X_x_X\packages

    gmake board_lib

    Test the changes: I would use a simple QSPI read write test case from diagnostics to confirm you can read and write from flash

    Rebuild Uniflash 

    http://software-dl.ti.com/processor-sdk-rtos/esd/docs/latest/rtos/index_board.html#rebuilding-board-utils 

    Replace the binary located in the Uniflash package:

    Place the binary from pdk_am437x_1_0_13\packages\ti\board\utils\uniflash\bin\idkAM574x into

    C:\ti\uniflash_4.5.0\processors\FlashWriter\idkAM437x

    Note: There is no change anticipated to ProcessorSDKSerialFlash.exe

    Regards,

    Rahul

  • Hi Rahul,
    Thank you for your prompt reply.
    I'll test it on a custom board.
  • Any update on this issue or can we close this issue.