Query Regarding Validating Example Programs in BLE using NRfConnect-3.7.0 for NRf5340 Device

[Jey]

Recently purchased nrf5340 to validate BT and BLE profiles.We have followed the guide and installed NRfConnect-3.7.0.

Installed BLE app and programmer app from nrfconnect application.
As per Guide. We want to validate the sample programs which are given in "Peripheral_Heart_Rate_nRF5340_DK".
Opened the device in the programmer app and "erase and write" with the given sample files.
Tried to open the device in the Bluetooth Low Energy App but, getting the following error.
2021-08-17T06:52:40.845Z ERROR Received status with code 0 PKT_SEND_MAX_RETRIES_REACHED, message: 'No response from device. Tried to send packet 6 times.'
2021-08-17T06:52:42.014Z DEBUG serial port read on port COM20 aborted.
2021-08-17T06:52:42.015Z INFO serial port COM20 closed.
2021-08-17T06:52:42.039Z ERROR Error occurred when opening port. Error code: NRF_ERROR_TIMEOUT (0xd)
Tried to open the device even with Server setup in the BLE app but the error is the same.

Program Write Logs:

2021-08-17T06:40:06.674Z INFO Application data folder: C:\Users\Jeyavenkatesh.r\AppData\Roaming\nrfconnect\pc-nrfconnect-programmer
2021-08-17T06:40:10.042Z DEBUG App pc-nrfconnect-programmer v1.4.11 official
2021-08-17T06:40:10.043Z DEBUG App path: C:\Users\Jeyavenkatesh.r\.nrfconnect-apps\node_modules\pc-nrfconnect-programmer
2021-08-17T06:40:10.043Z DEBUG nRFConnect 3.7.0, required by the app is (^3.6.0)
2021-08-17T06:40:10.043Z DEBUG nRFConnect path: C:\Users\Jeyavenkatesh.r\AppData\Local\Programs\nrfconnect\resources\app.asar
2021-08-17T06:40:10.044Z DEBUG HomeDir: C:\Users\Jeyavenkatesh.r
2021-08-17T06:40:10.044Z DEBUG TmpDir: C:\Users\JEYAVE~1.R\AppData\Local\Temp
2021-08-17T06:40:10.099Z INFO Using nrfjprog library 10.12.1, pc-nrfjprog-js 1.7.6
2021-08-17T06:40:10.533Z VERBOSE Could not fetch serial number for serial port at COM1
2021-08-17T06:40:19.369Z INFO Using nrfjprog to communicate with target
2021-08-17T06:40:27.254Z INFO Using J-Link Software version 6.88
2021-08-17T06:40:29.591Z INFO Segger serial: 960111107
2021-08-17T06:40:29.591Z INFO Segger speed: 2000 kHz
2021-08-17T06:40:29.591Z INFO Segger version: J-Link OB-K22-NordicSemi compiled Jan 21 2020 17:33:01
2021-08-17T06:40:29.593Z INFO Core probed: 960111107
2021-08-17T06:40:29.593Z INFO Core RAM: 512KiB
2021-08-17T06:40:29.593Z INFO Core ROM: 1024KiB in pages of 4KiB
2021-08-17T06:40:29.880Z INFO Model: NRF5340_xxAA_ENGD.
2021-08-17T06:40:32.371Z INFO Segger serial: 960111107
2021-08-17T06:40:32.372Z INFO Segger speed: 2000 kHz
2021-08-17T06:40:32.372Z INFO Segger version: J-Link OB-K22-NordicSemi compiled Jan 21 2020 17:33:01
2021-08-17T06:40:32.372Z INFO Core probed: 960111107:1
2021-08-17T06:40:32.372Z INFO Core RAM: 64KiB
2021-08-17T06:40:32.372Z INFO Core ROM: 256KiB in pages of 2KiB
2021-08-17T06:40:33.736Z INFO Core0: Reading device non-volatile memory. This may take a few seconds.
2021-08-17T06:40:34.971Z INFO Core0: UICR has been read. Click read button to read full non-volatile memory.
2021-08-17T06:40:35.102Z INFO Core1: Reading device non-volatile memory. This may take a few seconds.
2021-08-17T06:40:36.146Z INFO Core1: UICR has been read. Click read button to read full non-volatile memory.
2021-08-17T06:40:41.458Z INFO Parsing HEX file: C:\Users\Jeyavenkatesh.r\Downloads\Peripheral_Heart_Rate_nRF5340_DK\Peripheral_Heart_Rate_nRF5340_DK\hci_open_amp.hex
2021-08-17T06:40:42.108Z INFO File was last modified at 12/2/2020, 2:06:52 PM
2021-08-17T06:40:45.791Z INFO Parsing HEX file: C:\Users\Jeyavenkatesh.r\Downloads\Peripheral_Heart_Rate_nRF5340_DK\Peripheral_Heart_Rate_nRF5340_DK\peripheral_hr.hex
2021-08-17T06:40:45.791Z INFO File was last modified at 12/2/2020, 2:06:50 PM
2021-08-17T06:41:36.837Z INFO Writing image to disable app readback protection
2021-08-17T06:41:36.837Z INFO Image path: C:\Users\Jeyavenkatesh.r\.nrfconnect-apps\node_modules\pc-nrfconnect-programmer\resources\firmware\disable_approtect_nrf5340_application.hex
2021-08-17T06:41:39.971Z INFO Writing image to disable app readback protection
2021-08-17T06:41:39.975Z INFO Image path: C:\Users\Jeyavenkatesh.r\.nrfconnect-apps\node_modules\pc-nrfconnect-programmer\resources\firmware\disable_approtect_nrf5340_network.hex
2021-08-17T06:41:45.270Z INFO Recovery procedure finished
2021-08-17T06:41:45.420Z INFO Using nrfjprog to communicate with target
2021-08-17T06:41:46.127Z INFO Using J-Link Software version 6.88
2021-08-17T06:41:46.721Z INFO Segger serial: 960111107
2021-08-17T06:41:46.722Z INFO Segger speed: 2000 kHz
2021-08-17T06:41:46.722Z INFO Segger version: J-Link OB-K22-NordicSemi compiled Jan 21 2020 17:33:01
2021-08-17T06:41:46.723Z INFO Core probed: 960111107
2021-08-17T06:41:46.723Z INFO Core RAM: 512KiB
2021-08-17T06:41:46.723Z INFO Core ROM: 1024KiB in pages of 4KiB
2021-08-17T06:41:47.007Z INFO Model: NRF5340_xxAA_ENGD.
2021-08-17T06:41:48.381Z INFO Segger serial: 960111107
2021-08-17T06:41:48.381Z INFO Segger speed: 2000 kHz
2021-08-17T06:41:48.381Z INFO Segger version: J-Link OB-K22-NordicSemi compiled Jan 21 2020 17:33:01
2021-08-17T06:41:48.381Z INFO Core probed: 960111107:1
2021-08-17T06:41:48.381Z INFO Core RAM: 64KiB
2021-08-17T06:41:48.381Z INFO Core ROM: 256KiB in pages of 2KiB
2021-08-17T06:41:49.343Z INFO Core0: Reading device non-volatile memory. This may take a few seconds.
2021-08-17T06:41:50.083Z INFO Core0: UICR has been read. Click read button to read full non-volatile memory.
2021-08-17T06:41:50.212Z INFO Core1: Reading device non-volatile memory. This may take a few seconds.
2021-08-17T06:41:51.068Z INFO Core1: UICR has been read. Click read button to read full non-volatile memory.
2021-08-17T06:41:51.259Z INFO Using nrfjprog to communicate with target
2021-08-17T06:41:51.850Z INFO Using J-Link Software version 6.88
2021-08-17T06:41:52.392Z INFO Segger serial: 960111107
2021-08-17T06:41:52.392Z INFO Segger speed: 2000 kHz
2021-08-17T06:41:52.392Z INFO Segger version: J-Link OB-K22-NordicSemi compiled Jan 21 2020 17:33:01
2021-08-17T06:41:52.393Z INFO Core probed: 960111107
2021-08-17T06:41:52.393Z INFO Core RAM: 512KiB
2021-08-17T06:41:52.393Z INFO Core ROM: 1024KiB in pages of 4KiB
2021-08-17T06:41:52.657Z INFO Model: NRF5340_xxAA_ENGD.
2021-08-17T06:41:53.892Z INFO Segger serial: 960111107
2021-08-17T06:41:53.893Z INFO Segger speed: 2000 kHz
2021-08-17T06:41:53.893Z INFO Segger version: J-Link OB-K22-NordicSemi compiled Jan 21 2020 17:33:01
2021-08-17T06:41:53.893Z INFO Core probed: 960111107:1
2021-08-17T06:41:53.893Z INFO Core RAM: 64KiB
2021-08-17T06:41:53.893Z INFO Core ROM: 256KiB in pages of 2KiB
2021-08-17T06:41:54.829Z INFO Core0: Reading device non-volatile memory. This may take a few seconds.
2021-08-17T06:41:55.532Z INFO Core0: UICR has been read. Click read button to read full non-volatile memory.
2021-08-17T06:41:55.670Z INFO Core1: Reading device non-volatile memory. This may take a few seconds.
2021-08-17T06:41:56.484Z INFO Core1: UICR has been read. Click read button to read full non-volatile memory.
2021-08-17T06:41:56.637Z INFO Writing procedure starts for core0
2021-08-17T06:42:03.245Z INFO Write procedure finished
2021-08-17T06:42:03.246Z INFO Writing procedure starts for core1
2021-08-17T06:42:19.158Z INFO Write procedure finished
2021-08-17T06:42:19.192Z INFO Using nrfjprog to communicate with target
2021-08-17T06:42:19.798Z INFO Using J-Link Software version 6.88
2021-08-17T06:42:20.343Z INFO Segger serial: 960111107
2021-08-17T06:42:20.344Z INFO Segger speed: 2000 kHz
2021-08-17T06:42:20.344Z INFO Segger version: J-Link OB-K22-NordicSemi compiled Jan 21 2020 17:33:01
2021-08-17T06:42:20.344Z INFO Core probed: 960111107
2021-08-17T06:42:20.344Z INFO Core RAM: 512KiB
2021-08-17T06:42:20.344Z INFO Core ROM: 1024KiB in pages of 4KiB
2021-08-17T06:42:20.627Z INFO Model: NRF5340_xxAA_ENGD.
2021-08-17T06:42:21.811Z INFO Segger serial: 960111107
2021-08-17T06:42:21.811Z INFO Segger speed: 2000 kHz
2021-08-17T06:42:21.811Z INFO Segger version: J-Link OB-K22-NordicSemi compiled Jan 21 2020 17:33:01
2021-08-17T06:42:21.811Z INFO Core probed: 960111107:1
2021-08-17T06:42:21.811Z INFO Core RAM: 64KiB
2021-08-17T06:42:21.812Z INFO Core ROM: 256KiB in pages of 2KiB
2021-08-17T06:42:22.791Z INFO Core0: Reading device non-volatile memory. This may take a few seconds.
2021-08-17T06:42:23.537Z INFO Core0: UICR has been read. Click read button to read full non-volatile memory.
2021-08-17T06:42:23.681Z INFO Core1: Reading device non-volatile memory. This may take a few seconds.
2021-08-17T06:42:24.529Z INFO Core1: UICR has been read. Click read button to read full non-volatile memory

BLE_APP Log:

2021-08-17T06:51:56.438Z INFO Application data folder: C:\Users\Jeyavenkatesh.r\AppData\Roaming\nrfconnect\pc-nrfconnect-ble
2021-08-17T06:51:57.346Z DEBUG App pc-nrfconnect-ble v2.5.2 official
2021-08-17T06:51:57.346Z DEBUG App path: C:\Users\Jeyavenkatesh.r\.nrfconnect-apps\node_modules\pc-nrfconnect-ble
2021-08-17T06:51:57.347Z DEBUG nRFConnect 3.7.0, required by the app is (^3.6.0)
2021-08-17T06:51:57.347Z DEBUG nRFConnect path: C:\Users\Jeyavenkatesh.r\AppData\Local\Programs\nrfconnect\resources\app.asar
2021-08-17T06:51:57.347Z DEBUG HomeDir: C:\Users\Jeyavenkatesh.r
2021-08-17T06:51:57.347Z DEBUG TmpDir: C:\Users\JEYAVE~1.R\AppData\Local\Temp
2021-08-17T06:51:57.519Z INFO Updated list of uuids with data from github.com/.../v1
2021-08-17T06:51:57.525Z VERBOSE Could not fetch serial number for serial port at COM1
2021-08-17T06:52:05.775Z INFO Connected to device with serial number: 000960111107 and family: nrf53
2021-08-17T06:52:05.775Z DEBUG Note: no pre-compiled firmware is available for the selected device. You may still use the app if you have programmed the device with a compatible connectivity firmware.
2021-08-17T06:52:05.775Z INFO The device is not in the list of supported devices. Attempting to open as a custom device.
2021-08-17T06:52:05.776Z INFO Opening custom device
2021-08-17T06:52:05.776Z INFO Note: firmware must be compatible with connectivity firmware version: 4.1.2, SoftDevice API version: 5 and baud rate: 1000000.
2021-08-17T06:52:05.782Z INFO Opening adapter connected to COM20
2021-08-17T06:52:06.745Z INFO Successfully opened COM20. Baud rate: 1000000. Flow control: none. Parity: none.
2021-08-17T06:52:06.746Z DEBUG State change: STATE_START -> STATE_RESET
2021-08-17T06:52:06.746Z DEBUG 1 -> [N/A] type: RESERVED_5 reliable: no seq#:0 ack#:0 payload_length:0 data_integrity:0 err_code:0x0
2021-08-17T06:52:06.755Z INFO Reset performed on adapter COM20
2021-08-17T06:52:07.065Z DEBUG State change: STATE_RESET -> STATE_UNINITIALIZED
2021-08-17T06:52:07.066Z DEBUG 2 -> [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
2021-08-17T06:52:07.328Z DEBUG 3 -> [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
2021-08-17T06:52:07.581Z DEBUG 4 -> [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
2021-08-17T06:52:07.834Z DEBUG 5 -> [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
2021-08-17T06:52:08.088Z DEBUG 6 -> [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
2021-08-17T06:52:08.339Z DEBUG 7 -> [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
2021-08-17T06:52:08.592Z DEBUG State change: STATE_UNINITIALIZED -> STATE_NO_RESPONSE
2021-08-17T06:52:08.592Z ERROR Received status with code 0 PKT_SEND_MAX_RETRIES_REACHED, message: 'No response from device. Tried to send packet 6 times.'
2021-08-17T06:52:09.758Z DEBUG serial port read on port COM20 aborted.
2021-08-17T06:52:09.826Z ERROR Error occured when opening port. Errorcode: NRF_ERROR_TIMEOUT (0xd)

2021-08-17T06:52:32.857Z INFO Device closed.
2021-08-17T06:52:38.046Z INFO Connected to device with serial number: 000960111107 and family: nrf53
2021-08-17T06:52:38.046Z DEBUG Note: no pre-compiled firmware is available for the selected device. You may still use the app if you have programmed the device with a compatible connectivity firmware.
2021-08-17T06:52:38.047Z INFO The device is not in the list of supported devices. Attempting to open as a custom device.
2021-08-17T06:52:38.047Z INFO Opening custom device
2021-08-17T06:52:38.047Z INFO Note: firmware must be compatible with connectivity firmware version: 4.1.2, SoftDevice API version: 5 and baud rate: 1000000.
2021-08-17T06:52:38.051Z INFO Opening adapter connected to COM20
2021-08-17T06:52:39.000Z INFO Successfully opened COM20. Baud rate: 1000000. Flow control: none. Parity: none.
2021-08-17T06:52:39.000Z DEBUG State change: STATE_START -> STATE_RESET
2021-08-17T06:52:39.001Z DEBUG 1 -> [N/A] type: RESERVED_5 reliable: no seq#:0 ack#:0 payload_length:0 data_integrity:0 err_code:0x0
2021-08-17T06:52:39.004Z INFO Reset performed on adapter COM20
2021-08-17T06:52:39.312Z DEBUG State change: STATE_RESET -> STATE_UNINITIALIZED
2021-08-17T06:52:39.313Z DEBUG 2 -> [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
2021-08-17T06:52:39.564Z DEBUG 3 -> [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
2021-08-17T06:52:39.814Z DEBUG 4 -> [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
2021-08-17T06:52:40.063Z DEBUG 5 -> [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
2021-08-17T06:52:40.327Z DEBUG 6 -> [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
2021-08-17T06:52:40.591Z DEBUG 7 -> [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
2021-08-17T06:52:40.844Z DEBUG State change: STATE_UNINITIALIZED -> STATE_NO_RESPONSE
2021-08-17T06:52:40.845Z ERROR Received status with code 0 PKT_SEND_MAX_RETRIES_REACHED, message: 'No response from device. Tried to send packet 6 times.'
2021-08-17T06:52:42.014Z DEBUG serial port read on port COM20 aborted.
2021-08-17T06:52:42.015Z INFO serial port COM20 closed.
2021-08-17T06:52:42.039Z ERROR Error occured when opening port. Errorcode: NRF_ERROR_TIMEOUT (0xd)

[ovrebekk]

Hi

What device are you using on the PC side to act as the Bluetooth central? 

When using the BLE app in nRF Connect for Desktop you need some nRF52 dongle or DK connected to the PC, as described here. 

Best regards
Torbjørn

[Jey]

Hi 

Thanks for your reply.

I am using nRF5340 DK on Windows10 PC to use nRF Connect and nRF toolbox on mobile.

Is DK not sufficient to do BLE testing using BLE App?

Is nRF52 dongle is mandatory to use with nRF5340-DK?

Thanks,

Jey

[ovrebekk]

Hi Jey

You can't use the nRF5340DK with the nRF Connect for Desktop BLE app, no. You need one of the boards mentioned in the documentation that I linked to earlier:

Supported devices

• PCA10056 nRF52840 Development Kit
• PCA10040 nRF52 Development Kit
• PCA10059 nRF52840 Dongle
• PCA10028 nRF51 Development Kit
• PCA10031 nRF51 Dongle

Jey said:

Is DK not sufficient to do BLE testing using BLE App?

If you use the nRF Connect mobile app then you don't need a separate dongle or board, and can connect to your nRF5340DK from the phone directly. For many purposes this might be sufficient, but the nRF Connect for Desktop BLE app has some features that the mobile app does not. 

The nRF52840 dongle (PCA10059) can be purchased for around 10 Euros/dollars, and is recommended to get as an accessory for your nRF5340DK if you want to use the nRF Connect for Desktop BLE app or the Nordic Bluetooth sniffer. 

Best regards
Torbjørn

[Jey]

Hi  Torbjørn,

         Thanks for your reply. will purchase the specified dongle and test it.

[ovrebekk]

You welcome. I will consider the case resolved then

BR
Torbjørn