PSoC™ 6 Forum Discussions

• cyacd2 is an encrypted file?

• How does Psoc Creator4.4 generate cyacd2 files  

Hi Community, 

I am currently exploring the utilization of a CYKIT-028 TFT Module in conjunction with both Raspberry Pi and ESP32 microcontrollers. However, I find myself in a bit of a quandary regarding the choice of IDE (Integrated Development Environment) and the necessity of using PSOC Creator.

Given my familiarity with PSOC Creator for working with PSOC4 MCUs in my professional capacity, I wonder if it is imperative to continue using PSOC Creator for interfacing with the CYKIT-028 TFT Module, or if there are alternative IDEs compatible with this display module. Additionally, I am seeking clarification on whether the TFT module can be seamlessly integrated with microcontrollers beyond the PSOC family, such as Raspberry Pi and ESP32.

Hi Infineon Community:

I tried to flash my CY8CKIT-062S2-43012 evaluation board with the "Machine_Learning_Imagimob_MTBML_Deploy" and also the "Machine_Learning_Imagimob_MTBML_Collection Data" on ModusToolbox 3.1. I got the following error on the console when going to debug mode.

***************************************
** 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] Cortex-M4 r0p1 processor detected
Info : [psoc6.cpu.cm4] target has 6 breakpoints, 4 watchpoints
Info : starting gdb server for psoc6.cpu.cm0 on 3332
Info : Listening on port 3332 for gdb connections
Info : starting gdb server for psoc6.cpu.cm4 on 3333
Info : Listening on port 3333 for gdb connections
Info : SWD DPIDR 0x6ba02477
Info : kitprog3: acquiring the device (mode: reset)...
[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
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.cm4, state: halted
Warn : Prefer GDB command "target extended-remote :3333" instead of "target remote :3333"
semihosting is enabled
Warn : No RTOS could be auto-detected!
Warn : No RTOS could be auto-detected!
Verifying region (0x10000000, 6352)... Match
Verifying region (0x10002000, 50376)... Match
Info : All data matches, Flash programming skipped
Info : SWD DPIDR 0x6ba02477
Info : SWD DPIDR 0x6ba02477
Error: Failed to write memory at 0xe0001Polling target psoc6.cpu.cm4 failed, tryin04c
g to reexamine
Info : [psoc6.cpu.cm4] Cortex-M4 r0p1 processor detected
Info : [psoc6.cpu.cm4] target has 6 breakpoints, 4 watchpoints
Info : [psoc6.cpu.cm0] external reset detected
Info : [psoc6.cpu.cm4] external reset detected
Info : SWD DPIDR 0x6ba02477
Error: Failed to write memory at 0xe000103c
Polling target psoc6.cpu.cm4 failed, trying to reexamine
Info : [psoc6.cpu.cm4] Cortex-M4 r0p1 processor detected
Info : [psoc6.cpu.cm4] target has 6 breakpoints, 4 watchpoints
Info : psoc6.cpu.cm4: Waiting up to 10.0 sec for valid Vector Table address...
Info : psoc6.cpu.cm4: Vector Table found at 0x10002000
Info : psoc6.cpu.cm4: bkpt @0x10002371, issuing SYSRESETREQ
Info : SWD DPIDR 0x6ba02477
[psoc6.cpu.cm4] halted due to breakpoint, current mode: Thread
xPSR: 0x61000000 pc: 0x10002370 msp: 0x080ff800, semihosting
Info : [psoc6.cpu.cm0] external reset detected

These are the two main errors I found:

Error: Failed to write memory at 0xe000104c

Error: Failed to write memory at 0xe000103c

I have to mention that I tested with the hello world SDK and I didn´t have any issues. I don't know if the issue is related to the size of the project or a problem with the internal memory of the MCU.

I have looked in the community for similar questions, but they didn´t help me solve my issue.

https://community.infineon.com/t5/PSoC-6/Error-Failed-to-read-memory-at-0xfffff000-Info-SWD-DPIDR-0x6ba02477/td-p/399334 

https://community.infineon.com/t5/ModusToolbox/Modus-Toolbox-3-0-programming-error-quot-Failed-to-write-memory-at-address-quot/td-p/386606 

Regards,

Luis Flores

I have a PSoC 6 BLE Pioneer Kit CY8CKIT-062-BLE (Rev *B, Rev 11) that I am trying to program the Hello World code example with. I have already upgraded to KitProg3 using the Firmware Loader application. 

I am able to successfully build the Hello World application and it looks like it is getting loaded onto the device but when it finishes loading, nothing happens on the board. I expect to see an LED blinking but I only see LED2 and LED4 fully on. 

The last message I see in the console is: 

Info : kitprog3: acquiring the device (mode: reset)...
[psoc6.cpu.cm0] halted due to debug-request, current mode: Thread 
xPSR: 0x21000000 pc: 0x00001f2c msp: 0x08047798
** 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: 0x00000f48 msp: 0x08047800
Info : SWD DPIDR 0x6ba02477
[psoc6.cpu.cm0] halted due to debug-request, current mode: Thread 
xPSR: 0x21000000 pc: 0x00001f2c msp: 0x08047798
Info : dropped 'gdb' connection
shutdown command invoked
Info : psoc6.dap: powering down debug domain...

I have attached the output log of the programmer. Am I missing a step or doing something wrong here? 

Dear Forum:
I do many test, I find the following phenomenon:

Before set MCU to Deep Sleep,
If I don't clear the SSR(serial status register) bit before close SPI,
MCU(PSoC6) can't enter deepsleep.

If I clear the SSR(serial status register) bit before close SPI,
MCU(PSoC6) can enter deepsleep.

I want to confirm:
does the SPI SSR bit affect MCU deepsleep or not.

Thank you.

Dear Forum:
We are doing our soft with pSoC6 CY8C6137BZI-F14,
We use the Modus IDE.

But when we use psoc programmer to write Hex file produced by Modus,
psoc programmer show the following error:
Hex File parsing failure. Unknown record type.

Can you tell me the reason.

Thank you.

When testing this routine, following the steps in Readme, Testing with AIROC ™ Bluetooth ® Connect App on Android, it was found that apps using Android can successfully connect, but those using iOS cannot, as shown in the figure. Later, I used bleak Python to write a GATT client program and attempted to establish a connection with the BLE board, but encountered the same error as the IOS App and was unable to connect. May I ask how I can solve it