We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
I am using Keil MDK 5.33 and the Segger J-Link Base V6.92. I'm running ST motor code on a STM32G431 MCU. When the motor is not running I can connect the debugger, run my program and inspect watch windows and peripherals. I can also communicate with simple commands over a UART interface. When I start the motor the watch windows stop updating and statically display garbage. I can still communicate over the UART interface while the motor is running. I do have the View->Periodic Update set to update windows but it doesn't occur.
If I then stop the debugger, the motor is still running and I cannot reconnect the debugger. I need to use the UART to stop the motor, then I can reconnect.
Is there a way to be able to have the Keil Watch Windows and debug variables update while the motor is running? Otherwise I am severely hampered in debugging. Is this an issue with the priority level settings? Can the J-link be locked out based on priority seetings?
Thanks for any help you can give,
BT
Original poster adding info:
1. I added a command to my uart code to display a program memory location. Doing this I can examine memory while the motor is running. I can see a variable of interest changing as expected in the uart display but the IDE displays AAAAAAAA for almost all watchpoints and peripheral registers.
2. If I use the IDE command Toolbox--> Window Update it does not for an update. All locations still display AAAAAAAA.