- Silicon Labs Community
- Welcome and Announcements
- Silicon Labs Knowledge Base
- 8-bit MCU
- 32-bit MCU
- Bluetooth / Wi-Fi
- Other Products Category
- Optical/RH/Temp Sensor
- Other Products
- Hardware and Software Tools
- Simplicity Studio and Software
- General Discussions and Suggestions
- Chinese Forum
- Software Libraries
- Development Kits
- Reference Designs
- Third Party Tools
- White Papers
- Official Blog of Silicon Labs
- Chinese Blog
09-12-2017 09:05 AM
I am considering to use BT121 via BGAPI. The Host is STM32F4 MCU.
Hardware connection to the module RX\TX,CTS\RTS.
My MCU using ST "Stop" mode to save power. In this mode the UART of the MCU is not working.
And it is wakes-up by RTC interrupt every 10ms.
Is BT121 have any mechanism to wake-up my MCU before send me resp. or event data via UART.
Some i/o that i can use as input to my MCU to wake-up my MCU from "Stop" mode.
In case of Quastion1 answer is negative.
What happens in BT121 firmware if i deactivate its CTS input (output i/o from my MCU) .
Will it (BT121 firmware) send rsp. or event packets to my MCU during the time its CTS input deactivated ?
Any timeout on this pin,before data (that is ready to be sended to my MCU) is dropped ?
09-22-2017 06:41 AM
Hello - The answer to your question 1 is simple: yes, this mechanism exists. In fact, please consider the option <host_wake_up port="x" pin="x" /> that you can enter into your hardware.xml project file: with that option you can indeed configure a module's output pin that will be automatically asserted when the module is about to send events or responses or data over the UART to host MCU - Best regards.
09-24-2017 12:47 AM
Do you know what time i have (my MCU) for wake-up. I mean after BT121 asserts the "host_wake_up" pin
is there any delay before it starts to send data via uart or BT121 relates on RTS\CTS control pins ?
09-25-2017 07:21 AM
There is no delay after the BT121 asserts the "host_wake_up" pin: data transfer from module to host MCU over UART will happen immediately after the "host_wake_up" pin is asserted, depending of course if the flow control's current status allows it.