Unable to see Digispark on USB bus

[lrvick]

So I can not seem to get my arch linux machine to see the digispark on the usb bus at all.... does not show up on lsusb or in /dev/tty* any ideas?

dmesg output:

[ 8997.399170] usb 3-1: new low-speed USB device number 60 using ohci_hcd
[ 8997.565852] usb 3-1: device descriptor read/64, error -62
[ 8998.239232] usb 3-1: device not accepting address 60, error -62
[ 8998.399181] usb 3-1: new low-speed USB device number 61 using ohci_hcd
[ 8998.565949] usb 3-1: device descriptor read/64, error -62
[ 8999.239260] usb 3-1: device not accepting address 61, error -62
[ 8999.399168] usb 3-1: new low-speed USB device number 62 using ohci_hcd
[ 8999.805892] usb 3-1: device not accepting address 62, error -62
[ 8999.965950] usb 3-1: new low-speed USB device number 63 using ohci_hcd
[ 9002.396042] usb 3-1: USB disconnect, device number 63
[ 9086.285941] usb 3-1: new low-speed USB device number 64 using ohci_hcd
[ 9086.855850] usb 3-1: device not accepting address 64, error -62
[ 9087.015987] usb 3-1: new low-speed USB device number 65 using ohci_hcd
[ 9087.585850] usb 3-1: device not accepting address 65, error -62
[ 9087.745828] usb 3-1: new low-speed USB device number 66 using ohci_hcd
[ 9091.142075] usb 3-1: USB disconnect, device number 66
[ 9172.645870] usb 3-1: new low-speed USB device number 67 using ohci_hcd
[ 9172.812553] usb 3-1: device descriptor read/64, error -62
[ 9173.082501] usb 3-1: device descriptor read/64, error -62
[ 9173.345861] usb 3-1: new low-speed USB device number 68 using ohci_hcd
[ 9173.512551] usb 3-1: device descriptor read/64, error -62
[ 9177.489221] usb 3-1: USB disconnect, device number 68

[Bluebie]

Sounds like electrical errors - tried different usb ports, through hubs, that sort of thing?

[digistump]

Irvick - I can\'t say I\'m familiar with arch linux at all - but I know sometimes this can be an issue with lsusb on linux

Hardware wise - like Bluebie said - are you plugging directly into a usb port? try it directly into a port, and try it in a hub if you have one.

If you have a second machine or one running windows or OS X - please try that as well, then we can establish if it is hardware or software.

In addition can you try the other Digisparks you got - to make sure it isn\'t a faulty unit?

Thanks,
Erik

[lrvick]

Tried multiple units. It actually seems to write if I unplug it and plug it back in a couple times when micronucleus is waiting. Little finicky but seems to be working now.

I may take a multimeter to my usb ports or something...

[digistump]

Irvick - sounds like either it is on the verge of not cooperating electrically with the machine OR the timing isn\'t matching up quite right with your linux. If you have a second machine, it\'d be great if you can try that (linux or not - but it\'d be great if it was running the same distro) and if you have back and front usb ports (on a tower) try the back ones.

Glad to hear it is at least working though!

[EMk]

Hi, I'm getting the same output on my Unbuntu 13.04 box.


I have a digiSpark + LCD shield and have downloaded the DigiUSB2LCD sketch from a Win7 64bit box.


Send/Receive on ubuntu is reporting back with "no digispark found".


Any tips?


Thanks in advance.

[Bluebie]

Have you installed the digiusb driver thing on ubuntu? digiusb on linux generally requires some weird text files be installed to give permission for regular users to access the device. If this is the problem, send and receive should work fine if you call them with sudo!

[EMk]

Hey Bluebie,


I followed the directions from the wiki, for Ubuntu, I downloaded the tar file and copied the udev rule file to /etc/udev/rules.d and also the alternate locate(just in case).  That was my understanding of the installation part.


Were there any additional steps?  The rest seemed to involve permissionsing to get the Digi-Arduino IDE to work so I didn't follow them.


Thanks in advance

[Bluebie]

I think that's all you need to do. Did you try with sudo to see if that works? One easy way to find out if it's a permissions problem.

[EMk]

Hey Bluebie,


I copied the udev commands to /etc/udev/rules.d and /lib/udev/rules.d via sudo and they have root permissions.


reading the udev rules, it looks like I should have /dev/ttyACM* device(s) when digiSparks are properly recognized.  I modified the send.cpp file to list through all the USB devices instead of just searching for DigiSpark vendor and product Ids.. and sure enough, DigiSpark ones are not listed by the system.

[Bluebie]

No what I mean is did you try running the digistump-provided send, recieve, or monitor apps with sudo? If you run those with root it bypasses all the usb permissions and gets direct access. If they work with root, we know it's a permissions problem - if they do not, it will be a hardware problem most likely

[EMk]

On my Ubuntu 13.04 64 LTS version, I can't get either the 32 or the 64 binaries included from the tar to run - they come back with


-bash: ./send: No such file or directory


however, I can compile from source that those run.  And running that in sudo mode still returns with "No DigiSpark Found".




I also installed libusb-compat-0.1.5 from source, have libusb-1.0-0/libusb-1.0-0-dev are installed along with libusb-0.1-4 via apt-get.


... I think my issue is that the OS fails to recognize the DigiUSB client on the DigiSpark or something.  I mean, when I plug it in, I get a loop of



device descriptor read/64, error -62

device descriptor read/64, error -62

device descriptor read/64, error -62

device not accepting address 64, error -62
device not accepting address 64, error -62
[size=78%]unable to enumerate USB device on port 2[/size]

[size=78%]Hmm.  Any tips/suggestions would be greatly appreciated.[/size]

[digistump]

1 - are you testing with the "fried" Digispark - if so, you won't get very far if it is in fact damaged.


2 - If you are using a known working one then have you tried programming it from this linux box - that might be a good start - trying to use micronucleus/the Digispark Arduino software to program it from that machine and see if that works first.


3 - Try a extension cable and/or hub - as well as removing other usb devices and trying different ports

[EMk]

Hey digistump,


1 - I've put the "fried" digispark aside -will be checking for shorts(like you described) over the weekend when I have more time.


2 - good point, I'll put some time aside this weekend to try that, thanks


3 - I have an extension cable, made no difference.  But I don't have an external, powered USB hub to test yet, no.

[Bluebie]

I saw errors like those when I connected a digispark to a raspberry pi through a usb 3.0 hub. Connecting directly to the pi's usb 2.0 ports fixed it. Playing with hubs might help. It sounds like the usb connection is glitching out a bit.