PSoC 6 MCU

https://www.cypress.com/products/psoc-6-microcontrollers-32-bit-arm-cortex-m4m0

No devices appear on PSoC 64 product selector.

Hello, I need to create a simple LCD display like the one in the photo, but with the PSOC 6.

But I couldn't quite understand the LCD interface of PSOC 6. Does anyone have an example of an LCD display to simply show a string like "Hello World!"? If so, could you provide an example project?

Hello

Questions related to this thread.

https://community.cypress.com/t5/PSoC-6-MCU/The-contents-of-the-HEX-file-are-different/m-p/266218#M9358

Customer using CYBLE-416045-02.
Files built using PSoC Creator vary in size depending on the PC on which they are created.

(Version4.3)

As a verification, I built a sample program of "BLE_Alert_Notification" and compared customers HEX, but the size was different.
When I checked it with software that compares HEX files, I found data that existed in only one of them.

What is the cause of this?

Best Regards

Hayato

Hi, in mqtt client anycloud is there a way to change the publishInfo.pPayload value in publisher_task.c file so that I can send numerical value instead of string or turn on ....

Hi all,

We have a CY8CKIT-064S0S2-4343W kit that we're trying to get up and running with the demonstration code that is generated from AWS. I'm following the getting started guide located here https://docs.aws.amazon.com/freertos/latest/userguide/getting_started_cypress_psoc64.html and have successfully done everything up to the point of getting working code.

I've managed to build and flash the provided demo application, and the board successfully boots but then halts shortly after with "ERROR: stack overflow" — the attached screenshot shows what is happening. This happened with no WiFi credentials set, I then tried to set WiFi credentials and the error still happened. 

Any help in resolving this issue would be appreciated!

Hello Community

I am working on a PSoC 6 Project which implements the CY8C6347FMI-BUD53

Programming environment is the ModuxToolBox Version:  2.2.0

Pushbutton connected to P0_4 ( wakeup pin ), PMIC_ENABLE connected to P0_5 (wakeup out).

I want to shut down the VDDD Domain for sleep. only keeping vbackup running for later pushbutton interrupt.

I tested this code.

// VDDD is shutdown at PMIC_ENABLE disabled, and Enter Hibernate.

if (Cy_SysPm_PmicIsOutputEnabled())

{

  Cy_SysPm_PmicUnlock();

  Cy_SysPm_PmicDisable(CY_SYSPM_PMIC_POLARITY_HIGH);

}

resStat = Cy_SysPm_SystemEnterHibernate();

// not reach

if (resStat != CY_SYSPM_SUCCESS) {

   printf("ERR Hibernate. ret:0x%x\r\n", resStat);

}

after that,

Pressing Pushbutton  while PSoC6_MCU is System_hibernate_mode, but pmic_wakup_out :P0[5] is not changed to High,

so and MCU does not return to System_LP_mode .

Hi all,

I am trying to send some BLE notifications from PSoC6 MCU (peripheral) to android. Using nrfconnect ble scanner app as central. Whenever I send a notification out, I get CY_BLE_ERROR_INVALID_PARAMETER error code on the device side for Cy_BLE_GATTS_Notification .  BLE stack runs on CM0.

The characteristic size is 512 bytes but I am only sending 50 bytes in this notification. Could this be the problem?

Thanks,

Vimal

Hi folks,

I'm working on enabling the backup domain on the PSoC 6. I followed the instructions in this post, and found that the new code generated by PSoC Creator removed a call to Cy_SysLib_ResetBackupDomain() during initialization, as well as some code to disable and enable ILO. I then found that this function's description mentions an "ILO glitch" which can occur when the PSoC is reset due to POR/BOD/XRES while the backup voltage is supplied to the system. 

When I generate code with "vBackup Source" set to VDDD, this function is called, but when I generate code with "vBackup Source" set to "Dedicated supply" it is not. However, the description of this function would seem to imply that the ILO glitch it is meant to address will only occur if the system has a dedicated backup power supply connected to VBACKUP. Could anyone shed light on why this function call is necessary when there is no backup supply? Is there any harm in removing this call if VBACKUP is shorted to VDDD?