cancel
Showing results for 
Search instead for 
Did you mean: 

PSoC™ 6

AlMi_3827461
New Contributor II

I've just acquired a CY8CKIT-062-BLE (Rev D) and have updated to KitProg3 as indicated in the board documentation 

AlMi_3827461_0-1637757263028.png

I have tried everything I can think of to communicate with the board via CMSIS-DAP in KitProg3 mode.  (See details below)
I've deleted Windows drivers under device manager, I've tried a couple of versions of KitProg3 firmware (the one automatically installed by PsoC Programmer and latest via fw-loader from Github.  Nothing working.

Any suggestions where to go next - it is almost like my Winusb driver is wrong device Ids or something? 

Various attempts:
I have tried openocd supplied in the tools folder of ModusToolBox with the following error:

AlMi_3827461_1-1637757460581.png

I've tried PSocProgrammer which fails with "Failed Connect to at 12:38:27 | Can't Open CMSIS-DAP port"
AlMi_3827461_2-1637757534179.png

I've tried "Cypress Programmer":

AlMi_3827461_3-1637757618482.png

 

 

0 Likes
6 Replies
GrCa_1363456
Contributor II

Almi,

With PSoC Programmer, did you click on the KitProg3 under Port Selection to select that port?

You mentioned using fw-loader, a tool that comes with modustoolbox. That tool can also be used to change the mode in which the kit is communicating.

fw-loader provides some options to change the mode of the KitProg running on the boards.

After starting fw-loader by typing "fw-loader" in Windows Start menu....

Use --device-list to see your device.

Use --mode commands to change your kitprog between four communication modes. Similar to pressing the mode switch on the kit, but gives more mode options.

If these don't work, open Device Manager in Windows and look for the kit. I like to view in Container Mode. See how the kit changes in Device Manager as you change modes using fw-loader. Make sure there are no red or orange  indicators in Device Manager noting a potential issue.

Greg

0 Likes
AlMi_3827461
New Contributor II

Greg,

With PSoC Programmer, did you click on the KitProg3 under Port Selection to select that port?

 Yes  - clicking on this initiates the process of connecting which fails with "Can't open CMSIS-DAP port"

Regarding use of fw-loader tool to list device and change modes, yes - this tool works fine for changing modes but the CMSIS-DAP Kitprog3 connection never connects. either when using SW3 or via tool to select the mode.

Regarding Device Manager, there are no warnings or errors in either Kitprog3 or DAPLink mode. See images:

AlMi_3827461_0-1637766095452.png

AlMi_3827461_1-1637766114910.png

 

0 Likes
GrCa_1363456
Contributor II

AlMi,

What Revision of the kit do you have? 

There's a Rev letter of the kit on the box and a Rev # of the main board on the bottom of the PCB.

Here's my Device Manager view when kit is in CMSIS-DAP BULK mode

GrCa_1363456_0-1637767313169.png

Changing to CMSIS-DAP HID mode (using SW3 Mode Select) then looks like

GrCa_1363456_2-1637768474534.png

 

Finally, switching to CMSIS-DAP view using SW3 Mode Select  ...

GrCa_1363456_3-1637768605615.png

 

Here's the views for each mode using fw-loader.

GrCa_1363456_4-1637768725554.png

 

Greg

 

 

0 Likes
GrCa_1363456
Contributor II

Some more notes...

  • fw-loader will NOT communicate with the kit if PSoC Programmer is connected to the kit
  • After updating KitProg 3 firmware from 1.11.243 to 2.21.1005, the SW3 Mode Select no longer changes the mode of the kit. I then use the command “./fw-loader --mode <mode>” in fw-loader to change between the five modes: 'kp3-hid', 'kp3-bulk', 'kp3-bootloader', 'kp3-daplink', 'kp3-dualuart'.
  • While in CMSIS-DAP Bulk mode, I updated firmware using fw-loader from 2.21 to 2.30 using the command “./fw-loader --update-kp3”
  • Now SW3 changes modes between DAPLink CMSIS-DAP and CMSIS-DAP Bulk. PSoC Programmer will NOT communicate when kit is in DAPLink CMSIS-CAP mode.

Greg

0 Likes
AlMi_3827461
New Contributor II

Greg,


What Revision of the kit do you have? 

There's a Rev letter of the kit on the box and a Rev # of the main board on the bottom of the PCB.

The Rev on the Box is "Rev *D", The PCB label is "Rev 13" and the PCB copper etch itself is "Rev08".

I too am on KitProg3 Version 2.30

AlMi_3827461_0-1637773995639.png

What is odd, is that in KitProg3 CMSIS-DAP (BULK) mode my Device manager lists do not mirror what you have...

AlMi_3827461_1-1637774228815.png


Yours has "HID-complaint vendor-defined device + USB Input Device", mine has "KitProg3 bridge"

I'll try on a different computer tomorrow

0 Likes
AlMi_3827461
New Contributor II

I tried a different computer, everything works just fine which rules out a hardware problem. 

It turns out that when I remove my HP Zbook-15 G3 from its Thunderbolt docking station, then everything works just fine. So there is something bizzare here where the docking station USB tree causes openocd to fail during the scan for attached device as it looks for the CMSIS-DAP USB instance.  I have this workaround for now.

0 Likes
Top labels