2017-04-13 03:58 PM
Hi!
I have a Nucleo64-446RE and every 5/10 minutes the board resets itself.
I'm using the Virtual COM to send data to my PC and plot it (among many other things), and when the board resets I lose the Serial connection. I need to re-open it in order to plot again. If after this reset I want to program the microcontroller I get the ''Unable to reset target'' message for which I need to unplug and replug the USB(which is also powering the board). I'm using the System Workbench for STM32.
Here's an oscilloscope picture of the NRST pin (blue), which confirms the reset. The red trace is a 3.3V pin, which shows there are no power issues.
Can you please help me debug this reset?
As I understand, it can't be a Hard Fault because (I think) in that case the system wouldn't reset but end up in an infinite loop. I haven't implemented any of the error handlers, but I think they're implemented by default with weak attributes.
Watching the following image:
From external sources:
From internal sources:
Thank you very much in advance for all your input!
Cheers,
Andrés
2017-05-31 10:49 AM
I have uninstalled ALL Dell support software and it is still reinstalling the driver every time I unplug and plug in the board, after manually removing it. I am running Windows 10 on a Dell Precision Tower 3420.
Anyone encounter this problem?
2017-06-01 06:59 PM
Yes, happened to me too on my Dell (window 10). STLink debug driver will reinstall (when ST board is connected) even u uninstalled.
Which should not caused you problem.
I find out the issue with below, it is due to Mv18 on board, I managed to borrow a board which has Mv15 STlink frimware.
The ERROR message is not show anymore.
Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
Info : STLINK v2 JTAG v28 API v2 M v18 VID 0x0483 PID 0x374B
I am able to ask anyone know where to get previous version of stsw-link007
2018-03-06 09:26 PM
The ST-Link V2-1 (with mass storage) is unusable. Randomly disconnects, resets target, ST-Link not found error, etc. Standalone ST-Link V2-0 is rock solid and works fine. It would be so nice to let us officially downgrade the onboard debugger. The hardware is the SAME.
There is only the unofficial way now: Download standalone ST-Link's old firmware binary from some dev forum, reflash onboard STM32F103, and update with official tool. It works fine.
I never missed the mass storage mode. Virtual serial port would be nice to have, but working debug is more important.
2018-03-06 11:11 PM
You could always convert it to a J-LINK OB
2018-03-06 11:20 PM
Yes, I know. I tried, but I did not like.
2018-03-08 09:20 AM
If you are using Dell, uninstall the Dell Service Application/Agent, which cause problem.
After I uninstall it, problem never come back for 9 months
2018-03-08 09:50 AM
I use a no-brand i7 desktop, a Lenovo notebook and two HP notebooks...
2018-11-28 05:36 AM
I had a similar issue developing on a 144 pin Nucleo-L496ZG.
It would reset every 10 minutes or so. If debugging then I'd get an exception and breakpoint at the start of main. If not debugging (just powering through the onboard ST Link) then I'd keep hearing the USB virtual com port drop out on the PC.
I seem to have cured this now by powering the Nucleo board off an external 5V supply connected to the Morpho pins. (Remember to swap jumper JP6 to the E5V setting and make sure JP1 is removed)
Hope this helps.
2019-03-30 10:25 AM
I have a total of four Dells. A PC and laptop both at home and at work. All exhibited the periodic reset. I stopped and disabled all Dell services on the home PC. My Nucleo has now been running for three hours without a reset. Can't wait to try it on the other Dells.
Thank you to all who suggested the Support Assist and agent. It has been a frustrating issue.
2019-08-06 08:56 PM
Thank you all guys, using STM32NucleoF411RE on a Dell Inspiron 3521 and almost quit on learning ST microcontrollers because of this periodical reset issue. Uninstalling Dell SupportAssist solved the problem.
regards,
Alberto M