No bluetooth advertisement is found

[danny0007]

Hi Community,

I made a custom board based on thingy53.

the custom board can be flashed with nRF5340-DK, I see the "merged_domains.hex" is flashed.

Also tried with nRF connect for desktop to flash the "dfu_application.zip", the result is the same.

the appliaction seems no problem, the output from the console looks same as on Thingy53:

*******************************************************************************

[00:00:00.005,187] <inf> Custom_MYMO: Starting Custom

[00:00:00.011,138] <inf> fs_nvs: 8 Sectors of 4096 bytes
[00:00:00.011,138] <inf> fs_nvs: alloc wra: 0, fd0
[00:00:00.011,138] <inf> fs_nvs: data wra: 0, 1c
[00:00:00.036,437] <inf> bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)
[00:00:00.036,468] <inf> bt_hci_core: HW Variant: nRF53x (0x0003)
[00:00:00.036,468] <inf> bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 54.58864 Build 1214809870
[00:00:00.038,757] <inf> bt_hci_core: No ID address. App must call settings_load()
[00:00:00.041,198] <inf> bt_hci_core: Identity: E6:0B:3C:01:47:D0 (random)
[00:00:00.041,229] <inf> bt_hci_core: HCI: version 5.4 (0x0d) revision 0x218f, manufacturer 0x0059
[00:00:00.041,259] <inf> bt_hci_core: LMP: version 5.4 (0x0d) subver 0x218f
return of bt_services_init:0
[00:00:00.044,982] <inf> Custom_MYMO: test print---0

[00:00:00.044,982] <inf> Custom_MYMO: Bluetooth initialized

[00:00:00.044,982] <inf> Custom_MYMO: test print---1

[00:00:00.050,628] <inf> Custom_MYMO: test print---2

[00:00:00.050,628] <inf> Custom_MYMO: Advertising successfully started

MCUBOOT_IMAGE_VERSION:0.0.3
switch LED
switch LED
switch LED
switch LED
switch LED

**************************************************************************************

As you can see "Advertising successfully started" , that means no issue for this function in main:

err = bt_le_adv_start(BT_LE_ADV_CONN, ad, ARRAY_SIZE(ad), sd, ARRAY_SIZE(sd));

    if (err) {

        LOG_ERR("Advertising failed to start (err %d)\n", err);

        return err;

    }

the problem is I can not find the bluetooth advertisement with mobile phone. how can I verify if the network core works correctly? or any other idea?

Best regards

Danny 

[ketiljo]

What's the specification for the 32 MHz crystal you're uisng? Espesially the CL value is important. The default value for the internal load caps is set for a crystal with CL = 8pF and you need to adjust this if you're using a different crystal. Else the frequency of the carrier will be out of spec. 

[danny0007]

this is the 32MHz I'm using: ndk_08142018_NX2016SA-32M-EXS00A-CS06465_SS-1389053.pdf

according to the datasheet, CL=10pF. 

this is the 32.768KHz c_NX2012SA_STD_MUB_1_e-1317508.pdf CL=12.5pF

shall I change them to other crystals? 

[Einar Thorsrud]

Hi,

The crystal should be fine, but you need to adjust the internal load capacitors in the nRF5340. Please see this post for details.

[danny0007]

Hi Einar Thorsrud ketiljo 

Thanks for the reply.

but the post confuses me more.

In the function is capacitance*2-14, but the calculation is talking about capacitance*2-4? 

The CL of my 32M crystal is 10pF, so (2*10pF -4pF)= 16 pF

I put these in the prj.conf:

CONFIG_SOC_HFXO_CAP_INTERNAL=y

CONFIG_SOC_HFXO_CAP_INT_VALUE_X2= 32

 it can be combiled and flashed, but the result is still the old same. any other comments?

and how can I fix this warning:

Many thanks

Danny

[Einar Thorsrud]

Hi Danny,

It looks like you are building for non-secure? That is no problem, but as the oscillator registers can only be controlled from secure, that means that they are set from TF-M in that case, so in your application you will see the missing dependency. It will be set from TF-M though, and you can experiment with it and read out the XOSC32MCAPS register using nrfjprog --memrd 0x400045c4 and see that you get a different value by setting it with your prj.conf settings than without it (you may need to power-cycle the device after chanign it to see the difference).

If this does not work, perhaps there are also other issues than the HFXO capacitors. Have you had your hardware (schematics and layout) reviewed by us at Nordic? If not, I suggest you sumitt your design for review so that we can see if it looks good from an RF perspective.

Einar