• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 55 subscribers
  • Views 360 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.

CC2651R3: Why is the startup file included in nortos library?

JHi
Expert 2730 points

Part Number: CC2651R3

As the title says, why is the startup file (startup_cc13x1_cc26x1_ticlang.c.obj) included in the nortos (nortos_cc26x1.a) library? How can I modify the startup file or the functions inside it?

  • 0
    TI__Guru**** 223757 points

    Hi JHi,

    <sdk_directory>kernel\nortos\startup\startup_cc13x1_cc26x1_ticlang.c includes the reset ISR (called when the processor first starts execution following a reset event) and the default fault handlers.  The resetISR immediately jumps to the C Initialization Routine (main) if processed correctly.  Why would you want to modify this file?

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    Expert 2730 points

    To modify the default handlers for example. There are also use cases where you has/want to do some stuff before jumping to main. Usually you include the startup file yourself to your project. I think this is just stupid to include it in a library. 

    From the docs:

    Startup Files
A “nortos” application should use the startup files and linker command files that come packaged with the “nortos” TI Driver examples. 
These files have been tailored for the devices and OS in use. The startup files contain the initialized vector table, which can be modified 
to suit the application needs. There is a different startup file and linker command file for each supported compiler (CCS, GCC, IAR).

The SimpleLink examples come packaged with the necessary startup and linker command files from the particular driverlib that is contained in the SDK.