• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 99 subscribers
  • Views 781 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.

Start application in TDA3xx secondary bootloader

Mayank Agarwal
Expert 2600 points

Hi,

How the main m4/c66 application is started from starterware secondary bootloader in Vision sdk

In Vision sdk i want to start my main function instead of main in main_ipu1_0.c.

My application was working fine for tda2xx board and now i have made changes for it to work on TDA3xx

I want to execute it on TDA3XX  evm board.

If i have to make changes in starterware sbl code for that.

Please reply

Regards

Mayank

  • 0
    TI__Guru* 96960 points
    I've moved your thread to the device forum.

    Todd
  • 0
    TI__Guru 55685 points
    Hi Mayank,

    SBL will parse the multi-core application image and identify the entry point for each core's application.
    Then SBL configures this entry point at start address register for each core and brings it out of reset (for slave cores) / jumps to this address for master core after completing SBL.

    You don't need to change SBL code for making your code start from custom_main.
    You should modify Vision SDK app to change the entry point from _c_int00 to custom_main.
    This can be done by specifying entry point in linker flags (-e custom_main).
    Hope this helps.

    Regards,
    Rishabh