3 Accessing RNBD350 Over UART
The most common application for the host MCU to control the RNBD350 module is via ASCII commands. For development and prototyping purposes, using a terminal emulator to send commands and data over UART is recommended. Any terminal emulator, such as TeraTerm (Windows®) or CoolTerm (Mac® OS X®), is used to control and configure the RNBD350 module via UART on the host PC.
With the RNBD350 module connected to a computer and a serial port enumerated for the UART port, run the terminal emulator to open the COM port using the port settings defined in the following table.
UART Setting | Default Value |
---|---|
Baud rate | 115200 |
Data bits | 8 |
Parity | None |
Stop bits | 1 |
Flow control | Disabled |
To enter Command mode, type $$$ into the terminal emulator. When the RNBD350 module enters Command mode, the RNBD350 module sends the string CMD>
via the UART to indicate the start of the Command mode session.
When in Command mode, valid ASCII commands are issued to control or configure the RNBD350 module. All commands end with a carriage return <cr>('\r', \x0d)
. Do not issue any subsequent command until a response is received for the previous command.
For commands, AOK
indicates a positive or successful response, whereas, Err
indicates an error or negative response. By default, when the RNBD350 module is ready to receive the next command, the command prompt CMD>
is sent to UART.
To return to Data mode, type ---<cr>. Also, in the connected and data channel enabled state, the RNBD350 module can enter into Data mode. For this, it is mandatory to have the UART transparent feature enabled. For details on enabling the UART transparent feature, refer to Default Service Configure (SS,<hex8>).
- The module supports Fast Data mode. In this mode, the module does not enter Command mode even if it receives
$$$
. To enable Fast Data mode, use commandSR
. For more details, refer to Set Application Options (SR,<hex16>). The RNBD350 module supports Low Power mode. If the RNBD350 module’s low power is enabled, the host MCU must wake up the RNBD350 module before sending the UART data out. To wake up the module, pull the UART RX indication pin (PB4) to low.