Tool/software:
I have tried transitioning to CCS 20.1.0. I have compiled my "old" code, that uses GCC, NoRTOS.
When I run it on the Launchpad, it runs for 1-10 minutes, and then traffic stops. The code is still executing, so I have tried the pause button
to find out what it is doing.
When I try to step with the debugger it claims
Exception has occurred.
Unable to step. A common cause of this is that all hardware breakpoints have been used.
This did not happen before, and I have in this case no breakpoints set.
This looks to me as "debugger problem in CCS.
I have also had problems starting the application, where just running it with the "proceed" button
did not cause the uart1 to start, and thus no command interpreter ( my own)
Stepping through the code through initialization into the "big loop" and THEN hitting "proceed"
would result in operating firmware. I can see no *critical* calls and stepping through them
behaves normally.
Since I am not using any of my "own" interrupts, but only the TI drivers and callbacks,
it seems there is some "race" condition.
I am using the UART2 driver ( 2 units), SPI driver ( 1 unit) radio driver (taken from the rfUARTbridge example)
a timer callback that decrements two timers once a mS.(to get timing)
This looks to me as a driver implementation problem, since I cannot understand how I could have developed a "race".
This is hard to debug, so ideas how to proceed are welcome, I do not rule out coding problems, but it is hard
to find those when the debug environment misbehaves(??)
Regards,
Gullik
