• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 142 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] MCU-PLUS-SDK-AM243X: [FAQ] How to debug/develop/migrate the flash driver for custom flash on non-TI EVM (OSPI/xSPI...

MCU-PLUS-SDK-AM243X: DFU program custom QSPI flash

Tony Tang
Mastermind 28217 points
Part Number: MCU-PLUS-SDK-AM243X
Other Parts Discussed in Thread: UNIFLASH

Tool/software:

About the default_dfu_ospi.cfg: 

Step 1: Need to rebuild sbl_dfu_uniflash.release.hs_fs.tiimage with new configuration following the adding support for a custom flash device guide? not find where highlighted it.

https://software-dl.ti.com/processor-industrial-sw/esd/ind_comms_sdk/am243x/09_02_00_08/mcu_plus_sdk/docs/api_guide_am243x/CUSTOM_FLASH_SUPPORT_GUIDE.html

#2.  Is -operation=flash-phy-tuning-data necessary? Does QSPI flash have tuning data also? where to get the data? from flash vendor?

  • 0
    TI__Mastermind 34254 points

    Hello Tony,

    For your first question the customer needs to modify the example.syscfg file at the following location: https://github.com/TexasInstruments/mcupsdk-core/tree/next/examples/drivers/boot/sbl_dfu_uniflash/am243x-evm/r5fss0-0_nortos/ti-arm-clang if they are using AM243-evm else a similar am243-lp directory is also there where they can modify.

    For the second question, the flash phy tuning data is not necessary but a sanity checking at later stages if the basic reads are working fine or not. Its really helpful when you use the Phy mode in OSPI as the Optimal tuning point when phy is enabled is found based on if the phy tuning data is being read or not.

    So you can keep it and it will be no harm as such.

    The data is already predefined and is stored in the drivers code in the array named as follows: gOspiFlashAttackVector. Please ask the customer to search for this.

    It is 128 bytes of data.

    Hopefully this resolves your doubts here.

    Regards,

    Vaibhav

  • 0 in reply to Vaibhav Kumar
    TI__Mastermind 28217 points
    Vaibhav Kumar said:
    the customer needs to modify the example.syscfg file at the following location

    I see the guide how to modify OSPi configuration, I mean if highlight it to rebuild sbl with modified OSPi configuration for customer board, would be good.

    Vaibhav Kumar said:
    The data is already predefined and is stored in the drivers code in the array named as follows: gOspiFlashAttackVector.

    The data is not OSPi flash dependent, it s based on AM243x OSPI flash controller? the data can be used for all vendor's OSPI flash? 

  • 0 in reply to Tony Tang
    TI__Mastermind 34254 points

    Hello Tony,

    Tony Tang said:
    I mean if highlight it to rebuild sbl with modified OSPi configuration for customer board, would be good.

    Can you reframe this sentence?

    Tony Tang said:
    The data is not OSPi flash dependent, it s based on AM243x OSPI flash controller? the data can be used for all vendor's OSPI flash? 

    So the 128 bytes of data you see defined in gOspiFlashAttackVector is consistent across all SoCs and is independent of the Flash Part vendor too.

    gOspiFlashAttackVector represents stress pattern which gets flashed to the flash part irrespective of the SoC and the Flash Part.

    Then this stress pattern is read back to make sure a basic sanity checking is done(to prove reads from the flash is done correctly)

    Regards,

    Vaibhav