Date: Mon, 16 Mar 2020 10:23:08 -0600 From: Ian Lepore <ian@freebsd.org> To: bmelo <bmelo@protonmail.com>, "freebsd-embedded@freebsd.org" <freebsd-embedded@freebsd.org> Subject: Re: STM32 not identified Message-ID: <2e1b00c4213037f308417c902291e0a88c06674b.camel@freebsd.org> 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 Mon, 2020-03-16 at 12:23 +0000, bmelo via freebsd-embedded wrote: > 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? > > You didn't say *what* you tried with devfs.rules. This is what I use (because I am the only user of this machine, so security is not a problem; these might not be good for a shared machine): [localrules=10] add path "ttyU*" mode 0666 add path "cuaU*" mode 0666 add path "ugen*" mode 0666 add path "usb/*" mode 0666 add path "usb" mode 0755 -- Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2e1b00c4213037f308417c902291e0a88c06674b.camel>