multiprotocol OpenThread 'CLI' sample - How to replace UART console interface with BLE interface?

Question

Hi, 
 The 'nRF Connect' SDK (v1.4.99-dev1) sample OpenThread CLI is programmed to receive 'ot' commands from UART console. When configured with multi-protocol support, the app also offers access to a few READ properties, over BLE, such as Device Name & Appearance (value:833 Heart Rate Sensor.) 
 Is there any way to replace the app's UART console with 'BLE' - i.e. instead of receiving 'ot' commands from UART console, make the OpenThread CLI app receive 'ot' commands from Bluetooth interface (e.g. from 'nRF Connect for Mobile') ? 
 
 Regards, 
 Sanju

Vidar Berg · Accepted Answer

Hi Sanju, 
 I have not tested it myself, but it looks like it should be possible if you enable CONFIG_SHELL_BT_NUS as in the NUS shell transport . Attached below is a modified version of the CLI example where I have tried to enable the BT shell. It may serve as a starting point. I have not verified that it actaully works with the host test scripts ( link ) 
 cli_ble.zip 
 Regards, 
 Vidar

Sanju · Answer

Hi Vidar, 
 CONFIG_BT_DEVICE_NAME was set to "NCS DUT" in prj.conf I changed it to "BT_NUS_Shell" and rebuilt the sample and retried ' Testing using shell_bt_nus '. Yet the test script threw the same "Target device not found" error. When checked with 'nRF Connect for Mobile' app, found that the device still advertised with device name "NCS DUT". The updated CONFIG_BT_DEV_NAME in 'prj.conf' doesn't seem to override the default device name. Hence updated (reconfigured) the same in subsys/bluetooth/host/Kconfig. 
 I successfully tested the newly built sample! Thank you very much! 
 Regards, Sanju

multiprotocol OpenThread 'CLI' sample - How to replace UART console interface with BLE interface?

Top Replies