TWR-K65F180M USB Not Detected

[thomasrind]

I'm trying to run the ksdk 1.3.0 USB CDC device MQX kds example on the TWR-K65F180M board but the usb isn't showing up in device manager. The Mini USB port is being used to debug with opensda and power the board and the micro USB port is being used for CDC. No other usb examples can make the micro usb show up in device manager either.

The serial communications work because of the mini USB being used as the debugger. The Task_Start function is called but non of the callback functions are called when the micro usb is plugged in. Is there a configuration I need to change to make it work?

[danielchen · Accepted solution]

Hi Thomas Rind

Please change the HIGH_SPEED macro , and rebuild all libraries and try again

Usb_descriptor.h (SDK_1.3_TWR-K65F180M\examples\twrk65f180m\demo_apps\usb\device\cdc\virtual_com):50
#ifndef HIGH_SPEED
#define  HIGH_SPEED                      (1)
#endif

I hope it helps

Have a great day,
Daniel

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

[thomasrind]

Thank you this solved the issue.

Can you control between Full Speed and High Speed or does USB CDC need to be High Speed?

Thanks,

Tom

[danielchen]

Hi Tom:

I didn't try full speed, but I think it should can control Full speed and High speed.

In KSDK1.3 , you need to change two macros,

one is USB_DEVICE_CONFIG_KHCI (0U) and #define USB_DEVICE_CONFIG_EHCI (0U)

the other is HIGH_SPEED.

This seems not a good code style. It is improved in  KSDK2.0, only one macro can control it, it is USB_DEVICE_CONFIG_EHCI

Please also note that , if you need to test full speed, please use twr-serial board.

Regards

Daniel

[thomasrind]

Mark,

Nothing happens when I drag any of the Bin files into the bootloader. I've tried on multiple of the same board. Is there anyway the jumpers need to be, I'm currently using the default configuration.

Thanks,

Tom

[mjbcswitzerland]

Tom

For OpenSDA firmware loading there are no jumpers that affect anything.

I would update the loader to the Segger one (the one delivered on the board tends to be broken nowadays since Windows 8.1/10 screwed up its operation). Latest ones are at OpenSDA Serial and Debug Adapter|NXP 

At the moment I tend to use the Segger ones since they are presently giving best behavior for debugging, loading and VCOM (although P&E look to be improving theirs too after their BIN loading stopped working with some recent Win 10 updates).

You will probably need a WIN 7 PC to do the boot loader update (although I have heard that latest Win 7 SPs are also causing it to fail...).

Regards

Mark

[mjbcswitzerland]

Hi

Try loading a binary from here: http://www.utasker.com/kinetis/TWR-K65F180M.html
to verify that the HW is Ok. It has MSD and CDC and operates correctly on the TWR-K65F180M as long as the HS USB cable is connected.

Regards

Mark

[thomasrind]

Hi Mark,
   I'm new to this and a bit confused on how exactly I should load the .bin file on. Am I just copying it into the bootloader of the K65 or am I suppose to do it through KDS and if so how exactly?

Also I can get something to show up in device manager using the BM USB CDC Device KDS example for the KSDK 2.2 for TWR-K65F180M if I change usb_device_config.h so that #define USB_DEVICE_CONFIG_KHCI (1U) becomes #define USB_DEVICE_CONFIG_KHCI (0U) and #define USB_DEVICE_CONFIG_EHCI (0U) becomes #define USB_DEVICE_CONFIG_EHCI (1U). Unfortunately the 2.2 SDK doesn't have MQX support which is why I'm using 1.3.0.

Thanks,

Tom

[mjbcswitzerland]

Tom

Binary files are simply dragged- and-dropped to the board when it shows up as a hard-drive (assuming you have a boot loader that doesn't suffer from Windows 8.1/10 problems).

Regards

Mark