• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 33 subscribers
  • Views 363 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.

AM263P4: UniFlash Application Offset

Kier
Mastermind 9620 points

Part Number: AM263P4
Other Parts Discussed in Thread: UNIFLASH

Tool/software:

Please can you confirm which address offset I should be using for UniFlash:

I'm using ' sbl_ospi.release.tiimage' as per the image above.

  • If I use Application Offset 0x60081000 as per the table, my application does not run.
  • If I use Application Offset 0x60080000 as per the  screenshot, my application runs.

Please confirm.

  • 0
    Mastermind 9620 points

    Any chance of a response please?

    I compared the following documents:

    a) file:///C:/ti/mcu_plus_sdk_am263px_10_01_00_34/docs/api_guide_am263px/TI_UNIFLASH_TOOL.html#autotoc_md425

    • Says the application start address in the table is 0x60080000

    b) file:///C:/ti/mcu_plus_sdk_am263px_10_01_00_34/docs/api_guide_am263px/TOOLS_FLASH.html#autotoc_md1039

    • Says the application start address in the table is 0x60081000

    In both cases the screenshot says 0x60080000.

    Which is correct please? Are they both correct and I'm missing something?

  • 0
    Mastermind 9620 points

    There is also a variation in the flash configuration files.

    Some are 0x80000:

    Others are 0x81000:

    Why is there a variation in the start address of the application? It does not seem dependent on .appimage or .mcelf.

    If the above are correct (are they?), there is a variation in the start address expected by different SBLs. Why is that please?

    What should I do for my own SBL?

  • 0 in reply to Kier
    TI__Expert 6876 points

    The application offset to be used comes from the SBL OSPI Application syscfg file. By default, it is 0x6008100 as shown in the below image. Could you please double check your OSPI SBL application syscfg value from which you obtained the .tiimage?

  • 0 in reply to Sahana H G
    Mastermind 9620 points

    Thanks for the information Sahana. At least I have a method to absolutely confirm the offset address for each SBL.

    Now I see why this is confusing. It seems that TI has changed the SBL OSPI offset address somewhere between SDK 9.2.0.56 and SDK 10.1.0.34:

    SDK 9.2.0.56 SBL OSPI

    SDK 10.1.0.34 SBL OSPI

    1) What is the reason for this change between SDKs?

    2) In the 10.1.0.34 SDK, the SBL OSPI offset is 0x81000 and SBL CAN offset is 0x80000. Why are they different?

    3) How do you calculate/decide the offset address anyway please?

  • 0 in reply to Kier
    TI__Intellectual 1150 points

    Hi,
    1) OSPI Phy tuning was enabled for the SBLs between those releases, and the phy attack vector is placed at 0x80000 by hardware design. So, we had to move the application offset.

    2)  We don't program the phy vector in SBL CAN UNIFLASH. This command is not sent:

    --operation=flash-phy-tuning-data

    Hence 0x80000 application offset works for sbl can uniflash.

    3) It is recommended to use 0x81000. Phy mode is enabled by default on SBL OSPI for better performance.

    Best,
    Aswathi