PSOC 6 WiFi BT Prototyping Kit error programming

[EvanK4]

Hello, My PSOC 6 WiFi BT Prototyping Kit cannot be programmed on Modus Toolbox.

It previously had worked without hassle but recently keeps giving errors such as:

Error: kitprog3: failed to acquire the device

Error: Error connecting DP: cannot read IDR

Error: DAP 'psoc6.cpu' initialization failed (check connection, power, transport, DAP is enabled etc.

I have tried everything but cannot seem to get it working! 

Any help would be much appreciated ASAP.

* KitProg firmware is out of date, please update to the latest version (2.30.1155)
* using fw-loader tool which can be found in the following folder
* C:/Users/EKene/ModusToolbox/tools_2.4/fw-loader

I have also tried this but am also getting errors within the fw-loader, but also keep getting errors here.

Whenever i enter a command, for example: '--device-list' it returns:

'bash: --device-list: command not found' 

Anybody got any recommendations?

Thank you,

Evan.

[AlenAn14]

Hi @EvanK4 ,

You have to use the '--device-list' as an argument with the command fw-loader. Please follow the below steps to use fw-loader to update the KitProg3 firmware:

1. Open 'Modus-Shell' from the windows search bar and navigate to the folder for fw-loader using the command "cd <path to fw-loader>".
In your case , this will be 

cd 'C:/Users/EKene/ModusToolbox/tools_2.4/fw-loader/bin"

2. Once here, enter the following command to see a list of connected devices

./fw-loader --device-list

  
3. To upgrade the KitProg3 firmware, use the following command

./fw-loader --update-kp3

Hope this helps

Warm Regards
Alen

[EvanK4]

Hi @AlenAn14, thanks for the reply!

That has worked perfectly for updating the KitProg3, thank you very much!

Now that the KitProg3 is updated, it is still showing errors when programming the application on modustoolbox as shown below:

Info : kitprog3: acquiring the device (mode: reset)...
Error: kitprog3: failed to acquire the device
Info : clock speed 2000 kHz
Error: Error connecting DP: cannot read IDR
Error: Error connecting DP: cannot read IDR
Error: Error connecting DP: cannot read IDR
Error: DAP 'psoc6.cpu' initialization failed (check connection, power, transport, DAP is enabled etc.)
Info : Power dropout detected, running power_dropout proc.
Power dropout, target voltage: 0.102 mV
** OpenOCD init failed **
shutdown command invoked
** Program operation failed **
srst_only separate srst_gates_jtag srst_open_drain connect_deassert_srst
Error: Error connecting DP: cannot read IDR
Error: Error connecting DP: cannot read IDR
Error: Error connecting DP: cannot read IDR
Error executing event reset-deassert-post on target psoc6.cpu.cm0:
C:/Users/EKene/ModusToolbox/tools_2.4/openocd/bin/../scripts/target/mxs40/mxs40_common.cfg:115: Error:
in procedure 'ocd_process_reset'
in procedure 'ocd_process_reset_inner' called at file "embedded:startup.tcl", line 788
in procedure 'mxs40_reset_deassert_post' called at file "C:/Users/EKene/ModusToolbox/tools_2.4/openocd/bin/../scripts/target/mxs40/psoc6_common.cfg", line 134
at file "C:/Users/EKene/ModusToolbox/tools_2.4/openocd/bin/../scripts/target/mxs40/mxs40_common.cfg", line 115
Error: Error connecting DP: cannot read IDR
Error executing event reset-deassert-post on target psoc6.cpu.cm4:
C:/Users/EKene/ModusToolbox/tools_2.4/openocd/bin/../scripts/target/mxs40/mxs40_common.cfg:115: Error:
in procedure 'ocd_process_reset'
in procedure 'ocd_process_reset_inner' called at file "embedded:startup.tcl", line 788
in procedure 'mxs40_reset_deassert_post' called at file "C:/Users/EKene/ModusToolbox/tools_2.4/openocd/bin/../scripts/target/mxs40/psoc6_common.cfg", line 169
at file "C:/Users/EKene/ModusToolbox/tools_2.4/openocd/bin/../scripts/target/mxs40/mxs40_common.cfg", line 115
Info : Power dropout detected, running power_dropout proc.
Power dropout, target voltage: 0.103 mV
Error: Error connecting DP: cannot read IDR
Info : psoc6.dap: powering down debug domain...
Error: Error connecting DP: cannot read IDR
Error: Error connecting DP: cannot read IDR
Warn : Failed to power down Debug Domains

Any idea what might be the problem?

Appreciate the help,

Regards,

Evan.

[AlenAn14]

Hi @EvanK4 ​

Can you please check if the power monitoring jumper, J8 (bottom layer of the board) is in place? Also verify if the Vbackup switch, SW7 is set to VDD/KitProg instead of SuperCap.

I noticed the line "Power dropout, target voltage: 0.103 mV" in the logs you have shared.
Do you have any additional connections to the board when performing the programming or only the KitProg C-Type USB is connected to the board?

Please measure the actual voltage on the VDD line and verify that it is 3.3V.

One additional test is to use Cypress programmer and try to acquire the device. This will indicate if it is an MTB issue or a hardware bug.

Warm Regards
Alen

[AlenAn14]

Hi @EvanK4 ,

Thread was locked due to inactivity for long time, you can continue the discussion on the topic by opening a new thread with reference to the locked one. The continuous discussion in an inactive thread may mostly be unattended by community users.

Thanks and Regards,
Alen