RE: nrf5340pdk requires nrf sdk connect v1.4 for bluetooth peripheral example

Einar Thorsrud — Wed, 27 Jan 2021 07:56:23 GMT

Hi Hogyun,

That is a valid point, though this product search page is generic and also contain outdated products. As you can see, most distributors are out of stock, and as the PDK is no longer produced (and has not been for a few months), they will never come back in stock.

Einar

RE: nrf5340pdk requires nrf sdk connect v1.4 for bluetooth peripheral example

ho-gyun choi — Tue, 26 Jan 2021 23:34:35 GMT

Hello Einar

I forgot to mention,

The nrf5340pdk is still available for purchase among the different distributors listed on the Nordic Semiconductor Official Website.

https://www.nordicsemi.com/About-us/BuyOnline?search_token=nRF5340-PDK&series_token=nRF5340

If the PDK is deprecated and no longer supported, it might be worth considering removing the product from the website.

Thank you,

Hogyun

RE: nrf5340 bluetooth peripheral no connected event

ho-gyun choi — Tue, 26 Jan 2021 02:23:47 GMT

Hello Einar,

I have confirmed that the v1.4-branch bluetooth peripheral_hr of nrf connect sdk works with the nrf5340pdk.

Thank you

RE: nrf5340 bluetooth peripheral no connected event

Einar Thorsrud — Mon, 25 Jan 2021 11:43:55 GMT

Hi Hogyun,

I am not able to reproduce this issue on a nRF5340 DK using the specified hash (e303a5162d694c78ae440b0f0450534f37803f50). Could it be that you are testing on the PDK? That is no longer supported and you should use an older version of the nRF Connect SDK for that (1.4.x or earlier) or use a DK instead.

Einar

RE: nrf5340 bluetooth peripheral no connected event

ho-gyun choi — Fri, 22 Jan 2021 14:08:20 GMT

The nRF Connect SDK version is master with commit hash:

ubuntu@molecule--vv-role-nrf-zephyr-dev:/opt/nrf/nrf$ git log
commit e303a5162d694c78ae440b0f0450534f37803f50 (HEAD -> master, origin/master)
Author: Simen S. Røstad <simen.rostad@nordicsemi.no>
Date:   Thu Dec 3 11:14:08 2020 +0100

    net: lib: Align upstream changes to mqtt_keepalive_time_left()
    
     - mqtt_keepalive_time_left() now returns -1 if keep alive messages are
       disabled. Handle this in the various cloud backends.

https://github.com/nrfconnect/sdk-nrf/commit/e303a5162d694c78ae440b0f0450534f37803f50

I have installed the nRF Connect iOS app and it is able to find the Zephyr Heartrate Sensor but it never seems to finish connecting successfully.

The output from the appcore and netcore do not log any new connect event.

output of appcore:

*** Booting Zephyr OS build v2.4.0-ncs1-2616-g3420cde0e37b  ***
Bluetooth initialized
Advertising successfully started
[00:00:00.280,548] <inf> bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)
[00:00:00.280,578] <inf> bt_hci_core: HW Variant: nRF53x (0x0003)
[00:00:00.280,578] <inf> bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 122.465
[00:00:00.283,630] <wrn> bt_hci_core: ECC HCI commands not available
[00:00:00.283,752] <inf> bt_hci_core: Identity: F6:80:24:F1:50:D0 (random)
[00:00:00.283,752] <inf> bt_hci_core: HCI: version 5.2 (0x0b) revision 0x2154, manufacturer 0x0059
[00:00:00.283,752] <inf> bt_hci_core: LMP: version 5.2 (0x0b) subver 0x2154

output of netcore:

*** Booting Zephyr OS build v2.4.0-ncs1-2616-g3420cde0e37b  ***
[00:00:00.005,981] <inf> sdc_hci_driver: SoftDevice Controller build revision: 
                                         7a 01 b4 17 68 14 99 b6  6a d1 f2 fd fe 59 63 e3 |z...h....
                                         43 ca fb 5c                                      |C..\     
--- 27 messages dropped ---
[00:00:00.020,202] <inf> hci_rpmsg: Got callback of id 0
[00:00:00.020,263] <inf> hci_rpmsg: Received message of 4 bytes.
[00:00:00.020,874] <inf> hci_rpmsg: Got callback of id 0
[00:00:00.020,935] <inf> hci_rpmsg: Received message of 4 bytes.
[00:00:00.021,667] <inf> hci_rpmsg: Got callback of id 0
[00:00:00.021,697] <inf> hci_rpmsg: Received message of 8 bytes.
[00:00:00.022,338] <inf> hci_rpmsg: Got callback of id 0
[00:00:00.022,399] <inf> hci_rpmsg: Received message of 4 bytes.
[00:00:00.023,132] <inf> hci_rpmsg: Got callback of id 0
[00:00:00.023,162] <inf> hci_rpmsg: Received message of 12 bytes.
[00:00:00.023,803] <inf> hci_rpmsg: Got callback of id 0
[00:00:00.023,864] <inf> hci_rpmsg: Received message of 12 bytes.
[00:00:00.024,597] <inf> hci_rpmsg: Got callback of id 0
[00:00:00.024,658] <inf> hci_rpmsg: Received message of 4 bytes.
[00:00:00.025,329] <inf> hci_rpmsg: Got callback of id 0
[00:00:00.025,390] <inf> hci_rpmsg: Received message of 4 bytes.
[00:00:00.026,153] <inf> hci_rpmsg: Got callback of id 0
[00:00:00.026,184] <inf> hci_rpmsg: Received message of 4 bytes.
[00:00:00.026,824] <inf> hci_rpmsg: Got callback of id 0
[00:00:00.026,885] <inf> hci_rpmsg: Received message of 4 bytes.
[00:00:00.027,648] <inf> hci_rpmsg: Got callback of id 0
[00:00:00.027,679] <inf> hci_rpmsg: Received message of 10 bytes.
[00:00:00.030,456] <inf> hci_rpmsg: Got callback of id 0
[00:00:00.030,517] <inf> hci_rpmsg: Received message of 19 bytes.
[00:00:00.031,280] <inf> hci_rpmsg: Got callback of id 0
[00:00:00.031,341] <inf> hci_rpmsg: Received message of 36 bytes.
[00:00:00.031,982] <inf> hci_rpmsg: Got callback of id 0
[00:00:00.032,012] <inf> hci_rpmsg: Received message of 36 bytes.
[00:00:00.032,745] <inf> hci_rpmsg: Got callback of id 0
[00:00:00.032,806] <inf> hci_rpmsg: Received message of 5 bytes.

CTRL-A Z for help | 115200 8N1 | NOR | Minicom 2.7.1 | VT102 | Offline | ttyACM1

Below are screenshots of the iOS app attempting to connect to the Zephyr peripheral_hr example. It seems to be stuck on "Connecting".

Thank you for your support

RE: nrf5340 bluetooth peripheral no connected event

Einar Thorsrud — Fri, 22 Jan 2021 13:03:52 GMT

Hi Hogyun,

Which nRF Connect SDK version do you use with your project? Also, do you get the same behaviour if testing with for instance nRF Connect for iOS or Android? If not, what do you see then?

Einar