Hi , nrf connect V.2.5.0 in windows 10 64bit, fails to launch Bluetooth low energy app. "DEBUG UART read operation on port aborted" is the log info which i came to know from the log file.

[bramha]

Hi , nrf connect V.2.5.0 in windows 10 64bit, fails to launch Bluetooth low energy app. "DEBUG UART read operation on port  aborted" is the log info which i came to know from the log file. May i get any useful info to run nrf connect in windows 10. surprisingly the same nrf connect is working for Programmer (experimental )app. i can connect the BL654 DVK and able to read the memory. I would like to know why the low energy app is not working. am i missing any Dll's to install. attached log file for the same for more detailed info.

Fullscreen 2018-10-05T11_47_34.774Z-log.txt Download

2018-10-05T11:47:36.016Z INFO Application data folder: C:\Users\PRO\AppData\Roaming\nrfconnect\pc-nrfconnect-ble
2018-10-05T11:47:36.167Z DEBUG App pc-nrfconnect-ble v2.2.0 official
2018-10-05T11:47:36.167Z DEBUG App path: C:\Users\PRO\.nrfconnect-apps\node_modules\pc-nrfconnect-ble
2018-10-05T11:47:36.167Z DEBUG nRFConnect 2.5.0 is supported by the app (^2.4.0)
2018-10-05T11:47:36.167Z DEBUG nRFConnect path: C:\Users\PRO\AppData\Local\Programs\nrfconnect\resources\app.asar
2018-10-05T11:47:36.167Z DEBUG HomeDir: C:\Users\PRO
2018-10-05T11:47:36.167Z DEBUG TmpDir: C:\Users\PRO\AppData\Local\Temp
2018-10-05T11:47:39.074Z INFO Validating connectivity firmware for device with serial number 000483049005...
2018-10-05T11:47:41.315Z INFO Connectivity firmware is valid.
2018-10-05T11:47:41.316Z INFO Getting information from J-Link debugger...
2018-10-05T11:47:43.061Z INFO Found device type: unknown. J-Link firmware: J-Link OB-SAM3U128 V3 compiled Jul 12 2018 12:17:50.
2018-10-05T11:47:43.061Z INFO Connectivity firmware version: 1.2.3. SoftDevice API version: 3. Baud rate: 1000000.
2018-10-05T11:47:43.063Z INFO Opening adapter connected to COM8
2018-10-05T11:47:43.602Z INFO Successfully opened COM8. Baud rate: 1000000. Flow control: none. Parity: none.

2018-10-05T11:47:43.602Z DEBUG State change: STATE_START -> STATE_RESET

2018-10-05T11:47:43.603Z DEBUG        1 ->  []
               type:          RESERVED_5 reliable: no seq#:0 ack#:0 payload_length:0 data_integrity:0 err_code:0
2018-10-05T11:47:43.604Z INFO Reset performed on adapter COM8
2018-10-05T11:47:43.904Z DEBUG State change: STATE_RESET -> STATE_UNINITIALIZED

2018-10-05T11:47:43.904Z DEBUG        2 ->  [01 7e ]
               type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0
               [SYNC]
2018-10-05T11:47:44.155Z DEBUG        3 ->  [01 7e ]
               type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0
               [SYNC]
2018-10-05T11:47:44.464Z DEBUG        4 ->  [01 7e ]
               type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0
               [SYNC]
2018-10-05T11:47:44.657Z DEBUG        5 ->  [01 7e ]
               type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0
               [SYNC]
2018-10-05T11:47:44.909Z DEBUG        6 ->  [01 7e ]
               type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0
               [SYNC]
2018-10-05T11:47:45.160Z DEBUG        7 ->  [01 7e ]
               type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0
               [SYNC]
2018-10-05T11:47:45.410Z DEBUG State change: STATE_UNINITIALIZED -> STATE_FAILED

2018-10-05T11:47:45.604Z DEBUG UART read operation on port  aborted.

[Susheel Nuguru]

seems like something went wrong on nRF Connect side. I have created an internal ticket for the developer to look into the log and comment back. For your reference the internal ticket number is NCP-2005

[Susheel Nuguru]

I missed the part to see that you are using custom hardware (BL654 DVK) 

the reason it works in Programmer app and not BLE app isn't necessarily strange. The Programmer app only deals with reading and writing to memory, no communication with FW is performed. The BLE app uses UART to communicate with the firmware. This communication seems to break down already at the first packet sent. nRF Connect sends the first setup command, [01 7e ], but gets no response from the connectivity firmware. 

As you already know that the NCP tries to connect to UART and in your configuration, the NCP does not seem to have proper access to UART pins. I am not certain why but a sniff on your UART lines to see what is being sent/Received will give you some better idea. The internal ticket NCP-2005 is now closed.

[bramha]

Hi Aryan. Thanks for the update. "As you already know that the NCP tries to connect to UART and in your configuration, the NCP does not seem to have proper access to UART pins." Could you please elaborate on this proper access to uart pins. Bcoz the problem described in earlier post is also observed with Power Profiler app along with Bluetooth Low Power application. I am using USB2 for flashing the firmware using jlink cdc uart and USB1 for data logging using console/terminal application.

nrf connect from mobile works as expected with out any issues. But for testing the nordic sdk examples, nordic connect desktop version is prescribed. so for the desktop version of nrf connect, i neither can update firmware for jlink when i connect for the first time nor test any above mentioned apps. 

pls find the attached snapshots of using nrf connect desktop version

[Susheel Nuguru]

The segger(debug) chip  on our DK implements the driver for CDC communication from the host over UART. This debug chip in turns communicates with nRF using a fixed pin numbers as UART pins in nRF chip. If in your custom board, if the pin numbers used to connect the CDC UART data to nrf is different, then the firmware flashed into nRF chip would not be able to communicate with nRF connect. 

Make sure that on your board the com port data from your PC goes to nRF pins this way

P5 -> RTS

P6->TXD

P7 -> CTS

P8 -> RXD

and sniff those lines. 

The above pin number is what the firmware flashed in your first image assumes that UART pins are and all the data from nRF side is on those pins. If the COM10 port is connected to different pins then there will be no communication.

Based on the spec of BL654 

The UART pins that are being used are different than what we used to communicate with COM ports.