CY8CPROTO-062-4343W nicht Programierbat mit ModusToolbox

ChRi_4015166 · ‎Oct 30, 2020

Ich bin nicht in der lage, mit der ModusToolbox das HelloWorld-Programm in das Board zu bekommen...

Komischerweise funktioniert es im Debug, aber es muss ja auch irgendwie ohne laufendes Debugging gehen...

Gibt es eine möglichkeit, dieses Board im PSoC-Creator zu programieren?

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

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 = 1.2.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/strom/ModusToolbox/tools_2.2/fw-loader

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

Info : KitProg3: Pipelined transfers enabled

Info : VTarget = 3.328 V

Info : kitprog3: acquiring the device...

Info : clock speed 2000 kHz

Info : SWD DPIDR 0x6ba02477

Info : psoc6.cpu.cm0: hardware has 4 breakpoints, 2 watchpoints

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

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

** Detected Device: CY8C624ABZI-S2D44

** 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 : 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 : kitprog3: acquiring the device...

psoc6.cpu.cm0 halted due to debug-request, current mode: Thread

xPSR: 0x41000000 pc: 0x00000190 msp: 0x080ff800

** 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: 0x0000012a msp: 0x080ff800

** Programming Started **

auto erase enabled

Info : Flash write discontinued at 0x1000179c, next section at 0x10002000

Info : Padding image section 0 at 0x1000179c with 100 bytes (bank write end alignment)

[100%] [################################] [ Erasing ]

[100%] [################################] [ Programming ]

Info : Padding image section 1 at 0x1000cf1c with 228 bytes (bank write end alignment)

[ 17%] [##### ] [ Erasing ]

[ 19%] [###### ] [ Erasing ]

[ 22%] [####### ] [ Erasing ]

[ 26%] [######## ] [ Erasing ]

[ 29%] [######### ] [ Erasing ]

[ 32%] [########## ] [ Erasing ]

[ 36%] [########### ] [ Erasing ]

[ 39%] [############ ] [ Erasing ]

[ 43%] [############# ] [ Erasing ]

[ 44%] [############## ] [ Erasing ]

[ 47%] [############### ] [ Erasing ]

[ 50%] [################ ] [ Erasing ]

[ 54%] [################# ] [ Erasing ]

[ 57%] [################## ] [ Erasing ]

[ 60%] [################### ] [ Erasing ]

[ 64%] [#################### ] [ Erasing ]

[ 68%] [##################### ] [ Erasing ]

[ 71%] [###################### ] [ Erasing ]

[ 72%] [####################### ] [ Erasing ]

[ 75%] [######################## ] [ Erasing ]

[ 81%] [######################### ] [ Erasing ]

[ 85%] [########################### ] [ Erasing ]

[ 88%] [############################ ] [ Erasing ]

[ 93%] [############################# ] [ Erasing ]

[ 95%] [############################## ] [ Erasing ]

[ 98%] [############################### ] [ Erasing ]

[100%] [################################] [ Erasing ]

[ 65%] [#################### ] [ Programming ]

[ 67%] [##################### ] [ Programming ]

[ 79%] [######################### ] [ Programming ]

[100%] [################################] [ Programming ]

wrote 51200 bytes from file C:/Users/strom/mtw/Hello_World_3/build/CY8CPROTO-062-4343W/Debug/mtb-example-psoc6-hello-world.hex in 2.617481s (19.102 KiB/s)

** Programming Finished **

** Program operation completed successfully **

srst_only separate srst_gates_jtag srst_open_drain connect_deassert_srst

Info : SWD DPIDR 0x6ba02477

shutdown command invoked

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

Rakshith · ‎Nov 09, 2020

Hi ChRi_4015166,

I programmed the hex file that you shared and I also did not see the LED blinking. Can you please try programming the attached hex file and let me know if that works?

If it works, can you try clicking on Generate Launches in your application and then programming the device? If still, you do not see the LED blinking in your application, please share the application on this thread or create a new workspace and let me know if the issue persists.

Thanks and Regards,

Rakshith M B

Thanks and Regards,
Rakshith M B

View solution in original post

Rakshith · ‎Nov 01, 2020

Hi ChRi_4015166,

Gibt es eine möglichkeit, dieses Board im PSoC-Creator zu programieren?

No, PSoC Creator cannot be used to program CY8CPROTO-062-4343W.

Nein, PSoC Creator kann nicht zum Programmieren von CY8CPROTO-062-4343W verwendet werden.

Ich bin nicht in der lage, mit der ModusToolbox das HelloWorld-Programm in das Board zu bekommen...
Komischerweise funktioniert es im Debug, aber es muss ja auch irgendwie ohne laufendes Debugging gehen...

According to the logs that you have provided, it is able to successfully program the device. Can you please let me know your observations when you program your device? Also, you mentioned that you are able to debug the device. Can you reset the device after debugging? Is the program getting executed as expected?

Gemäß den von Ihnen bereitgestellten Protokollen kann das Gerät erfolgreich programmiert werden. Können Sie mir bitte Ihre Beobachtungen mitteilen, wenn Sie Ihr Gerät programmieren? Außerdem haben Sie erwähnt, dass Sie das Gerät debuggen können. Können Sie das Gerät nach dem Debuggen zurücksetzen? Wird das Programm wie erwartet ausgeführt?

Thanks and Regards,

Rakshith M B

Thanks and Regards,
Rakshith M B

Kenshow · ‎Nov 01, 2020

Hi,

Instructions for updating the firmware are displayed.

Why don't you try this?

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/strom/ModusToolbox/tools_2.2/fw-loader

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

Regards,

Kenshow

ChRi_4015166 · ‎Nov 02, 2020

I have updated the firmware in the meantime. Nevertheless the problem still exists.

Debugging works, but the normal download of the program does not work. After the posted log nothing happens on the board, not even after a reset. Debugging works also only with the HelloWorld program, with a CapSense for example not.

I will solder a 10pin header at work tomorrow and try to program it with a JLink.

Thanks

Kenshow · ‎Nov 03, 2020

Hi,

It's a pity that updating the firmware didn't help.

By using JLink, I hope you will be able to fine whether this is an emulation issue or a device issue.

Regards,

Kenshow

ChRi_4015166 · ‎Nov 04, 2020

An attempt to flash Hello World with the JLink produced the following output...

J-Link GDB Server failed:
Device name 'CY8C6xxA_CM0p_sect256KB_tm' not recognised. Please check http://www.segger.com/supported-devices.html for the supported device names.

Do I have to change any variables or set up devices manually?

I have not made any changes in the setup, a demo from the BSP should run on a demo board just like that...

Sorry, but ModusToolbox seems to me to be very contra intuitive...

Log:

Strict limitation error. Please check for correct device name and settings.SEGGER J-Link GDB Server V6.40 Command Line Version
JLinkARM.dll V6.40 (DLL compiled Oct 26 2018 15:06:02)
Command line: -if swd -device CY8C6xxA_CM0p_sect256KB_tm -endian little -speed auto -port 2331 -swoport 2332 -telnetport 2333 -vd -ir -localhostonly 1 -singlerun -strict -timeout 0 -nogui
-----GDB Server start settings-----
GDBInit file:                  none
GDB Server Listening port:     2331
SWO raw output listening port: 2332
Terminal I/O port:             2333
Accept remote connection:      localhost only
Generate logfile:              off
Verify download:               on
Init regs on start:            on
Silent mode:                   off
Single run mode:               on
Target connection timeout:     0 ms
------J-Link related settings------
J-Link Host interface:         USB
J-Link script:                 none
J-Link settings file:          none
------Target related settings------
Target device:                 CY8C6xxA_CM0p_sect256KB_tm
Target interface:              SWD
Target interface speed:        auto
Target endian:                 little
Connecting to J-Link...
J-Link is connected.
Failed to set device (CY8C6xxA_CM0p_sect256KB_tm). Unknown device selected?ERROR : Failed to set device.
GDBServer will be closed...
Shutting down...

Rakshith · ‎Nov 08, 2020

Hi ChRi_4015166,

Can you please try using the Cypress Programmer, connect to the device, and perform a read to log operation? If that works can you please try programming the hex/elf file using Cypress Programmer?

Also, can you please attach the hex file that you are using so that I can program the device from my end and let me know my observations?

Sorry, but ModusToolbox seems to me to be very contra intuitive...

I apologize for the inconvenience caused. Using ModusToolbox should be easy and direct, or at least we are trying to make it that way. If it turns out to be an issue with the tool, then we will definitely try to fix the issue from our end.

Thanks and Regards,

Rakshith M B

Thanks and Regards,
Rakshith M B

ChRi_4015166 · ‎Nov 08, 2020

Hi RakshithM_16,

Here the Log from the Programmer after Connect to the Board:

Info : [CyBridge] Start API initialization
Info : [CyBridge] Hardware initialization complete (1850 ms)
Info : Connected - KitProg3 CMSIS-DAP BULK-1320156503068400 FW Version 2.10.878
Info : Selected Device: CY8CPROTO-062-4343W-1320156503068400
Info : Reading SMIF configuration from file: mtb-example-psoc6-hello-world.elf
Warn : Failed to parse SMIF configuration: Sflash section not found in ELF image
Info : Detecting SMIF configuration from target device
Warn : Could not detect SMIF regions for device: CY8CPROTO-062-4343W_external/PSoC 61/62/63
Info : ** Probe-config: kit_CY8CPROTO-062-4343W_external.cfg
Info : Open On-Chip Debugger 0.10.0+dev-3.0.0.665 (2020-03-20-10:13)
Info : Licensed under GNU GPL v2
Info : For bug reports, read
Info : http://openocd.org/doc/doxygen/bugs.html
Info : debug_level: 2
Info : adapter speed: 1500 kHz
Info : serial: 1320156503068400
Info : transport: swd
Info : rst type: xres
Info : efuse: off
Info : sflash restrict: 0
Info : adapter speed: 2000 kHz
Info : ** Auto-acquire enabled, use "set ENABLE_ACQUIRE 0" to disable
Info : cortex_m reset_config sysresetreq
Info : cortex_m reset_config sysresetreq
Info : srst_only separate srst_gates_jtag srst_open_drain connect_deassert_srst
Info : SFlash programming disallowed, see 'sflash_restrictions' command
Info : Using CMSIS loader 'CY8C6xxA_SMIF' for bank 'psoc6_smif0_cm0' (footprint 6485 bytes)
Info : tcl server disabled
Info : Listening on port 4445 for telnet connections
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: 2.10.878
Info : KitProg3: Pipelined transfers enabled
Info : VTarget = 3.326 V
Info : kitprog3: acquiring PSoC device...
Info : clock speed 2000 kHz
Info : SWD DPIDR 0x6ba02477
Info : psoc6.cpu.cm0: hardware has 4 breakpoints, 2 watchpoints
Info : psoc6.cpu.cm0: external reset detected
Info : ***************************************
Info : ** Silicon: 0xE453, Family: 0x102, Rev.: 0x12 (A1)
Info : ** Detected Device: CY8C624ABZI-S2D44
Info : ** Detected Main Flash size, kb: 2048
Info : ** Flash Boot version: 3.1.0.378
Info : ** Chip Protection: NORMAL
Info : ***************************************
Info : psoc6.cpu.cm4: hardware has 6 breakpoints, 4 watchpoints
Info : psoc6.cpu.cm4: external reset detected
Info : Listening on port 3333 for gdb connections
Info : Listening on port 3334 for gdb connections
Info : accepting 'telnet' connection on tcp/4445
Info : Open On-Chip Debugger
Info : init_target
Info : SWD DPIDR 0x6ba02477
Info : kitprog3: acquiring PSoC device...
Info : target halted due to debug-request, current mode: Thread
Info : xPSR: 0x41000000 pc: 0x00000190 msp: 0x080ff800
Info : ** Device acquired successfully
Info : ** psoc6.cpu.cm4: Ran after reset and before halt...
Info : target halted due to debug-request, current mode: Thread
Info : xPSR: 0x01000000 pc: 0x0000012a msp: 0x080ff800
Info : flash 'psoc6_2m' found at 0x10000000
Info : flash 'psoc6_2m' found at 0x14000000
Info : flash 'psoc6_2m' found at 0x16000000
Info : flash 'psoc6_2m_efuse' found at 0x90700000
Info : flash 'cmsis_flash' found at 0x18000000
Info : #0 : psoc6_main_cm0 (psoc6_2m) at 0x10000000, size 0x00200000, buswidth 4, chipwidth 4
Info : #1 : psoc6_work_cm0 (psoc6_2m) at 0x14000000, size 0x00008000, buswidth 4, chipwidth 4
Info : #2 : psoc6_super_cm0 (psoc6_2m) at 0x16000000, size 0x00008000, buswidth 4, chipwidth 4
Info : #3 : psoc6_efuse_cm0 (psoc6_2m_efuse) at 0x90700000, size 0x00000400, buswidth 1, chipwidth 1
Info : #4 : psoc6_main_cm4 (virtual) at 0x10000000, size 0x00000000, buswidth 0, chipwidth 0
Info : #5 : psoc6_work_cm4 (virtual) at 0x14000000, size 0x00000000, buswidth 0, chipwidth 0
Info : #6 : psoc6_super_cm4 (virtual) at 0x16000000, size 0x00000000, buswidth 0, chipwidth 0
Info : #7 : psoc6_efuse_cm4 (virtual) at 0x90700000, size 0x00000400, buswidth 1, chipwidth 1
Info : #8 : psoc6_smif0_cm0 (cmsis_flash) at 0x18000000, size 0x04000000, buswidth 4, chipwidth 4
Info : #9 : psoc6_smif0_cm4 (virtual) at 0x18000000, size 0x00000000, buswidth 0, chipwidth 0
Info : cyp status: OK
Info : cyp_get_mpn
Info : ** Detected device PN: CY8C624ABZI-S2D44 SiliconID: E453 Revision: 12 FamilyID: 102 DIE: PSoC6A2M

Programming .hex File:

Info : program_device "C:/Users/strom/mtw/Hello_World_4/build/CY8CPROTO-062-4343W/Debug/mtb-example-psoc6-hello-world.hex" "0"
Info : ** Program image C:/Users/strom/mtw/Hello_World_4/build/CY8CPROTO-062-4343W/Debug/mtb-example-psoc6-hello-world.hex offset:0 **
Info : SWD DPIDR 0x6ba02477
Info : kitprog3: acquiring PSoC device...
Info : target halted due to debug-request, current mode: Thread
Info : xPSR: 0x41000000 pc: 0x00000190 msp: 0x080ff800
Info : ** Device acquired successfully
Info : ** psoc6.cpu.cm4: Ran after reset and before halt...
Info : target halted due to debug-request, current mode: Thread
Info : xPSR: 0x01000000 pc: 0x0000012a msp: 0x080ff800
Info : ** Programming Started **
Info : auto erase enabled
Info : Flash write discontinued at 0x1000179c, next section at 0x10002000
Info : Padding image section 0 at 0x1000179c with 100 bytes (bank write end alignment)
Info : [100%] [################################] [ Erasing ]
Info : [100%] [################################] [ Programming ]
Info : Padding image section 1 at 0x1000cf1c with 228 bytes (bank write end alignment)
Info : [100%] [################################] [ Erasing ]
Info : [100%] [################################] [ Programming ]
Info : wrote 51200 bytes from file C:/Users/strom/mtw/Hello_World_4/build/CY8CPROTO-062-4343W/Debug/mtb-example-psoc6-hello-world.hex in 1.889163s (26.467 KiB/s)
Info : ** Programming Finished **
Info : cyp status: OK
Info : cyp_get_mpn
Info : ** Detected device PN: CY8C624ABZI-S2D44 SiliconID: E453 Revision: 12 FamilyID: 102 DIE: PSoC6A2M
Info : reset run
Info : SWD DPIDR 0x6ba02477
Info : target halted due to debug-request, current mode: Thread
Info : xPSR: 0x01000000 pc: 0x100023b6 msp: 0x080ff7f8
Info : Polling target psoc6.cpu.cm0 failed, trying to reexamine
Info : Examination failed, GDB will be halted. Polling again in 100ms
Info : Polling target psoc6.cpu.cm4 failed, trying to reexamine
Info : SWD DPIDR 0x6ba02477
Info : psoc6.cpu.cm4: hardware has 6 breakpoints, 4 watchpoints
Info : psoc6.cpu.cm0: external reset detected
Info : Polling target psoc6.cpu.cm0 failed, trying to reexamine
Info : psoc6.cpu.cm0: hardware has 4 breakpoints, 2 watchpoints
Info : psoc6.cpu.cm4: external reset detected
Info : target halted due to debug-request, current mode: Thread
Info : xPSR: 0x01000000 pc: 0x100023b6 msp: 0x080ff7f8

Programming .elf File:

Info : program_device "C:/Users/strom/mtw/Hello_World_4/build/CY8CPROTO-062-4343W/Debug/mtb-example-psoc6-hello-world.elf" "0"
Info : ** Program image C:/Users/strom/mtw/Hello_World_4/build/CY8CPROTO-062-4343W/Debug/mtb-example-psoc6-hello-world.elf offset:0 **
Info : SWD DPIDR 0x6ba02477
Info : kitprog3: acquiring PSoC device...
Info : target halted due to debug-request, current mode: Thread
Info : xPSR: 0x41000000 pc: 0x00000190 msp: 0x080ff800
Info : ** Device acquired successfully
Info : ** psoc6.cpu.cm4: Ran after reset and before halt...
Info : target halted due to debug-request, current mode: Thread
Info : xPSR: 0x01000000 pc: 0x0000012a msp: 0x080ff800
Info : ** Programming Started **
Info : auto erase enabled
Info : Padding image section 1 at 0x1000cf1c with 228 bytes (bank write end alignment)
Info : [100%] [################################] [ Erasing ]
Info : [100%] [################################] [ Programming ]
Info : wrote 53248 bytes from file C:/Users/strom/mtw/Hello_World_4/build/CY8CPROTO-062-4343W/Debug/mtb-example-psoc6-hello-world.elf in 1.791406s (29.027 KiB/s)
Info : ** Programming Finished **
Info : cyp status: OK
Info : cyp_get_mpn
Info : ** Detected device PN: CY8C624ABZI-S2D44 SiliconID: E453 Revision: 12 FamilyID: 102 DIE: PSoC6A2M
Info : reset run
Info : SWD DPIDR 0x6ba02477
Info : target halted due to debug-request, current mode: Thread
Info : xPSR: 0x01000000 pc: 0x100023b6 msp: 0x080ff7f8

In both cases, even after an external reset, no LED flashes, as this is the case when debugging with this code.

Rakshith · ‎Nov 09, 2020

Hi ChRi_4015166,

I programmed the hex file that you shared and I also did not see the LED blinking. Can you please try programming the attached hex file and let me know if that works?

If it works, can you try clicking on Generate Launches in your application and then programming the device? If still, you do not see the LED blinking in your application, please share the application on this thread or create a new workspace and let me know if the issue persists.

Thanks and Regards,

Rakshith M B

Thanks and Regards,
Rakshith M B

ChRi_4015166 · ‎Nov 09, 2020

Hi RakshithM_16,

The hex-file can be flashed with the programmer and works immediately...

After creating a new workspace and Generate Launch before each flash it works...

Where was the error and what do I have to be aware of for the future?

Thanks and Regards,

Christoph

Rakshith · ‎Nov 10, 2020

Hi Christoph,

After creating a new workspace and Generate Launch before each flash it works...

I do not think generating launches every time is necessary. Generating the launches once should fix any issues with the launches. Please let me know if this works.

Where was the error and what do I have to be aware of for the future?

As the shared hex file was not working, I think the issue is with the build task. In the previous workspace can you try refreshing the quick panel, perform a clean and then build the project again. Once this is complete program the device. Please let me know your observations.

Thanks and Regards,

Rakshith M B

Thanks and Regards,
Rakshith M B

CY8CPROTO-062-4343W nicht Programierbat mit ModusToolbox

Re: CY8CPROTO-062-4343W nicht Programierbat mit ModusToolbox

Re: CY8CPROTO-062-4343W nicht Programierbat mit ModusToolbox

Re: CY8CPROTO-062-4343W nicht Programierbat mit ModusToolbox

Re: CY8CPROTO-062-4343W nicht Programierbat mit ModusToolbox

Re: CY8CPROTO-062-4343W nicht Programierbat mit ModusToolbox

Re: CY8CPROTO-062-4343W nicht Programierbat mit ModusToolbox

Re: CY8CPROTO-062-4343W nicht Programierbat mit ModusToolbox

Re: CY8CPROTO-062-4343W nicht Programierbat mit ModusToolbox

Re: CY8CPROTO-062-4343W nicht Programierbat mit ModusToolbox

Re: CY8CPROTO-062-4343W nicht Programierbat mit ModusToolbox

Re: CY8CPROTO-062-4343W nicht Programierbat mit ModusToolbox