Forum Replies Created
-
Posts
-
Well, this is weird. I did try with Segger j-link firmware, but I just couldn’t get it working well. It crashed, “lost” the device and only driver reinstall made it reappear. During debug session it would work for a while and then start randomly throwing “cannot read mem loc”, after which couldn’t even reconnect to back j-link… Tried this in VisualGDB and Eclipse.
Switched the Nucleo-F303RE back to st-link and now works like a charm, again. Maybe it’s something with my Win10 setup, drivers etc. Same behaviour with F303 and L011 nucleos after upgrade. Sticking with St-Link for now :).
I have one the nano size F031 nucleo coming, so hopefully I can use that for the small form-factor stuff. Though, would be nice to get this solved sometime. Probably will try this on another PC, see what it does there.
Thanks for quick response!
I tried the 0.10 release, it has the same issue. At least trying with the stm32l0discovery.cfg.
I will try the Segger later tonight. Is it possible to ‘downgrade’ back to standard st-link after the Segger upgrade? Not that I would want to do that, if it works, but just to be sure.
