Author Topic: Stuck again - device plugged in, but code not uploaded. (Read 6162 times)

Zak · « **on:** January 01, 2013, 05:08:07 pm »

Hello,
I'm stuck again. Using the simple blink code ( http://digistump.com/wiki/digispark/tutorials/connecting ), the IDE requests for me to put in the device, but the digisparks I have don't work. I have a few digisparks. One isn't recognized at all by windows, and the other comes up as an unknown device. I've tried re-installing the drivers to no avail. Help.
Zak

digistump · « **Reply #1 on:** January 01, 2013, 07:25:30 pm »

Zak - is this issue persisting? Do you have a second machine to test with? This sounds like a driver issues but also could be related to the USB prot/cable/hub/no hub/ etc

Some ideas to try can be found in this thread: http://digistump.com/board/index.php?p=/discussion/85/getting-started-with-your-digispark

Zak · « **Reply #2 on:** January 01, 2013, 07:37:31 pm »

So far, yes. I have two computers available to me (minus a few pi\'s). The first is the windows box, and the second is a linux laptop, but I couldn\'t get the arduino IDE to start. (Some java issue.) On the windows box, I tried connecting to multiple usb hubs, but I still get the same usb issues. I also tried uninstalling and reinstalling the driver, but I still have the same issue.

I just tried a third, out of the box, digispark, and it came up with unknown driver issue. Could I have soldered something to one of them to make it not recognize itself as a usb device on the compuer?

digistump · « **Reply #3 on:** January 01, 2013, 08:17:23 pm »

What have you soldered to them so far? It is certainly possible - when you plug them in there should be nothing except for the headers soldered to them - at least to start with.

Can you by chance post the exact unknown driver issue message you get - or take a screenshot? This is so far the first report of what seems to be an actual drive issue.

Thanks for working through this with us!

Macjbraun · « **Reply #4 on:** January 02, 2013, 03:51:38 pm »

This is what worked for me on a Mac. Use a hub with no other devices plugged into the hub. It would not work if I plugged it in directly, with an extension cable or had a mouse plugged into the hub.

Zak · « **Reply #5 on:** January 02, 2013, 06:37:49 pm »

Hi Digistump & Macjbraun,

Ok... All I soldered was the headers... I just dumped the two sparks that I had with issues, trying again with a clean one...

Ah, it was what Macjbraun was saying... I had a mouse plugged in, which caused the device not to react.

After one partial upload, I was just able to successfully write to one fully... time for some weekend experimenting!

Zak

digistump · « **Reply #6 on:** January 02, 2013, 06:48:25 pm »

Zak - that\'s wonderful you got it to work! I have about 5 things on my hub, one of which is a hub with 3 other things and a mouse, keyboard, and printer - all on a Mac Mini 2011 with windows and OS X - so I wouldn\'t have guessed that solution.

Great tip Macjbraun - thanks!

MichaelMeissner · « **Reply #7 on:** January 02, 2013, 10:27:15 pm »

I wonder if having the mouse plugged into the hub made everything run at USB 1.1 speeds. IIRC, many usb hubs run at the speed of the slowest component plugged in.

Zak · « **Reply #8 on:** January 03, 2013, 11:04:32 am »

Michael - very well could be... It\'s just a generic usb mouse I got with my dell...

digistump - Yes, it is weird... I might just get a dedicated usb hub for it, to see if it makes a difference.

Bluebie · « **Reply #9 on:** January 03, 2013, 02:39:08 pm »

Digisparks are low-speed devices anyway, like a mouse, so it shouldn\'t matter all that much, but I think they are usb 2.0 devices. I haven\'t heard of this slowing to weakest link behaviour on USB before. Wouldn\'t that mean if you plug a mouse in to a mac laptop the webcam would stop working? Usually the webcam, bluetooth, keyboard and trackpad in mac laptops connect via usb through a separate hub (which connects to the root hub)

Digisparks are extremely sensitive to the timing of USB signals though. As they have no crystal, they calibrate their system clock off the USB connection, so a dodgy hub or other devices might be able to interfere with those \'start of frame\' pulses and mess things up? The USB standard specifies that those pulses need to be very accurate, but maybe most other devices don\'t mind so much so some cheap hubs can get away with not doing it right? Or maybe there is some situation where some pulses are skipped?