Recent Posts

71

Digispark (Original) Support / Re: Bad CPU type in executable

« Last post by granzeier on November 14, 2019, 03:17:44 am »

Hey Moderators, can someone please delete this person's account - all the spam we are getting is muddying up the board. I have reported a bunch of these spammers, but never gotten a response, nor has the spam been deleted.

If you need another set of eyes to watch over this board, I check it out a couple times a day, and am willing to kill off the spam, and get rid of the spammers.

72

Digispark (Original) Support / Re: Digispark looses program after power cycle

« Last post by nikdob70 on November 13, 2019, 06:52:47 pm »

Bump ... Anyone resolve this? I got a new batch of Digispark boards today doing this.

73

Digispark (Original) Support / Upgrading micronucleus and installing a program all at once

« Last post by twomiletower on November 12, 2019, 04:44:21 pm »

Hi! Bit of an unusual one here: a friend's project requires a micronucleus bootloader that doesn't have the 5-second programming delay at startup.

What we didn't realise is upgrading the bootloader also erases the program memory.

We realised this *after* sealing about a half-dozen Digisparks inside glued enclosures with only a USB cable poking out - no means to connect the reprogramming pin to ground to put the program back on it afterwards.

My question is this: is it possible to simulataneously upgrade the micronucleus bootloader while also writing a compiled program to the chip? It'd save us a lot of time and hassle if we can. My best guess is compiling our program code and somehow merging it with micronucleus-1.11-entry-jumper-pb0-upgrade (the firmware we're using, without the startup delay), and then using micronucleus --upgrade to write it all to the Attiny85 at once. Or something like that.

Quite how we do this I have no idea. Any help would be appreciated (not that we're not aware this is partly our own stupidity, but, hey, life lesson I guess).

74

Digispark (Original) Support / Re: Digispark ATTiny85 won't run after power loss

« Last post by John on November 07, 2019, 01:06:42 pm »

I get the same behavior, except Arduino 1.6.5-r5.  5 boards all exhibit the same behavior.  These do not say "Digispark" on them; just "ATttiny 85".

75

Digispark (Original) Support / Re: Bad CPU type in executable

« Last post by lukasthebird on November 06, 2019, 12:28:36 pm »

I think its the same error as I also encountered and solved here: https://digistump.com/board/index.php/topic,3198.msg14379.html#msg14379

76

Digispark Pro Support / Re: Mac OS X Catalina: 64-bit Support for Arduino IDE

« Last post by lukasthebird on November 06, 2019, 12:27:24 pm »

I played around a bit with the json file and with my custom made it now works.
Just use this one https://github.com/LukasSchulz/arduino-boards-index/blob/master/package_digistump_index.json and reinstall the Digistump AVR package in the boards manager.

77

Digispark (Original) Support / Re: Upgrading firmware on clone (rev 3)

« Last post by rubberduck on November 06, 2019, 06:04:28 am »

You can upload this via the micronucleus executeable: https://github.com/micronucleus/micronucleus/raw/master/upgrade/releases/upgrade-t85_default.hex
./micronucleus --run upgrade-t85_default.hex

Please give some seconds (maximum 30) to finish the upgrade as this is a sketch which is uploaded with the old bootloader and then will be run. It's only task is then to upgrade the bootloader and kill itselves after that.

78

Digispark (Original) Support / Re: Digimouse.h and Digikeyboard.h in same sketch

« Last post by rubberduck on November 06, 2019, 06:00:04 am »

https://github.com/adafruit/Adafruit-Trinket-USB/tree/master/TrinketHidCombo

Should provide what you want to have. Not tested yet by me.

79

Digispark (Original) Support / Re: "Unknown Device", Windows 7

« Last post by brawcore on November 04, 2019, 03:06:13 pm »

2019 and same here :/

80

Digispark (Original) Support / Re: "Unknown Device"

« Last post by brawcore on November 04, 2019, 02:37:41 pm »

same here.
it was working so fine, now is just the 'unknow device'