Recent Posts

Pages: [1] 2 3 ... 10

@DigiStump or DigiCDC Developer(s): Can you please help with some support here?  My DigiSpark project is stuck on this issue.

If I am posting in the wrong forum or website, or if I am asking for help from the wrong people, please point me in the right direction.  I need help with this, as I do not know anything about USB or CDC protocol.


So I did a little more digging into the problems I am having with the DigiCDC "Echo" example.

When I, instead, tried the DigiKeyboard example (using the HID protocol), I got the same compiler error about usbdrvasm.S, but the compile completed and the program "uploaded" into the DigiSpark okay (using Micronucleus bootloader), and I got the keyboard messages show up in my Arduino editor window (which I still had opened and which still had focus when the program started running on the DigiSpark).  So that example works just fine (despite the compiler error).

However, my DigiSpark project needs BIDIRECTIONAL serial protocol, as it needs to respond to user inputs from a terminal emulator (or something like the Arduino IDE Serial Monitor window), as well as providing outputs and statuses to the user.

So when I repeated the test with the "Echo" example using the DigiCDC library, I got the compiler error again, and the compilation still completed and uploaded.  But this time I got the Windows USB error.  In the Windows Device manager, the error said something about an invalid device configuration descriptor.  (I forget the exact message, and I do not have the DigiSpark board with me at the moment to try it again; I did all of this testing yesterday.)

I searched around some of the forums and found that others have run into this problem for the past couple of years or so (apparently since Windows 8 or 8.1), but I have not seen posted anywhere, any solution or instruction on how to fix it.

Some specific questions:
  • Is there some change I can make to the DigiCDC library source or the "Echo" example source, to fix the device configuration?  For example, can something be changed in the DigiCDC library's usbconfig.h file, to get rid of the Windows "invalid configuration" error?
  • Is there some other driver that I must install in Windows 10 to get CDC protocol to work?
  • Is there something else that needs to be done with the DigiCDC library source, the "Echo" example source, or Windows 10, in order to get the DigiSpark to communicate over USB using CDC protocol?

Please help me here; I need  a solution to this issue to continue with my project, and I have run out of things to try.  I specifically purchased some DigiSpark boards so that I could do serial communication over the USB port, but it seems I should not have done so.  I really hate the thought of having to switch to using a ATtiny85 with a software serial driver and a USB-to-serial dongle. :(

BTW, it seems that the other issue that I posted about earlier with the compiler error is not as important, since the programs will still finish compiling (and the HID examples, at least, still seem to work, although I cannot use that), but if there is a fix for the compiler error, as well, I would like to know about it.

Thanks and best regards,
Digispark (Original) Support / Usage of DigiSpark pins PB1, PB3 and PB4?
« Last post by DuinoSoar on July 18, 2019, 02:14:08 pm »
Hello, again.

For some of my potential DigiSpark projects, I am wondering about using pins PB1, PB3 and PB4 for functions where the on-board LED (for PB1), or the USB port (for PB3 and PB4), are not required for the application.

With the various resistors, Zeners, and the LED hanging off of these pins (and, don't forget about that 1.5 K pull-up on PB3 near the USB connector!), what special precautions (if any) need to be considered when using these pins in any of their available functions?

For example (and without limiting the discussion to these), in reference to the "official DigiSpark schematic" at [PDF]:
  • How would the USB components (R1, R2, R3, D1 and D2) affect using PB3 or PB4 in the various digital or analogue modes?
  • Could PB3 even be used as an analogue input, given the R3 pull-up (1.5K)?
  • What about trying to use PB3 as digital input WITHOUT pull-up?  Is that even possible?
  • How would the LED and the R5 "pull-down" affect the use of PB1?
Is there a web page or document somewhere that describes these issues?

Oh, and while I am at it, is diode D3 (connected between the USB +5V pin and the board's +5V Vcc "rail") being used in some kind of special mode, or is that an error in the schematic (i.e. it looks backward)?  And if it is an error, why has this "official schematic" never been corrected?

Thanks and best regards,

While compiling ("Verifying") the DigiCDC "Echo" example, I got the error (replaced the base part of the file path with "..."):

Error while detecting libraries included by ...\AppData\Local\Arduino15\packages\digistump\hardware\avr\1.6.7\libraries\DigisparkCDC\usbdrvasm.S

Is there something I need to do to fix the above error?

In spite of this error, the compilation seemed to complete, anyway, and reported the amount of space used/remaining, etc.  So I tried "uploading", the program to the DigiSpark, and when it started running, Windows 10 reported a USB device error:

USB device not recognized The last USB device you connected to this computer malfunctioned, and Windows does not recognize it.

I tried unplugging and re-plugging DigiSpark from/to USB and, after the 5-second bootloader timeout, got the same error.  I already installed the DigiStump drivers in Windows 10.  Is there another Windows driver that I must install for DigiCDC?

Also, perhaps I missed it, but I did not see anywhere, how a terminal emulator (or, for that matter, Arduino IDE Serial Monitor) should be set up to communicate serially with the DigiSpark over USB/CDC?  What baud rate and bit protocol should be used on the PC side?  (I understand that the DigiSpark CDC library does not need a baud rate, but I am asking about the PC side setup.)

Is there a more detailed reference or user documentation somewhere for DigiCDC, including a list of all API calls, etc., and how to set up the serial communication on "the other side" (i.e. the device or terminal with which DigiCDC is communicating)?

I would really like to get this working, as i have a project in mind to use it.

[Just edited the above.  I just today noticed the "Modify" button near the top of my posts, so I fixed this one and deleted the other two "replies" that I posted yesterday.]

Thanks and best regards,
Digispark (Original) Support / Re: Digispark attiny85 board can´t LOW PB pins
« Last post by granzeier on July 16, 2019, 12:12:29 pm »
Did you configure the pin as an output with PinMode (
If the pin is configured as an input, when you try to write a low, it will disable the internal pull-up resistor, and you will see a float.
Digispark (Original) Support / Digispark attiny85 board can´t LOW PB pins
« Last post by smascare on July 16, 2019, 04:28:57 am »
Hello All Community!

I´m powering digispark attiny85 with 9V in the Vin and Gnd pins.

When programming any pin to set to LOW in the OUTPUT, i verify high voltage in that pin (about + 3V).

When i use digitalWrite(2, LOW) not obtain a Low voltage on pin 2.

What is wrong?
Official Announcements / Re: ChibiOS on Digispark Pro
« Last post by mena on July 15, 2019, 09:57:46 pm »
Thank you very much Very useful >>>>ดาวน์โหลด slotxo
Oak Support / Can't configure Wi-Fi after "restoring your oak to factory setting"
« Last post by jirapon on July 15, 2019, 02:36:13 am »
I don't know if the following is the cause of my issue. I cannot store my wifi settings on my oak. I is perpetually blinking 3 burst led then pause.

So I finally got myself a uart and got the latest firmware on my oak successful. I've been following the instructions from: However I have a problem. The following text is written on that page:

"This will not restore an Oak that has had its Particle Config overwritten at 0x100000 and 0x201000 - a device where that has occured can be partially restored by this method but then will need its device id set via serial, and you'll need to have recorded it previously. Then connect at 115200 baud and send set\n40\n{"device-id":"123456789012345678901234"}\n where 123456789012345678901234 is replaced by your device-id. You can also send a raw POST to with the same JSON while connected to the AP of the Oak"

I do know my device-id however the rest of that text didn't make much sense to me. How do I: "Then connect at 115200 baud and send set\n40\n{"device-id":"my device id"}\n"

And then: "You can also send a raw POST to with the same JSON while connected to the AP of the Oak""

Any assistance would be greatly appreciated.

Oak Support / Re: Oak Setup broken?
« Last post by yoyo4456 on July 14, 2019, 08:26:51 pm »

Online slots, play on mobile
Easy to play, earn real money
Win Jackpot all the time
apply at : slotxo
Digispark (Original) Support / Digispark Not Appearing in Win10-Dev
« Last post by dxmaster on July 14, 2019, 06:57:25 am »
So, I'm using the insider build of windows 10 on one of my laptops and when I plug in my digispark windows isnt even acknowledging the fact that something was plugged in. I tried multiple USB ports both direct off the computer and on hubs and none of them are showing the device appear even for a split second in the device manager. Also, the driver installation states that my version of windows is not supported. It seems work work just fine on my Surface Pro.

Any suggestions on what might be causing this? Is there something where this was blocked entirely in the newest windows insider builds?
Pages: [1] 2 3 ... 10