| 1 |
On 09/28 05:03, Mateusz Lenik wrote: |
| 2 |
> On Thu, Sep 28, 2017 at 05:03:14PM +0200, tuxic@××××××.de wrote: |
| 3 |
> > I have one of these: |
| 4 |
> > |
| 5 |
> > Bus 006 Device 018: ID 16d0:0753 MCS Digistump DigiSpark |
| 6 |
> > |
| 7 |
> > ... snip ... |
| 8 |
> > |
| 9 |
> > SUBSYSTEMS=="usb", ATTRS{idVendor}=="16d0", ATTRS{idProduct}=="0753", MODE:="0666" |
| 10 |
> > KERNEL=="ttyACM*", ATTRS{idVendor}=="16d0", ATTRS{idProduct}=="0753", MODE:="0666", ENV{ID_MM_DEVICE_IGNORE}="1" |
| 11 |
> |
| 12 |
> This udev rule looks fine, it tries to make the device nodes |
| 13 |
> readable/writeable to everyone and makes modemmanager ignore it. |
| 14 |
> |
| 15 |
> My guess would be that you don't have the correct serial port driver |
| 16 |
> built or loaded, so ttyACM nodes are not created at all. |
| 17 |
> |
| 18 |
> Take a look at dmesg contents when the device gets plugged in. |
| 19 |
> |
| 20 |
> -- |
| 21 |
> mlen |
| 22 |
|
| 23 |
|
| 24 |
Hi mlen, |
| 25 |
|
| 26 |
thanks for your help ! :) |
| 27 |
|
| 28 |
The interesting thing is: I have a pololu avr programmer (v20, an |
| 29 |
ISP-programmer it is), which uses also /dev/ttyACM<n>...and that |
| 30 |
one works fine. I plugged it in simultanously to ensure all drivers |
| 31 |
get loaded...and then I plugged in the Digispark...and udec does |
| 32 |
nothing. |
| 33 |
|
| 34 |
Or do I misinterpret here something? |
| 35 |
|
| 36 |
Cheers |
| 37 |
Meino |
Archives