PSoC™ 6 Forum Discussions
According to following table from https://www.cypress.com/documentation/product-brochures/psoc-6-mcu-new-standard-internet-things UDBs should be present in all PSoC >= 61
but datasheet for example PSoC 62x8 and 62xA have no UDBs according to datasheet (https://www.cypress.com/documentation/datasheets/psoc-62-cy8c62x8-cy8c62xa-datasheet ). There are no UDBs mentioned except reference in acronym table. It is interesting 62x5 family has also no reference to UDB in datasheet but 62x6 and 62x7 UDB contains.
Is correct that 62x5, 62x8 and 62xA have no UDB or they have it and it is just ommited in datasheet?
Show LessThe Open Documentation Team is looking for a few great beta testers. People interested in a single place to find their documentation and a place where it will be updated on their feedback. The Cypress Community has always been a place of collaboration with you, our users, and we’d like to extend an invitation to give us feedback on this new platform between now and January 10th, 2021.
The first documentation platform we’re opening is for PSoC 6 and AnyCloud customers and offers all the documentation you, the developers, need in one place. The Open Documentation platform allows users to find all the development documentation in one place, complete with real-time updates from our software and support teams based on inputs and questions from our developer community. This creates a responsive, easier to use platform for you to find everything throughout your development process.
This platform will host the latest version of the documentation along with continuous updates from our support organization based on questions from you, our Community members. We look forward to hearing your feedback on this beta PSoC 6 and AnyCloud book and collaborating with you on better documentation going forward.
Jump over and test out the PSoC 6 and AnyCloud platform here.
Let us know here what you think of the platform. Test out the in-documentation feedback tool too. We’d love to hear any other documentation books you would like us to build.
Thank you for being a part of our commitment to continually improving our developer experience! I appreciate your help in making this the best tool we can.
Thank you,
Robyn Weil
Digital Technologies Team
Show LessHi 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...
Show LessI have successfully programmed and unprogrammed PSoC demos on the CY8CPROTO-062-4343W boards but once I program an aws_demo the board is bricked. The board runs the firmware but cannot be reprogrammed. I have tried this on 3 different boards with the same results. This thread discussed the same problem without providing a solution. BTW I have updated the adapter firmware tried the Cypress programmer as well.
Any help will be appreciated since I have had to order 3 new boards.
Log of errors
Open On-Chip Debugger 0.10.0+dev-4.1.0.1058 (2020-08-11-03:45)
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 = 1 TDO = 1 nTRST = 0 nRESET = 1
Info : CMSIS-DAP: Interface ready
Info : KitProg3: FW version: 2.10.878
Info : KitProg3: Pipelined transfers enabled
Info : VTarget = 3.325 V
Info : kitprog3: acquiring the device...
Error: kitprog3: failed to acquire the device
Info : clock speed 2000 kHz
Info : SWD DPIDR 0x6ba02477
Info : SWD DPIDR 0x6ba02477
Error: Failed to read memory at 0xe000ed00
Polling target psoc6.cpu.cm0 failed, trying to reexamine
Info : SWD DPIDR 0x6ba02477
Info : SWD DPIDR 0x6ba02477
Examination failed, GDB will be halted. Polling again in 100ms
Error: Failed to read memory at 0xe000ed00
Polling target psoc6.cpu.cm0 failed, trying to reexamine
Info : SWD DPIDR 0x6ba02477
Info : SWD DPIDR 0x6ba02477
Error: Failed to read memory at 0xe000ed00
Examination failed, GDB will be halted. Polling again in 300ms
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
** Device is not present in the UDD
Error: Failed to read memory at 0x16000000
Error: mem2array: Read @ 0x16000000, w=4, cnt=1, failed
Info : SWD DPIDR 0x6ba02477
Error: Failed to read memory at 0x16002004
Error: mem2array: Read @ 0x16002004, w=4, cnt=1, failed
Error: Invalid FlashBoot: High version word of Flash Boot is zero
Info : SWD DPIDR 0x6ba02477
Error: Failed to read memory at 0x402020c4
Error: mem2array: Read @ 0x402020c4, w=4, cnt=1, failed
Error executing event examine-end on target psoc6.cpu.cm0:
/Applications/ModusToolbox/tools_2.2/openocd/bin/../scripts/mem_helper.tcl:6: Error:
in procedure 'program'
in procedure 'ocd_process_reset'
in procedure 'ocd_process_reset_inner' called at file "embedded:startup.tcl", line 279
in procedure 'cy_get_set_device_param' called at file "/Applications/ModusToolbox/tools_2.2/openocd/bin/../scripts/target/mxs40/psoc6_common.cfg", line 129
in procedure 'show_chip_protection' called at file "/Applications/ModusToolbox/tools_2.2/openocd/bin/../scripts/target/mxs40/cy_get_set_device_param.cfg", line 164
in procedure 'mrw' called at file "/Applications/ModusToolbox/tools_2.2/openocd/bin/../scripts/target/mxs40/cy_get_set_device_param.cfg", line 118
at file "/Applications/ModusToolbox/tools_2.2/openocd/bin/../scripts/mem_helper.tcl", line 6
Info : SWD DPIDR 0x6ba02477
Error: Failed to read memory at 0xe000ed00
Info : SWD DPIDR 0x6ba02477
Info : SWD DPIDR 0x6ba02477
Info : AP write error, reset will not halt
Info : SWD DPIDR 0x6ba02477
Info : SWD DPIDR 0x6ba02477
in procedure 'program'
Info : SWD DPIDR 0x6ba02477
Polling target psoc6.cpu.cm4 failed, trying to reexamine
Info : SWD DPIDR 0x6ba02477
Info : SWD DPIDR 0x6ba02477
Error: Failed to read memory at 0xe000ed00
Examination failed, GDB will be halted. Polling again in 100ms
** Program operation failed **
srst_only separate srst_gates_jtag srst_open_drain connect_deassert_srst
Polling target psoc6.cpu.cm0 failed, trying to reexamine
Info : SWD DPIDR 0x6ba02477
Info : SWD DPIDR 0x6ba02477
Error: Failed to read memory at 0xe000ed00
Examination failed, GDB will be halted. Polling again in 700ms
***************************************
Info : SWD DPIDR 0x6ba02477
** Device is not present in the UDD
Error: Failed to read memory at 0x16000000
Error: mem2array: Read @ 0x16000000, w=4, cnt=1, failed
Info : SWD DPIDR 0x6ba02477
Error: Failed to read memory at 0x16002004
Error: mem2array: Read @ 0x16002004, w=4, cnt=1, failed
Error: Invalid FlashBoot: High version word of Flash Boot is zero
Info : SWD DPIDR 0x6ba02477
Error: Failed to read memory at 0x402020c4
Error: mem2array: Read @ 0x402020c4, w=4, cnt=1, failed
Error executing event examine-end on target psoc6.cpu.cm0:
/Applications/ModusToolbox/tools_2.2/openocd/bin/../scripts/mem_helper.tcl:6: Error:
in procedure 'ocd_process_reset'
in procedure 'ocd_process_reset_inner' called at file "embedded:startup.tcl", line 279
in procedure 'cy_get_set_device_param' called at file "/Applications/ModusToolbox/tools_2.2/openocd/bin/../scripts/target/mxs40/psoc6_common.cfg", line 129
in procedure 'show_chip_protection' called at file "/Applications/ModusToolbox/tools_2.2/openocd/bin/../scripts/target/mxs40/cy_get_set_device_param.cfg", line 164
in procedure 'mrw' called at file "/Applications/ModusToolbox/tools_2.2/openocd/bin/../scripts/target/mxs40/cy_get_set_device_param.cfg", line 118
at file "/Applications/ModusToolbox/tools_2.2/openocd/bin/../scripts/mem_helper.tcl", line 6
Info : SWD DPIDR 0x6ba02477
Info : SWD DPIDR 0x6ba02477
Info : SWD DPIDR 0x6ba02477
Info : SWD DPIDR 0x6ba02477
Error: DP initialisation failed
Info : psoc6.dap: powering down debug domain...
Warn : Failed to power down Debug Domains
Show LessHi Everyone,
I have a same issue as Debug the CM4 core
Programming successfull debug fails:
psoc creator error dbg.0006
I am using P6 BLE pioneer kit
I have PSoC Creator 4.4, The latest PDL 3.1.3 and psoc Prorammer version is 3.29.0.
I've tried the workaround as well with the infinite loop. The device stoped, but "nowhere". I mean: Not in the infinite loop. I saw the disassemly window, and line -1
then i pressed step into in debug window, I got another error:
psoc creator error dbg.0007
the run request failed encountered error (cannot find bounds of current function)
The request to run the application on the target failed. Make sure that your code is valid and that the selected target supports debugging.
Could somebody help with any good advise please?
Many thanks in advance!
Attila
Show LessIs there an example for using implementing an upgradable BLE stack using the newer DFU SDK? I'm trying to upgrade my project based on CE220960 to use PDL 3.1.0 and the newer DFU SDK.
CE216767 uses DFU and BLE but isn't quite what I'm looking for because I need it to have the upgradable stack.
I am currently using PSoC Creator 4.2 but have plans to eventually migrate to ModusToolbox sometime in the future in case it matters.
Any help would be appreciated.
Show LessI am running the PSoC 6 BLE Pioneer kit and some of the pins aren't working.
I have set up a bunch of pins to be strong drive GPIO: P0.3, P13.6, P13.7, P7.0.
P0.3 which is the onboard LED works, and so does P13.6. But P13.7 and P7.0 stay floating or at 0V
Any ideas why some pins work and some are not on the pioneer kit?
Show LessIn the datasheet for the CY8C6347BZI-BLD54 it says there are 9 SCBs, but one is a deep sleep SCB.
Can I use the deep sleep SCB during normal operation, and if so what pins can I use it with?
I only see 8 SCBs in the datasheet table 8: Multiple Alternate Functions
I need to set up 4 SPI buses and 5 UARTS.
Show LessFollow-up to an earlier question (Can I change the opcode configuration registers of a datapath during runtime? ), but with a slightly different core topic:
Are macros for defining a datapath's opcodes available in C? Something like
CS_ALU_OP__AND | CS_SRCA_A0 | ...(and so on)
That would be much more readable and maintainable than configuring the opcodes in the datapath config tool and then copying binary values over to C.
Show Less