• State Resolved
  • Locked Locked
  • Replies 18 replies
  • Answers 4 answers
  • Subscribers 97 subscribers
  • Views 1850 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.

RTOS/TDA2EVM5777: QSPI Flash based SBL & APP images fail to boot as expected

Sathiyan Sathiyan
Intellectual 500 points

Part Number: TDA2EVM5777

Tool/software: TI-RTOS

Hi,

http://processors.wiki.ti.com/images/b/b7/TDA_SBL_UserGuide.pdf

By following above guide and with the use of TDA2XX board, we try to generate and flash SBL & Application images into QSPI flash. In the end there is NO complete application loading.

This is the snapshot of Terminal prints after SBL TIIMAGE file is loaded.

- can you point out why "SBL Initial Config Failed" comes and how to overcome this?

Below are the prints in Terminal window after loading the APP muticore image binary - FYI, MPU_CPU1_ID (value = 1) was used to generated this.

<<<<<< 

DRA72x SBL Boot

SBL Initial Config Failed

DPLL Configuration Completed

Clock Domain Configuration Completed

Module Enable Configuration Completed

TI EVM PAD Config Completed

DDR Config Completed

App Image Download Begins

Manufacturer ID - 0x1

Device ID - 0x18

WARNING: Device Id Does not Match

Trying to boot App Image with header version 1

WARNING: Device Id Does not Match

MPU CPU0 Image Load Completed

App Image Download Completed

*****************************************************************

PMCCNTR counts once every 64 clock cycles, multiple by 64 to get actual CPU cycles

SBL Initial Config Cycles - 69304 (5.54 ms)

SOC Init Cycles - 217592 (17.40 ms)

DDR Config Clock Cycles - 57379 (4.59 ms)

App Image Load Cycles - 505157 (40.41 ms)

Slave Core Bootup Cycles - 17950 (1.43 ms)

SBL Boot-up Cycles - 868601 (69.48 ms)

Time at which SBL started IPU1_0 - 71878497 (5750.27 ms)

****************************************************************

Jumping to MPU CPU0 App

<<<<<< 

There is no output prints as expected for the "Hello World" print - either in Console or in Terminal window.

It's bit urgent so kind attention & inputs are needed soon to resolve... kindly let me know if any additional info. needed.

Thanks & Regards,

Sathiyan

  • 0
    TI__Guru 55685 points
    Hi,
    You can follow the below sequence to debug:
    1. Can you set the board in debug mode as per the user guide.
    2. Use CCS to load SBL (built in debug mode) and single step to identify the failure.

    Regards,
    Rishabh
  • 0 in reply to Rishabh Garg
    Intellectual 500 points
    Hi,

    Thanks for quick input. Yes debug mode was mode in SW2 as per user guide.

    Do you mean to debug SBL execution and see why "Init Config Failed" error happens? Let me try.
    But before to that I doubt the options used while creating SBL & APP images. If there is any input in that angle, that would help.

    Thanks,
    Sathiyan
  • 0 in reply to Sathiyan Sathiyan
    TI__Guru 55685 points
    Hi,

    Did you change anything in default options?
    Are you using custom board or EVM?

    Regards,
    Rishabh
  • 0 in reply to Rishabh Garg
    Intellectual 500 points
    Hi,

    It's a EVM board only. Which "default options" you point out?

    By options in my previous comment, I meant the build options that should be input to generate the SBL (via gmake) and APP (via CCS tool followed by RPRC conversion & then Multicore image generation tool).

    Thanks,
    Sathiyan
  • 0 in reply to Sathiyan Sathiyan
    TI__Guru 55685 points
    Hi,

    The build command is given in section 4 of SBL user guide.
    I meant that you need to set debug mode in SYSBOOT and then load the SBL using CCS.

    Regards,
    Rishabh
  • 0 in reply to Rishabh Garg
    TI__Guru 55685 points
    Hi,

    One more point.
    You need to set SW2 for QSPI as per SBL user guide and not debug when you are trying QSPI SBL boot.

    Regards,
    Rishabh
  • 0 in reply to Rishabh Garg
    Intellectual 500 points
    Hi,

    Yes your above two comments based steps were already taken care... I believe because of this only such Terminal prints (one after SBL alone loaded stage and next after App image loading) are shown in boot sequence.

    My queries :
    1) is the "SBL init config failed" [gets printed as part of the SBL boot sequence] an issue for an incomplete App boot-up ?
    2) is there any application note or any other older post in forum or any other document available - which throws light on the command options used in SBL generation (.xa15fg and .tiimage files) & then the APP Image generation (,.rprc and .bin files) ?

    Thanks in advance,
    - Sathiyan
  • 0 in reply to Sathiyan Sathiyan
    TI__Guru 55685 points
    Hi,

    I will once look at sbl code and get back to you on 1. For 2 I am not sure what is not clear. It’s explained very well in SBL userguide.

    Regards,
    Rishabh
  • 0 in reply to Rishabh Garg
    Intellectual 500 points
    Hi,

    Thanks for your plan on 1. I wait. Also do you need any generated file to be attached here, so that you can refer the values and henceforth, go through the SBL code?

    I think 2 is related to the issue pointed in 1. As there are variables (like build options, target configurations, boot modes, etc.,) while generating SBL & APP (as per the SBL user guide), we had to logically pick the values for almost all variables but for some there was trial & error based input involved. I doubt the "SBL init config failed" pointed in 1 is due to some missing details which I intend to get clarified by 2
    To name a few of the missing details :
    - M4 is master or A15 is master?
    - Core ID / Device ID configuration for the Target and the corresponding value usage while building the APP multicore image ?
    - QSPI flash writer loading into M4 or A15? (FYI, am always unable to load into M4 as the guide says)
    - SBL ELF and SBL TIIMAGE loading order ? and loaded into which target?

    May be when you get back on 1 [ on what all cases "SBL init config failed" is hit ], we can narrow down things w.r.t 2 and proceed further.

    Thanks in advance,
    Sathiyan
  • 0 in reply to Sathiyan Sathiyan
    TI__Guru 55685 points
    Hi,

    You have misinterpreted my comment.
    I would like to re-iterate that all the information you need for SBL is already there in user guide.
    It seems that you are trying to run TDA2E SBL on TDA2 board in above case. Same is mentioned in SBL user guide chapter 2.
    My suggestion to you would be to go through PDK getting started videos for basics:
    training.ti.com/getting-started-adas-platform-development-kit-pdk
    After that go through SBL user guide.

    Regards,
    Rishabh
  • 0 in reply to Rishabh Garg
    TI__Guru 55685 points
    Hi,

    I haven't heard back from you, I'm assuming you were able to resolve your issue.
    If not, just post a reply below (or create a new thread if the thread has locked due to time-out).

    Regards,
    Rishabh
  • 0 in reply to Rishabh Garg
    Intellectual 500 points

    Hi,

    No the option (as per Chapter 2) to select for "evmDRA72x or TDA2xx" is yet to be tried and whole steps are yet to be checked.

    Thanks for trying to know the conclusion, but kindly wait until another 4-5 hours by which I can get back to you whether the issue is resolved completely or not.

    Meanwhile, is it possible to enable more debug prints in the SBL - because "SBL Initial Config failed" lacks more information rather if the debug logs point out the problematic configuration or (combination of configurations), then it would be much helpful & effective. Hope you agree !

    Thanks,

    Sathiyan

  • 0 in reply to Sathiyan Sathiyan
    Intellectual 500 points
    Hi,

    Also FYI, the time delay incurred (to verify your suggested steps) is because we are currently working to complete our customised application (which we can directly build with CCS) and test with these SBL user guide steps directly.

    Thanks for understanding !
    - Sathiyan
  • 0 in reply to Rishabh Garg
    Intellectual 500 points
    Can we get more debug prints or logs in SBL (that can be seen in UART terminal) to ourselves get clarified on these doubts :-
    - M4 is master or A15 is master?
    - Core ID / Device ID configuration for the Target and the corresponding value usage while building the APP multicore image ?
    - QSPI flash writer loading into M4 or A15? (FYI, am always unable to load into M4 as the guide says)
    - SBL ELF and SBL TIIMAGE loading order ? and loaded into which target?
  • 0 in reply to Sathiyan Sathiyan
    TI__Guru 55685 points
    Hi,

    I would strongly recommend you to go through basic training material first whenever you are done with custom application.
    A15 is master for TDA2x device and flash writer should be run from M4 as given in user guide.
    SBL elf is not loaded. It is converted to tiimage which is loaded by SBL.
    Device/Core Id configuration and usage is documented in SBL user guide.
    You can also see various scripts under <pdk>\packages\ti\boot\sbl_auto\tools folder.

    Regards,
    Rishabh
  • 0 in reply to Rishabh Garg
    TI__Guru 55685 points
    Hi,

    I haven't heard back from you, I'm assuming you were able to resolve your issue.
    If not, just post a reply below (or create a new thread if the thread has locked due to time-out).

    Regards,
    Rishabh
  • 0 in reply to Rishabh Garg
    Intellectual 500 points
    >> reply on Feb 18, 2019 2:56 PM
    >> To name a few of the missing details :
    >> - M4 is master or A15 is master?
    >> - Core ID / Device ID configuration for the Target and the corresponding value usage while building the APP multicore image ?
    >> - QSPI flash writer loading into M4 or A15? (FYI, am always unable to load into M4 as the guide says)
    >> - SBL ELF and SBL TIIMAGE loading order ? and loaded into which target?

    >> reply on Feb 20, 2019 7:27 AM
    >> Can we get more debug prints or logs in SBL (that can be seen in UART terminal) to ourselves get clarified on these doubts :-
    >> - M4 is master or A15 is master?
    >> - Core ID / Device ID configuration for the Target and the corresponding value usage while building the APP multicore image ?
    >> - QSPI flash writer loading into M4 or A15? (FYI, am always unable to load into M4 as the guide says)
    >> - SBL ELF and SBL TIIMAGE loading order ? and loaded into which target?

    Hi Rishabh,

    Though the above two replies/queries are still open (in our perspective), for now we are able to flash & boot the Mailbox Multicore Example Application.. based on some of the inputs from you. So this thread can be closed and for any queries related to above two reply posts, we shall open new post, particularly based on our own customized application boot/flash status. Thanks for the support rendered !

    Regards,
    Sathiyan
  • 0 in reply to Sathiyan Sathiyan
    TI__Guru 55685 points
    Hi,

    I would suggest you to go through my last reply and the training material to be clear on the basics.

    Regards,
    Rishabh