2024-08-18 07:21 PM
Hello there
Just tried connecting my STM32F4DISCOVERY board to my PC. It appears that the underlying operating system recognizes the driver/device correctly. I've tried this on both Windows 10 and Linux and this seems to be the case on both.
Here is part of the kernel log message on Ubuntu:
Aug 18 18:39:47 MBP kernel: [ 1497.590243] usb 3-2: new full-speed USB device number 5 using xhci_hcd
Aug 18 18:39:48 MBP kernel: [ 1497.739857] usb 3-2: New USB device found, idVendor=0483, idProduct=3748, bcdDevice= 1.00
Aug 18 18:39:48 MBP kernel: [ 1497.739873] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Aug 18 18:39:48 MBP kernel: [ 1497.739877] usb 3-2: Product: STM32 STLink
Aug 18 18:39:48 MBP kernel: [ 1497.739881] usb 3-2: Manufacturer: STMicroelectronics
Aug 18 18:39:48 MBP kernel: [ 1497.739884] usb 3-2: SerialNumber: 066CFF3238504B3043193820
And this is what I see on STM32CubeProgrammer:
18:40:56 : STM32CubeProgrammer API v2.17.0 | Linux-64Bits
18:40:56 : ST-LINK error (DEV_CONNECT_ERR)
I'm at my wit's end trying to get this connected to my PC. The exact same message is seen on STM32CubeProgrammer on a windows machine. Of course the windows kernel log would change.
The board is currently running the demonstration firmware that toggles the LEDs in a circular manner for 8 times then it toggles them all together. I'm attaching the pic. I've scraped the web looking for a way to get this connected but they suggest resetting the board via the STM32CubeProgrammer but for this to work, it has to be detected by it. So im in a catch 22 kind of situation here.