Loading...
 

SW4STM32 and SW4Linux fully supports the STM32MP1 asymmetric multicore Cortex/A7+M4 MPUs

   With System Workbench for Linux, Embedded Linux on the STM32MP1 family of MPUs from ST was never as simple to build and maintain, even for newcomers in the Linux world. And, if you install System Workbench for Linux in System Workbench for STM32 you can seamlessly develop and debug asymmetric applications running partly on Linux, partly on the Cortex-M4.
You can get more information from the ac6-tools website and download (registration required) various documents highlighting:

System Workbench for STM32

Forum List Topic List

[ prev topic ]  

STM32F4 USB connection unrecognised

Posted by konje on 2017-05-18 19:56

Hi,

I am working on Ubuntu 16.04 and cant detect my STM32 discovery board on the system. I installed st-link and when I run st-util with board connected I get:

$ st-util
st-util 1.3.1
2017-05-18T18:51:43 WARN src/usb.c: Couldn’t find any ST-Link/V2 devices

Aslo when I try to detect the board by lsusb, fdisk or $ ls /dev/ | grep sd command, the board is not listed (as I would expect sdb* there). The output before and after running the comand is the same:
sda
sda1
sda2
sda3
sda4
sda5
sda6

I have jumpers on CN3 connectors. Can anyone help please? Does it has anything to do with the reset button - if yes how do you reset via terminal?

Reads: 8121
Link
Posted by jLn_38 on 2017-05-19 08:27

Hi Konje,

Did you check that Udev rules are installed ?
FYI The SystemWorkbench installer packages all the required stuff to enable STLink through USB.

Here are the expected rules: 

$ ls -1 /etc/udev/rules.d/*stlink*
/etc/udev/rules.d/49-stlinkv1.rules
/etc/udev/rules.d/49-stlinkv2-1.rules
/etc/udev/rules.d/49-stlinkv2.rules
Link
Posted by konje on 2017-05-19 11:11

Yes, I have them isntalled. Also I checked the board on another PC that I programmed the STM board before and I also got connection error this time. The power led lights up and programator LED1 blinks red - if thats any indication.

I imagine that udev rules should work on reboot. Alternativelly, I treid restart udev rules command but for some reason that command didnt work, I got: “failed to connect to upstart” (apparetnly upstart was replaced by systemd).

Link
Posted by niftynei on 2018-03-09 01:21

I’m having a very similar issue — plugging my dev board (Nucleo-F091) into the USB isn’t showing up when I run `lsusb`. Also running Ubuntu 16.04.

I copied the udev rules so there’d be one with an `stlink` group permission (and added myself to it) with no visible effect. Any pointers of what else to look at?

/etc/udev/rules.d$ sudo ls -la
total 44
drwxr-xr-x 2 root root 4096 Mar 8 16:14 .
drwxr-xr-x 4 root root 4096 Feb 8 23:08 ..
-rw-r--r-- 1 root root 471 Mar 8 15:45 49-stlinkv1.rules
-rw-r--r-- 1 root root 532 Mar 8 15:45 49-stlinkv2-1.rules
-rw-r--r-- 1 root root 530 Mar 8 15:45 49-stlinkv2.rules
-rw-r--r-- 1 root root 717 Feb 7 22:32 49-stlinkv3.rules
-rw-r--r-- 1 root stlink 471 Mar 8 16:14 50-stlink1.rules
-rw-r--r-- 1 root stlink 532 Mar 8 16:14 50-stlinkv2-1.rules
-rw-r--r-- 1 root stlink 530 Mar 8 16:14 50-stlinkv2.rules
-rw-r--r-- 1 root stlink 717 Mar 8 16:14 50-stlinkv3.rules
-rw-rw-r-- 1 root root 848 Jul 27 2017 ant-usb-sticks.rules

Link