Skip to main content

Troubleshooting

This section lists known issues, along with any workarounds.

Wrong COM port name() for KitProg3-based devices with AIROC targets on Windows​

COM ports for a KitProg3-based device with AIROC™ targets may be wrongly recognized in the system for two reasons:

  • Driver is not up-to-date - COM port(s) is/are listed in the Device Manager as a "USB Serial Device", instead of expected "HCI UART"/"Peripheral UART" name(s).

    Solution is to manually update driver(s) for each COM port to the latest one, which is delivered with the latest version of fw-loader tool (See Where to get it section).

    In the Device Manager, go to the USB Serial Device device(s) and click on Update driver > Browse my computer for drivers and navigate to the kp-firmware\drivers\KitProg3\KitProg3UART folder, delivered with fw-loader tool. Click Next and Install.

  • KitProg3 FW on the device is not up-to-date - DualUart COM ports are detected as "KitProg3 Primary USB-UART" and "KitProg3 Secondary USB-UART" instead of "HCI UART" and "Peripheral UART". In bulk/HID modes, the COM port is listed as "KitProg3 USB-UART" instead of the expected "HCI UART."

    Solution is to update the device FW to the latest one (See Updating KitProg3 section ).

On Windows, after updating to KitProg3 v2.10, PSOC Creator, PSOC Programmer, CAPSENSE Tuner, or the Bridge Control Panel can't connect to a device​

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 the KitProg3, Windows may continue using the old driver "hidusb" for I2C/SPI bridging instead of the proper driver for bulk endpoints - "winusb". To fix this issue, follow these steps:

  1. In the Device Manager, find Composite Device for the KitProg3 device.

    1. Change View to Devices by container .

    2. Find KitProg3 CMSIS-DAP or MiniProg4 CMSIS-DAP and open the container.

  2. Right click on USB Composite Device and choose Uninstall device .

  3. Click on Scan for hardware changes button.

On Windows, after upgrading to KitProg3 v2.10 in CMSIS-DAP Bulk mode, simultaneous use of the USB-I2C/SPI bridging and debugging is not possible​

Previous versions of KitProg3 implement I2C/SPI bridging using HID endpoints. In version 2.10 and later, bridging is implemented on bulk endpoints to improve performance. After the upgrade, Windows cannot use the I2C/SPI bridging interface and the CMSIS-DAP bulk interface at the same time because of a WinUSB driver limitation. If you would like to use debug and I2C/SPI bridging at the same time, there are two possible workarounds:

  • If performance for programming and debug is not critical, switch KitProg3 to CMSIS-DAP HID mode via fw-loader command.

  • If you need faster performance for programming and debug, use the onboard KitProg3 for programming purposes and MiniProg4 for bridging purposes or vice versa. Both devices can be in CMSIS-DAP bulk mode.

On Windows 10 in Bulk mode (amber status LED on), the kit is not recognized by the programming tool, and debug does not work with ModusToolbox or PSOC Creator. If I switch to HID mode, it works​

Several versions of the KitProg3 CMSIS-DAP driver may be available on your machine. Instead of using the correct driver, Windows uses a wrong or faulty driver. As a result, the kit in Bulk mode will not be recognized by programming/debug tools.

The solution is to reinstall the native driver:

  1. Open the Device Manager and go to the KitProg3 CMSIS-DAP device.
  2. Right-click the device and select Uninstall from the context menu (Select check box Delete the driver software for this device if present)
  3. After uninstalling re-plug the device.
  4. Right-click the device and select Update driver software... from the context menu.
  5. In the wizard, select Search automatically for updated driver software .

CMSIS-DAPv2 interface driver for DAPLink mode isn't installed properly on Windows 10​

It is possible to have incorrect drivers installed for the device, for example, if custom drivers were installed. Solution to this issue is to reinstall drivers:

  1. Uninstall the Mbed serial driver and the USB Composite Device Driver.

    1. In the Device Manager, select the View menu and choose the "Devices by container" option.

    2. In the list of devices, find "mbed Serial Port (COMXX)" and uninstall it.

      • Right-click the device and select Uninstall from the context menu.
      • Select the ** Delete the driver software for this device** check box, if present.

    3. c. In the list of devices, find "Device" or "DAPLink CMSIS-DAP".

      • Open it and make sure it contains the entry "DAPLINK" or "mbed Composite Device".

      • Uninstall "CMSIS-DAP v2", "USB Composite Device", and "mbed Composite Device" devices from this container.

        • Right-click the device and select Uninstall from the context menu.
        • Select the Delete the driver software for this device check box, if present)

  2. Click the Scan for Hardware Changes button in the Device Manager to install the correct drivers.

How do I recover a corrupted KitProg3 image?​

Although unlikely, it is possible to corrupt the KitProg3 image, for example, if a firmware update is interrupted.

To fix this issue, put the KitProg3 into bootloader mode. (Press the Mode switch while plugging in the kit.) Then follow the instructions for your programmer.

  • Launch ModusToolbox™ Programmer, which automatically updates the KitProg3 firmware.

    OR

  • Launch PSOC™ Programmer, and update KitProg3 firmware via Utilities > Update firmware option.

Last updated on