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

next in thread | previous in thread | raw e-mail | index | archive | help
Here is my devfs.rules:

[devfsrules_common=3D7]
add path 'ad[0-9]\*'=09=09mode 666
add path 'ada[0-9]\*'=09mode 666
add path 'da[0-9]\*'=09=09mode 666
add path 'acd[0-9]\*'=09mode 666
add path 'cd[0-9]\*'=09=09mode 666
add path 'cuaU[0-9]\*'            mode 666
add path 'mmcsd[0-9]\*'=09mode 666
add path 'pass[0-9]\*'=09mode 666
add path 'xpt[0-9]\*'=09mode 666
add path 'ugen[0-9]\*'=09mode 666
add path 'usbctl'=09=09mode 666
add path 'usb/\*'=09=09mode 666
add path 'ttyU[0-9]\*'=09mode 666
add path 'lpt[0-9]\*'=09mode 666
add path 'ulpt[0-9]\*'=09mode 666
add path 'unlpt[0-9]\*'=09mode 666
add path 'fd[0-9]\*'=09=09mode 666
add path 'uscan[0-9]\*'=09mode 666
add path 'video[0-9]\*'=09mode 666
add path 'tuner[0-9]*'  mode 666
add path 'dvb/\*'=09=09mode 666
add path 'cx88*' mode 0660
add path 'iicdev*' mode 0660
add path 'uvisor[0-9]*' mode 0660




Sent from ProtonMail, Swiss-based encrypted email.

=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Original Me=
ssage =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90
On Monday, 16 de March de 2020 =C3=A0s 13:23, Ian Lepore <ian@freebsd.org> =
wrote:

> 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 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):
>
> [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
>
> -- Ian





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?PqPJsTGStXlx_9UIEWwnA7Z0ip3OgWhtZolrYRZz--dY3Wd1n9arptplfRd1LmBxQ6KA92JA7V33I6ZNrmq1oezPjb-Q3uuBZIfIzxbYziQ=>