SDK 15 ble_app_cli

RE: SDK 15 ble_app_cli

Jakub Rzeszutko — Tue, 22 May 2018 05:54:04 GMT

Hi,

If you do not see command execution on RTT backend you can try to change line ending character in the NRF_CLI_DEF macro for this backend. By default you have '\n' , please try with with '\r'.

Regarding mirroring it is behaving as it was designed. For each backend separate CLI object is created with the same commands list. All objects can print logs at the same time but effect of nrf_cli_fprintf will be visible only on the CLI where it was used.

RE: SDK 15 ble_app_cli

BrianK — Mon, 21 May 2018 21:56:08 GMT

Hi jakub,

Thank you for the reply!

It is also working for me now using the python script as you mentioned. I will mark this question answered.

Also from above:

2: Yes I think the RTT backend doesn't send the correct line-end (on macOS at least) so I cannot see any results from cli commands

4: By 'mirroring' I meant that cli command outputs from one transport showing in all other transports. I see now that this is not the case. That is no problem since I really only need to use ble_cli.

Thanks again,

Brian

RE: SDK 15 ble_app_cli

jakub — Sat, 19 May 2018 07:17:34 GMT

Hi,

1. You shall see the same command list for all transports.

2. For RTT backend I recommend to configure PuTTY according to CLI documentation for RTT transport. Next RTT session shall be started by JLinik.exe because JLinkViewer or SES RTT debugger can steal some characters.

3. When I will be at the offce on Monday I can support a bit more regarding configration.

4. Regardin mirroring I am not sure if I understand you correctly. Nevertheless try to execute command: cli echo off.

I was testing ble_cli with python script attached to the example not with any other Nordic tool.