• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 2 answers
  • Subscribers 31 subscribers
  • Views 230 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.

Original question:

AM2634-Q1: AM2634 HSM issue about hs-fs files and debug tips?

AM2634-Q1: Customer has already convert HS-SE devices, but it failed when setup as QSPI boot mode?

Shaoxing Ke
Expert 3590 points
Part Number: AM2634-Q1
Other Parts Discussed in Thread: UNIFLASH

Tool/software:

Hi Experts,

I am asking for my customers here.

When boot mode is changed to QSPI startup, and the image.HS files of SBL_NULL.hs and SBL_QSPI,hs  are programming into FLASH respectively. The data received from the serial port shows that SBL_QSPI startup failed as below. Could you give us debug suggestion or direction here?

  • 0
    TI__Expert 3590 points

    Hi Experts,

    Any updated progress about this issue?

  • 0
    TI__Mastermind 44364 points
    Shaoxing Ke said:
    and the image.HS files of SBL_NULL.hs and SBL_QSPI,hs  are programming into FLASH respectively. The data received from the serial port shows that SBL_QSPI startup failed as below.

    Hi Shaoxing, Can you share the how customer is flashing these? And address offsets where these are flashed. 
    Also thery should not flash both SBL null and SBL QSPI,

    If they want to use CCS to debug anf load example binary use SBL NULL

    Or 

    If they want to put application image also in  flash they should use SBL QSPI+ Application binary to flash.

  • 0 in reply to Nilabh Anand
    TI__Expert 3590 points

    Hi Nilabh,

    They flashing the image.hs files by JTAG over UniFlash.

    When the chip convert from HS-FS to HS-SE, the code will stuck at  QSPI_SBL code as Function Bootloader_parseMultiCoreAppImage, return vaule -1. And then it failed to go into APP R5F0-0 core app. So how to solve this issue or debug this issue? Thanks.

  • 0 in reply to Shaoxing Ke
    TI__Mastermind 44364 points

    Hi Shaoxing,

    1. As per the documentation of TIFS, The requirement is to use MCU PLUS SDK compatible with particular TIFS SDK version ex, USe MCU PLUS SDK 10.0 with TIFS SDK 10.0.

    2. OTP Keywriter is also dependent on the SDK version, the documentation mentions the required MCU PLUS SDK version