Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 16 Mar 2020 14:02:15 -0600
From:      Ian Lepore <ian@freebsd.org>
To:        bmelo <bmelo@protonmail.com>
Cc:        "freebsd-embedded@freebsd.org" <freebsd-embedded@freebsd.org>
Subject:   Re: STM32 not identified
Message-ID:  <c0026f4471f409303b6cac0baa577cf49171c669.camel@freebsd.org>
In-Reply-To: <PqPJsTGStXlx_9UIEWwnA7Z0ip3OgWhtZolrYRZz--dY3Wd1n9arptplfRd1LmBxQ6KA92JA7V33I6ZNrmq1oezPjb-Q3uuBZIfIzxbYziQ=@protonmail.com>
References:  <bCyCGMfT-ROSVe2TXJJdJeOI3UkecbyDDrz8CTIcXPAoZwyKvYS4ZkgaQxMiXgvT7VNOTARJ0PLmbcvLU_WNxPPd578NDl0ZyZ7h_m8xSb0=@protonmail.com> <2e1b00c4213037f308417c902291e0a88c06674b.camel@freebsd.org> <PqPJsTGStXlx_9UIEWwnA7Z0ip3OgWhtZolrYRZz--dY3Wd1n9arptplfRd1LmBxQ6KA92JA7V33I6ZNrmq1oezPjb-Q3uuBZIfIzxbYziQ=@protonmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 2020-03-16 at 16:46 +0000, bmelo wrote:
> Here is my devfs.rules:
>=20
> [devfsrules_common=3D7]
> add path 'ad[0-9]\*'		mode 666
> add path 'ada[0-9]\*'	mode 666
> add path 'da[0-9]\*'		mode 666
> add path 'acd[0-9]\*'	mode 666
> add path 'cd[0-9]\*'		mode 666
> add path 'cuaU[0-9]\*'            mode 666
> add path 'mmcsd[0-9]\*'	mode 666
> add path 'pass[0-9]\*'	mode 666
> add path 'xpt[0-9]\*'	mode 666
> add path 'ugen[0-9]\*'	mode 666
> add path 'usbctl'		mode 666
> add path 'usb/\*'		mode 666
> add path 'ttyU[0-9]\*'	mode 666
> add path 'lpt[0-9]\*'	mode 666
> add path 'ulpt[0-9]\*'	mode 666
> add path 'unlpt[0-9]\*'	mode 666
> add path 'fd[0-9]\*'		mode 666
> add path 'uscan[0-9]\*'	mode 666
> add path 'video[0-9]\*'	mode 666
> add path 'tuner[0-9]*'  mode 666
> add path 'dvb/\*'		mode 666
> add path 'cx88*' mode 0660
> add path 'iicdev*' mode 0660
> add path 'uvisor[0-9]*' mode 0660
>=20

I suspect the escaped wildcards are causing a problem, try using
"cuaU*" instead of "cuaU[0-9]\*" (and likewise for all the rules, I
don't think there is any device that puts a literal * in the devfs
name).

-- Ian



>=20
>=20
>=20
> Sent from ProtonMail, Swiss-based encrypted email.
>=20
> =1B$B!>!>!>!>!>!>!>=1B(B Original Message =1B$B!>!>!>!>!>!>!>=1B(B
> On Monday, 16 de March de 2020 s 13:23, Ian Lepore <ian@freebsd.org>
> wrote:
>=20
> > On Mon, 2020-03-16 at 12:23 +0000, bmelo via freebsd-embedded
> > 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?
> >=20
> > You didn't saywhat 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):
> >=20
> > [localrules=3D10]
> > 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
> >=20
> > -- Ian
>=20
>=20
>=20




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c0026f4471f409303b6cac0baa577cf49171c669.camel>