• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 16 subscribers
  • Views 291 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CC1352P7: How to set up autostart to main function?

Petru-Felician Birau
Prodigy 30 points
Part Number: CC1352P7
Other Parts Discussed in Thread: SYSCONFIG,

I am using the Simplelink SDK 6.4 and the SysConfig 1.8.2 in the CCS 12.2 environment. I started developing my own software starting with the project sensor_oad_onchip_secure_LP_CC1352P7_1_tirtos7_ticlang. I use a custom board, with an P7 and an CC1352 Debugger to flash.

I would like the program to always start at the main function. The Reset Handler (vector #1) in Sysconfig -> TI RTOS -> HAL -> Hwi ->Core Exception Handlers is set to _c_int00 (default). When I unplug the power or reset the board, the program has following debug informations: 

"WaitHibProdNext + 0x2 () at C:/ti\ccs1220\ccs\ccs_base\emulation\gel\images\cc26xx\cc26x2x7_driverlib_rom_syms.out:{3} 0x1000118e{4}"
Break at address "0x50001000" with no debug information available, or outside of program code.

How can I set up a the reset vector to point to the main function? Alternatively what could be the source of this problem?

I experimented with the Launchpad CC1352P7 and it has the same behaviour.

  • 0
    TI__Guru* 83181 points

    First of all, you should start by using the versions of the different tools that are recommended for the SDK release you are using:

    For simplelink_cc13xx_cc26xx_sdk_6_40_00_13, you should use CCS-12.1.0. This version of CCS uses SysConfig 1.14.0.2667.

    The next thing you should do when since you have a custom board, is to make sure that you are able to run some of our simple default example in our SDK on your HW.

    You can start by testing to build and download for example rfPacketRX and rfPacketTX.

    Use SysConfig through CCS to make the necessary changes to fit your HW.

    When you have verified that all this is running, you can proceed with more advanced projects like the sensor_oad_onchip_secure.

    The out of box example for the sensor_oad_onchip project uses the Linux Collector to update the FW on a sensor device.

    Please note that prebuilt images are only provided for the 1352R1 device. If you are using a different device, please refer to section Generating the Required Binary Images in this document on how to build the images from the projects.

    If you are experiencing problem it is important that you provide us with all the steps you have done (all changes made to the default examples in the SDK) for use to be able to re-create the problem at our end, to be able to help you.

    It is always a good idea to try things out on our LPs first, as that makes it easier for us to the exact same thing.

    If you have everything up and running on a LP, it is only the porting step to a different HW that is left, and if that is HW that you have tested so that you know it is OK, porting is just a matter of setting up SysConfig correctly.

    Siri