Unlock the Gateway: Join the Embed Threads
Unlock the Possibilities: Dive In with Login Access
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have used STM32CUBE IDE & created a project for the board (STM32F103RB).
Then I have tried debug my board by clicking on ‘Debug as’ option.
Then I have observed this below message in the console
‘Target is not responding, retrying…’
I have also attached the detailed snapshot of the error here. Please help me solve this issue.
Hello,
Have you wait to finish flashing process which is ongoing? I believe you have pressed continue button while flashing is ongoing which may cause this type of issues.
Also you can check below link for more information in which same kind of error has been resolved which you are facing.
https://community.st.com/t5/stm32cubeide-mcu/failed-to-execute-mi-command/td-p/282321
Yes I have waited until the error has shown up. And I didn’t see any continue button during this process.
And from the ST community page which I have seen , the issue is resolved once the flash is cleared using STM32CUBE programmer. I will tried that & update you.
Let me know if you are familiar of this above clearing process.
Hello,
Thanks for providing updates.
Let me know once you verify at your end.
Regards,
Ritesh Prajapati
Clearing the Flash with Cube Programmer has resolved the issue.
But the issue was reproducible when programmed with
CUBE IDE on a specific laptop.
Then I have re installed CUBE ide & checked then it started working.
Thanks a lot for your prompt response.
It means there may be flash cache issue while using STM32 Cube IDE specific into that Laptop.
Let me know if need any further help from my end.
Regards,
Ritesh Prajapati
Hello,
Disconnect and connect again to solve this issue. This type of error occurs when previous debugging was not successfully completed.
In my case this didn’t work but it got resolved in other ways mentioned above.