Author Topic: Should a new digispark register as a USB device? (Read 5391 times)

dclaar · « **on:** January 05, 2013, 07:33:20 pm »

Before I started messing with the DigiSpark, I thought I'd plug it in and see if anything recognized it. So far, doesn't seem like it. Maybe this is the wrong way to go about it, but I'm a N00b in the arduino world...

Thanks,
Doug

Windows 7 on a Dell XPS 630:

Problem signature:
P1: x64
P2: USB\VID_16D0&PID_0753&REV_0102

Driver Management concluded the process to install driver NULL Driver for Device Instance ID USB\VID_16D0&PID_0753\6&17B0FF81&0&2 with the following status: 0xe0000203.
Driver Management concluded the process to install driver NULL Driver for Device Instance ID USB\VID_16D0&PID_0753\6&17B0FF81&0&3 with the following status: 0xe0000203.

ubuntu 12.04 (on a samsung NP-N310 laptop):
[ 102.160077] wlan0: no IPv6 routers present
[ 127.324176] usb 1-3: new high-speed USB device number 4 using ehci_hcd
[ 127.458757] hub 1-3:1.0: USB hub found
[ 127.459080] hub 1-3:1.0: 4 ports detected
[ 146.208474] usb 1-3.3: new low-speed USB device number 5 using ehci_hcd
[ 151.128219] usb 1-3.3: USB disconnect, device number 5

Jan 5 17:37:41 kernel: [ 127.324176] usb 1-3: new high-speed USB device number 4 using ehci_hcd
Jan 5 17:37:41 kernel: [ 127.458757] hub 1-3:1.0: USB hub found
Jan 5 17:37:41 kernel: [ 127.459080] hub 1-3:1.0: 4 ports detected
Jan 5 17:38:00 kernel: [ 146.208474] usb 1-3.3: new low-speed USB device number 5 using ehci_hcd
Jan 5 17:38:00 mtp-probe: checking bus 1, device 5: "/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3.3"
Jan 5 17:38:00 mtp-probe: bus: 1, device: 5 was not an MTP device
Jan 5 17:38:05 kernel: [ 151.128219] usb 1-3.3: USB disconnect, device number 5

macbook air on Mountain Lion:
pcscd[]: Non-smartcard device launched pcscd [Vendor: 0X16D0, Product: 0X753]

dclaar · « **Reply #1 on:** January 05, 2013, 07:39:12 pm »

I was actually looking at http://android.serverbox.ch/?p=427, which seemed to indicate that his arduino was recognized out of the box as a tty device, but maybe he forgot a few details, and there\'s setup required, or that\'s a unique characteristic of his device.

I\'m going to go through the setup procedures and see if that helps!

digistump · « **Reply #2 on:** January 05, 2013, 07:46:10 pm »

The setup is a good place to start, then troubleshooting section - then come back here and let us know if you still are having issues with them.

The page you linked to is a very different device, with a very different chip.

Thanks
Erik

dclaar · « **Reply #3 on:** January 05, 2013, 09:30:21 pm »

It works! Cool beans! It is very fussy, though: You have to unplug it, click update, then replug it, or you get:

Assertion failed: res >= 4, file library/micronucleus_lib.c, line 63

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application\'s support team for more information.
> Please plug in the device ...
> Press CTRL+C to terminate the program.