Other Parts Discussed in Thread: AWR2243BOOST, UNIFLASH, AM2634
Tool/software:
Hello!
I'm working with AM273x Evaluation Module connected with AWR2243BOOST board, and running the Visualizer Demo application. Also working with a fork of the demo project.
The problem I struggle with is very unreliable debugging. This doesn't happen when running the app from ROM (flashed with uniflash).
1. Around two out of five debug runs result in the execution of the program landing early (even before landing `main()`) in `HwiP_undefined_handler`, or `HwiP_data_abort_handler`/`HwiP_data_abort_handler_const`. This is random, and happens also in other applications, both single-core apps (e.g. running only from R5F0; I have tried running UDP client and TCP client from the MCU PLUS SDK) and multicore (e.g. R5F0 + C66, as in the Visualizer Demo). This is very cumbersome, because when debugging large programs, I need to re-load the program multiple times, and one program loading takes a lot of time already. Why is debugging so unstable? I would really appreciate some support of making it more reliable.
2. Grouping while debugging multicore apps doesn't work as intended. According to this guide 
, I'm trying to create a "Permanent Group" to start the cores at the same time. The problem is that hitting "Resume" on the group:
Leads to C66 not being run. The "Debug" view claims it's run:
But it's not, as when I "Pause" it, then it's still at main() entry:
It would be OK for me to run the cores separately, one after another, but in such a case the Visualizer Demo app gets out of sync, resulting in a crash.
