Search Results
Search results 1-4 of 4.
This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.
-
Hi Nino! Today it came out that it was application specific and it was my mistake. Certain operation caused system under-voltage and MCU was acting not predictably. At some point it stopped working even with the ST-Link, so it was a lead to investigate further. Additional power filtration fixed the problem. In the end it was not a J-Link problem, just my bad design. Thank you for everybody help. Regards: - Tomasz
-
Happened to me once again this morning. Debug stopped working while resuming program with j-link. Programming it once with ST-Link fixed the problem. does anyone encountered similar problem? - Tomasz
-
Hi, I have just tried using ST-Link just a moment ago and it works flawlessly. Weird thing is that J-Link started working after using ST-Link, but I have been here before...I get to work and at some point I get the same behaviour as above. Earlier I also tested deleting the debug configuration in Atollic, or a clean build, but none of it fixed the problem. - Tomasz
-
Hi everyone, I am running j-link base with latest firmware (2019 Mar 21) to debug STM32F415RG, using Atollic TrueSTUDIO ver 9.1.0 (Eclipse Neon). Sometimes the debug session runs with no problems, but most of a time a get an error when I try to run the session using "Resume". When I use "Step Over" or "Step Into" it always works fine. Here is an Console output of debug session init: Source Code (61 lines) As soon as I hit the "Resume" button the console outputs ERRORs and the debug process can n…