search

chipKIT32 / chipKIT32-MAX

Multi-platform IDE derived version from Arduino 0022 for the chipKit.
http://chipkit.net
Other
108 stars 76 forks source link

chipKIT boards show up as Teensy boards in Windows Device Manager #551

Open JacobChrist opened 9 years ago

JacobChrist commented 9 years ago

When the Teensy drivers are installed chipKIT stk500v2 drivers show up as Teensy:

image

EmbeddedMan commented 9 years ago

I have tried to reproduce this, and have been unable to. I installed Arduino 1.0.6, then Teensyduino (which installed it's USB drivers). I then took a Teensy 2.0, compiled a sketch for it that used USB serial, downloaded it and confirmed it's operation. While plugged in, the Teensy shows up as "Teensy USB Serial (COM4)" as expected.

I then unplugged the Teensy, and plugged in a Fubarino Mini with a serial based sketch. The Fubarino shows up as chipKIT USB Serial (Stk500v2 compatible) (COM14).

With both plugged in at the same time, I get proper USB names for both boards.

This is under Windows 8.1 64 bit.

JacobChrist commented 9 years ago

We see this on two different Windows 7 computers. On Feb 13, 2015 2:44 PM, "Brian Schmalz" notifications@github.com wrote:

I have tried to reproduce this, and have been unable to. I installed Arduino 1.0.6, then Teensyduino (which installed it's USB drivers). I then took a Teensy 2.0, compiled a sketch for it that used USB serial, downloaded it and confirmed it's operation. While plugged in, the Teensy shows up as "Teensy USB Serial (COM4)" as expected.

I then unplugged the Teensy, and plugged in a Fubarino Mini with a serial based sketch. The Fubarino shows up as chipKIT USB Serial (Stk500v2 compatible) (COM14).

With both plugged in at the same time, I get proper USB names for both boards.

This is under Windows 8.1 64 bit.

— Reply to this email directly or view it on GitHub https://github.com/chipKIT32/chipKIT32-MAX/issues/551#issuecomment-74340448 .

EmbeddedMan commented 9 years ago

I feel like this is some strange driver mis-match issue under Windows. I can't reproduce the issue under Windows 7 or Windows 8, but then my development system is probably pretty 'unique' and doesn't represent a typical user's machine.

To help me debug this problem could you plug in both a chipKIT USB board (like Fubarino) and a Teensy board and then run USBView.exe (http://www.softpedia.com/get/System/System-Info/USBView.shtml) and send me a screenshot with those two fully expanded?

ricklon commented 9 years ago

I've seen this problem as well. I've had to reset Windows drivers. This was on Windows 7 machines.

JacobChrist commented 9 years ago

Could this have anything to do with chipKIT using a VID/PID assigned by FTDI?

On Fri, Aug 21, 2015 at 8:07 AM, Ricklon notifications@github.com wrote:

I've seen this problem as well. I've had to reset Windows drivers. This was on Windows 7 machines.

— Reply to this email directly or view it on GitHub https://github.com/chipKIT32/chipKIT32-MAX/issues/551#issuecomment-133456796 .

Jacob Christ ProLinear/PONTECH, Inc. 1-877-985-9286 Phone 1-413-235-1651 Fax http://www.pontech.com

EmbeddedMan commented 9 years ago

Great question. I'm not sure what the mechanism would be though. We use an FTDI VID of 0x0403 with a custom (hopefully unique) PID of 0xA662. If Teensy is also using the same VID and PID as us, then I think they're probably doing something wrong. :-) But my guess is that they are not using those VIDs and PIDs.

My guess is that there is an error in either their INF file or ours that is stomping on the other INF file. Remember, we don't have our own driver - we just have an INF file that says to Windows "when you see this VID/PID combo, use your built-in usbser.sys driver". Both their INF and our INF file say that same thing.

This issue needs more investigation. I'm happy to do it, but it's going to be a while before I can find the time.

*Brian

On Fri, Aug 21, 2015 at 9:10 AM, Jacob Christ notifications@github.com wrote:

Could this have anything to do with chipKIT using a VID/PID assigned by FTDI?

On Fri, Aug 21, 2015 at 8:07 AM, Ricklon notifications@github.com wrote:

I've seen this problem as well. I've had to reset Windows drivers. This was on Windows 7 machines.

— Reply to this email directly or view it on GitHub < https://github.com/chipKIT32/chipKIT32-MAX/issues/551#issuecomment-133456796

.

Jacob Christ ProLinear/PONTECH, Inc. 1-877-985-9286 Phone 1-413-235-1651 Fax http://www.pontech.com

— Reply to this email directly or view it on GitHub https://github.com/chipKIT32/chipKIT32-MAX/issues/551#issuecomment-133477525 .

JacobChrist commented 9 years ago

I have new information. I just plugged in an Arduino Uno and it shows up as a Teensy in the Device Manager. Teensy is just rude.

EmbeddedMan commented 9 years ago

There must be some INI magic that Paul's doing in the Teensy driver install INF file that allows this behavior. I'm not a wizard with INF files and don't know how, but that's what must be going on.

*Brian

On Thu, Aug 27, 2015 at 3:31 PM, Jacob Christ notifications@github.com wrote:

I have new information. I just plugged in an Arduino Uno and it shows up as a Teensy in the Device Manager. Teensy is just rude.

— Reply to this email directly or view it on GitHub https://github.com/chipKIT32/chipKIT32-MAX/issues/551#issuecomment-135546655 .