Hello,
I am currently using S32K3X4EVB-Q172. The the issue was found while learning how to configure STM in the project without SDKs. I am not sure if this issue still exists with SDKs.
How to reproduce this issue:
The only workaround I found is to make a new workspace.
The workarounds that did not work are:
I would be very thankful for any help in this matter.
Kind Regards,
Aleksander
Solved! Go to Solution.
While preparing an example project I found out that the workspaces were breaking only if I used console routed to Telnet (set by default) and added STM0 related registers to Watch Registers .
For me, the problem is solved: I need to route console to GDB client.
The only problem that still persists is that it is still uknown, what corrupts the workspaces and how to repair them.
I don't know if it will be still useful but:
Can you share the project so that I can test it on my side?
I attached exampleproject.zip file with an example project folder.
To achieve the error you need to route console to Telnet and add STM0 registers to Watch Registers
Hi Aleksander,
Can you share a screenshot of the error message?
In windows, Task Manager, can you locate PEMmicro gdb and end the task?
Does it happen when you use Debug_Flash?
Regards,
Daniel
Can you share a screenshot of the error message?
After suspenging I get those errors:
After terminating I get this error:
In windows, Task Manager, can you locate PEMmicro gdb and end the task?
I assume this is the task you wanted me to end:
Ending the task does not resolve the issue. After relaunching the problem still exists.
Does it happen when you use Debug_Flash?
Yes. To get the full picture you should know, that flashing program is done succesfully. After restarting the board, LED from Dio_Example blinks ten times but debugging is still impossible.
Kind Regards,
Aleksander
Hi @wyzykpimot,
Still not sure what can be the root cause.
But you said that you reset the MCU after it has been flashed, and debugging after that is not possible.
Do you attach the debugger back to the MCU after the reset?
Was the HSE_FW installed on the MCU?
BR, Daniel
But you said that you reset the MCU after it has been flashed, and debugging after that is not possible.
Little misunderstanding because of my wording. What I meant was:
After Debug_Flash the problem still exists. What I do know is that at least part of the debug session worked. Why? Because after I reset microcontroller, it starts executing the program I flashed in Debug_Flash. I cannot connect to the microcontroller after resetting too.
Do you attach the debugger back to the MCU after the reset?
After using the configuration you suggested and connecting to the MCU after the reset I get following informations:
When I suspend the debug session, it always shows this line of code:
Which is located in startup_cm7.s
Was the HSE_FW installed on the MCU?
It was not. I only tested the functionality of basic peripherials on this board.
Kind Regards,
Aleksander
Can you post the 3rd image once again, the resolution is very low.
Thanks
I pasted the first line:
/*BKPT #1 - removed to avoid debug fault being escalated to hardfault when debugger is not attached or on VDK*/ /* last instruction for the debugger to dump results data */
Kind Regards,
Aleksander
Hi @wyzykpimot,
It is hard to say.
Can you share the project so that I can test it on my side?
If you don't want to share it here, you can create a ticket.
Regards,
Daniel
While preparing an example project I found out that the workspaces were breaking only if I used console routed to Telnet (set by default) and added STM0 related registers to Watch Registers .
For me, the problem is solved: I need to route console to GDB client.
The only problem that still persists is that it is still uknown, what corrupts the workspaces and how to repair them.
I don't know if it will be still useful but:
Can you share the project so that I can test it on my side?
I attached exampleproject.zip file with an example project folder.
To achieve the error you need to route console to Telnet and add STM0 registers to Watch Registers
Hello wyzykpimot,
I have the same problem. Did you resolve the issue?.