2017-09-26 01:21 PM
My STM32L496G-Discovery shows up as an 'Unknown Device' in the Windows 7 Device manager.
I tried connecting to it with the ST-LINK Utility, it gives a 'No ST_LINK detected' error message.
Is there a way to directly connect to U6 (the 32F103 running ST-LINK firmware) over USB to do DFU?
#st-link #st-link-errorSolved! Go to Solution.
2017-09-26 06:35 PM
Having broken firmware in the ST-LINK, as delivered, isn't something we see much of, more likely something specific to the system.
daemon tools?
2017-09-27 09:16 AM
Vangelis,
Thank you, this was the knock on the head I needed.
Connected another ST dev board, and it also shows as an 'unknown device'.
So, It looks like a problem with the driver.
2019-01-06 11:53 PM
same problem
on a Gentoo Linux machine
Yesterday the atollicTrueStudio told me that the STLink firmeware on my STM32F411 Nucleo is old and there is an update available
-> OK
then i debugged a part of software ...all works for about 2houres
OK then i disconnected the board,
powered off my PC and today it doesn't work any more
the Program on the Target is still running like charm
BUT
there is no more connection
dmesg
[551559.359615] usb 11-4: USB disconnect, device number 6
[551563.688058] usb 11-4: new full-speed USB device number 7 using ohci-pci
[551563.967202] usb 11-4: New USB device found, idVendor=0483, idProduct=374b
[551563.967210] usb 11-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[551563.967214] usb 11-4: Product: STM32 STLink
[551563.967217] usb 11-4: Manufacturer: STMicroelectronics
[551563.967220] usb 11-4: SerialNumber: 066AFF494851877267065831
[551563.969199] usb 11-4: can't set config #1, error -62
dmesg
[551559.359615] usb 11-4: USB disconnect, device number 6
[551563.688058] usb 11-4: new full-speed USB device number 7 using ohci-pci
[551563.967202] usb 11-4: New USB device found, idVendor=0483, idProduct=374b
[551563.967210] usb 11-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[551563.967214] usb 11-4: Product: STM32 STLink
[551563.967217] usb 11-4: Manufacturer: STMicroelectronics
[551563.967220] usb 11-4: SerialNumber: 066AFF494851877267065831
[551563.969199] usb 11-4: can't set config #1, error -62
st-info --probe
setting new configuration (0 -> 1)
Found 1 stlink programmers
serial:
openocd: ""
flash: 0 (pagesize: 0)
sram: 0
chipid: 0x0000
descr: unknown device
so it looks like Atollic has, with this update, killed the STLink on my nucleo device :oops: :evil:
perhaps somebody knows how to fix this problem
2019-01-07 12:02 AM
NO DRIVER PROBLEM
another STM32F411 nucleo from the same batch
i bought 4 of this at the same time 3 working like charm
[583125.632133] usb 11-4: new full-speed USB device number 13 using ohci-pci
[583125.931172] usb 11-4: New USB device found, idVendor=0483, idProduct=374b
[583125.931175] usb 11-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[583125.931176] usb 11-4: Product: STM32 STLink
[583125.931177] usb 11-4: Manufacturer: STMicroelectronics
[583125.931178] usb 11-4: SerialNumber: 066EFF494851877267013639
[583125.941190] usb-storage 11-4:1.1: USB Mass Storage device detected
[583125.941383] scsi host8: usb-storage 11-4:1.1
[583125.943287] cdc_acm 11-4:1.2: ttyACM0: USB ACM device
[583127.019180] scsi 8:0:0:0: Direct-Access MBED microcontroller 1.0 PQ: 0 ANSI: 2
[583127.019398] sd 8:0:0:0: Attached scsi generic sg5 type 0
[583127.029117] sd 8:0:0:0: [sde] 1056 512-byte logical blocks: (541 kB/528 KiB)
[583127.035123] sd 8:0:0:0: [sde] Write Protect is off
[583127.035126] sd 8:0:0:0: [sde] Mode Sense: 03 00 00 00
[583127.041129] sd 8:0:0:0: [sde] No Caching mode page found
[583127.041132] sd 8:0:0:0: [sde] Assuming drive cache: write through
[583127.121279] sd 8:0:0:0: [sde] Attached SCSI removable disk
2022-04-18 06:56 AM
Hi, I’m in the same situation here, brand new Nucleo board, and I get the following with
st-info — probe
setting new configuration (0 -> 1)
Found 1 st-link programmers
seria: XXXXXXXXXXXXXXXXXX < Edit
flash: 0 (pagesize: 0)
sram: 0
chipid: 0x0000
descr: unknown device
It will not connect to the board.
Any procedure to resolve this?
Thanks,