Other things I have tried:
Plugged both boards into computer at the same time and compared properties of KitProg2 via windows device manager. The only difference is install date. All other pertinent info is the same (version, etc).
On my untouched board, the one that still works, led4 (power) is the only led that is lit. When the problem boards are in this same configuration they produce the error.
The plot thickens. See psoc programmer image below. Under Port Selection there are two entries. The first one is for the board that works. The second one is for the board that does not work.
The following warning pops up whenever I plug any board in while psoc programmer is running. The update firmware button is always disabled.
Just to clarify, I am not using psoc programmer to program. Just to help debug this issue.
On the CY8CKIT062-WIFI BT board, there is a mode select switch (S3). Press the SW3 button on your board. After this, LED2 and LED4 will be lit. You will be able to program your board in WICED since the kit is now in HID Mode.
You can use fw-loader(Firmware Loader) from Modus Toolbox 2.1 release.You can display the list of your connected devices and can get the information of the mode of your connected device using this fw-loader by using the command fw-loader --device-list. Could you please check this command and attach the screenshot of the same?
Here are both boards with LEDs 2 and 4 lit:
Neither board can be programmed in this configuration. Both return this error: "**** OpenOCD failed..."
This is the same error returned when no boards are plugged in. This has to be an important clue.
Here are both boards with only LED4 lit:
The good board (1719...) can be programmed just fine.
The bad board (1C21...) returns "**** OpenOCD failed..." as if the board is not recognised or not plugged in at all.
See image I posted on April 22, 2020 7:58 AM for complete error.
First of all, I tried programming a WICED Project with KitProg3 HID mode (LED4 will be lit and LED2 will function as a breathing LED) and it works fine. To toggle to HID mode without pressing SW3, in the FW-loader, use the command fw-loader --mode kp3-hid.
Second, I could not see any issues with toggling between KitProg 3 and KitProg 2. KitProg2 HID mode appears as a mass storage device (like a USB drive - KitProg2 (D:)). If you view the Device Manager by 'Devices by connection', the KitProg 2 HID appears like the image shown below.
As AditiB_81 mentioned, WICED projects can be programmed only in HID mode (Correction: Only LED4 will be lit)
When using kitProg3 I can't get only LED4 to be lit. I have tried with SW3 and fw-loader. The modes do appear to change according to "fw-loader --device-list", however, LED4 is never the only LED lit. When downloading with kitProg3 the error is always the same as illustrated in my Apr 22, 2020 7:58 AM post.
Only LED 4 is lit. Still get same error. Our device managers are very different. Am I missing a driver?
The device manager when using my good board is exactly the same as when using bad board.
For KP3, the HID mode is indicated by breathing LED2 (at 1Hz). For KP2 HID, LED2 will not be lit.
I can see the drivers remain the same. Thanks for confirmation.
So, in KP3, there are three modes present - CMSIS-DAP BULK, CMSIS-DAP HID and an other mode called DAP-LINK. the DAP-LINK is a custom application downloaded into the KitProg.
In KP2, only two modes present in which one of them is in HID. But when you try to transition from KP3 to KP2, the custom application DAP-LINK is unaffected. If you have downgraded your kit to KP2, you can switch to DAP-LINK by pressing SW4.
Now, I want you to do two things,
First, when in KP3 - Try the command fw-loader --mode kp3-daplink on the command line. Then try downloading the application.
Second, when in KP2, Press the switch SW4. Now, try downloading the FW and let me know if any of the two steps work.
You can try programming your WICED application with Kitprog2 CMSIS-DAP HID mode. I downgraded to Kitprog2 from Kitprog3 using fw-loader and I can successfully build the code. You can try the following steps to build your application successfully.
Following your sequence of steps:
--> Upgraded to Kitprog3 using fw-loader for MODUS applications.
-->Downgraded to kitprog2 using fw-loader for WICED applications.
--> Change to Kitprog2 CMSIS-DAP HID mode for building WICED applications by pressing SW3. After this check for the mode through fw-loader using the command fw-loader --device-list. Only LED4 will be lit on the board.
--> Build your application in WICED. I am attaching the build log and openocd.txt files.