Is there any way to remove the 5 seconds programming delay at powerup ?

[tom-englert]

This seems to be exactly what I need - however all the links are outdated.
Can someone help me to find the latest hex files that remove the 5sec delay?

[tom-englert]

I think I figured out the file locations by my own:
https://github.com/embedded-creations/micronucleus-t85/tree/master/upgrade/releases
and
https://github.com/micronucleus/micronucleus/tree/master/commandline/builds/Windows

But now I have another problem:
- I can change the bootloader, that works fine
- I can upload my program with Arduino, works fine, too
- After uploading, my program starts immediately, and works fine
- But after restarting my digispark nothing happens, my program does not start.

I have tried all boot loaders, with and without delay, but none of them seem to work

@bluebie any idea what I did wrong?

[tom-englert]

Finally I found the working version with jumper at PB0:
https://github.com/micronucleus/micronucleus/tree/v1.11/upgrade/releases
micronucleus-1.11-entry-jumper-pb0-upgrade.hex

[PeterV]

I can't get this to work. Tried all firmwares from this:
https://github.com/micronucleus/micronucleus/tree/v1.11/upgrade/releases

The micronucleus.exe displays
writing: 100% complete
>> Micronucleus done. Thank you!

I waited minutes before disconnecting, but it looks like just the same firmware all over again.
It doesn't matter if I burn one with jumper or just a normal. After disconnecting and connecting it boots into development mode and doesn't run the app.

When I use arduino to upload a program, it uploads fine and the program runs fine until I disconnect, and it never runs again.

Any way to reset my firmware?
I'm really desperate.

[yoh-there2]

Peter, sorry, a bit late to reply but you probably forgot to add the --run option to the command line. Been there, done that.

[Grezzo]

Sorry to resurrect and old thread, but I think this is the right place to post...

I tried updating the firmware to micronucleus-1.06-jumper-v2-upgrade.hex and it appeared to work, but I wasn't able to program it using arduino IDE, even if I connected P5 to GND as I plugged it in.

I then updated to micronucleus-1.06-upgrade.hex, and was able to program it using the arduino IDE.

I then tried switching back and forth a few times, and now it doesn't work at all. I can't even change the firmware any more. As soon as I plug it in, Windows says that it doesn't recognise it, regardless of whether I have P5 connected to GND as I plug it in (which looks like it's skipping the bootloader - right?)

Does it sound like I've buggered the firmware upload somehow, or does it sound like a hardware failure? Am I shorting the right pins? Do I need to try to use an arduino to update it using ISP mode?

Thanks in advance for any help

[Grezzo]

I think it's probably beyond my current ability to fix this because the attiny is soldered to the board and appears to no longer have a working micronucleus on it.

Oh well, at least they are cheap.

I've ordered a replacement, but I would like to upgrade the firmware on the new one to remove the 5 second delay, so I would like to know what is likely to have gone wrong with this one, so I can try to avoid it in future.

[smartynov]

Sorry to resurrect and old thread, but I think this is the right place to post...

I tried updating the firmware to micronucleus-1.06-jumper-v2-upgrade.hex and it appeared to work, but I wasn't able to program it using arduino IDE, even if I connected P5 to GND as I plugged it in.

I'm not sure about v1.06, but I micronucleus-1.11-entry-jumper-pb0-upgrade.hex requires P0 to be connected to the ground for programming, not P5. I tried it on my and it works fine.

Make sure you first connect P0 to GND, then start uploading from IDE, and then connect digispark to USB. Make sure you have a good contact between P0 and GND. If uploading of program fails (it fails sometimes), just try once more.

[DeuxVis]

FYI that thread explains how to get a recent micronucleus firmware with the jumper programming scheme on your digispark : http://digistump.com/board/index.php/topic,1868.msg2555.html

[JS7777]

Hello,

got this message when uploading micronucleus-1.06-jumper-v2.hex with micronucleus.exe :

Program file is 1838 bytes too big for the bootloader!

i don't understand, anyone ?

Regards

[JS7777]

Got it fix because i took the wrong .hex, it should be micronucleus-1.06-jumper-v2-upgrade.hex and not micronucleus-1.06-jumper-v2.hex.

But as soon as I plug it in with pin5 to ground, Windows says that it doesn't recognise it. if i don't connect p5 it goes to program mode. So it's all messed up.

micronucleus-1.11-entry-jumper-pb0-upgrade.hex works fine.

[Fardenco]

For me the easiest way is either to use the modified bootloader that wait for programming only if an input is grounded (you can find it previously on this thread), or if you need to free memory by removing the bootloader, just reset the hv fuses and use a usbasp with a soic8 clip like this one

to come directly around the chip to flash it.

[JS7777]

Thanks

I'm finding the source code for micronucleus-1.11-entry-jumper-pb0-upgrade.hex

Make file etc...

[nobsy]

This does not work on my Mac, nor on Window10.
Any suggestions welcome.

[Rimbaldo]

I know it’s an old topic, but would this changing bootloader method work on the Digispark Pro, so it could boot without waiting 5 seconds? Do they share the same bootloader? If not, is there an workaround to the Digispark Pro, to allow it to boot without waiting those 5 seconds?

Thanks!