Not able to Program Any file.

Status
Not open for further replies.

RCAFrules

Member
Hello All

I just got my first Teensy 3.1 and I am am unable to program it with any file. I tried getting help fround my supplier but they directed me here.
My configuration is as follows:
Windows 8.1, Arduino 1.6.1 with teensyduino 1.21

It appears that the halfkay boot loader will not start, when I push the reset button I hear my computer make a noise as thou a new device was detected but the blinking continues. When I try to load the "HelloSerialMonitor" program provided with the teensyduino I get the following message at the bottom half of the Ardino software
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
Opening Teensy Loader...
Teensy did not respond to a USB-based request to automatically reboot.

Please press the PROGRAM MODE BUTTON on your Teensy to upload your sketch.
//////////////////////////////////////////

When I press the reset nothing happens , still just that blinking light.


Log file and program file attached.
 

Attachments

  • log.txt
    4.5 KB · Views: 215
  • HelloSerialMonitor.txt
    730 bytes · Views: 160
Compiled and worked on my Windows & Teensy 3.1. Do you have another serial terminal program open? Maybe unplug the 3.1 and re-plug and check the connected port.

I'm thinking something is blocking TeensyDuino from accessing the 3.1 properly. Close TeensyDuino and the IDE and start fresh. Looking at the menu / Tools / Port you should see just the COM# port your teensy is on and should be able to open the monitor. Then upload. If no response then push the Teensy button and check the verbose info output on TeensyDuino again.
 
Thanks for the quick response. I am not able to load any program, pushing the reset never loads the halfway boot loader, the light continues to flash. I did try it on a different PA with Vista to no anvail. I also tried connectin the Teensy to powered hub that was NOT connected to a PC so as to provide only power to the Teensy and I was still unable to invoke the boot loader, blink program continues to run .
 
This may be a question for Paul or others to see but ...

If running the blink sketch pressing the button should stop it - as I think you are expecting - when the Bootloader starts up.

If there is a good USB connect - then the PC should find the waiting bootloader.

I have found if I do multiple presses I can abort the Bootloader - but usually any single press activates the Bootloader - and when present TeensyDuino jumps to action.

Can you open Device Manager and go to the Ports section and see if there are any teensy devices showing there when connected?
 
odd, 3.1 not dead or it wouldn't show. But it is seeing it oddly. I recall reading drivers weren't needed for this - but if you re-ran Teensyduino.exe setup and forced driver install - with IDE and all shut down it might make a difference next time.
 
odd, 3.1 not dead or it wouldn't show. But it is seeing it oddly. I recall reading drivers weren't needed for this - but if you re-ran Teensyduino.exe setup and forced driver install - with IDE and all shut down it might make a difference next time.

I have uninstalled and re-installed the serial driver several times accompanied with a reboot all to no avail. I have tried 2 different versions of Arduino (1.0.6 and 1.6.1) still no joy. I still don't understand why this device won't work.
 
After 5 days of trying to load any program I officially give up on this controller, unless of course someone can provide me with some new helpful information.
 
Puzzling - I opened my first three 3.1's and all work right - as does the one LC I pulled out - that is the extent of my expertise. Something really wrong with the Teensy or that I'm not seeing in your setup. Is your supplier mail order not local? When you say 'Serial' you don't mean the separate PJRC download? But the USB setup on page 2 of TeensyDuino setup?
TDSSetup.png
 
I just plugged in one of my Teensy 3.1 and using same setup other than I'm on windows 7 64 bit.

My settings are 72 mhz and teensy 3.1.
Below is what displays after upload completes in the IDE bottom portion

Sketch uses 9,900 bytes (3%) of program storage space. Maximum is 262,144 bytes.
Global variables use 2,432 bytes (3%) of dynamic memory, leaving 63,104 bytes for local variables. Maximum is 65,536 bytes.

And if you have a prior sketch loaded (blinky), you should not require to push the button. The window of the buttons should just say Reboot OK

The HID/win32 vid:16C0 pid:0486 is the teensy..
 
Just saw this related to an LC - but it shows some other diagnostics. I'm assuming your board is still 'unsoldered' to anything and only plug is to USB?

https://forum.pjrc.com/threads/27624-Coming-Soon-Teensy-LC-(low-cost-Teensy)?p=68911&viewfull=1#post68911

> Verify
> Program pin
> Also the 3.1 has a reset on bottom
> Press button during powerup

Also this TyQt app may help in diagnostics - it shows what com/usb ports host a Teensy if any:
https://forum.pjrc.com/threads/27825-Teensy-Qt?highlight=tyqt
 
Puzzling - I opened my first three 3.1's and all work right - as does the one LC I pulled out - that is the extent of my expertise. Something really wrong with the Teensy or that I'm not seeing in your setup. Is your supplier mail order not local? When you say 'Serial' you don't mean the separate PJRC download? But the USB setup on page 2 of TeensyDuino setup?
View attachment 3940

Supplier is mail order "Robot shop". Serial is the separate one as well as the one installed withe teensyduino.
 
Just saw this related to an LC - but it shows some other diagnostics. I'm assuming your board is still 'unsoldered' to anything and only plug is to USB?

https://forum.pjrc.com/threads/27624-Coming-Soon-Teensy-LC-(low-cost-Teensy)?p=68911&viewfull=1#post68911

> Verify
> Program pin
> Also the 3.1 has a reset on bottom
> Press button during powerup

Also this TyQt app may help in diagnostics - it shows what com/usb ports host a Teensy if any:
https://forum.pjrc.com/threads/27825-Teensy-Qt?highlight=tyqt

What about the program pin?
Tried holding reset button when plugging in usb, no change,
I tried slowing the arduino down to 48 mhz and I saw it say erasing followed by uploading the I error. (auto correct does strange things)
 
Last edited:
I'm not sure what the deal with the separate serial is - I've not used it - just wanted to know you had the indicated USB.

The other thread noted 'shorting the program to GND' as a way to wake it up - as well as DoubleClick on the button (I've gotten restart for other reasons like talking to my Android Phone) with a LONG press - followed by one or more quick presses - easy to identify it waking if the sketch blinks the LED13.

When connected to Windows does it connect with the 'Sound'? Does it disconnect when you LONG press the button - the re-connect on release?

The 3.1 also has the reset on the bottom - I've not touched yet - but it might show you something - not sure if it needs to go high or low.

If TeensyDuino is seeing it and trying and never succeeding it is something I have not seen and Paul would be best to review a good 'verbose' script of those events.

Maybe you are watching and saw this [LC but links to TShoot page]: https://forum.pjrc.com/threads/27624-Coming-Soon-Teensy-LC-(low-cost-Teensy)?p=68935&viewfull=1#post68935
 
Last edited:
I just plugged in one of my Teensy 3.1 and using same setup other than I'm on windows 7 64 bit.

My settings are 72 mhz and teensy 3.1.
Below is what displays after upload completes in the IDE bottom portion

Sketch uses 9,900 bytes (3%) of program storage space. Maximum is 262,144 bytes.
Global variables use 2,432 bytes (3%) of dynamic memory, leaving 63,104 bytes for local variables. Maximum is 65,536 bytes.

And if you have a prior sketch loaded (blinky), you should not require to push the button. The window of the buttons should just say Reboot OK

The HID/win32 vid:16C0 pid:0486 is the teensy..

Arduino is never able to reboot teensy, I get "Please press the PROGRAM MODE BUTTON on your Teensy to upload your sketch".
 
Just saw this related to an LC - but it shows some other diagnostics. I'm assuming your board is still 'unsoldered' to anything and only plug is to USB?

https://forum.pjrc.com/threads/27624-Coming-Soon-Teensy-LC-(low-cost-Teensy)?p=68911&viewfull=1#post68911

> Verify
> Program pin
> Also the 3.1 has a reset on bottom
> Press button during powerup

Also this TyQt app may help in diagnostics - it shows what com/usb ports host a Teensy if any:
https://forum.pjrc.com/threads/27825-Teensy-Qt?highlight=tyqt

I have tried TyQt app it shows // capabilities reboot, serial // location usb-3-2@1//
TyQt log shows the following when try uploading the HelloSerialMonitor:
I/O error while writing to '\\.\HID#VID_16C0&PID_0486&MI_01#7&2A3797B7&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}'
Reboot does not seem to work, trigger manually
 
Last edited:
It does connect with a sound but sometimes it continually makes the sound sound as thou connection is alternating between connected and disconnected.
 
I just uninstalled the windows serial driver followed by a reinstall of teensduino which install the serial driver.
Next I launched Arduino 1.6.1 and attempted to Compile and upload the HelloSerialMonitor program.
Attached is a snap shot of Arduino and below is the Verbose information.
One thing to note is the 2 buttons between Open Hex file and Auto are always grayed out.

21:26:49: Teensy Loader 1.21, begin program
21:26:49: File "sketch_mar24a.cpp.hex". 12160 bytes, 5% used
21:26:49: Listening for remote control on port 3149
21:26:49: initialized, showing main window
21:26:50: remote connection opened
21:26:50: remote cmd: "comment: Teensyduino 1.21 - WINDOWS"
21:26:50: remote cmd: "dir:C:\Users\Gord\AppData\Local\Temp\build8438191353250243149.tmp\"
21:26:50: remote cmd: "file:HelloSerialMonitor.cpp.hex"
21:26:50: File "HelloSerialMonitor.cpp.hex". 15276 bytes, 6% used
21:26:50: remote cmd: "status"
21:26:50: status data sent
21:26:50: remote cmd: "auto:eek:n"
21:26:50: remote connection closed
21:26:50: remote connection opened
21:26:50: remote cmd: "status"
21:26:50: status data sent
21:26:50: remote cmd: "status"
21:26:50: status data sent
21:26:50: HID/win32: vid:046D pid:C52B ver:2401
21:26:50: HID/win32: vid:046D pid:C52B ver:2401
21:26:50: HID/win32: vid:046D pid:C52B ver:2401
21:26:50: HID/win32: vid:046D pid:C52B ver:2401
21:26:50: HID/win32: vid:046D pid:C52B ver:2401
21:26:50: HID/win32: vid:06A3 pid:0765 ver:0109
21:26:50: HID/win32: vid:046D pid:C52B ver:2401
21:26:50: remote cmd: "status"
21:26:50: status data sent
21:26:50: remote cmd: "status"
21:26:50: status data sent
21:26:50: remote cmd: "status"
21:26:50: status data sent
21:26:50: remote cmd: "status"
21:26:50: status data sent
21:26:50: remote cmd: "status"
21:26:50: status data sent
21:26:50: remote cmd: "status"
21:26:50: status data sent
21:26:50: remote cmd: "status"
21:26:50: status data sent
21:26:50: remote cmd: "status"
21:26:50: status data sent
21:26:51: remote cmd: "status"
21:26:51: status data sent
21:26:51: remote cmd: "status"
21:26:51: status data sent
21:26:51: remote cmd: "status"
21:26:51: status data sent
21:26:51: remote cmd: "status"
21:26:51: status data sent
21:26:51: remote cmd: "status"
21:26:51: status data sent
21:26:51: remote cmd: "status"
21:26:51: status data sent
21:26:51: remote cmd: "status"
21:26:51: status data sent
21:26:51: remote cmd: "status"
21:26:51: status data sent
21:26:51: remote cmd: "status"
21:26:51: status data sent
21:26:52: remote cmd: "status"
21:26:52: status data sent
21:26:52: remote cmd: "status"
21:26:52: status data sent
21:26:52: remote cmd: "status"
21:26:52: status data sent
21:26:52: remote cmd: "status"
21:26:52: status data sent
21:26:52: remote cmd: "status"
21:26:52: status data sent
21:26:52: remote cmd: "status"
21:26:52: status data sent
21:26:52: remote cmd: "status"
21:26:52: status data sent
21:26:52: remote cmd: "status"
21:26:52: status data sent
21:26:52: remote cmd: "status"
21:26:52: status data sent
21:26:53: remote cmd: "status"
21:26:53: status data sent
21:26:53: remote cmd: "status"
21:26:53: status data sent
21:26:53: remote cmd: "status"
21:26:53: status data sent
21:26:53: remote cmd: "status"
21:26:53: status data sent
21:26:53: remote cmd: "status"
21:26:53: status data sent
21:26:53: remote cmd: "status"
21:26:53: status data sent
21:26:53: remote cmd: "status"
21:26:53: status data sent
21:26:53: remote cmd: "status"
21:26:53: status data sent
21:26:53: remote cmd: "status"
21:26:53: status data sent
21:26:54: remote cmd: "status"
21:26:54: status data sent
21:26:54: remote cmd: "status"
21:26:54: status data sent
21:26:54: remote cmd: "status"
21:26:54: status data sent
21:26:54: remote cmd: "status"
21:26:54: status data sent
21:26:54: remote cmd: "status"
21:26:54: status data sent
21:26:54: remote cmd: "status"
21:26:54: status data sent
21:26:54: remote cmd: "status"
21:26:54: status data sent
21:26:54: remote cmd: "status"
21:26:54: status data sent
21:26:54: remote cmd: "status"
21:26:54: status data sent
21:26:55: remote cmd: "status"
21:26:55: status data sent
21:26:55: remote cmd: "status"
21:26:55: status data sent
21:26:55: remote cmd: "status"
21:26:55: status data sent
21:26:55: remote cmd: "status"
21:26:55: status data sent
21:26:55: remote cmd: "status"
21:26:55: status data sent
21:26:55: remote connection closed
21:28:37: Auto Button event
21:28:37: Auto mode: disabled
21:28:37: Auto Button event
21:28:37: Auto mode: enabled
21:28:46: Verbose Info event
 

Attachments

  • HelloSerialMonitor.JPG
    HelloSerialMonitor.JPG
    71 KB · Views: 790
Can anyone answer this for me. If I launch the Teensy Loader and then load a hex file, should the 2 buttons between load and auto turn green? I have seen then go green and still have not been able to anything, it's been a week now. HELP please.
 
In my opinion this product I have (Teensy 3.1) is defective.
I would love to be proved wrong so I can start doing something useful rather then troubleshooting for it 1 week now.
 
Can anyone answer this for me. If I launch the Teensy Loader and then load a hex file, should the 2 buttons between load and auto turn green?

No. Those buttons remain gray / disabled until Teensy Loader detects a Teensy in bootloader mode (HID device with USB ID 16C0:0478).
 
In my opinion this product I have (Teensy 3.1) is defective.

There very well may be a problem with the pushbutton. Or something else about the hardware may be damaged. We certainly can replace it if that's the case.

The fact that you're seeing the RawHID device and the LED is blinking means the processor and USB are working fine.

Can you try just a couple simple things?

When you press and hold the pushbutton on Teensy, it should stop. The RawHID device should vanish from the Windows Device Manager, and the LED should stay off. If the pushbutton is physically defective, you'll see no response.
 
There very well may be a problem with the pushbutton. Or something else about the hardware may be damaged. We certainly can replace it if that's the case.

The fact that you're seeing the RawHID device and the LED is blinking means the processor and USB are working fine.

Can you try just a couple simple things?

When you press and hold the pushbutton on Teensy, it should stop. The RawHID device should vanish from the Windows Device Manager, and the LED should stay off. If the pushbutton is physically defective, you'll see no response.

When I push and hold the button the Teensyduino RawHID device disappears but when I release the button it reappears and the flashing light starts up again.
 
Status
Not open for further replies.
Back
Top