| 1 |
Hi, |
| 2 |
|
| 3 |
may bet this is part of the theory about the relationship |
| 4 |
between the forest and the trees...I am trying this already |
| 5 |
for a longer time. |
| 6 |
|
| 7 |
I have one of these: |
| 8 |
|
| 9 |
|
| 10 |
|
| 11 |
When plugged in, lsusb reports those as: |
| 12 |
Bus 006 Device 018: ID 16d0:0753 MCS Digistump DigiSpark |
| 13 |
|
| 14 |
and in the verbose form: |
| 15 |
Bus 006 Device 018: ID 16d0:0753 MCS Digistump DigiSpark |
| 16 |
Device Descriptor: |
| 17 |
bLength 18 |
| 18 |
bDescriptorType 1 |
| 19 |
bcdUSB 1.10 |
| 20 |
bDeviceClass 255 Vendor Specific Class |
| 21 |
bDeviceSubClass 0 |
| 22 |
bDeviceProtocol 0 |
| 23 |
bMaxPacketSize0 8 |
| 24 |
idVendor 0x16d0 MCS |
| 25 |
idProduct 0x0753 Digistump DigiSpark |
| 26 |
bcdDevice 1.06 |
| 27 |
iManufacturer 0 |
| 28 |
iProduct 0 |
| 29 |
iSerial 0 |
| 30 |
bNumConfigurations 1 |
| 31 |
Configuration Descriptor: |
| 32 |
bLength 9 |
| 33 |
bDescriptorType 2 |
| 34 |
wTotalLength 18 |
| 35 |
bNumInterfaces 1 |
| 36 |
bConfigurationValue 1 |
| 37 |
iConfiguration 0 |
| 38 |
bmAttributes 0x80 |
| 39 |
(Bus Powered) |
| 40 |
MaxPower 100mA |
| 41 |
Interface Descriptor: |
| 42 |
bLength 9 |
| 43 |
bDescriptorType 4 |
| 44 |
bInterfaceNumber 0 |
| 45 |
bAlternateSetting 0 |
| 46 |
bNumEndpoints 0 |
| 47 |
bInterfaceClass 0 |
| 48 |
bInterfaceSubClass 0 |
| 49 |
bInterfaceProtocol 0 |
| 50 |
iInterface 0 |
| 51 |
|
| 52 |
On the web site of digistump there is listed the following udev-rule, |
| 53 |
which I copy-pasted into |
| 54 |
ls -l /etc/udev/rules.d/49-micronucleus.rules |
| 55 |
-rw-r--r-- 1 root root 809 2017-09-28 16:23 /etc/udev/rules.d/49-micronucleus.rules |
| 56 |
|
| 57 |
the contents of that rule is: |
| 58 |
|
| 59 |
# UDEV Rules for Micronucleus boards including the Digispark. |
| 60 |
# This file must be placed at: |
| 61 |
# |
| 62 |
# /etc/udev/rules.d/49-micronucleus.rules (preferred location) |
| 63 |
# or |
| 64 |
# /lib/udev/rules.d/49-micronucleus.rules (req'd on some broken systems) |
| 65 |
# |
| 66 |
# After this file is copied, physically unplug and reconnect the board. |
| 67 |
# |
| 68 |
SUBSYSTEMS=="usb", ATTRS{idVendor}=="16d0", ATTRS{idProduct}=="0753", MODE:="0666" |
| 69 |
KERNEL=="ttyACM*", ATTRS{idVendor}=="16d0", ATTRS{idProduct}=="0753", MODE:="0666", ENV{ID_MM_DEVICE_IGNORE}="1" |
| 70 |
# |
| 71 |
# If you share your linux system with other users, or just don't like the |
| 72 |
# idea of write permission for everybody, you can replace MODE:="0666" with |
| 73 |
# OWNER:="yourusername" to create the device owned by you, or with |
| 74 |
# GROUP:="somegroupname" and mange access using standard unix groups. |
| 75 |
# |
| 76 |
|
| 77 |
After inserting that rule I did a |
| 78 |
udevadm control --reload-rules |
| 79 |
as root and inserted the Digispark. |
| 80 |
|
| 81 |
As listed above, lsusb could list the Digispark...but udev ignores it. |
| 82 |
I can find the device under /dev/bus/...., though. |
| 83 |
But there is no device created by udev directly in /dev. |
| 84 |
|
| 85 |
Since the Arduino-IDE needs any port to send the firmware to I am |
| 86 |
currentlu out of business. |
| 87 |
|
| 88 |
I can see the trees...but where is the forest? |
| 89 |
|
| 90 |
Thanks a lot for any enlightment in advance! |
| 91 |
Cheers |
| 92 |
Meino |
Archives