Windows 7 (64bit) standlone teensy loader stalls during upload sometimes?

Status
Not open for further replies.
J

JKIM

Active member
Hey all,

I have a product that uses the teensy 3.1 bootloader chip on a custom board. My customers are instructed to download the teensy loader app when it is necessary to upgrade the product.

I have had quite a few customers running into an issue when performing an upgrade on Windows 7 (64bit, SP1), the loader starts, but then fails at about halfway through the process (57% to be exact using my hex file).

I am using the following code, triggered by a button combination on the product to start the bootloader:
// delay is required (for some reason?))
delay(160);
_reboot_Teensyduino_();

Luckily I have the reset button accessible to the customer so they can force a bootload, which then completes successfully.

I am a Mac user, and have used the reboot function probably a few thousand times without any problems ever on Mac OS X and a Windows 8 Surface tablet, so it seems isolated to Windows 7 users.

Has anyone else run into this?
 
I've never seen this happen with Teensy 3.1 boards.

Can you get the 57% stall if you upload your code onto a PJRC-made Teensy 3.1 board?
 
PaulStoffregen said:
I've never seen this happen with Teensy 3.1 boards.

Can you get the 57% stall if you upload your code onto a PJRC-made Teensy 3.1 board?
Click to expand...

Thanks Paul,

I need to see if I can actually recreate the issue using my board... I don't have immediate access to a Win 7 machine.
If I can find a Win7 box I hope to gather more information and try it on a PJRC Teensy also

Is there any difference between using the reboot function and the hardware reset button to kick in the bootloader?
 
OK, I created a Win7 64 bit VM for testing and it works every time...
In the meantime I had a few more customers get the same failure on Win7, so I will try and get a physical Win7 box built.
The VM USB layer may be masking the problem.
 
I am still getting quite a few user reports around this error.
I think it may be related to the fact that the user is using the loader for the first time, and using a key combo to start the bootloader (using _reboot_Teensyduino_(); not the hardware reset button).

Could it be that the loader fails because windows is looking to install a driver during the first time Teensy is connecting? Then the download fails, and the user is forced to use the reset button to kick off the updater a second time, and it seems to work after that point.
 
Last edited:
Status
Not open for further replies.
Back
Top