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.

CC1350: First processor triggered reset after flashing with Uniflash results in hang

Part Number: CC1350
Other Parts Discussed in Thread: UNIFLASH

Hello,

In my application, a recovery process from a specific fault includes a SysCtrlSystemReset() call to reboot the device and reinitialise all tasks, peripherals, etc. I'm experiencing an issue where a reset of thing kind triggered after flashing via uniflash will cause the system to hang. That's obviously not the outcome you'd want from a process intended to recover from faults!

What's unusual is that this only occurs on the first reset after flashing devices via uniflash. To recreate the issue I simply have a clock that will trigger a reset after 1 minute of operation, and roughly 75% of the time this hang will occur. 

In order to determine the extent of this fault I've tested a few things. The most recent of which is having UART writes spread throughout the startup process of my main task. When the restart occurs and the device hangs I see no output on UART. From this I suppose the device is either failing to restart, getting stuck before tasks are initialised/started in main().

It's a difficult thing to debug since debugging with CCS isn't possible due to the reset. Any idea what the problem could be, or how to go about narrowing it down/debugging further?

The project is built on CC13xx Simplelink SDK 1.40 and tirtos_cc13xx_cc26xx_2_21_00_06.