sdk14 ble_app_uart not working

RE: sdk14 ble_app_uart not working

robotjosh — Tue, 22 Aug 2017 15:11:09 GMT

I refiled this bug here devzone.nordicsemi.com/.../

RE: sdk14 ble_app_uart not working

robotjosh — Tue, 22 Aug 2017 15:01:51 GMT

I think I have found the problem, it is due to a missing low frequency crystal on the ble central device that I am connecting. I should file another issue for this.

RE: sdk14 ble_app_uart not working

Jørgen Holmefjord — Tue, 22 Aug 2017 08:41:03 GMT

Did you try with the precompiled hex-file, as I suggested above?

RE: sdk14 ble_app_uart not working

robotjosh — Fri, 18 Aug 2017 14:22:45 GMT

I made these observations using a logic analyzer on the serial line to rule out any problem with the software. I am using armgcc with pca10040, sdk14.0.0_3bcc1f7

RE: sdk14 ble_app_uart not working

Jørgen Holmefjord — Fri, 18 Aug 2017 07:31:27 GMT

What serial software are you using, and what is the settings of the connection? I have tested the example with my setup and it works as expected.

RE: sdk14 ble_app_uart not working

robotjosh — Wed, 16 Aug 2017 15:06:32 GMT

I was able to wait for the notifications enabled message and then try to send a string. It does not trigger anything on the uart output. I know the uart output itself is working because of the "Uart start" message it prints on bootup.

RE: sdk14 ble_app_uart not working

Jørgen Holmefjord — Wed, 16 Aug 2017 14:46:34 GMT

You should get a message saying "Notifications enabled", I cannot see this on your screenshot. Could you try flashing the precompiled hex-file found in [SDK_ROOT]\examples\ble_peripheral\ble_app_uart\hex\ble_app_uart_pca10040_s132.hex to make sure there have been no changes to the SDK/example?

RE: sdk14 ble_app_uart not working

robotjosh — Wed, 16 Aug 2017 14:39:53 GMT

I attached the log to the main post. Entering text into that input does not add anything to the log.

RE: sdk14 ble_app_uart not working

Jørgen Holmefjord — Wed, 16 Aug 2017 14:26:28 GMT

Could you post the log from the "terminal" window in nRF Toolbox?

RE: sdk14 ble_app_uart not working

robotjosh — Wed, 16 Aug 2017 14:24:47 GMT

I was connected- disconnected and reconnected to make sure. The command input is no longer disabled but entering strings does not appear to do anything.

RE: sdk14 ble_app_uart not working

Jørgen Holmefjord — Wed, 16 Aug 2017 14:19:59 GMT

Did you connect first? You will not be able to write any commands before you are connected to the UART device.

RE: sdk14 ble_app_uart not working

robotjosh — Wed, 16 Aug 2017 14:18:38 GMT

I see the terminal like part of the screen but the write command input is disabled. I was able to assign a string to one of the buttons but pressing it does not appear to do anything.

RE: sdk14 ble_app_uart not working

Jørgen Holmefjord — Wed, 16 Aug 2017 14:13:49 GMT

Try rotating the screen or slide the screen towards right side. Then you should se a terminal-like window. You can also click edit, and add commands to the gray boxes to simplify transmission of given commands.

RE: sdk14 ble_app_uart not working

robotjosh — Wed, 16 Aug 2017 14:11:14 GMT

I tried nrf toolbox for ble, it was able to connect and go to a uart tab, but this screen is a 3x3 grid of gray boxes that do not appear to do anything. I don't see any input to enter a uart string. The only input on this screen appears to be a disconnect button, which does not appear to do anything when pressed.

RE: sdk14 ble_app_uart not working

Jørgen Holmefjord — Wed, 16 Aug 2017 13:48:26 GMT

Could you try nRF Toolbox app on the phone as well? Is the issue on transfers both to and from the phone?

RE: sdk14 ble_app_uart not working

robotjosh — Wed, 16 Aug 2017 13:31:05 GMT

I am using PCA10040 and flashed with all default options from sdk14. To rule out uart software, I attached a logic probe and am seeing the same behavior. I used a phone with nrfconnect app and also tried with blescan app with same results.

RE: sdk14 ble_app_uart not working

Jørgen Holmefjord — Wed, 16 Aug 2017 13:17:22 GMT

How did you test the example? Are you testing against phone or other board? Which terminal software are you using? I'm not able to reproduce this issue with my board and phone.