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.

CCS/CC1352R: Difference restart to restart via debugger

Part Number: CC1352R
Other Parts Discussed in Thread: SYSBIOS

Tool/software: Code Composer Studio

Hi,

I use Code Composer Studio together with XDS110 Debugger to put my program into the CC1352R device. When I start debugging, means the program is loaded directly via debugger, it works. But when I press the Restart button (menu Run / Restart) the processor does a reset but it doesn't work. I'm running into the exception handler where the CPU_SCS_CFSR_INVSTATE bit is set.

So is there something in the processor that is not initialized to default values when I press the restart button? There has to be a different between both kinds of program start. I also don't know that CPU_SCS_CFSR_INVSTATE really tells me. I'm new with CC1352R processors, before we used ATMEL processors.

I'm also using TI-RTOS if that helps. At compile time first sysbios/rom_sysbios.aem4f is build which seems to be some special firmware first loaded (into special areas of processors flash?). Could this be the difference?

Thanks in advance

Erwin

  • What SDK version and example do you test this?

  • When I go under Project Properties / General / Products it showd my SimpleLink CC13x2 26x2 SDK under which I've selected 3.40.0.02

    So I guess this is the SDK I'm using.

    My software is not an example Software. It's out product software.

    Regards

    Erwin

  • Erwin,

    In CCS clicking the "restart" button just moves the PC to the entry point. From CCS documentation:

    • Reset: performs a reset on the core or device. The small inverted arrow allows selecting among the available resets.
    • Restart: issues a restart when either symbols or a program is loaded to the target device. A Restart simply re-positions the PC register to the entry point (typically _c_int00 or the reset vector).

    It's possible that something isn't getting set back to its initial/default state which could be causing issues. You probably want to use the reset button to reset the MCU to default state.

    Regards,

    Daniel