PSoC™ 6

Where can I find more detail for selecting a MHz XTAL for Bluetooth_LE  or  BLE ECO for PSoC 63?

Table 58 in the CY8C63x6, CY8C63x7 datasheet identifies two oscillators for the BLE ECO input of a PSoC 63: 16 MHz and 32 MHz.

The BLE ECO appears to be the connection to the XI/XO pins referred to in Figure  5 of the same document.

There’s a single note in AN218241, PSoC 6 MCU Hardware Design Considerations regarding the BLE ECO that states: "It should be noted that the ECO available as part of the BLE radio has its own pins (XI and XO). You can add the load capacitor, crystal accuracy, and startup time details in the AltHF clock configure window as shown in Figure 9. External load capacitors for the BLE ECO are not required."  Again here, it doesn't state any difference in the ECO frequency selected. Does the frequency of the crystal connected to the XI/XO pins matter as long as it matches the frequency identified in the brown box of Figure 9?

Greg

Hi.

I'm trying to use the HAL System Power Management library to put the CM4 to sleep. So far, I've had no luck, and as I have found too many times, there is very little documentation available, and no examples. What documentation exists (e.g. Architecture TRM) is unclear, even suggesting that only masked interrupts can wake up a sleeping CPU.

Here's the environment:

• PSoC 63 with BLE in a custom board.
  • MTB 2.3.0 
  • BSP 2.3.0
  • PDL 2.3.0
  • HAL 2.1.0
• CM4 and CM0+ running FreeRTOS
• Several peripherals in use (BLE, I2C, UART, SPI, RTC, TWPCM, etc.)

1. I registered four callbacks using cyhal_syspm_register_callback(). 
2. I call cyhal_syspm_sleep().
3. The four callbacks are called with state set to CYHAL_SYSPM_CB_CPU_SLEEP and mode set to CYHAL_SYSPM_CHECK_READY. All callbacks return true.
4. The four callbacks are called again with state set to CYHAL_SYSPM_CB_CPU_SLEEP, but this time mode set to CYHAL_SYSPM_BEFORE_TRANSITION.
5. The four callbacks are immediately called a third time with state set to CYHAL_SYSPM_CB_CPU_SLEEP, but this time mode set to CYHAL_SYSPM_AFTER_TRANSITION.

The first problem is that the CPU either doesn't sleep, or wakes up immediately. I disable the RTOS SysTick interrupt in one of the callbacks. I also disable several other peripheral interrupts, and turn off the BLE stack, none of which has made a difference. It's likely that some interrupt is firing, but I can't think of a good way to determine which is the culprit.

The second problem is that the stated behavior, namely that the callbacks are called on wakeup (CYHAL_SYSPM_AFTER_TRANSITION) in the reverse of the order in which they are called on sleep (CYHAL_SYSPM_CB_CPU_SLEEP) does not match the observed behavior.
Callbacks are always called in the same order, even when one of the callbacks returns false in response to CYHAL_SYSPM_CHECK_READY.

Has anyone successfully used cyhal_syspm_sleep() to put one of the CPUs to sleep?

Thanks,

-Nick

Hello,

I am using modustoolbox 2.4 with 256k flash PSoC6 controller which has CM0+ and CM4 cores. I want that cores should be deepsleep mode. I am calling 

"Cy_SysPm_CpuEnterDeepSleep(CY_SYSPM_WAIT_FOR_INTERRUPT); " from CM4 core. Would CM0+ core also enters into deepsleep? I am expecting current consumption in range of 10uA, but I am measuring around ~2mA. Could you suggest?

How can can I check that CM0+ is in deepsleep or not? I also checked Switching_Power_Modes example code. I am not able to locate the main function of CM0+ core. There is only startup function as below:

Where is main function of CM0+ in Modustoolbox example code.