Clash of Teensyduino USB and Atmel Jungo... Also TI LDC1000EVM

[bboyes]

So everything with Teensy has been peachy on my desktop PC (Win7 Pro64) until I installed an Atmel SAMD20 Xplained Pro development board. Now Teensy 3 parts are not recognized when plugged in. And the Atmel SAMD20 is recognized as "Teensy USB Serial (COM29)" in Device Manager. Similar clash on my Win7 Pro64 notebook after I installed a TI LDC1000EVM: after installing that EVM, then Teensyduino, the EVM was not recognized.

The only way I could get the LDC1000EVM (notebook PC) to connect was to plug it in and uninstall the (incorrectly used?) Teensy USB Serial driver, checking the option to delete the driver software, then reinstalling the EVM software. I have not yet tried to use Teensy on that notebook since doing this.

On my desktop PC, at work, I uninstalled the Teensy USB driver when the Atmel Xplained Pro board was plugged in. Unplugged that board, re-ran the Teensyduino 1.18 installer, which said that the USB driver needed to be installed (of course: I deleted it in the previous step). Plugged in Teensy 3. Heard the tone which should indicate USB connecting. But there is no "Teensy" USB port visible in Device Manager. I plugged in an Arduino Uno R3 and it was recognized and its COM port shows up in Device Manager.

Now what? Google... Apparently this is a known problem with Atmel Studio 6.X, which changed to Jungo USB drivers.

One recommended fix might be libusb-win32: http://www.visualmicro.com/post/2014/01/17/AvrIsp-MkII-Usb-Driver-for-Arduino.aspx but when I try to run the wizard, with Teensy3 plugged in, it is not enumerated, so this hits a dead end.

So, try uninstalling the Jungo driver. Teensy 3 still not recognized.

I'm lost. Any ideas? Anyone else having this clash of USB?

 

[bboyes]

Well, at home on the Lenovo notebook I can go back and forth between Teensy3 and the TI LDC1000EVM. Atmel Studio 6.1 is installed on this system, too, but I have not tried SAMD20 kit on it since I don't have one at home. Anyway, the point is that something on my 3-year-old office PC has apparently messed up the USB drivers. I was seeing the Atmel debug driver properties claim it was written by PJRC.

On the notebook it's a recent clean Win7 install, so it has had fewer USB drivers in its history thus far. Is there some procedure for somehow starting clean with USB drivers, other than a complete fresh OS install on a blank boot disk?

 

[PaulStoffregen]

So, try uninstalling the Jungo driver. Teensy 3 still not recognized.

Really, the only thing to try is running the Serial Installer again, the unplug and reconnect the Teensy. Hopefully the New Hardware Wizard will find it again after re-running the installer. Or in the Device Manager, if it's showing up as an unknown device, and you've recently run that installer, you could right click and use the option to update the driver. Click Yes is Windows asks to find the driver automatically.

This is all to just get Teensy to be recognized while it's trying to be a Serial device.

You could use Arduino and select a non-Serial device from the Tools > USB Type menu. Then upload to the Teensy, and it will become that other type of device. Only Serail needs the driver. The others all work without any extra stuff.

Of course, on an old XP machine that's had its registry corrupted, all bets are off.

 

[bboyes]

Paul - thanks for the reply. I tried rerunning Teensyduino, re-plugging Teensy, I went back a several restore points (this is Win7 Pro64) and finally got Teensy to be recognized, and I am able to program it and use the serial debug console, but Device Manager reports it is not Teensy:
- so I tried updating the driver letting Windows find the update, but that failed:

At least I can get back to development on my main PC, but I am fearful it may fail again.
Prior to this I could not get Teensyduino to load a file onto Teensy.

On two other machines (both Win7 Pro64 notebooks) I can have the Atmel tools, TI tools, and Teensy and Arduino all installed without clashing. So it doesn't seem to be the tools per se, rather some corrupted aspect of USB or registry on my main development system (which admittedly has a ton of demo board and peripheral stuff installed - hard to avoid that).

Does anyone know of a way to somehow clear out USB drivers and start over, without a whole clean install of Win7? I tried googling that and have some things to try, such as http://www.nirsoft.net/utils/usb_devices_view.html

It may be time to get a new SSD and try a new clean install of my OS... but at the moment I have a pile of work to get done in the next week, so I would prefer to defer that...

 

[PaulStoffregen]

Does anyone know of a way to somehow clear out USB drivers and start over

I wish I knew such a thing!

 

[bboyes]

Stranger it gets...

OK, after a hiatus of a month I am back in this tar pit. Re-read Paul's last advice. Selected "unknown device" in device manager, and right-clicked, then "Update Driver Software", but selected "Let me pick from a list..."

Then I selected Manufacturer: PJRC.COM. LLC. and Model: Teensy USB Serial, and continue through.

and this dire warning

Then Teensy3 showed up as COM10.
Until I loaded a program into it. It became again "unknown device" and I could not use the Arduino Serial Monitor because COM10 no longer existed.
I repeated the above steps. This time it installed as COM11. And it seems to persist through at least one program load.
Closed Arduino IDE, restarted, and COM11 is still there.

I have to find a longer term solution to this. I use a lot of development tools and have to be able to switch between them. And many have only a Windows IDE so using Linux is not the perfect solution either. Is Linux USB less flaky than Windows? Is Windows 8.1 any better - or worse?

 

[Nantonos]

I notice that when Microsoft talks about Serial over USB, they always frame it in terms of "Serial Modem". I believe they consider Serial support only relates to legacy modems that no-one uses anymore, and thus put zero effort into it.

If you have enough memory, using virtual machines might be a way forward. Either Linux or Windows as you prefer, but running virtual machines with one development environment in each.