Psoc6 BLE低功耗模式是否可以将Core M0 Plus和M4唤醒到活动模式？

你好，
BLE被停止，寄存器被保存在深度休眠模式中，因此根本不应该产生祝福中断。
对于睡眠，这是可能的，当您启用ISR为两个核心。
当做，
阿希姆



     以下为原文
  Hi,
 
BLE is stopped and the registers are retained in Deep Sleep Mode, so there should be no BLESS Interrupt generated at all.
For Sleep, this is possible when you enable the isr for both cores.
 
regards,
Achim

你好，
对阿希姆的响应的一个修正，祝福中断（触发每个广告/连接间隔）是一个深度睡眠中断，并且能够唤醒来自DeepSleep的内核。
也就是说，将一个中断映射到两个内核不是一个好主意。虽然从理论上讲，它可以映射到两个内核并唤醒它们。在WHO清除中断时，将存在一个竞争条件。如果您使用的是BLE组件/PDL，那么它将祝福中断映射到实现控制器的核心。
如果你需要唤醒另一个核心，那么你可以使用IPC从被祝福中断（控制器核心）唤醒的核心通知另一个核心。还要注意的是，当您为BLE选择“双核架构”时，CM0+（Controller）通过IPC SoeStudio唤醒CM4（主机），每当需要在主机端处理数据时。可以将回调附加到IPC中断，并可以使用该回调来处理所需的数据。
如果你需要帮助的话，请告诉我。
当做，
Meenakshi Sundaram R



     以下为原文
  Hello,
 
One correction to Achim's response, the BLESS interrupt (that triggers every Advertisement/Connection interval) is a DeepSleep interrupt and is capable of waking up the cores from DeepSleep.
 
That said, it is not a good idea to map a single interrupt to both the cores. Though theoretically it can be mapped to both the cores and wake-up both of them. There will exist a race condition on who clears the interrupt. If you are using the BLE component/PDL, then it maps the BLESS interrupt to the core that implements the controller.
 
If you need to wake-up the other core, then you can use IPC to notify the other core from the core that is woken up by the BLESS interrupt (controller core). Also note that when you select the "Dual-core architecture" for BLE, then CM0+ (controller) wakes-up CM4 (Host) through the IPC SystemPipe, whenever there is a need to process data on the host side. You can attach a callback to the IPC interrupt and can use that to process the required data.
 
Let me know if you need any help with that.
 
Regards,
Meenakshi Sundaram R

你好，msur：
如果保佑ISR可以唤醒核心从深度睡眠模式。说，如果连接已建立，之间的两连接事件核心的控制器可以进入深度睡眠模式。下一个连接的事件发生后，一个中断的祝福可以唤醒核心处理B乐活动。因为产品用户电力的电池，需要降低功耗。
你有没有降低电力消耗的好主意？



     以下为原文
  Hi,msur:
    If the bless isr can wake up the core from the Deep Sleep  mode .Say that if the a connection has established,between the tow connection event the core of the controller can into the Deep Sleep mode.After the next connection event happen ,a interrupt  of the bless can wake up the core to handle the BLE event .Because the product of customer power by the battery and need to reduce power consumption.

   Do you have any good idea to reduce power consumption?

是的，这是完全可能的。你可以参考我们的PSoC 6在这里找到我的例子-CE212736-PSoC 6 MCU与蓝牙低能量（BLE）连接-找到一个关于如何实现它的例子。在例子中，CM4（主机）依赖于来自CM0+（控制器）的IPC中断（系统管道）来唤醒它并处理BLE事件。CM0+依赖于祝福中断（广告或连接）来唤醒DeepSleep。
当做，
Meenakshi Sundaram R



     以下为原文
  Yes this is perfectly possible. You can refer to our PSoC 6 Find me example here - CE212736 - PSoC 6 MCU with Bluetooth Low Energy (BLE) Connectivity - Find Me for an example on how to implement it. In the example, CM4 (host) relies on IPC interrupt (System pipe) from CM0+(Controller) to wake it up and Process the BLE Events. And CM0+ relies on the BLESS interrupt (either advertisement or connection) to wake it up from DeepSleep.
 
Regards,
Meenakshi Sundaram R

MHU：
当读取代码示例CE212736时，存在一些问题：
1：你说CM4（主机）依赖于来自CM0+（控制器）的IPC中断（系统管道）来唤醒它并处理BLE事件。CM0+依赖于祝福中断（广告或连接）来唤醒DeepSleep。但是，我找不到如何实现它的代码。你能告诉我那个地方吗？
2：我仍然对低功耗模式句柄有疑虑，如果CM4和CM0+可以进入两个广告事件之间的DS模式。如果答案是肯定的，那么如何监视CelpTyReC-PDU的祝福呢？
3：CybLuxEvtStaskSuthDoutho完成将如何以及何时发生？
请帮帮我，谢谢。



     以下为原文
  Hi msur：
    There are some question when reading the code example  CE212736 :

1:You  say that CM4 (host) relies on IPC interrupt (System pipe) from CM0+(Controller) to wake it up and Process the BLE Events. And CM0+ relies on the BLESS interrupt (either advertisement or connection) to wake it up from DeepSleep. However ,I don't find the code about  how to achieve it .Could you show me the place.

 
2:I still have some doubts about the low power mode handle that if the CM4  and the CM0+ can go into DS mode between the tow advertising events. If the answer is yes,how the BLESS to monitor the CONNECT_REC PDU?
 
3:How and when the CY_BLE_EVT_STACK_SHUTDOWN_COMPLETE will be happened?
 
    Could  you help  me please,thanks.
 

你好，
对您的询问-
1。作为一个用户，你不必做大量的编码来达到这个目的。BLE中间件和创建者DWR配置负责这些。所有你需要做的是为CM0 +，使祝福中断CM0 +在“中断”选项卡DWR。在CM4，确保cy_ipc_systemsemainit()，cy_ipc_systempipeinit()，cy_flash_init()称为部分初始化。注意，CM4 init是部分systeminit API（定义在system_psoc63_cm4。C文件），只需要打电话，如果你改变你的项目的初始化代码。一旦这些初始化完成，BLE自动唤醒CM0 +广告每间隔（你需要开始广告以及这）当有请求同行，CM0 +核心醒来CM4在IPC。
2。是的，CM0+和CM4都可以进入DeepSleep。BLE子系统采用世界海关组织（lfclk）和一个内部定时器（可一）产生中断所有广告/连接间隔。在这个中断，BLE子系统处理广告和连接请求。用户代码将调用cy_ble_processevents API将连接请求（如果收到）到主机（CM4）。这个推应该唤醒CM4。通常涉及cy_ble_processevents()其次CM0 +代码cy_syspm_deepsleep -中断唤醒设备从DeepSleep和这个代码确保processevents进入前又叫DeepSleep。
三。收到的cy_ble_evt_stack_shutdown_complete（从主机CM4在双核模式）当你打电话cy_ble_stackshutdown API。请注意，API是非阻塞的，你将需要调用cy_ble_processevents直到事件发生以确保停机命令处理。
我知道这个答案，或者如果您有任何疑问。
和头-我们正在研究一种先进的应用笔记，讲述设计的应用程序使用的PSoC 6。
当做，
Meenakshi Sundaram R



     以下为原文
  Hello,
 
To your queries -
1. You, as a user, does not have to do a lot of coding to achieve that. The BLE middleware and the Creator DWR configuration takes care of these. All you need to do is - For CM0+, enable the BLESS interrupt for CM0+ in the "Interrupts" tab of DWR. For CM4, make sure Cy_IPC_SystemSemaInit(), Cy_IPC_SystemPipeInit(), Cy_Flash_Init() are called as part of initialization. Note that the init for CM4 is done as part of SystemInit API (defined in system_psoc63_cm4.c file) and only needs to be called, if you change the initialization code in your project. Once these initialization is complete, the BLE automatically wakes up the CM0+ every advertisement interval (you need to start advertisement as well for this) and when there are requests from peer, CM0+ core wakes up CM4 over IPC.
 
2. Yes both CM0+ and CM4 can enter DeepSleep. The BLE sub system uses the WCO (LFCLK) and an internal timer (available in DeepSleep) to generate interrupt every advertisement/connection interval. In this interrupt, the BLE sub system processes advertisement and connection requests. The user code is expected to call Cy_BLE_ProcessEvents API to push the connection request (if received) to the host (CM4). This push is supposed to wake up CM4. Typically the CM0+ code involves Cy_BLE_ProcessEvents() followed by Cy_SysPm_DeepSleep - the interrupt wakes up the device from DeepSleep and this code makes sure ProcessEvents is called before entering DeepSleep again.
 
3. The CY_BLE_EVT_STACK_SHUTDOWN_COMPLETE is received (from the host - CM4 in dual-core mode) when you call Cy_BLE_StackShutdown API. Note that the API is non-blocking and you will need to call Cy_BLE_ProcessEvents till the event is generated to make sure the ShutDown command is processed.
 
Let me know if this answers or if you have any further queries.
 
And a heads-up - we are working on a advanced application note, which talks about Designing BLE applications using PSoC 6.
 
Regards,
Meenakshi Sundaram R