USB Device - End-user experience

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

USB Device - End-user experience

792件の閲覧回数
danielg14
Contributor I


Hi,

We have a Kinetis K20 micro-controller on our new product which will be released to the public within the next 6 months. The product interfaces with the PC via the K20's USB port which is designed to run as a virtual com port. The code for the USB was based on an example codewarrior project.

During developement we used the ini configuration file from the codewarrior project to install the driver on our computers.

We now want to take the proper steps of releasing this USB capable product and we want to make sure that we take the proper steps. We also want the end-user's experience to be as simple as possible.

How can we, if possible, have the end-user's computer detect the USB device as our product and install the appropriate device driver? We would like to avoid having to provide the ini file to the user and having them install it manually.

ラベル(1)
タグ(1)
0 件の賞賛
3 返答(返信)

574件の閲覧回数
danielg14
Contributor I

Thanks for the responses!

I guess we'll provide our customers with the driver. That's unfortunate but we can deal with it.

0 件の賞賛

574件の閲覧回数
tjhartnett
Contributor I

getting the drivers to install automagically is lot of effort. requires u to get your device to be Microsoft WHQL. best and most feasiable way to get an easy setup is to create your .inf file for the drivers, then use Wix Tools to create an .msi file which will install the drivers. This way your customer just needs to download the .msi and double click on it, or the .msi can be distributed with your product

574件の閲覧回数
mjbcswitzerland
Specialist V

Hi

The PC side is quite complicated (and may require several weeks and more of learning, experimenting) and it may be best to contract a specialist company to do the work - try someone like Jungo who may be able to sell you a package to do it.

If you only needed to support Windows 10 users it is no longer necessary to have a driver at all for CDC. Simply set the device class/sub-class/protocol (in the device descriptor) to 2, 2, 0 (as recommended by Microsoft) and WIndows 10 will automatically install the correct driver without any user involvement....

Regards

Mark

0 件の賞賛