K60 + TWR-SER USB echo demo doesn't work

[MikeAdv]

I'm trying to get the USB_device demo working with a K60 and a TWR-SER.  The documentation suggests that it is just a simple echo through a COM port.

Do I need to connect USB cables to both the K60 board and the TWR-SER board?

I have tried various different jumper settings and can't seem to make anything work.  I'm using Windows XP.  I seem to either be able to get to where Windows only see's the OSJTAG USB device or it gives me the error message: "USB Device Not Recognized.  One of the USB devices attached to this computer has malfunctioned, and Windows does not recognize it.  For assistance in solving this problem, click this message."

I try to then install the driver supplied with the demo (Freescale_CDC_Driver_Kinetis.inf) but it won't let me install that.

Any hints on getting this working?

[admin]

Check out this discussion. I haven't used OSJTAG in a while, but this did the trick for me.

The "USB Device Not Recognized.  One of the USB devices attached to this computer has malfunctioned, and Windows does not recognize it.  For assistance in solving this problem, click this message." probably means your device didn't enumerate and probably isn't communicating at all, so you won't be able to install the driver until it does.

If I remember correctly, you need two USB cables: one for OSJTAG and one for the USB Serial driver.

Tom

[MikeAdv]

Maybe I should ask a related question.

What I'm really trying to do is create our prototype application and have that application output periodic data through the USB (USB virtual COM port would work fine and probably be the easiest.)

I'd really prefer to not have to use the TWR-SER card.  Is there anyway to do this?  From what I can see in the schematic of the TWR-K60 card, there really isn't a viable way to do this -- the USB signals from the K60 only go to the TWR connector.  

Is there any way I could use the OSJTAG to periodically get data out of the application (without the obvious of stopping it and reading memory)?

[admin]

Do you only need access to the data while you are debugging?  If so, you can use UART5, which is routed to the On Board OSBDM/Serial Bridge circuitry and should be accessible over the debug cable through the P&E toolkit.

Do you have an RS232 connection available? UART0 is routed through the J3 header on the K60 Tower board which you could jumper to an RS232 Adapter to access through a COM port.

Tom

[MikeAdv]

Data out just while I'm debugging would be fine.

I can see in the schematic how UART5 is routed back to the USB to serial bridge.  Indeed, that seems to be how the accelerometer demo works that comes with the device.

However, it all seems to be intermittent as to whether it works or not.  

I created an application that just streams data to UART5.  However, I can't get the PE Micro Terminal application to even open up the USB port.  So I decided I'd try just the accelerometer demo.  That didn't work with the board I've modified -- probably no surprise there.  I've removed the accel program from the FLASH.  I have another eval board sitting here so I tried that.  I was able to get the Serial Port Graphing Utility V2.00 to work once, at least through the Terminal Window I could talk to the eval board -- nothing on the "Scope."  However, even with the accel terminal window working, when I tried to use the PE micro terminal utility, again, I couldn't even open the USB port.

I'm not sure if I'm just dealing with flaky USB drivers.  Right now I se "PEMicro USB Serial Port (i1)" under "Jungo" in the Device Manager and then I see "Open Source BDM - Debug Port" under "LibUSB-Win32 Devies".  Anyone know if this is what I should see?

I'll try to remove and reinstall the driver and see if that help any.

[MikeAdv]

Looks like it was indeed a driver issue.  I went to the PE web site and downloaded the drivers and now I am able to write from the eval board, through the OJTAG, to the PE micro USB to serial bridge.

I think that will work for what I need to do.