cancel
Showing results for 
Search instead for 
Did you mean: 

Knowledge Base Articles

[Windows Only] Debug/Programming Tools Do Not Work After Upgrading to KitProg3 v2.10 - KBA231027

ChaitanyaV_61
Employee

[Windows Only] Debug/Programming Tools Do Not Work After Upgrading to KitProg3 v2.10 - KBA231027

Author: VitaS_81           Version: **

Translation - Japanese: [Windowsのみ] KitProg3 v2.10にアップグレードした後、デバッグ/プログラミングツールが機能しない - KBA231027 - Community Translated (JA)

Problem: 

On Windows, after updating to KitProg3 v2.10, debug/programming tools such as PSoC® Creator™, PSoC Programmer, CapSense® Tuner, and Bridge Control Panel cannot connect to a device. An example of this behavior is that KitProg3 device is available but cannot be selected in the tool.

Background:

Previous versions of KitProg3 implement I2C/SPI bridging using HID endpoints. In version 2.10 and newer, bridging is implemented on bulk endpoints for improved performance. After updating, Windows continues to use the old driver ‘hidusb’ for I2C/SPI bridging instead of the proper driver for bulk endpoints, ‘winusb’.

Solution:

Do the following to manually remove USB drivers:

  1. In Device Manager, find Composite Device for KitProg3 device.
        1.1. Change View to Devices by container.
        1.2. Locate KitProg3 CMSIS-DAP or MiniProg4 CMSIS-DAP and open the container
         pastedImage_11.png
  2. Right-click USB Composite Device and choose Uninstall device.
  3. Click Scan for hardware changes.
0 Likes
Version history
Revision #:
1 of 1
Last update:
‎Sep 14, 2020 05:20 AM
Updated by:
 
Contributors