Author Topic: Bricking stories  (Read 1804 times)

ivoras

  • Newbie
  • *
  • Posts: 1
Bricking stories
« on: May 04, 2016, 01:53:54 pm »
Apparently Digisparks are extremely easy to brick.

Ok, the first one I bricked by choosing the "Pro" in the Arduino IDE when it was not a Pro hardware. Now it does something which looks like it's constantly rebooting: when connected to a Windows machine, Windows would play the "device inserted" sound, wait about a second, then play the "device disconnected" (or is it failed?) sound. Repeated forever. So ok, I'll chalk that to experimenting and to learning experience.

The second one, I modified the plain old Fade example, to run on pin 1, and I modified the fadeAmount var to 10, not really looking at the code. And... it didn't work. Looking at the code, of course there's a reason why: it tests for equality of brigthness to 0 or 255, not for <= 0 and >= 255. But when I tried to upload the changed code... nothing: Windows doesn't play the "device connected" sound when I plug it in, nothing happens in Device Manager and of course, the boot loader cannot find it. Interestingly, it looks like the program starts running immediately, without the 5 second pause (it lights up the LED, just not in the way I wanted), which seems like the USB bootloader got removed??? On a third device I can program stuff in repeatedly, so it's not something I'm doing differently. Could it have been from writing invalid values (< 0, > 255) with analogWrite to pin 1?

Is there something I can do to recover either of the devices?
« Last Edit: May 04, 2016, 02:09:18 pm by ivoras »