11 February 2021 14:39
Hi - I did a from-scratch setup in a Vmware VM for the first time in a while… with udev rules, group file permissions etc.
for some reason dmesg shows the device come up as usual with ttyACM0
[ 415.330479] hid-generic 0003:03EB:2111.0003: hiddev0,hidraw1: USB HID v1.11 Device [Atmel Corp. EDBG CMSIS-DAP] on usb-0000:02:03.0-1/input0
[ 415.330544] cdc_acm 1-1:1.1: ttyACM0: USB ACM device
but when trying to flash it tries to write to /dev/hidraw1 - which is permission denied (although if you chmod it that device does work)
I’m sure I’m missing something simple on the “setting up” ?
using PORT=/dev/ttyACM0 works but I was sure RIOT had a default that worked without before?
11 February 2021 17:05
Did you configure your
udev rules properly so you have write access to the newly connected device? While you don’t tell which distribution you are using in your VMware setup or what your knowledge level is with Linux, but the
ArchLinux Wiki documents quite well how to do that.
11 February 2021 18:00
my installer adds a file with the usual
KERNEL==“hidraw*”, SUBSYSTEM==“hidraw”, MODE=“0664”, GROUP=“plugdev”
My little script is quite handy for new-comers:
This file has been truncated.
# Installs all you need to start with RIOT-os on Ubuntu
# ubuntu packages, arm compiler and riot-os
# for this reason it will use sudo - to install packages
# it can also download RIOT (into current dir so you may have to move it up to ~/RIOT for an easy life)
# and the ARM compiler will be put in a central location (so you need to set PATH)
# Kirk Martinez June 2020
# ubuntu 20 only has python3 - affects python3-serial and python3-pip
# needs sudo to install packages and config files
sudo apt install python3-serial git build-essential python3-pip
sudo apt install pkg-config autoconf automake libtool libusb-dev libusb-1.0-0-dev libhidapi-dev libftdi-dev libudev-dev
pip3 install pyserial
if [ -e RIOT ] ; then
echo "you already have a RIOT dir here"
echo "getting RIOT-OS from github"
git clone git://github.com/RIOT-OS/RIOT.git
11 February 2021 19:50
Is your user account in the permission group
plugdev? You can check using the
12 February 2021 09:11
yep - dialout and plugdev. So people don’t get caught with this I put it into the installer and a reminder to logout/back in
I’m beginning to think it was a subtle change in behaviour from ubuntu 18 to 20