Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

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

Hello
I am trying to run a simple zephyr bluetooth sample using nrf Connect SDK v. 1.5.1
I am using your nRF5340 DK  The sample I am running is: beacon
I followed your instructions as shown here (to build/download/debug):
 developer.nordicsemi.com/.../gs_programming.html

The nrf Connect Options are the following:
nrf Connect SDK Release: 1.5.1
nRF Connect Toolchain Version: 1.5.1
Projects: beacon
Board Name: nrf5340dk_nrf5340cpuappns

I am able to build and download to the board. I can see on the serial port that
the sample is running. I see a green LED blinking. I can step through the sample using the SES.

However, I am not able to see the beacon using nRF Connect on my Android phone
or while scanning using gatttool with a Raspberry PI 4. Also, I used a spectrum
analyzer to verify if there is any BT signal in the 2.4 GHz band coming out of
the module and was able to confirm there isn't any signal at all.

In summary: the beacon sample is running but there is no RF signal coming out of
the nRF5340 DK board. Any idea of what I might be doing wrong or not doing at
all?
I should also say that the same thing happens with the eddystone and peripheral
samples that I tried.

Thanks



Parents
  • 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.

Reply
  • 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.

Children
No Data
Related