PSoC™ 6 Forum Discussions

Hello,
i was experimenting with the PSOC63 CPU and at one time I tried to set the M0+ Core to 12,5MHz (FLL 50 -> 25 Mhz / 2 divider). The M4 Core is at 50 MHz.

It didn't really work and i wanted to reprogram it again with a 25MHz Clock for the M0+ (which worked before). But I cannot reprogram the MCU with kitprog3.

Board is a CYC8PROTO-063-BLE. Coding on Linux.

This is the output of the failing flashing process:

Open On-Chip Debugger 0.11.0+dev-4.3.0.1746 (2021-09-16-15:53)
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
Warn : SFlash programming allowed for regions: USER, TOC, KEY
Info : Using CMSIS-DAPv2 interface with VID:PID=0x04b4:0xf155, serial=172201A500249400
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 = 1 TDO = 1 nTRST = 0 nRESET = 0
Info : CMSIS-DAP: Interface ready
Info : KitProg3: FW version: 2.30.1155
Info : KitProg3: Pipelined transfers enabled
Info : VTarget = 3.320 V
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.)
** 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:
/home/matthias/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 "/home/matthias/ModusToolbox/tools_2.4/openocd/bin/../scripts/target/mxs40/psoc6_common.cfg", line 134
at file "/home/matthias/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:
/home/matthias/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 "/home/matthias/ModusToolbox/tools_2.4/openocd/bin/../scripts/target/mxs40/psoc6_common.cfg", line 169
at file "/home/matthias/ModusToolbox/tools_2.4/openocd/bin/../scripts/target/mxs40/mxs40_common.cfg", line 115
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
Error: Error connecting DP: cannot read IDR

Hi, Sir.

I'm starting to bring up the customer board that cy8ckit_64b0s2_4343w. But when I change to another example, ex: from hello world to Blinky LED, I always need to re-provision it again. So, may I have a method to skip it? 

Thanks
Hugh

Hi, I just downloaded and installed Modus Toolbox. I tried to create an empty project and get the following error. 

Summary:

BSP: PSOC6-GENERIC

Template Application(s): Empty PSoC6 App

Application(s) Root Path: C:/Users/liu.chao3/mtw

Press "Create" to create the selected application(s).

Collecting application data...

Info: The following entered on the command line will create the exact same project as that created with the GUI tool:

C:/Users/liu.chao3/ModusToolbox/tools_2.4/project-creator/project-creator-cli.exe --board-id PSOC6-GENERIC --board-uri https://github.com/cypresssemiconductorco/TARGET_PSOC6-GENERIC --board-commit latest-v3.X --app-id mtb-example-psoc6-empty-app --app-uri https://github.com/cypresssemiconductorco/mtb-example-psoc6-empty-app --app-commit latest-v3.X --cypress-tools C:/Users/liu.chao3/ModusToolbox/tools_2.4 --target-dir C:/Users/liu.chao3/mtw --user-app-name Empty_PSoC6_App --output-for-machine --use-modus-shell --offline

==============================================================================

= Cloning 'mtb-example-psoc6-empty-app' =

==============================================================================

Cloning https://github.com/cypresssemiconductorco/mtb-example-psoc6-empty-app into C:/Users/liu.chao3/mtw directory...

env git clone --progress --origin cypress /cygdrive/c/Users/liu.chao3/.modustoolbox/offline/git/https___github.com_cypresssemiconductorco_mtb-example-psoc6-empty-app/mtb-example-psoc6-empty-app Empty_PSoC6_App

Cloning into 'Empty_PSoC6_App'...

done.

Checking out latest-v3.X...

env git checkout --progress latest-v3.X

Note: switching to 'latest-v3.X'.

You are in 'detached HEAD' state. You can look around, make experimental

changes and commit them, and you can discard any commits you make in this

state without impacting any branches by switching back to a branch.

If you want to create a new branch to retain commits you create, you may

do so (now or later) by using -c with the switch command. Example:

git switch -c <new-branch-name>

Or undo this operation with:

git switch -

Turn off this advice by setting config variable advice.detachedHead to false

HEAD is now at a9e053c Upload mtb-example-psoc6-empty-app 3.0.0.181

env git remote set-url cypress https://github.com/cypresssemiconductorco/mtb-example-psoc6-empty-app

==============================================================================

= Creating "TARGET_PSOC6-GENERIC.mtb" file(s) =

==============================================================================

C:/Users/liu.chao3/mtw/Empty_PSoC6_App/deps/TARGET_PSOC6-GENERIC.mtb was added

C:/Users/liu.chao3/mtw/Empty_PSoC6_App/deps/TARGET_CY8CPROTO-062-4343W.mtb was removed

==============================================================================

= Updating Makefile for "Empty_PSoC6_App" =

==============================================================================

==============================================================================

= Applying the Latest Version Locking for "Empty_PSoC6_App" =

==============================================================================

C:/Users/liu.chao3/mtw/Empty_PSoC6_App/deps/TARGET_PSOC6-GENERIC.mtb was updated

==============================================================================

= Getting Dependencies for "Empty_PSoC6_App" =

==============================================================================

C:/Users/liu.chao3/ModusToolbox/tools_2.4/modus-shell/bin/make.exe getlibs CY_GETLIBS_OFFLINE=true CY_TOOLS_PATHS=C:/Users/liu.chao3/ModusToolbox/tools_2.4

Tools Directory: C:/Users/liu.chao3/ModusToolbox/tools_2.4

==============================================================================

= Importing libraries =

==============================================================================

Git is git version 2.33.0, found at /usr/bin/git

Resolving dependencies...

CY_GETLIBS_OFFLINE variable is set.

Force switching to offline mode.

Getting manifests from offline contents...

Found offline super-manifest: file:///C:/Users/liu.chao3/.modustoolbox/offline/manifests-v2.X/mtb-super-manifest-fv2.xml

Processing super-manifest file:///C:/Users/liu.chao3/.modustoolbox/offline/manifests-v2.X/mtb-super-manifest-fv2.xml...

Successfully acquired the information.

INFO - Warning: Multiple versions of "core-make" requested. Keeping version "latest-v1.X" and discarding version "release-v1.9.0".

C:/Users/liu.chao3/mtw/Empty_PSoC6_App/libs/core-lib.mtb was added

C:/Users/liu.chao3/mtw/Empty_PSoC6_App/libs/core-make.mtb was added

C:/Users/liu.chao3/mtw/Empty_PSoC6_App/libs/mtb-hal-cat1.mtb was added

C:/Users/liu.chao3/mtw/Empty_PSoC6_App/libs/mtb-pdl-cat1.mtb was added

C:/Users/liu.chao3/mtw/Empty_PSoC6_App/libs/psoc6cm0p.mtb was added

C:/Users/liu.chao3/mtw/Empty_PSoC6_App/libs/recipe-make-cat1a.mtb was added

Dependencies resolved.

Searching application directory (.mtb)...

Found 7 .mtb file(s)

Processing file "C:/Users/liu.chao3/mtw/Empty_PSoC6_App/deps/TARGET_PSOC6-GENERIC.mtb"

==============================================================================

ERROR: --ABORTING--

: Script : C:/Users/liu.chao3/ModusToolbox/tools_2.4/make/getlibs.bash

: Bash path : /usr/bin/bash

: Bash version: 4.4.12(3)-release

: Exit code : 1

: Call stack : trap_exit extract_data find_mtbs main

C:/Users/liu.chao3/ModusToolbox/tools_2.4/make/getlibs.bash: line 646: currLibCommit: unbound variable

make: *** [C:/Users/liu.chao3/ModusToolbox/tools_2.4/make/getlibs.mk:121: getlibs] Error 1

Project "Empty_PSoC6_App" failed to create.

"make getlibs" failed.

Failed to create and export "Empty_PSoC6_App" application.

Also I tried to uninstall modustoolbox and restart my computer, then I install modustoolbox again, but it's no use, still have this problem. 

The environment PATH variable ：

I am attempting to utilize the arm dsp cores with the Psoc5LP system from cypress.

Primarily the fft example is what I am interested in replicating, but I am confused slightly on how cores work. I have used the picoblaze core on Xilinx Spartan-6 before but I have never used premade cores, especially for Psoc.

I have looked at the psoc system reference guide and found information on CMSIS under startup and linking, but it does not make full sense to me. could someone please point me in the right direction to get me started? also will I have to download all the files individually that I need such as the arm_math.c for the fft example (if so I think that's the only file I need?), or will I just need to download the CMSIS version 4.3 from arms website.

I'm trying to implement spectral flux analysis and autocorrelation using these cores and I think they are a good echatrandom place to start.

Thanks in advance,

I am using a PSoC6 CM4 for BLE discovery, and also use an uart for external debug. I want to make sure to save as much as possible in power, so i want to run few seconds scanning, and then a period of extreme low power.

I test hibernate, but it looks like the unit restarts after waking up instead of continuing my 'loop'

Created project in psoc creator, and use vscode for the main-code.

Questions:
1: How can i go in hibernate, and preferably not restart/ reinitialise?
2: once i add the UART, the current in hibernate goes up to 350uA, even if i do not initialise it. How can i change that? Without UART placed in de design, it goes to 1uA

All idea's/help are welcome

CY8CKIT-062S2-43012 maximum 600kbit's throughput with AnyCloud: TCP

I used the AnyCloud: TCP client example and added for loop to transmit dummy messages.
I Could not get more than 600kbit of throughput with TCP to a remote host over the wide web (amazon server).
compering the test with Linux system with same wifi module, I got 5Mbits throughput with TCP,

it looks like the 600kbit barrier is a software/configuration issue

see attached source code and pcap 

please advise

i build the example "hello world" by use CY8CKIT-062S2-43012 and get 2 error .

make[1]: *** [../mtb_shared/core-make/release-v1.9.0/make/core/build.mk:529: C:/Users/??恭???/mtw/Hello_World/build/CY8CKIT-062S2-43012/Debug/mtb-example-psoc6-hello-world.elf] Error 1
make: *** [../mtb_shared/core-make/release-v1.9.0/make/core/main.mk:434: secondstage_build] Error 2

What's  that mean?

Thanks.