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.

CC1310: Inconsistency in reset, Code doesn't get executed after SysCtrlSystemReset() API is called.

Part Number: CC1310

Hi,

I have two program code in cc1310 flash, bootloader and application, the bootloader is placed in address 0x0. And also there is a sector allocated for storing some configurations.

So after every reset, CPU execution starts with the bootloader. 

Bootloader

After using the RF core and UART, the bootloader triggers a reset using SysCtrlSystemReset() API.

Again bootloader execution starts and jumps to the application.

Application

There is also a reset from the application when some command received over RF.

But the problem is these resets from bootloader and application is inconsistent, 

It always works, but sometimes after these resets API called, the bootloader doesn't execute.

Can any one help please?

  • Hi,

    I have more information for your understanding.

    Both of my programs are using BIOS in flash, commented following in .cfg file,

    /*var ROM = xdc.useModule('ti.sysbios.rom.ROM');
    if (Program.cpu.deviceName.match(/CC26/)) {
        ROM.romName = ROM.CC2650;
    }
    else if (Program.cpu.deviceName.match(/CC13/)) {
        ROM.romName = ROM.CC1350;
    }*/

    m3Hwi.resetVectorAddress = 0x0 for bootloader.

    m3Hwi.resetVectorAddress = application starting address for application.

    CCFG is placed in the last sector, 0x1FFA8.

    configuration sector is the second last sector, 0x1E000.

    One more information is that the bootloader is using 96 % of the 20KB SRAM.

    After software reset, when CPU hanged, when I make a hard reset, the code runs from the bootloader and working perfectly, the error only happens when there is an SW reset triggered using SysCtrlSystemReset () API.

  • Hi,

    We will look into it and get back to you ASAP. Please bear with us.

    Thanks,

    PM

  • HI,

    Can anyone please suggest a clue. My assumption is that the CPU hangs somewhere in the startup code of bootloader after triggering a software reset.

    Thanks,

    Kannan Vinod

  • Hi,

    Is the problem due to the debugger connected?

    Best Regards,

    Kannan Vinod

  • Hi Kannan,

    Are you running a debug session? does this also happen when the device is just free running? 

    How do you know that both SysCtrlSystemReset () calls are successful? 

    Thanks,

    Alexis

  • Hi Kannan,

    Haven't heard back from you so I'm assuming you've resolved your issue. Feel free to respond or open a new thread if you have additional questions or information to add.

    Thanks,

    Alexis