FRDM-K22F: Auto-loading the virtual com driver?

cancel
Showing results for 
Search instead for 
Did you mean: 

FRDM-K22F: Auto-loading the virtual com driver?

595 Views
benjamin_tait
Contributor II

I have been working with the Hello World VCom project. I have gotten it to work, by uploading the firmware to the Freedom board, and manually installing the openSDA driver though Windows' Device Manager, as specified here: https://www.mathworks.com/help/supportpkg/freedomboard/ug/install-drivers-for-freescale-frdm-kl25z-b..., to the correct COM port.

The Freedom board's SDK supplies an inf file. However, simply installing the .inf through pnputil, or copying to the Windows inf directory, does not suffice towards getting a new computer to recognize the Freedom board's serial VCom port as a serial device, and attaching either the openSDA serial driver or default Windows serial driver to it. After running pnputil on the inf file, the device gives the error, "A service installation section in this INF is invalid" when I examine it in Device Manager.

I would like some command-line method I can run in a setup batch file, which will configure the device driver correctly -- i.e. I would not like users of my device to have to go into device manager and add the driver manually. Is there some way of doing this via command-line?

0 Kudos
6 Replies

321 Views
mjbcswitzerland
Specialist V

Hi

If you are using Windows 10 and the USB VCOM interface is set up correctly there is no driver installation (or *.inf) files necessary.
See links below for Win 10 compatible VCOM binaries for the FRDM-K22F and reference *.inf files for other Windows systems.
If you prefer a high performance and industrially proven VCOM solution (which allows multiple/composite VCOM and VCOM to K22 UART bridges) you can download the open source version containing all needed.
The K22 and its USB OTG module is simulated for better code analysis and testing (using Visual Studio - also available free as VS2015 or VS2017 community edition).

Regards

Mark

Complete Kinetis solutions for professional needs, training and support: http://www.utasker.com/kinetis.html
Kinetis K22:
- http://www.utasker.com/kinetis/FRDM-K22F.html
- http://www.utasker.com/kinetis/TWR-K22F120M.html
- http://www.utasker.com/kinetis/BLAZE_K22.html
- http://www.utasker.com/kinetis/tinyK22.html

USB:
- http://www.utasker.com/docs/uTasker/uTaskerV1.3_USB_Demo.PDF
- http://www.utasker.com/docs/uTasker/USB_User_Guide.PDF
- http://www.utasker.com/docs/uTasker/uTaskerRNDIS.pdf

uTasker: supporting >1'000 registered Kinetis users get products faster and cheaper to market
Request Free emergency remote desk-top consulting at http://www.utasker.com/services.html

Open Source version at https://github.com/uTasker/uTasker-Kinetis

0 Kudos

321 Views
benjamin_tait
Contributor II

Thank you for your reply.

However, I am using windows 7. I do seem to need some sort of inf/driver files. I was hoping someone could explain where I might find these (since the SDK provided one, which I attached to my original post, doesn't seem to work).

Thanks

0 Kudos

321 Views
kerryzhou
NXP TechSupport
NXP TechSupport

Hi Benjamin Tait,

  What's the on board debugger firmware you are using? CMSIS DAP, JLINK or opensda, do you install the related driver at first?


Have a great day,
Kerry

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

- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

0 Kudos

321 Views
benjamin_tait
Contributor II

Hello kerryzhou,

Thank you for your reply.

I am using CMSIS DAP board debugger firmware. 

As described in my original post, once the VCOM demo app is loaded, I can go into the Windows Device Manager, right click the virtual serial COM port created on the debugger USB connector, and associate the OpenSDA CDC serial driver  (or the default Windows serial driver) with the device.

I would like to automate this process, so that a batch file can be run from an installer, and automatically install the driver to the correct COM port - I don't want the user to have to go into Device Manager and do this manually, from Windows 7.

I had thought I could do this with the default INF included with NXP's SDK demo (ie using pnputil to install the inf file from a Windows batch script), but I get the error I mentioned in my original post. If you could shed any light on how to go about installing the serial driver to the COM device via command line, I would really appreciate it.

Thanks,

Ben

0 Kudos

321 Views
mjbcswitzerland
Specialist V

For Windows 7 you need to ensure that the PID/VID in the *.inf matches with your value in the code.

Regards

Mark

0 Kudos

321 Views
kerryzhou
NXP TechSupport
NXP TechSupport

Hi Ben,

  If you are using CMSIS DAP, you need to download  and install the mbed windows serial port driver:

Windows serial configuration - Handbook | Mbed 

In factor, after you install the mbed windows serial port driver, you don't need to add the inf file by yourself, the on board debugger will search it automatically.

I also use the win7 system on my side, the serial com is also installed automatically.

  Please try it again.

Have a great day,
Kerry

 

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

 

- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

0 Kudos