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

[Bluebie]

Glad you guys are finding it useful!    <3

[XtremeIN]

Hello all,
I have messing around with removing the bootloader for sometime and I can not get it to work.  I have Vista and it took some searching to figure out how to get the needed code in the Command Prompt window (Vista does not allow drag and drop to/in the Command Prompt window). Once I got past that everything seemed to go smooth until I tested my DS. The code run in the Command Prompt seemed to work fine. It tried a couple of times and finally gave me a 100% complete. I downloaded a simple sketch that blinks the internal LED on PIN1.  It does nothing. Yes I unplugged the DS after changing the bootloader. Yes I had a jumper going from PIN 5 to GND. with no luck getting the sketch to work I tried it on a stock DS, works fine.  After a few more hours of trying with no avail I decided to revert the DS back to the original bootloader. SAME SENEARO.... Command Prompt gave a 100% complete and I cannot get the sketch to run.

Please help
Micheal

[Mark]

Michael

Out of interest did you wait 10 seconds after the new bootloader upload, before unplugging.?
Jenna made the comment, and I assume it was for the bootloader to finish internally writing.

Mark

[Bluebie]

Yep you need to give it a few seconds to rewrite the bootloader. Please understand that you are not "removing the bootloader", you are just replacing it with a different version which uses a button or jumper instead of a delay. I don't know why your blink sketches wouldn't be working, but it sounds like you're having a lot of trouble uploading programs to your digispark regardless?

[XtremeIN]

I waited atleast 30 seconds to make sure it had time to rewrite the bootloader. I went back to rewatch the video and I noticed some thing. I inserted a stock DigiSpark then removed it and replaced it with the alt bootloader DS, they both show the same in the Device Manager......
 
Micheal
 
 

[Bluebie]

It's the same bootloader, so it shows up as the same device, it is just configured slightly differently to use a button instead of a timeout. This is the expected behaviour.

[Mark]

Michael
You say you are using Vista.
I wonder if there is a permissions issue.

I haven't had or touched Vista, but is it possible to start the Command Prompt with Administrator rights.?
I'm wondering if its some form of permissions issue.
The fact it comes back with writing and the 100% is puzzling.

Has anyone else running Vista tried the new bootloader.?

Mark

[XtremeIN]

Thanks for the info Jenna.
 
Mike, I tried running the Command Promt in as Admin, same effect......
 
Micheal

[Mark]

Michael.
Answered your PM ... probably not a lot of help to you.

This is a nuisance I know, but can we step through the process, just to (a) be sure, (b) try to isolate the cause (c) help someone in future that might have the same issue?


I'm making the assumption that once you've programmed the DS, you remove the jumper from Pin5 ?
This takes it out of 'bootload mode' to 'run my sketch as soon as I'm powered' mode.


If we can verify the following.
1. Does a normal DS cause the computer to make a noise when its plugged in.?
2. Does the revised DS also make a noise.?
3. Does the revised DS make a noise if the jumper from Pin5 to ground is in.? (means its accepted the new bootloader)
4. Is the Pin5 lead/jumper/wire a good fit in the socket.? (A slight kink will help)
5. Is the slight wear pattern on the USB aligned with the gold pcb tracks.?
6. Is the wear present on all 4 pins.?
7. Can you program sketches into an unmodified DS, without any issues.?
8. When the DS is present, what CommPort is it using.?

A simple Yes/No unless it needs more is fine.


In the meantime I'll ask some questions about Vista, and why it appears to be so different.


Mark

[Bluebie]

Digisparks do not use comm ports. The Serial Port setting in the digispark arduino software is not used by any aspect of the program uploading. The bootloader works via raw USB messages.

[Mark]

Oops true.

I'll edit it.
It's a strange problem.
I would have thought that Vista would have rejected the program and not come up with the 100%, otherwise it should work.

Its likely to be something simple, as I know your bootloader works...

Mark

[XtremeIN]

 OK, so now I have a new issue.....
 
 I tried to change the bootloader using my wifes computer (Windows 7).  Plugged in the DS that I have been trying to get working with the new BL. The computer made the ding sound, but it showed up as an Unknown Device. After several failed attempts to correct the drivers I gave up. I then tried an stock DS. Works fine. USB see its, knows what it is.  I then went on to trying to update the BL on this DS.  Using the drag and drop method I placed the files into the Command Prompt and hit enter. The Command Prompt then said please plug in device. I plugged in the older DS, the computer dinged, said not recognized and did nothing. Removed that DS and placed in a stock DS, it started rewriting the BL. After a few tries it said 100%. While waiting the recommended 10 sec the computed then dinged again and said it was now an unrecognized device.........
 
 Micheal
 

[Mark]

Okay I know this is getting frustrating...

1. On the wife's Laptop did you run the driver  .....\DigiSpark\Digispark - Windows Driver\InstallDriver.exe  before plugging in any DS.?

Any chance you can go through the 7 questions in my post so we can establish a benchmark?

Any time a device is unplugged from a USB, windows knows, and when a device is detected it wants to run to the internet to find a driver .. and it fails because they aren't there in www land, then the 5 sec time disconnects the device.

Now you have 2 DS (in theory) that have a 'no delay' bootloader, can you program either once you insert the wire in Pin5 and plug in.??



mark

[Sergio]

From your post it appears the digisparks only malfunction "after" you download the .hex file.
I would check the .hex bootloader file you have saved from github does not have "garbage" characters or it is truncated. Open it in notepad (not wordpad) and check that the first and last line match the one online. Also, are you using 1.05 or 1.06 bootloader?

[digistump]

It would make sense it would show up as an unknown device unless you are connecting P5 to GND - since it won't run the bootloader anyway - are you connecting P5 to ground when you try to program it?