cancel
Showing results for 
Search instead for 
Did you mean: 

PSoC 6 MCU

David_Zhang
New Contributor II

Hi  Cypress:

   when we use  kitprog3 to programmer pso62 mcu , but it show error as below:  please advice it ;

Error Logo:

Open On-Chip Debugger 0.10.0+dev-4.1.0.1058 (2020-08-11-03:47)

Licensed under GNU GPL v2

For bug reports, read

http://openocd.org/doc/doxygen/bugs.html

Info : auto-selecting first available session transport "swd". To override use 'transport select <transport>'.

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 loader 'CY8C6xxA_SMIF' for bank 'psoc6_smif0_cm0' (footprint 14672 bytes)

Warn : SFlash programming allowed for regions: USER, TOC, KEY

Info : CMSIS-DAP: SWD  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: 1.21.707

Warn :

*******************************************************************************************

* KitProg firmware is out of date, please update to the latest version (2.10.878)

* using fw-loader tool which can be found in the following folder

* C:/Users/a89114/ModusToolbox/tools_2.2/fw-loader

*******************************************************************************************

Info : KitProg3: Pipelined transfers enabled

Info : VTarget = 2.834 V

Info : kitprog3: acquiring the device...

Info : clock speed 2000 kHz

Info : SWD DPIDR 0x6ba02477

Info : SWD DPIDR 0x6ba02477

Error: Failed to write memory at 0xe000ee00

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

***************************************

** Silicon: 0xE455, Family: 0x102, Rev.: 0x12 (A1)

** Detected Device: CY8C624AFNI-S2D43

** Detected Main Flash size, kb: 2048

** Flash Boot version: 3.1.0.378

** Chip Protection: NORMAL

***************************************

Info : psoc6.cpu.cm4: hardware has 6 breakpoints, 4 watchpoints

Info : SWD DPIDR 0x6ba02477

Info : AP write error, reset will not halt

Info : SWD DPIDR 0x6ba02477

Info : SWD DPIDR 0x6ba02477

in procedure 'program'

Info : psoc6.cpu.cm4: external reset detected

** Program operation failed **

Polling target psoc6.cpu.cm0 failed, trying to reexamine

Info : SWD DPIDR 0x6ba02477

Info : SWD DPIDR 0x6ba02477

Error: Failed to write memory at 0xe000ee00

Examination failed, GDB will be halted. Polling again in 100ms

srst_only separate srst_gates_jtag srst_open_drain connect_deassert_srst

Info : SWD DPIDR 0x6ba02477

Info : SWD DPIDR 0x6ba02477

Info : SWD DPIDR 0x6ba02477

Info : SWD DPIDR 0x6ba02477

Error executing event reset-deassert-post on target psoc6.cpu.cm0:

C:/Users/a89114/ModusToolbox/tools_2.2/openocd/bin/../scripts/target/mxs40/mxs40_common.cfg:99: Error:

in procedure 'ocd_process_reset'

in procedure 'ocd_process_reset_inner' called at file "embedded:startup.tcl", line 279

in procedure 'mxs40_reset_deassert_post' called at file "C:/Users/a89114/ModusToolbox/tools_2.2/openocd/bin/../scripts/target/mxs40/psoc6_common.cfg", line 128

at file "C:/Users/a89114/ModusToolbox/tools_2.2/openocd/bin/../scripts/target/mxs40/mxs40_common.cfg", line 99

Info : SWD DPIDR 0x6ba02477

Polling target psoc6.cpu.cm0 failed, trying to reexamine

Info : SWD DPIDR 0x6ba02477

Error: Failed to write memory at 0xe000ee00

Examination failed, GDB will be halted. Polling again in 100ms

Polling target psoc6.cpu.cm0 failed, trying to reexamine

Info : SWD DPIDR 0x6ba02477

Info : SWD DPIDR 0x6ba02477

Error: Failed to write memory at 0xe000ee00

Examination failed, GDB will be halted. Polling again in 300ms

shutdown command invoked

Info : psoc6.dap: powering down debug domain...

0 Likes
1 Solution
MiDa_1966691
New Contributor II

@David_Zhang,

I recently had the same issue: 
I removed the Kitprog3 and placed a header on it to use as a standalone programmer
– I was using ( PSoC 6 BLE Prototyping Kit (CY8CPROTO-063-BLE).

KitProg3 - SWD lines -

I was able to program cypress DVK on the other end of  with the KitProg3 , but when I tried to program a external board using a different device it would not even see the silicon ID.

Solution that worked for me:

I see from your message your  programmer is at:

nfo : KitProg3: FW version: 1.21.707

In the message it is asking you to upgrade : to a newer version

*******************************************************************************************

* KitProg firmware is out of date, please update to the latest version (2.10.878)

* using fw-loader tool which can be found in the following folder

* C:/Users/a89114/ModusToolbox/tools_2.2/fw-loader

*******************************************************************************************

Note: My KitProg3 was at an older firmware version too .

           I updated my KitProg3 to the latest firmware version – and then was able to program my external device.

I’m not sure what changed from - KitProg3: FW version: 1.21.707 – to latest version (2.10.878)

But it worked for me:

I think it must have something to do with the Cypress programmer and vectors for the PSOC6 devices not in the previous KitProg 3  firmware version.

 – Since I looked with a logic analyzer and I could see the handshake happening even when it was not working.

Update your Kitpro3 programmer to the newest firmware rev and I think that will fix your issue.

BTW:  I  was using  ModusToolbox and the Cypress programmer –

Hope that helps

-Mike

View solution in original post

0 Likes
2 Replies
Rakshith
Moderator
Moderator

Hi @David_Zhang ,

 

From the logs, I see that you are programming using ModusToolbox. Can you please confirm the same? 

Did you try programming a standard PSoC 6 Dev Kit? Were you able to successfully program in this case?

Also, can you please let me know the steps that you followed in creating a custom BSP?

Thanks and Regards,
Rakshith M B
0 Likes
MiDa_1966691
New Contributor II

@David_Zhang,

I recently had the same issue: 
I removed the Kitprog3 and placed a header on it to use as a standalone programmer
– I was using ( PSoC 6 BLE Prototyping Kit (CY8CPROTO-063-BLE).

KitProg3 - SWD lines -

I was able to program cypress DVK on the other end of  with the KitProg3 , but when I tried to program a external board using a different device it would not even see the silicon ID.

Solution that worked for me:

I see from your message your  programmer is at:

nfo : KitProg3: FW version: 1.21.707

In the message it is asking you to upgrade : to a newer version

*******************************************************************************************

* KitProg firmware is out of date, please update to the latest version (2.10.878)

* using fw-loader tool which can be found in the following folder

* C:/Users/a89114/ModusToolbox/tools_2.2/fw-loader

*******************************************************************************************

Note: My KitProg3 was at an older firmware version too .

           I updated my KitProg3 to the latest firmware version – and then was able to program my external device.

I’m not sure what changed from - KitProg3: FW version: 1.21.707 – to latest version (2.10.878)

But it worked for me:

I think it must have something to do with the Cypress programmer and vectors for the PSOC6 devices not in the previous KitProg 3  firmware version.

 – Since I looked with a logic analyzer and I could see the handshake happening even when it was not working.

Update your Kitpro3 programmer to the newest firmware rev and I think that will fix your issue.

BTW:  I  was using  ModusToolbox and the Cypress programmer –

Hope that helps

-Mike

View solution in original post

0 Likes
Top labels