Hi all,
I have an application deployed on multiple targets. (Systemview Sources 3.54, PC Application 3.52a)
On hardware with STM32F4 & L4, all is well.
I've recently added boards with an STM32H7 & U5 and I can't seem to reliably connect via Systemview.
Case 1:
If I previously had a debugger (GDB) attached, the Systemview log shows
-> JLink: T-bit of XPSR is 0 but should be 1. Changed to 1.
-> Warning: Target is halted. SystemView Buffer might not be available, yet.
No connection can be established.
Case 2:
If I power on the device (no GDB attached),
-> I get a "DAP error while reading AIRCR" popup
Afterwards, SystemView works just fine.
Case 2 works only once per power cycle, if I try to connect again, it causes a reset on the target system.
Does anyone have an idea what causes this behavior?
Regards,
Manuel
I have an application deployed on multiple targets. (Systemview Sources 3.54, PC Application 3.52a)
On hardware with STM32F4 & L4, all is well.
I've recently added boards with an STM32H7 & U5 and I can't seem to reliably connect via Systemview.
Case 1:
If I previously had a debugger (GDB) attached, the Systemview log shows
-> JLink: T-bit of XPSR is 0 but should be 1. Changed to 1.
-> Warning: Target is halted. SystemView Buffer might not be available, yet.
No connection can be established.
Case 2:
If I power on the device (no GDB attached),
-> I get a "DAP error while reading AIRCR" popup
Afterwards, SystemView works just fine.
Case 2 works only once per power cycle, if I try to connect again, it causes a reset on the target system.
Does anyone have an idea what causes this behavior?
Regards,
Manuel