I am encountering a bug in my firmware that causes the cc26xx to stop executing and simply hang. The bug goes away when I specify that CCS debugger config should disable all interrupts.
How do I find out what exceptions are being fired using CCSv6, provided that the cc26xx is connected via a USB XDS110 devpack debugger? Do I have to set a breakpoint in every single exception handler? Is there a better way?
Hi,
The Cortex M cores have some event counters built into the core that can count certain events including Exceptions. These are accessible via the Breakpoints view in CCS
However, I couldn't find hardware support to trigger a breakpoint on ALL exceptions.
if you are using a Real-time OS you can get additional exception support:
On the other hand, there is a chance to monitor these Exceptions using the Interrupt Profiler with the SWO Trace (menu Tools --> Hardware Trace Analyzer --> Interrupt profiler). CCS supports SWO Trace over 2-wire cJTAG if you configure it this way:
However, in order for this to work the code must be configured to output the SWO Trace data at the beginning of your code (SWO Trace data can be output in any pin in this device, therefore the requirement). For details, check the thread below:
https://e2e.ti.com/support/wireless_connectivity/bluetooth_low_energy/f/538/p/412139/1574406#1574406
In addition to that, you must be sure the hardware is wired to output SWO trace data. Unfortunately I am not entirely sure if the SensorTag hardware is wired this way but perhaps the experts in the wireless connectivity forum can help you with that.
Hope this helps,
Rafael
For Cortex M devices, under the GEL files -> ARM Advanced Features -> Vector Catch you can set breakpoints on different types of errors:desouza said:However, I couldn't find hardware support to trigger a breakpoint on ALL exceptions.
Does that help to set a breakpoint for ANY type of exception?
[The above screenshot was from debugging a Cortex-M4F but think the same also applies to Cortex-M3 devices]
