Shell NUS issue

[Dmitry Kr]

Dear Nordic, 

We've faced with the issue on Zephyr Shell NUS module. 

The captured reaction is just on 'Enter' press in terminal. It seems it has some kind of loopback inside, but why?
The other side is ble_uart_c example at nRF52840DK. (edited) 

We've tried a lot of different config changes (heap, stack increase for different threads), without any positive result. Do you have any meaning on that? What we should check here?

P.S. Do you have ready to use HEX with BLE_UART_C example compiled for nRF52840Dongle with UART-over-USB emulation?

[Sigurd]

Hi,

 Try setting CONFIG_SHELL_BT_NUS_RX_RING_BUFFER_SIZE to 256

I recommend using Putty terminal.

http://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.5.1/nrf/gs_testing.html?highlight=putty#how-to-connect-with-putty

P.S. Do you have ready to use HEX with BLE_UART_C example compiled for nRF52840Dongle with UART-over-USB emulation?

No, I don't think so. 

[Dmitry Kr]

Dear Sigurd, 

I've tried:

1. changing both RX and TX Shell NUS ring buffer sizes up to 4096 bytes. 

2. turning off shell echo and disabling log output to shell.

3. turning off colorization.

No positive outcome on the issue.

[Sigurd]

1) What sample are you using ? Is it shell_bt_nus ?

2) What version of NCS are you using ? NCS v1.5.0?

[Dmitry Kr]

1) No. I've just added shell_bt_nus_init()  and shell_bt_nus_enable() calls as in the example. It's hard to port the example to our board, and I have only one DK right now - and it's running ble_uart_c. I have few dongles, but there is no examples how to run NUS client on dongle.

2) NCS 1.5.1. When I tried 1.5.0 there was the same result.

[Sigurd]

Dmitry Kr said:

I've just added shell_bt_nus_init()  and shell_bt_nus_enable()

1) You added this to the peripheral_uart sample?

2) does it work with the shell_bt_nus sample?

[Dmitry Kr]

1) No. I've added that to our application.

2) No, I can't run it with our board definition files, I'll try this example.

[Sigurd]

Dmitry Kr said:

2) No, I can't run it with our board definition files, I'll try this example.

 Ok. Note that we have this issue mentioned in the known-issues section that might be relevant as well:

NCSDK-8321: NUS shell transport sample does not display the initial shell prompt uart:~$ on the remote terminal.
Also few logs with sending errors are displayed on the terminal connected directly to the DK. This issue is caused by the shell being enabled before turning on the notifications for the NUS service by the remote peer.

Workaround: Enable the shell after turning on the NUS notifications or block it until turning on the notifications.

[Dmitry Kr]

I've added this check and shell enable function call to connection handler, as metioned in shell_bt_nus example, as it can be seen on the first screenshot. It works, bt_nus$ prompt appears.

[Sigurd]

Ok, so the issue you described initially in this case has now been solved?

[Dmitry Kr]

Not yet. 

Please don't close the ticket until we report (hope this week).

[Dmitry Kr]

Dear Sigurd, 

I've found it works with two devboards (52840 + 5340) one running central_uart and another running shell_bt_nus examples. This issue definately related to some middleware modules of Zephyr that we enable on our board (e.g. USB or others). We'll check that.

[Dmitry Kr]

Dear Sigurd, 

Finally we've made that, the shell works over BT NUS connection. We've checked it with nRF52840DK running BT UART CENTRAL example.

Could you please advice if we have ability to:

1. Speed up NUS transport over BT connection.

2. Make it possible to transfer special symbols (up-arrow, down-arrow, Tab and so on) - it works but after pressing 'Enter' key. E.g. to get command list it should be pressed Tab then Enter. Is there any setting in Shell NUS or NUS layer to send the byte(s) not only after receiving 'Enter' chars, but after some timeout too?

Do you have any suggestions on that?