Hi,
On the custom PCB, we have an app running on Dialog, where a main MCU keeps sending data to be send through BLE via UART. The DA is in Buck Mode Configuration with only XTAL16. The app works fine without any sleep mode.
1. I am trying to enable extended sleep mode in the app. Can you please explain, in this scenario where UART peripheral will be active with data to be transmitted intermittently, is it possible to enable extended sleep mode. Will SDK take care of peripheral activity and then enable sleep in between BLE events? I could see that in ble_app_sleepmode where the sleep mode is enabled there's no activity in peripherals.
2. I was not able to find download link for DSPS central project, neither in SDK 5.0.4. Please share me the sources for this example if possible.
Thanks,
Aparna
Hi aparna.anand,
The peripherals will be disabled while the device is in sleep mode and also the UART communication will not be valid if there is no XTAL16 operating and settled (there will be missing data junk etc), so, when the device is in sleep mode you wont be able to operate the UART. The UART is operational when the device is awake and advertising or connected and while is awake due to a connection interval. So while you are in extended sleep mode the time slots that the device wakes up and sleeps automatically, only then you can have valid UART functionallity. The SDK in the sleeping and waking up procedure it only takes into account the BLE events and not any peripheral activity. So if you would like to have UART functionallity in your project with sleep you will have to make sure that the device is awake at that time, for example, the DSPS when operating in sleep mode, it disables the sleep while running (arch_disable_sleep) when data should be transmited, so if the buffers that store the data are empty (no data transmition) the application re-enables sleep and continues waking up and sleeping in order to keep the connection alive with empty BLE events. This is also valid for reception, thats why the DSPS is functional only when using the UART flow control, when the 580 its awake it asserts the RTS during active state in order to indicate to the UART connected device that it is awake and it can receive data otherwise it de-asserts the RTS indicate to the external device that it can not receive any data.
Regarding the DSPS, you will be able to find the DSPS reference design in the Reference design section under Dialog Serial Port (DSPS) link.
Thanks MT_dialog