-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
STLink v2 Debug Problems #26
Comments
@MrAlexandrKolesnikov Hello! Can you please try to execute the same configuration in the EWARM workbench and see if it works there? |
@jlonnberg Hello! In IAR workbench everything build and debug work too |
@MrAlexandrKolesnikov |
@jlonnberg 8.40.2 |
@MrAlexandrKolesnikov I've now tested this with an ST-Link v2 and a STM32F103ZE card which also uses a flashloader. For me, this works in both EWARM and VS-Code so I'm currently unable to reproduce the problem. The log seems to indicate that none of the application is actually flashed which might indicate that something is wrong with the configuration. Is the launch requests driver options exaclty the same as the ones found in the settings catalog for the EWARM project? If they are, is it possible for you to try with another probe to see if it's the probe that triggers the issue? |
Hi, I try to start debugging but nothing comes out, the firmware is not written to memory
launch.json
Debug console autput:
The text was updated successfully, but these errors were encountered: