• State Verified Answer
  • Replies 2 replies
  • Subscribers 74 subscribers
  • Views 1147 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 240757
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nRF5340 PDK - peripheral_hr sample not working when built from source

jafp

Hi all,

I successfully flashed the peripheral_hr sample from the Getting Started guide into my nRF5340 PDK (from here: https://infocenter.nordicsemi.com/index.jsp?topic=%2Fug_gsg_ncs%2FUG%2Fgsg%2Ffirst_test.html). The NRF Toolbox app showed connected and the heartrate and battery updated.The UART output showed:

***** Booting Zephyr OS build v1.14.99-ncs3-snapshot2-1329-g6d7f8d05df81 *****
Bluetooth initialized
Advertising successfully started
[00:00:00.023,406] <inf> bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)
[00:00:00.023,437] <inf> bt_hci_core: HW Variant: nRF53x (0x0003)
[00:00:00.023,437] <inf> bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 1.14 Build 99
[00:00:00.025,451] <inf> bt_hci_core: Identity: cf:25:54:1e:77:5e (random)
[00:00:00.025,482] <inf> bt_hci_core: HCI: version 5.1 (0x0a) revision 0x0000, manufacturer 0x05f1
[00:00:00.025,482] <inf> bt_hci_core: LMP: version 5.1 (0x0a) subver 0xffff
Connected
[00:00:12.184,448] <inf> hrs: HRS notifications enabled
[00:00:12.364,471] <inf> bas: BAS Notifications enabled
Disconnected (reason 0x13)
[00:00:17.704,925] <inf> bas: BAS Notifications disabled
[00:00:17.704,956] <inf> hrs: HRS notifications disabled

Now, when building the same sample from source, the NRF Toolbox app fails to subscribe to subscriptions - it simply reports invalid handle, and the UART does not show that it has subscribed to notifications. I also tried connecting with the NRF Connect app, but it simply crashed. I also tried connected the NRF Connect app to an Nordic Thingy and that worked perfectly.

***** Booting Zephyr OS build v2.0.99-ncs1-rc1-764-gb687d5d02214 *****
Bluetooth initialized
Advertising successfully started
[00:00:00.023,040] <inf> bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)
[00:00:00.023,040] <inf> bt_hci_core: HW Variant: nRF53x (0x0003)
[00:00:00.023,071] <inf> bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 2.1 Build 0
[00:00:00.025,329] <inf> bt_hci_core: Identity: cf:25:54:1e:77:5e (random)
[00:00:00.025,329] <inf> bt_hci_core: HCI: version 5.1 (0x0a) revision 0x0000, manufacturer 0x05f1
[00:00:00.025,329] <inf> bt_hci_core: LMP: version 5.1 (0x0a) subver 0xffff
Connected
Disconnected (reason 0x13)

I few details:

  • fw-nrfconnect-nrf currently points at 233fb7c8fec195ffe8476f422f034288943fb28d
  • gcc-arm-none-eabi-9-2019-q4-major-win32 toolchain.
  • nRF Toolbox 4.5.1 on iPhone 8 with iOS 131.3

I did an experiment with the latest periperal_hr application code, and then the old (1.14.99) HCI app for the network processor and that worked.

Any ideas?

Is the NRF5340 and the NCS simply not mature yet to play around with it?

Thanks!

Parents Reply Children
  • +1 in reply to Matt

    Hi , good point - I simply downloaded the latest version of the toolchain from Arm's website.

    However, it doesn't seem to be the root cause of the issue. I tried with another phone (also iPhone 8, iOS 13.1.3), and here it worked. Then I tried to uninstall all nRF apps from the first iPhone, rebooted it and installed the apps again, and now it's working.

    Still not sure really what happened.

    Best,
    Jacob

Related
Terms of service