5.9.2 Status Event

The following table lists the status event returned by the RNBD350 module via UART when a specific event occurs.

Table 5-38. Status Event Returned by the RNBD350 Module
Status Event Default Delimiter (%)Description
System Configuration
%REBOOT%Reboot finished
%RMT_CMD_OFF%End of Remote Command mode
%RMT_CMD_ON%Start of Remote Command mode
%RMT_TX_POWER%Remote TX power level
%PHY_UPDATED,<ConnHandle>,<Tx PHY>,<Rx PHY>%PHY update successful
%ERR_PHYUPDATE,<ConnHandle>%PHY update fail
Advertising

%<Addr>,<Addr Type>,<name>, <UUIDs>,<RSSI>%

Received connectable advertisement
%<Address>,<Addr_Type>,<RSSI> Brcst:<Broadcast Payload>%Received non-connectable advertisement
%ADV_TIMEOUT%Advertisement timeout, if advertisement time is specified by command A
Connection
%CONN_PARAM,<Interval>, <Latency>,<Timeout>%Update connection parameters of connection interval, latency and supervision timeout
%CONNECT,<0-3>,<Addr>,<ConnHandle>%Address Type<0-3>:
  • 0 – Public address type
  • 1 – Random static address type
  • 2 – Random resolvable address type
  • 3 – Random non resolvable address type
%DISCONNECT,<ConnHandle>%Bluetooth® Low Energy connection lost
%ERR_CONNPARM,<ConnHandle>%Failed to update connection parameters
%ERR_CONN,<ConnHandle>%Failed to connect a remote device
%ERR_READ%Failed to read characteristic value
%ERR_WRITE%Failed to write characteristic value
Security
%BONDED%Security materials such as link key are saved into PDS
%KEY:<Key>%Display the six digit security key
%KEY_REQ%Request input security key
%SECURED%Bluetooth Low Energy link is secured
%ERR_RMT_CMD%Failed to start remote command, due to insecure Bluetooth Low Energy link or mismatch PIN code
%ERR_SEC%Failed to secure the Bluetooth Low Energy link
GATT
%STREAM_OPEN%UART transparent data pipe is established
%INDI,<hdl>,<hex>%

Append connection handle in multiple link: %INDI,<hdl>,<hex>,<connHandle>%

Received value indication <hex> for characteristic handle <hdl>
%NOTI,<hdl>,<hex>%

Append connection handle in multiple link: %NOTI,<hdl>,<hex>,<connHandle>%

Received value notification <hex> for characteristic handle <hdl>
%ERR_MEMORY%Running out of dynamic memory
%WC,<hdl>,<hex>%

Append connection handle in multiple link: %WC,<hdl>,<hex>,<connHandle>%

Received start/end notification/indication request <hex> for characteristic configuration handle <hdl>,<connHandle> (Connection handle in multiple link scenario)
%WV,<hdl>,<hex>%

Append connection handle in multiple link: %WV,<hdl>,<hex>,<connHandle>%

Received write request <hex> for characteristic handle <hdl>,<connHandle> (Connection handle in multiple link scenario)
%RE_DISCV%Received data indication of service changed, redo service discovery
DFU

%OTA_REQ,<connHandle >, <fwImageSize >, <fwImageId>, <fwImageVer>[,<fwImageChksum/hex16>,<fwImageCrc16/hex16>]%

OTA DFU request with parameters to describe the image. Optional parameters “fwImageChksum” and “fwImageCrc16” are used in Host OTA DFU, they exist in OTAU Header v2
%OTA_START,<imageType>%OTA DFU procedure starts for the corresponding image type
%OTA_UPDATING,<updatedPercentage>%OTA DFU updating progressing indication
%OTA_FAIL%OTA procedure fails
%OTA_CCOMPLETE%OTA procedure completed
%VALIDATING%OTA/MCU DFU image validating
%VALIDATION_SUCCESS%OTA/MCU DFU image validation success
%VALIDATION_FAIL%OTA/MCU DFU image validation fail
%DFU_TIMEOUT%OTA/MCU DFU timeout

%OTA_DATA,<fragment id/hex8>,<length/hex16>,<payload>%

MCU DFU image segmented payload is transmitted to the host, and the payload content is in hex. This event is used in the Host OTA DFU procedure.

The first parameter is the fragment ID that the Host MCU used in identifying received payload data; the second parameter is following payload length, the third parameter is the payload in hex