Author Topic: Getting started with your Digispark! (Read 35548 times)

digistump · « **Reply #30 on:** December 21, 2012, 10:38:26 am »

Sturgeon:

Things to confirm:
Digispark is selected both as Board and Programmer.

You\'ve run the InstallDriver.exe file in the Windows Driver folder and this brought up a dialog that at the end told you the Digispark Bootloader was ready to use. See the attachment for what this should look like.

You are connecting the Digispark directly to the USB port - after it prompts you to \"Plug in device now...\"

If you are using a cable, try plugging directly in. If you are using a hub, try plugging directly in. If you are plugging directly in try it with a hub if you have one.

The DIgispark likely own\'t show in device manager since it is only active for 5 seconds, but you can try opening device manager and plugging it in while watching to see if it shows up.

The message you are getting about USB Device Not Recognized suggests that the Digispark may be having issues connecting to your computer or your computer recognizing it, this suggests a bad cable, a bad hub, an unusually low USB port voltage, etc - try the suggestions about ports and cables above.

Let me know if any of this helps. Do you have more than one Digispark? If so, try with a couple as there is always the possibly of the rare faulty Digispark.

Thanks!
Erik

LenLarson · « **Reply #31 on:** December 21, 2012, 10:42:55 am »

Ok, I downloaded the IDE on my Mac OSX 10.8.2
After I expand it using the Archive utility I get a 200MB Arduino IDE file, but when I click on it I get this error: “Digispark Ready - Arduino 1.03” is damaged and can’t be opened. You should move it to the Trash.
Any ideas?

digistump · « **Reply #32 on:** December 21, 2012, 10:49:34 am »

LenLarson - I\'d give the download another shot - I\'ll hop over to OS X now and double check that it\'s good.

digistump · « **Reply #33 on:** December 21, 2012, 11:00:11 am »

Len - just switched over to OSX did a fresh download from the link on the wiki, unzipped and it worked. - Please try downloading again and let me know if it works.

Sturgeon · « **Reply #34 on:** December 21, 2012, 11:10:40 am »

Erik:

Things confirmed:
1) Digispark is selected to Board(Tiny Core) and Programmer.
2) InstallDriver.exe installed with no errors.
3) Connect to USB 2.0 port (Windows response \"device not recognized\" ) / Connected to USB keyboard hub (no response from windows) / Connected to USB 3 (no response from windows)
4) I tried a second Digispark and got the same results.

I\'m going to try an older PC with USB 1.0.

Thanks!
Joe

digistump · « **Reply #35 on:** December 21, 2012, 11:22:18 am »

@Joe

Laptop or Desktop?
It works for me on USB 2.0 ports - works on my 3.0 ports too on one computer but not the other, generally incompatibility with hardware has to do with a cheapo, not quite to spec, usb controller - but so far I have only seen that in cheapo hubs (though most cheap hubs work just fine).

If you have a hub I\'d try that, and trying on other machines is certainly a good idea. If we can establish that it works for you on something, then we can take it from there and see if we can\'t get it to work on your main machine.

Thanks,
Erik

digistump · « **Reply #36 on:** December 21, 2012, 11:23:48 am »

I missed that you did try it on a hub -- perhaps my luck with hubs has been that they are either powered or on a very short cord....

Sturgeon · « **Reply #37 on:** December 21, 2012, 12:02:57 pm »

Erik,

The Desktop I\'m using is a Dell XPS 8300 with one or two Intel i7-2600 CPU\'s at 3.40Ghz. All the equipment accessory (keybaord/mouse/hub) is from Dell.

I\'ll keep you posted !!

Thanks,

Joe

Sturgeon · « **Reply #38 on:** December 21, 2012, 02:23:47 pm »

Erik,

Using a Dell OPTIPLEX 745 I got the following errors. Progress!!! Any Clue?

Thanks again,
Joe

LOG

Binary sketch size: 756 bytes (of a 6,010 byte maximum)
Running Digispark Uploader...
Plug in device now...
> Please plug in the device ...
> Press CTRL+C to terminate the program.
> Device is found!
connecting: 20% complete
connecting: 23% complete
connecting: 27% complete
connecting: 30% complete
connecting: 34% complete
connecting: 40% complete
> Device looks like ATtiny85!
> Available space for user application: 6010 bytes
> Suggested sleep time between sending pages: 8ms
> Whole page count: 94
> Erase function sleep duration: 752ms
parsing: 40% complete
parsing: 60% complete
> Erasing the memory ...
erasing: 60% complete
.
.
.
erasing: 79% complete
>> Eep! Connection to device lost during erase! Not to worry
>> This happens on some computers - reconnecting...
>> Reconnected! Continuing upload sequence...
erasing: 80% complete
> Starting to upload ...
writing: 80% complete
.
.
.
writing: 82% complete
>> Abort mission! An error has occured ...
>> Please unplug the device and restart the program.

Bluebie · « **Reply #39 on:** December 21, 2012, 02:28:15 pm »

Do you always get an error exactly like this one, or does it sometimes work and sometimes not? When it fails does it always fail at 82% complete?

Bluebie · « **Reply #40 on:** December 21, 2012, 02:30:25 pm »

Also are you running Windows, Linux, or OS X on your optiplex? What is the CPU speed?

Sturgeon · « **Reply #41 on:** December 21, 2012, 02:49:22 pm »

Hi There,
I\'m running Windows 8 on the Dell OPTIPLEX 745.

Good news, the second Digispark uploads with no issue every time. The first Digispark, uploaded only once after 7 attempts. The errors are always the same. Do I have one bad Digispark?

Joe

Bluebie · « **Reply #42 on:** December 21, 2012, 03:19:36 pm »

Okay, it\'s a voltage conversion problem. This is a fairly common problem with V-USB designs using zenner diodes to limit their voltage levels.

@digistump The nightmare begins?

Sounds like maybe something\'s not soldered on well enough (one of the three resistors, or one of the two zenner diodes connecting to the D+ and D- middle two wires on the usb connector). If they\'re soldered on well and it still doesn\'t work, perhaps one of the resistors or zenner diodes is outside the tolerances required by your usb ports.

I\'ll leave it to @digistump to figure out how to fix this. If you\'re bored and have some little blue or white LEDs laying around you could try connecting them between each of the two middle USB wires and ground on the USB connector (not the headers on the digispark) without any resistors. They\'ll light up and blink a bunch on USB activity and might help keep voltages within spec, but they could just as easily make things even less reliable. V-USB stuff is a pain to get right.

Sturgeon · « **Reply #43 on:** December 21, 2012, 05:38:13 pm »

Hello Bluebie,

I\'m back from dinner. Anyway, the second Digispark has no issues!!! I\'m going to wait for @digistamp before I start hacking at the first unit.

Thanks!!

digistump · « **Reply #44 on:** December 21, 2012, 06:10:55 pm »

@Sturgeon - how about we send you a replacement and a prepaid envelope to send us the faulty one back? Send me an email at ekettenburg at digistump dot com

Since it is the first reported fault I\'d like to check it and make sure that it truly is faulty.

With 40k of them being produced we expect some to be faulty and our factory will replace any we return, not really worth it once we pay postage but we want to make sure the ones being made right now are done right.

@Bluebie is correct that V-USB devices are a bit delicate, but we\'ve made Digisparks with very precise components - 1% resistors, only one brand of zener diode - so we feel they should work on 90%+ of machines and in our experience so far, a properly built one works on every test machine we have. That said, sometimes these components are out of tolerance and the factory only checks 10% of incoming components - so it is entirely possible that a bad component or solder joint caused it. Our test jigs used at the factory check for mistakes but they wouldn\'t necessarily catch something just out of tolerance.

One other questions- did the second one work on the XPS too? If so then I\'d bet good money the first one just has a faulty part on it.