Digistump development board attiny85 non-communicative

For a project I bought three Digistump ATtiny85 development boards. Got some other issues resolved but now two of them won’t connect, ie. no da Donk sound when Windows recognizes a new USB connection. To save plugging/unplugging I got a USB cable with a switch to cycle power to the board when it's upload time. I plugged one directly into the PC's USB port and there's no difference. I don’t believe they’re completely inop. (bricked) since one, which had a blink type program loaded still runs that after the startup delay however I can’t load a sketch to these two devices.

The error message:

> Device search timed out

Failed uploading: uploading error: exit status 1

Some searching revealed that a; this is not unknown for this board and, b; there’s a technique to "unbrick" these processors.

I have the materials on hand to build the high voltage programmer, if needed. Before I do that I’m asking the forum:

  1. for an opinion whether this circuit could / will work on a development board with all its ancillary components in place.
  2. whether just a plain vanilla Arduino as ISP (low voltage programmer) might do the same thing.

In either case I wouldn't be using the USB connections, I'd connect directly to the processor I/O ports.

My board:

A representative schematic of the development board:

Thanks for looking.

I've built that HVP circuit and it works fine with a standalone ATtiny (or in my case, an ATtiny in a ZIF socket on a shield plugged into an Uno with the HVP sketch in it). The only signal I'd have any qualms about in your case is pin 2, PB3, SCI. R3 and D1 are going to aggresively try and keep SCI around 3.6V. With the series 1K resistor between the Uno and the ATtiny you've got a really nice voltage divider going on there. You could try it and see; there's sufficient series resistance that the Uno's output isn't going to be damaged.

If it doesn't work, and especially if this is a one off thing to unbrick it and then use it as normal again, temporarily removing R1 would probably do the trick.

I think it is worth a try.

The currently preferred Arduino boards platform for Digispark support is the excellent TinyCore by MCUdude/Hansibull:

Some documentation on the subject here:

https://github.com/MCUdude/TinyCore/blob/v0.8.0/avr/extras/ATtiny_x5.md#user-content-micronucleus

It wouldn't be pretty but I could probably get R1 out. I don't have the equipment or skills to reinstall it so... If it doesn't work that's the end.

The currently preferred Arduino boards platform for Digispark support is the excellent TinyCore by MCUdude/Hansibull:

I saw that on my earlier thread and I did download it. However I have the Micronucleus working and didn't want to switch horses in the middle of the stream.

I'll give that a go first. My little project then for tomorrow will be making an ISP cable.

That is reasonable. I'm sure you can perform a "Burn Bootloader" operation with whichever Arduino boards platform you are using currently.

@dougp

You may try to program the above ATtiny85 chip uisng Arduino UNO as an ISP programmer to blink the onboard LED.

One thing that puzzles me is that Windows doesn't react at all when these boards are plugged in. There's no USB connect sound and no new device appears, so the ATtiny never seems to enumerate as a USB device.

Given that, is ISP or even HV programming really the next logical step, or does the complete lack of USB enumeration suggest a hardware problem instead?

Edit:
It might also be worth checking with USBDeview from NirSoft. If the board doesn't even appear there when plugged in, that would suggest it never starts USB enumeration, which seems more like a hardware or low-level firmware problem than an upload issue.

I do get a USB connect sound. Nothing changes in WIN11 device manager but the DM display does flash as if it's updating.

Screenshot of USB viewer on my machine (Thanks for the link):

The annunciator goes grey when Digispark board disconnected/powered off.

Infuriatingly, although I haven't got the ISP thing working yet, the test board does now connect to the USB port and it will accept downloads. :confused: :angry:

What is the difference between Upload and Download in the context of Arduino IDE. In the IDE, I see only "Upload" button.

That's useful information. If USBDeview identifies the Digispark bootloader, then the USB interface and bootloader are at least working on that board.

Does this now apply to all three boards?

You're right. Sketches are uploaded  via the IDE. Old habit not completely broken.

It's very curious. Board "A" has not yet stopped connecting. Board "B" and "C" both failed. After connecting "B" to the programmer (NANO) and attempting to upload the blink sketch nothing happened. When "B" was then reconnected direct to USB port it responded and would accept a sketch.
Same thing with "C", after connecting to programmer (with no upload attempt) "C" connected as USB device and accepts sketches.

???

I had the same habit while I had been downloading code into 8085/8086/8051 before meeting Arduino IDE which says "Upload". Arduino Team has enumertaed many many names which are not logical.

Just a thought: these boards seem unreliable. Even if you manage to get them working again, I wouldn't trust them in a real project. They're fine for tinkering, but I'd use different boards for anything important.
At some point, the value of further troubleshooting simply isn't worth the time invested.

Yeah, I'm not impressed. Still, if I go on I'll have two spare boards. :zany_face:

Worst comes to worst I have a Trinket M0 sitting idle.

Fair enough. Nice solution, as long as the learning is still worth the time. :slightly_smiling_face:

I have seen a similar conclusion stated by Adafruit:

https://www.adafruit.com/product/1501#:~:text=Description-,Deprecation%20Warning,-%3A%20The%20Trinket%20bit

Deprecation Warning: The Trinket bit-bang USB technique it uses doesn't work as well as it did in 2014, many modern computers won't work well. So while we still carry the Trinket so that people can maintain some older projects, we no longer recommend it.

https://www.adafruit.com/product/1222#:~:text=Description-,Deprecation%20Warning,-%3A%20The%20Gemma%20bit

Deprecation Warning: The Gemma bit-bang USB technique it uses doesn't work as well as it did in 2014, many modern computers won't work well. So while we still carry the Gemma so that people can maintain some older projects, we no longer recommend it.

These statements are for different products, but those products use the same "bit-banged USB" (V-USB) approach as the Digispark.

I haven't encountered any problems personally while using the Digispark, but I have only used mine for a few quick uploads performed as experiments when supporting users requesting assistance here.