Hi;
When I enabled sleep in user_config.h as ARCH_EXT_SLEEP_ON. My ADV ınterval is 1000ms. The system wakeup periodicly 1000ms. I think an ble event is triggered at the end of interval. And system is wakeup, advertise and sleep.. I want to learn;
where does it start working after wake up?
Setup:
Software: We are using DA14583 IoT Sensor for the reference design and run the RAW Project.
Hardware: The original design to control the power is based on a switcher, which means that when the switcher is off, the MCU will stop to work.
However, for real application, we would like to change the original switcher design to "softly" control, by entering the extended sleep mode and disable advertising if the button is not pressed.
As a result, we would like to revise the original firmware to realize the “wake-up“” function.
Questions:
Now we would like to wake up the DA14583 and start advertising with the press of a button (Input P2_1). How can I do that in RAW Project?
Could you please some hints to me. Thank you very much!
Hi
I was reading the application note for external wake up mechanism via UART, and saw that the RTS line must be pulsed by the host.
What is the minimum amount of time for which the line must be held high before going low again so that the wake up is guaranteed ?
Best
Ankit
Beside the advertising interval, I'd like to wake up our application on a asynchrone fashion as described in your documentation.
We use the extended sleep mode.
Before putting a sleep, I configure the ports, register the callback function and enable the irq.
Downloading und running the application by J-Link and everything works well.
Programming the same application into our EEPROM by SmartSnippets it behaves different. Everything is working the same, but the callback function got never called. The advertising interval is working fine.
After reading all the documentation about sleeping modes and waking up I can't figure out why it is not working.
Any help welcome.
Best regards
Armin