usb-uart driver

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

usb-uart driver

Jump to solution
3,239 Views
skunky
Contributor II

Hi Everybody. I'm having an issue with the FRDM-KL26Z board. I updated the boot code with the latest from PE Micro. All I could find to download from them was debug boot code. I downloaded the Quick Start Package, which includes some precompiled examples. I have found that when I install any of the precompiled examples, I can't get the USB connection to the KL26Z processor working. I'm referring here to the port labeled KL26ZUSB, not the port labeled SDA.

Windows just can't find a driver for the KL26ZUSB port. It shows up in my device manager as a USB-UART. with an exclamation mark. This is true with Windows 7, and Windows XP. Does anyone know where I can get the driver I need to talk to the KL26Z processor?

0 Kudos
Reply
1 Solution
2,126 Views
mjbcswitzerland
Specialist V

Hi Mark

If I understand correctly you are missing the Freescale USB-driver's INF file - otherwise the images loaded to the K26 are running and the host is seeing the USB device.

If you don't find the drivers you can take any INF that is for the standard Windows USB-CDC and modify the VID/PID settings to suit the device that you connect and then it will be able to operate.

You can do the following:

- at µTasker Kinetis FRDM-KL26Z support there are binary images that can be loaded and also INF files for 32 and 64 bit Windows.

- you can load the images and then use the drivers from there for the installation to get a USB-CDC connection to your board with 3 interfaces (as practice).

- if you are only interested in getting the Freescale demos working (with one interface) you can the take the INF file that you verified and modify the VID/PIDs in it to match the ones used by the Freecale demo [You can see the values when you open up the characteristics of the USB interface with the exclamation mark and then select its HW IDs].

After modifying to match these and saving under a new name you can then point the driver installation to the directory that it is in and it will allow it to operate.

The .INF is in fact for 1 to 6 USB-CDC interfaces (so that it can be used for any KL or K device with up to 6 USB-UART briges - 5 on a FRDM-K64F for example: µTasker Kinetis FRDM-K64F support) and should be OK for any number (including 1).

If there are still difficuties with the Freescale demo you can remove the additional interfaces so that it falls back to the simplest case:

%DESCRIPTION%=DriverInstall, USB\VID_15a2&PID_0044 <- keep this one

%DESCRIPTION%=DriverInstall, USB\VID_15a2&PID_0044&MI_00 <- remove all additional (optional) interfaces

%DESCRIPTION%=DriverInstall, USB\VID_15a2&PID_0044&MI_02

%DESCRIPTION%=DriverInstall, USB\VID_15a2&PID_0044&MI_04

%DESCRIPTION%=DriverInstall, USB\VID_15a2&PID_0044&MI_06

%DESCRIPTION%=DriverInstall, USB\VID_15a2&PID_0044&MI_08

%DESCRIPTION%=DriverInstall, USB\VID_15a2&PID_0044&MI_0a

As you see, the VID/PID combination 0x15a2/0x0044 is used by the USB-CDC in the uTasker framework, which is Freescale's VID and a PID officially allocated by Freescale to the project.

Probably you will find the Freescale CDC demo to use the same VID and you will just need to change its PID. For example, Freescale uses PID 0x0072 for the dedicated FreeMaster application on the TWR-KM34Z50M (which I never found a driver for so did the same modification to get it running). The Freescale KBOOT USB-HID loader uses 0x0073, etc.

Regards

Mark

Kinetis: µTasker Kinetis support

KL26: µTasker Kinetis FRDM-KL26Z support / µTasker Kinetis Teensy LC support

Composite USB: µTasker USB Device Configuration

USB User's Guide: http://www.utasker.com/docs/uTasker/USB_User_Guide.PDF

For the complete "out-of-the-box" Kinetis experience and faster time to market

View solution in original post

0 Kudos
Reply
3 Replies
2,126 Views
dorianhildebran
Contributor I

Had the same Problem with a KL46z.

Windows found the Driver for the SDA-USB, but not for the other USB port.

The Driver from µTasker Kinetis FRDM-KL26Z support solved the Problem. Had to

choose for the Driver manually and got a warning first (not signed driver), but at the end it appears as comport in in the device manager.

Thanks guys.

0 Kudos
Reply
2,126 Views
skunky
Contributor II

That solved it. I actually grabbed the driver from the SDA side, and used that. Once I changed the USB and PID, it worked beautifully! Thanks Mark!

0 Kudos
Reply
2,127 Views
mjbcswitzerland
Specialist V

Hi Mark

If I understand correctly you are missing the Freescale USB-driver's INF file - otherwise the images loaded to the K26 are running and the host is seeing the USB device.

If you don't find the drivers you can take any INF that is for the standard Windows USB-CDC and modify the VID/PID settings to suit the device that you connect and then it will be able to operate.

You can do the following:

- at µTasker Kinetis FRDM-KL26Z support there are binary images that can be loaded and also INF files for 32 and 64 bit Windows.

- you can load the images and then use the drivers from there for the installation to get a USB-CDC connection to your board with 3 interfaces (as practice).

- if you are only interested in getting the Freescale demos working (with one interface) you can the take the INF file that you verified and modify the VID/PIDs in it to match the ones used by the Freecale demo [You can see the values when you open up the characteristics of the USB interface with the exclamation mark and then select its HW IDs].

After modifying to match these and saving under a new name you can then point the driver installation to the directory that it is in and it will allow it to operate.

The .INF is in fact for 1 to 6 USB-CDC interfaces (so that it can be used for any KL or K device with up to 6 USB-UART briges - 5 on a FRDM-K64F for example: µTasker Kinetis FRDM-K64F support) and should be OK for any number (including 1).

If there are still difficuties with the Freescale demo you can remove the additional interfaces so that it falls back to the simplest case:

%DESCRIPTION%=DriverInstall, USB\VID_15a2&PID_0044 <- keep this one

%DESCRIPTION%=DriverInstall, USB\VID_15a2&PID_0044&MI_00 <- remove all additional (optional) interfaces

%DESCRIPTION%=DriverInstall, USB\VID_15a2&PID_0044&MI_02

%DESCRIPTION%=DriverInstall, USB\VID_15a2&PID_0044&MI_04

%DESCRIPTION%=DriverInstall, USB\VID_15a2&PID_0044&MI_06

%DESCRIPTION%=DriverInstall, USB\VID_15a2&PID_0044&MI_08

%DESCRIPTION%=DriverInstall, USB\VID_15a2&PID_0044&MI_0a

As you see, the VID/PID combination 0x15a2/0x0044 is used by the USB-CDC in the uTasker framework, which is Freescale's VID and a PID officially allocated by Freescale to the project.

Probably you will find the Freescale CDC demo to use the same VID and you will just need to change its PID. For example, Freescale uses PID 0x0072 for the dedicated FreeMaster application on the TWR-KM34Z50M (which I never found a driver for so did the same modification to get it running). The Freescale KBOOT USB-HID loader uses 0x0073, etc.

Regards

Mark

Kinetis: µTasker Kinetis support

KL26: µTasker Kinetis FRDM-KL26Z support / µTasker Kinetis Teensy LC support

Composite USB: µTasker USB Device Configuration

USB User's Guide: http://www.utasker.com/docs/uTasker/USB_User_Guide.PDF

For the complete "out-of-the-box" Kinetis experience and faster time to market

0 Kudos
Reply