Announcements

Help us improve the Power & Sensing Selection Guide. Share feedback

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
WeGa_288606
Level 4
Level 4
25 sign-ins 10 sign-ins 5 sign-ins

Hello, 

 

I have two CY8CPROTO-062-4343W kits both which seem to have stopped programming in either ModusToolbox (3.0) or Cypress Programmer. They were working fine. If I use DAP I can program the boards however and I can use both my KitProg3 to program a custom board we have without problems. This just happens when trying to program the PROTO boards. I can occasionally get a connection to the board but then programming still fails. I have been working with FreeRTOS, emfile, Empty Dual Core, and Hello World examples from the GitRepos.  

 

The connection to the board fails with outputs as follows:

 

WeGa_288606_0-1677094072431.png

WeGa_288606_1-1677094335382.png

 

 

 

1 Solution
LeoMathews
Moderator
Moderator
Moderator
First question asked 500 replies posted 100 solutions authored

Hi @WeGa_288606 

I have tried programming the attached hex file at my end using the same CY8CPROTO-062-4343W board. The programming was successful on my end:

LeoMathews_0-1677739623076.png

 

Can you please try programming any other hex file for the device and see if it's working? Probably the kits may be damaged. Also can you please try manually erasing the device and re-program the board again?

Thanks and Regards,
Leo

 

View solution in original post

0 Likes
11 Replies
LeoMathews
Moderator
Moderator
Moderator
First question asked 500 replies posted 100 solutions authored

Hi @WeGa_288606 

Can you please ensure that the power selection jumper(J3) used to select the PSoC 6 MCU’s supply
voltage (P6.VDD) between 1.8 V and 3.3 V is connected between pins 2 and 3? If not, please connect the pins using the jumper and try programming the board again.

LeoMathews_0-1677124871523.png

 

Thanks and Regards,
Leo

0 Likes

Hi @LeoMathews 

 

Yes the jumper is in the correct place and the behavior is the same. 

Thank you, 

Wess

0 Likes
LeoMathews
Moderator
Moderator
Moderator
First question asked 500 replies posted 100 solutions authored

Hi @WeGa_288606 

Can you please make sure the kit is properly connected via the usb cable? Please note that, if you are programming using ModusToolbox eclipse IDE, close the Cypress Programmer. The error can occur if the device is already acquired by Cypress Programmer, then the device won't be recognized by MTB. 

Thanks and Regards,
Leo 

 

0 Likes

Hi @LeoMathews 

 

Yes the kit is plugged into USB. Cypress Programmer is not simultaneously running with MTB. 

Thanks, 

Wess

0 Likes
LeoMathews
Moderator
Moderator
Moderator
First question asked 500 replies posted 100 solutions authored

Hi @WeGa_288606 

Can you please try updating the kitprog firmware using fw-loader? 

Thanks and Regards,
Leo

0 Likes

Hi @LeoMathews 

The kitprog3 firmware is already at its latest. 

0 Likes
WeGa_288606
Level 4
Level 4
25 sign-ins 10 sign-ins 5 sign-ins

Hi @LeoMathews 

Here is what I call a "luck log" output from an occasional connection to the protoboard. I cant generally get this far as because it typically stops at "Error: Error connecting DP: cannot read IDR". 

 

Started by GNU MCU Eclipse
Open On-Chip Debugger 0.11.0+dev-4.4.0.2134 (2022-09-08-13:07)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
kitprog3 set_latest_version: C:/Users/...../ModusToolbox/tools_3.0/fw-loader 2.40.1241
adapter speed: 2000 kHz
adapter srst delay: 25
adapter srst pulse_width: 25
** Auto-acquire enabled, use "set ENABLE_ACQUIRE 0" to disable
cortex_m reset_config sysresetreq
cortex_m reset_config sysresetreq
Info : Using CMSIS-flash algorithms 'CY8C6xxA_SMIF' for bank 'psoc6_smif0_cm0' (footprint 17056 bytes)
Info : CMSIS-flash: ELF path: ../flm/cypress/cat1a/CY8C6xxA_SMIF.FLM
Info : CMSIS-flash: Address range: 0x18000000-0x1FFFFFFF
Info : CMSIS-flash: Program page size: 0x00001000 bytes
Info : CMSIS-flash: Erase sector size: 0x00040000 bytes, unified
Warn : SFlash programming allowed for regions: USER, TOC, KEY
Info : Using CMSIS-DAPv2 interface with VID:PID=0x04b4:0xf155, serial=0A0C10F301237400
Info : CMSIS-DAP: SWD supported
Info : CMSIS-DAP: Atomic commands supported
Info : CMSIS-DAP: FW Version = 2.0.0
Info : CMSIS-DAP: Interface Initialised (SWD)
Info : SWCLK/TCK = 1 SWDIO/TMS = 1 TDI = 0 TDO = 0 nTRST = 0 nRESET = 1
Info : CMSIS-DAP: Interface ready
Info : KitProg3: FW version: 2.40.1241
Info : KitProg3: Pipelined transfers enabled
Info : KitProg3: Asynchronous USB transfers enabled
Info : VTarget = 3.326 V
Info : kitprog3: acquiring the device (mode: reset)...
Info : clock speed 2000 kHz
Info : SWD DPIDR 0x6ba02477
Info : [psoc6.cpu.cm0] Cortex-M0+ r0p1 processor detected
Info : [psoc6.cpu.cm0] target has 4 breakpoints, 2 watchpoints
Info : [psoc6.cpu.cm0] external reset detected
***************************************
** Silicon: 0xE402, Family: 0x102, Rev.: 0x11 (A0)
** Detected Device: CY8C624ABZI-D44
** Detected Main Flash size, kb: 2048
** Flash Boot version: 3.1.0.45
** Chip Protection: VIRGIN
***************************************
Info : [psoc6.cpu.cm4] Cortex-M4 r0p1 processor detected
Info : [psoc6.cpu.cm4] target has 6 breakpoints, 4 watchpoints
Info : [psoc6.cpu.cm4] external reset detected
Info : starting gdb server for psoc6.cpu.cm0 on 3333
Info : Listening on port 3333 for gdb connections
Info : starting gdb server for psoc6.cpu.cm4 on 3334
Info : Listening on port 3334 for gdb connections
Error: Error connecting DP: cannot read IDR
Error: [psoc6.cpu.cm0] DP initialisation failed
Error: Error connecting DP: cannot read IDR
Error: Error connecting DP: cannot read IDR
Info : kitprog3: acquiring the device (mode: reset)...
Info : SWD DPIDR 0x6ba02477
Info : [psoc6.cpu.cm0] external reset detected
psoc6.cpu.cm0 halted due to debug-request, current mode: Thread
xPSR: 0x81000000 pc: 0x10000d56 msp: 0x08001fd8
** Device acquired successfully
** psoc6.cpu.cm4: Ran after reset and before halt...
psoc6.cpu.cm4 halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x10002a18 msp: 0x080ff7c8
Started by GNU MCU Eclipse
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : accepting 'gdb' connection on tcp/3333
Info : New GDB Connection: 1, Target psoc6.cpu.cm0, state: halted
Warn : Prefer GDB command "target extended-remote :3333" instead of "target remote :3333"
Verifying region (0x10000000, 15792)... Mismatch
Info : Data mismatch, proceeding with flash programming
Info : Flash write discontinued at 0x10003db0, next section at 0x10008000
Info : Padding image section 0 at 0x10003db0 with 80 bytes (bank write end alignment)

[ 48%] [############### ] [ Erasing ]Error: timeout waiting for algorithm, a target reset is recommended
Error: SROM API execution failed. Status: 0x080008D0
Error: failed erasing sectors 0 to 30
Error: [psoc6.cpu.cm0] clearing lockup after double fault
Polling target psoc6.cpu.cm0 failed, trying to reexamine
Info : [psoc6.cpu.cm0] Cortex-M0+ r0p1 processor detected
Info : [psoc6.cpu.cm0] target has 4 breakpoints, 2 watchpoints
Error: Error connecting DP: cannot read IDR
Error: [psoc6.cpu.cm0] DP initialisation failed
Error: Error connecting DP: cannot read IDR
Error: Error connecting DP: cannot read IDR
Info : kitprog3: acquiring the device (mode: reset)...
Info : SWD DPIDR 0x6ba02477
Info : [psoc6.cpu.cm0] external reset detected
psoc6.cpu.cm0 halted due to debug-request, current mode: Thread
xPSR: 0x81000000 pc: 0x10000d56 msp: 0x08001fd8
** Device acquired successfully
** psoc6.cpu.cm4: Ran after reset and before halt...
psoc6.cpu.cm4 halted due to debug-request, current mode: Thread
xPSR: 0x21000000 pc: 0x10002a16 msp: 0x080ff7c8
Info : dropped 'gdb' connection

0 Likes
LeoMathews
Moderator
Moderator
Moderator
First question asked 500 replies posted 100 solutions authored

HI @WeGa_288606 

Can you please send me the hex file you used to program the board? I'll try the same from my end to understand the issue.

Thanks and Regards,
Leo

0 Likes
lock attach
Attachments are accessible only for community members.

Hi @LeoMathews 

Please find zip of hex attached. 

This is the primary error when the programmer attaches to the device at all:

 

Open On-Chip Debugger 0.11.0+dev-4.4.0.2134 (2022-09-08-13:07)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
kitprog3 set_latest_version: C:/Users/..../ModusToolbox/tools_3.0/fw-loader 2.40.1241
adapter speed: 2000 kHz
adapter srst delay: 25
adapter srst pulse_width: 25
** Auto-acquire enabled, use "set ENABLE_ACQUIRE 0" to disable
cortex_m reset_config sysresetreq
cortex_m reset_config sysresetreq
Info : Using CMSIS-DAPv2 interface with VID:PID=0x04b4:0xf155, serial=0A0C10F301237400
Info : CMSIS-DAP: SWD supported
Info : CMSIS-DAP: Atomic commands supported
Info : CMSIS-DAP: FW Version = 2.0.0
Info : CMSIS-DAP: Interface Initialised (SWD)
Info : SWCLK/TCK = 1 SWDIO/TMS = 1 TDI = 0 TDO = 0 nTRST = 0 nRESET = 1
Info : CMSIS-DAP: Interface ready
Info : KitProg3: FW version: 2.40.1241
Info : KitProg3: Pipelined transfers enabled
Info : KitProg3: Asynchronous USB transfers enabled
Info : VTarget = 3.329 V
Info : kitprog3: acquiring the device (mode: reset)...
Info : clock speed 2000 kHz
Info : SWD DPIDR 0x6ba02477
Warn : target psoc6.cpu.cm0 examination failed
Info : SWD DPIDR 0x6ba02477
Warn : target psoc6.cpu.cm4 examination failed
Info : starting gdb server for psoc6.cpu.cm0 on 3333
Info : Listening on port 3333 for gdb connections
Info : starting gdb server for psoc6.cpu.cm4 on 3334
Info : Listening on port 3334 for gdb connections
Info : SWD DPIDR 0x6ba02477
Info : SWD DPIDR 0x6ba02477
Error: [psoc6.cpu.cm0] Target not examined, reset NOT asserted!

Info : psoc6.dap: powering down debug domain...
Info : SWD DPIDR 0x6ba02477

0 Likes
LeoMathews
Moderator
Moderator
Moderator
First question asked 500 replies posted 100 solutions authored

Hi @WeGa_288606 

I have tried programming the attached hex file at my end using the same CY8CPROTO-062-4343W board. The programming was successful on my end:

LeoMathews_0-1677739623076.png

 

Can you please try programming any other hex file for the device and see if it's working? Probably the kits may be damaged. Also can you please try manually erasing the device and re-program the board again?

Thanks and Regards,
Leo

 

0 Likes
LeoMathews
Moderator
Moderator
Moderator
First question asked 500 replies posted 100 solutions authored

Hi @WeGa_288606 ,

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,
Leo

0 Likes