Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
Problem: When KitProg3 is in CMSIS-DAP Bulk mode, it is not possible to debug (for example, in ModusToolbox, PSoC Creator) and use USB-I2C/SPI bridging (for example, in CapSense® Tuner, Bridge Control Panel) at the same time. This affects the Windows only. It does not affect Linux or macOS users.
Background: Previous versions of KitProg3 implemented USB-I2C/SPI bridging using HID endpoints. In version 2.10 and newer, bridging is implemented on bulk endpoints for improved performance over I2C/SPI. However, Windows cannot use the USB-I2C/SPI bridging interface and the CMSIS-DAP bulk interface at the same time because of a WinUSB driver limitation.
Solution: If you would like to use debug and USB-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 the fw-loader utility. Firmware Loader is installed with ModusToolbox software, and is available separately on GitHub.
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.