About the Bluetooth mesh light samples question on NRF5340

[Hugh Wu]

Hi there,

I wanted to bring up the Bluetooth samples on NRF5340 development kit on NRF CONNECT SDK v2.2.0. 

After building and flashing it, I can see the UART log on my COM port device via putty.

Here is my build command: 

west build -b nrf5340df_nrf5340_cpuapp on the path ./ncs/v2.2.0/nrf/samples/bluetooth/mesh/light

and I flash the bin file on the path ./ncs/v2.2.0/nrf/samples/bluetooth/mesh/light/build/zephyr/merged_domains.hex

here is the opening log:

*** Booting Zephyr OS build v3.2.99-ncs1 ***
I: Starting bootloader
I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Boot source: none
I: Swap type: none
I: Bootloader chainload address offset: 0xc000
*** Booting Zephyr OS build v3.2.99-ncs1 ***
Initializing...
[00:00:00.011,444] <inf> fs_nvs: 8 Sectors of 4096 bytes
[00:00:00.011,474] <inf> fs_nvs: alloc wra: 0,Bluetooth initialized
fc8Mesh initialized

[00:00:00.011,474] <inf> fs_nvs: data wra: 0, 2c
[00:00:00.031,036] <inf> bt_hci_core: No ID address. App must call settings_load()

And then, I also installed the nrf mesh, and followed up the video as link https://www.youtube.com/watch?v=XthbU9NP0Yg

I can find my device on the Network of nrf mesh app, and then it can connect to my devices.

but my console appeared with two errors and warm messages:

[00:00:00.011,474] <inf> fs_nvs: data wra: 0, 2c
[00:00:00.031,036] <inf> bt_hci_core: No ID address. App must call settings_load()
[00:14:37.269,226] <wrn> bt_hci_core: opcode 0x2039 status 0x09
[00:14:37.269,256] <err> bt_adv: Failed to start advertiser
[00:14:37.269,256] <err> bt_mesh_adv_ext: Advertising failed: err -111
[00:14:37.853,637] <wrn> bt_l2cap: Ignoring data for unknown channel ID 0x003a

could I know what something is wrong I met?

Thanks 

Hugh

[Hieu]

Hello Hugh,

In your log, I see a 14-second difference from boot until the error happened. Were there some manual trigger/external events before the error happened?

Hieu

[Hugh Wu]

Hi Hieu,

Thanks for your reply, 

No, The 14-second logs happened after clicking the network device from the Nrf mesh App.

[Hugh Wu]

Hi there,

I followed this video https://www.youtube.com/watch?v=Jt2ui22fBjM&t=872s for trying to build up my mesh network.

But I don't have the Thingy:53 device for a mesh light node, so I replace it with NRF5340 DK,

And I also get the provisioned timeout that "Requesting Composition Data..." after clicking the "no OOB" type to provision the device

The UART log as below:

*** Booting Zephyr OS build v3.2.99-ncs1 ***
Initializing...
[00:00:00.448,547] <inf> fs_nvs: 8 Sectors of 4096 bytes
[00:00:00.448,547] <inf> fs_nvsBluetooth initialized
: alloc Mesh initialized
wra: 0, fe8
[00:00:00.448,547] <inf> fs_nvs: data wra: 0, 0
[00:00:00.466,400] <inf> bt_hci_core: No ID address. App must call settings_load()
[00:00:42.885,589] <wrn> bt_l2cap: Ignoring data for unknown channel ID 0x003a
[00:00:47.937,774] <inf> bt_mesh_main: Primary Element: 0x0007
 

Sorry, I don't know how to reproduce the first version log I sent, does anyone assist me with how to set up the Bluetooth mesh network? 

[Hieu]

Hi Hugh,

Sorry for the late follow-up. We are facing a holiday understaffed situation, and my family is just recovering from some surprisingly long lasted health issues.

I personally encountered the same symptom where the provisioned timeout at "Requesting Composition Data..." If I recall correctly, the fix for me was to disable debug options in the build.

Could you please try both of these and let me know if one or both works?

- Disable debug options

- Use NCS v2.0.2, but still build with debug options

[Hugh Wu]

Hi Hieu,

I’m sorry to hear about that. Hope you and your family are going well. 

I think I resolved this problem, I tried to enable the automatic connection on the mesh app of proxy icon, and then I can provision devices by using no OOB as well. Just following the video, I added group, subscribed it, set publish, and whatnot. Finally, I pressed the button from light switch device, and then I saw the led1 was turned on/off on the light device. 
Everything turn out great. 

Hugh