RE: Problem running zephyr Bluetooth samples with nrf5340 DK using nrf Connect SDK

Amanda Hsieh — Wed, 11 Aug 2021 05:59:32 GMT

Happy to help. 🙂

-Amanda

RE: Problem running zephyr Bluetooth samples with nrf5340 DK using nrf Connect SDK

jrs — Tue, 10 Aug 2021 23:01:06 GMT

Thanks a lot for the reply.

Indeed, I was not programming the network sample from SES.

Once I did that I am able to run the beacon and peripheral samples and I am able to see the signal over the air, as well as I am able to see it using nRF Connect on my Android phone.

Thanks

RE: Problem running zephyr Bluetooth samples with nrf5340 DK using nrf Connect SDK

Amanda Hsieh — Wed, 04 Aug 2021 07:35:29 GMT

Hi,

Do you Program the network sample from SES?

When programming the network with SES v5.34a:

If you get an error message as "Illegal value 0x21009E50 written to register 67 (PSP_NS) ignored", you could execute the commands in the Readback protection section.

There is a known issue with "Illegal value 0x21009E50 written to register 66 (MSP_NS) ignored". Then, I would suggest you use west build and flash via Tool Manager and open command prompt

Locate under zephyr\samples\bluetooth\beacon and execute

west build -b nrf5340dk_nrf5340_cpuappns && west flash --recover

I get the log from the app core as

*** Booting Zephyr OS build v2.4.99-ncs1-3525-g4d068de3f50f  ***

Starting Beacon Demo

Bluetooth initialized

Beacon started, advertising as F6:3C:E5:EB:AD:84 (random)

[00:00:00.028,839] <inf> bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)

[00:00:00.028,839] <inf> bt_hci_core: HW Variant: nRF53x (0x0003)

[00:00:00.028,839] <inf> bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 207.15633 Build 4214451480

[00:00:00.032,684] <inf> bt_hci_core: Identity: F6:3C:E5:EB:AD:84 (random)

[00:00:00.032,714] <inf> bt_hci_core: HCI: version 5.2 (0x0b) revision 0x21c2, manufacturer 0x0059

[00:00:00.032,714] <inf> bt_hci_core: LMP: version 5.2 (0x0b) subver 0x21c2

With nRF Connect mobile app:

-Amanda H.