Teensy 2.0 Teensy Loader Error

Status
Not open for further replies.
T

transcendtient

Member
I'm having a really confusing time right now.

I've never had any problems with the loader, in fact I've been using it for my Teensy++ 2.0 for months.
I plugged in the 2.0's I bought a week ago and now the loader doesn't work for either. Below is a video with this behavior.
http://www.youtube.com/watch?v=TeqohEXw2_o&feature=youtu.be

The IDE compiles for the Teensy 2.0, but I have to rummage through my temp folder to find the compiled hex manually with the loader.

To try and make sure it wasn't just the Arduino install, I now have 1.03, 1.53, and 1.02 (my original install) and I've installed the Teensyduino package on all of them.

Any ideas would be greatly appreciated.
 
I don't have any problems programming it, communicating with it, NONE of that is a problem. It's the automated process that's mussed.
Yes I've tried plugging it into different USB ports, and if it were the cable I wouldn't be able to program it.

The problem is the Teensy loader is opened by the IDE, and then the IDE forgets where the hell it is. Is there some place I can check a program path?
 
Communication between Arduino and the Teensy Loader is done by a localhost (127.0.0.1) networking connection.

Perhaps you've got a firewall or security program that's preventing network connections, even when they're only localhost connections between programs running on your own computer?
 
Thank you so much, I reset my router recently and I'm guessing that could be it. I'll scour through my firewall permissions, but if you know the names of those permissions I'd appreciate it. I'm really unfamiliar with networking.
My local IP was 10.0.0.2 and on reset it changed to 127.0.0.1.

EDIT: I added permissions, then just turned the firewall off, didn't work.
 
Last edited:
Here is the verbose output of the loader.
22:29:56: Verbose Info event
22:30:24: remote connection opened
22:30:25: remote connection opened
22:30:25: remote connection opened
22:30:26: remote connection opened
22:30:26: remote connection opened
22:30:26: remote connection opened
22:30:27: remote connection opened
22:30:27: remote connection opened
22:30:27: remote connection opened
22:30:28: remote connection opened
22:30:28: remote connection opened
22:30:28: remote connection opened
22:30:29: remote connection opened
22:30:29: remote connection opened
22:30:29: remote connection opened
22:30:30: remote connection opened
22:30:30: remote connection opened
22:30:31: remote connection opened
22:30:31: remote connection opened
22:30:31: remote connection opened
22:30:32: remote connection opened
22:30:32: remote connection closed
22:30:32: remote connection closed
22:30:32: remote connection closed
22:30:32: remote connection closed
22:30:32: remote connection closed
22:30:32: remote connection closed
22:30:32: remote connection closed
22:30:32: remote connection closed
22:30:32: remote connection closed
22:30:32: remote connection closed
22:30:32: remote connection closed
22:30:32: remote connection closed
22:30:32: remote connection closed
22:30:32: remote connection closed
22:30:32: remote connection closed
22:30:32: remote connection closed
22:30:32: remote connection closed
22:30:32: remote connection closed
22:30:32: remote connection closed
22:30:32: remote connection closed
22:30:32: remote connection closed

So it opens crap tons of connections for some reason.
 
Something on your PC is interfering with the communication between these 2 programs. What, I do not know.

A firewall on your router doesn't matter. This is a localhost connection to 127.0.0.1, which is known as the loopback address. It's a special address (of a software-emulated network interface) that allows programs running on your computer to open connections to each other, without any outside communication. Since the networking is all internal to your computer, the settings on any external routers do not matter. The packets never make it to any physical interface and can never leave your computer. It's all software-only networking inside your machine. Only a software-based firewall, or other software running on your machine that modifies the computer's networking, or horribly messed up network settings, can interfere.

Usually Microsoft's built-in firewall or 3rd party firewalls like Zone Alarm will prevent the connection from opening at all, so I'd guess it's probably not a normal firewall product.

I mostly use Linux, so I'm not a Windows expert. I solve pretty much all Windows problems like this by restoring a fresh whole-disk image of a clean Windows install.... which really only works nicely if you don't ever use Windows as a primary system and all your files are on a reliable Linux or Mac machine, or a server somewhere.

If you don't do regular backups, I'd highly recommend backing up all your important data now. This may be just a simple wrong setting, but it might also be a sign your Windows install has something very wrong?
 
I deleted the entire program, the preferences, reinstalled Arduino IDE and Teensyduino, and still a no go. I'm not down to reinstall my operating system simply because one program isn't working.
This is completely a problem with the IDE and the Teensy Loader since the sketches compile correctly, the only thing is the loader never points to the recently compiled program and therefore can't program the Teensy.
 
When I got a new update from my AVG antivirus this happened to me too.
Temporarily disabled AVG and it worked again.
If you didn't check antivirus yet, it's a quick test...

I also think a reinstall might be a bit much if it is your 'main' system, I'd first check if a system restore to something like 1 month ago helps...
Make a new System Restore point of your current settings first so you can always restore to current state!

Here is a 'netstat -a -n' of my connections to/from the loader, maybe it helps you to see something thats not right:
When I upload code using Windows7 to the Teensy, a connection is opened to:
Code: 
  TCP    127.0.0.1:3149         0.0.0.0:0              LISTENING
  TCP    127.0.0.1:3149         127.0.0.1:55780        ESTABLISHED

After uploading only the loader is still running (because I didn't close it)
Code: 
  TCP    127.0.0.1:3149         0.0.0.0:0              LISTENING
When I close the loader, the LISTENING interface also disappears.


I do have to agree with Paul, 127.0.0.1 is a local loopback interface so it has to be something local on the computer itself, routers cannot affect this.
Not being able to send data to 127.0.0.1 usually means that there is some kind of security software, or a forwarding service like a proxy that is delaying/rerouting the data.

Anyway, hope you get this sorted out!
 
If you're only getting one connection then something is really mussed. I get a crapton.
TCP 127.0.0.1:3149 0.0.0.0:0 LISTENING
TCP 127.0.0.1:3149 127.0.0.1:55638 ESTABLISHED
TCP 127.0.0.1:3149 127.0.0.1:55640 ESTABLISHED
TCP 127.0.0.1:3149 127.0.0.1:55642 ESTABLISHED
TCP 127.0.0.1:3149 127.0.0.1:55644 ESTABLISHED
TCP 127.0.0.1:3149 127.0.0.1:55646 ESTABLISHED
TCP 127.0.0.1:3149 127.0.0.1:55648 ESTABLISHED
TCP 127.0.0.1:3149 127.0.0.1:55650 ESTABLISHED
TCP 127.0.0.1:3149 127.0.0.1:55652 ESTABLISHED
TCP 127.0.0.1:3149 127.0.0.1:55654 ESTABLISHED
TCP 127.0.0.1:3149 127.0.0.1:55656 ESTABLISHED
TCP 127.0.0.1:3149 127.0.0.1:55658 ESTABLISHED
TCP 127.0.0.1:3149 127.0.0.1:55660 ESTABLISHED
TCP 127.0.0.1:3149 127.0.0.1:55662 ESTABLISHED
TCP 127.0.0.1:3149 127.0.0.1:55664 ESTABLISHED
TCP 127.0.0.1:3149 127.0.0.1:55666 ESTABLISHED
TCP 127.0.0.1:3149 127.0.0.1:55668 ESTABLISHED
TCP 127.0.0.1:3149 127.0.0.1:55670 ESTABLISHED
TCP 127.0.0.1:3149 127.0.0.1:55672 ESTABLISHED
TCP 127.0.0.1:3149 127.0.0.1:55674 ESTABLISHED
 
Just rechecked to make sure, but yeah I get 1 for the loader popup window (listening) and 1 for the actual upload (established).

At least the connection to 127.0.0.1:556xx is made so we know your loopback interface is listening and accepting connections.
You could try to run 'msconfig' and disable everything in the 'Startup' section, make sure that there is no software interfering.

If that doesn't help I would start to think about things like Windows Updates and such that might have changed a critical setting on your system.
As far as I know the only way to test that is to do a System Restore or a reinstall/restoring a backup of your Windows.

If all else fails you could try to install a network sniffer like Wireshark, see if there are packets being sent/received, but I have no experience with that myself.
 
Lord I figured it out. 2:20AM. I was using some incompatible settings on Auslogics BoostSpeed. I hope my esoteric nimrodery helps someone else out someday.
 
Status
Not open for further replies.
Back
Top