Date: Mon, 16 Mar 2020 21:43:29 +0100 From: Andrew Stevenson <andrew@ugh.net.au> To: bmelo <bmelo@protonmail.com> Cc: "freebsd-embedded@freebsd.org" <freebsd-embedded@freebsd.org> Subject: Re: STM32 not identified Message-ID: <4A28D043-960F-465F-AC1A-9B6AD839783E@ugh.net.au> In-Reply-To: <bCyCGMfT-ROSVe2TXJJdJeOI3UkecbyDDrz8CTIcXPAoZwyKvYS4ZkgaQxMiXgvT7VNOTARJ0PLmbcvLU_WNxPPd578NDl0ZyZ7h_m8xSb0=@protonmail.com> References: <bCyCGMfT-ROSVe2TXJJdJeOI3UkecbyDDrz8CTIcXPAoZwyKvYS4ZkgaQxMiXgvT7VNOTARJ0PLmbcvLU_WNxPPd578NDl0ZyZ7h_m8xSb0=@protonmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 16. Mar 2020, at 13:23, bmelo via freebsd-embedded = <freebsd-embedded@freebsd.org> wrote: >=20 > Hi, I have a STM32 Nucleo board and installed stlink from ports here. = But all the time I run st-util command I get the message: > WARN usb.c: Couldn't find any ST-Link/V2 devices > The Nucleo creates cuaU0 and ttyU0 in /dev. It seems like a permission = problem, but I have no idea how to fix that. I already tried to edit = /etc/devfs.rules and the problem persists. /dev/cuaU0 is uucp:dialer and = ttyU0 is root:wheel. > Any idea? Are you sure its permission problem? Doesn=E2=80=99t st-util search via = the USB VID/PID? Maybe running in verbose mode might give some idea of = where it's failing. Do you see your device when you rub usbconfig? Do = the VID/PID match whatever st-util is expecting? HTH, Andrew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A28D043-960F-465F-AC1A-9B6AD839783E>