Device not connecting in boot loader mode

RE: Device not connecting in boot loader mode

Edvin — Wed, 27 Nov 2019 08:58:09 GMT

[quote user="Edvin Holmseth"]And what is the specs of the LFXTAL?[/quote]

12pF for the caps is correct if the internal capacity of the XTAL is 8pF.

You can read about it here:

https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.nrf52832.ps.v1.1%2Fclock.html&cp=4_2_0_18_1_3&anchor=concept_pln_z5y_2q

The capacitance on the capacitors should be:

C = 2xC_L - C_pin

C_L = capacitance on the XTAL

C_pin = 4 (nRF specification).

So on the DK, C_L = 8pF, so the capacitors should be:

C = 2x8-4 = 12pF

But it may not be the same for your capacitor.

Also, please make sure you set the XTAL accuracy in sdk_config.h according to the accuracy on your XTAL from it's specification.

BR,

Edvin

RE: Device not connecting in boot loader mode

ssc — Wed, 27 Nov 2019 06:53:26 GMT

[quote userid="26071" url="~/f/nordic-q-a/54435/device-not-connecting-in-boot-loader-mode/222122"]Do you have an external XTAL? I was actually wondering what the values were. [/quote]

Yes i do have an external crystal ABS07-32.768kHz is used .

[quote userid="26071" url="~/f/nordic-q-a/54435/device-not-connecting-in-boot-loader-mode/222122"]what is the value of the capacitors on your custom board (the ones connected between the XTAL and the nRF)[/quote]

12pF

RE: Device not connecting in boot loader mode

Edvin — Tue, 26 Nov 2019 13:56:48 GMT

Do you have an external XTAL? I was actually wondering what the values were.

But if you used NRF_CLOCK_LF_SRC_XTAL, what is the value of the capacitors on your custom board (the ones connected between the XTAL and the nRF)? And what is the specs of the LFXTAL?

RE: Device not connecting in boot loader mode

ssc — Tue, 26 Nov 2019 09:34:15 GMT

Following were the clock configurations before the change in boot loader:

For Application:

NRF_SDH_CLOCK_LF_SRC = NRF_CLOCK_LF_SRC_SYNTH
NRF_SDH_CLOCK_LF_RC_CTIV = NRF_CLOCK_LF_SRC_RC
NRF_SDH_CLOCK_LF_RC_TEMP=_CTIVNRF_CLOCK_LF_SRC_RC
NRF_SDH_CLOCK_LF_ACCURACY= NRF_CLOCK_LF_ACCURACY_20_PPM

For boot loader:

NRF_SDH_CLOCK_LF_SRC = NRF_CLOCK_LF_SRC_XTAL
NRF_SDH_CLOCK_LF_RC_CTIV = NRF_CLOCK_LF_SRC_RC
NRF_SDH_CLOCK_LF_RC_TEMP=_CTIVNRF_CLOCK_LF_SRC_RC
NRF_SDH_CLOCK_LF_ACCURACY= NRF_CLOCK_LF_ACCURACY_20_PPM

RE: Device not connecting in boot loader mode

Edvin — Tue, 26 Nov 2019 09:16:36 GMT

Are all the clock configurations in your bootloader and the application the same? Before you changed to NRF_CLOCK_LF_SRC_SYNTH in the bootloader, of course.

The settings I am asking about are:

NRF_SDH_CLOCK_LF_SRC
NRF_SDH_CLOCK_LF_RC_CTIV
NRF_SDH_CLOCK_LF_RC_TEMP_CTIV
NRF_SDH_CLOCK_LF_ACCURACY

Note that these are not the same as:

NRFX_CLOCK_CONFIG_LF_SRC. I am looking for the defines with "..._SDH_..."

Can you list these defines from the bootloader project and for the application project?

BR,

Edvin

RE: Device not connecting in boot loader mode

ssc — Sat, 23 Nov 2019 07:00:07 GMT

Hello Edvin ,

I think it is clock related issue. I change the NRF_SDH_CLOCK_LF_SRC to NRF_CLOCK_LF_SRC_SYNTH instead of NRF_CLOCK_LF_SRC_XTAL . Then Boot-loader worked for all over voltage range of 5 volt to 30 volts. I have question that if Application BLE worked fine then why Boot loader had issue ?

Thanks and regards

RE: Device not connecting in boot loader mode

Edvin — Fri, 22 Nov 2019 14:19:46 GMT

If it doesn't show up in nRF Connect for desktop either, then there must be something wrong. Have you tried to sniff the connection? Does the central send a service discovery message?

RE: Device not connecting in boot loader mode

ssc — Fri, 22 Nov 2019 13:55:05 GMT

[quote userid="26071" url="~/f/nordic-q-a/54435/device-not-connecting-in-boot-loader-mode/221533"]Can you try to connect to it with nRF Connect for desktop? It should always do service discovery, while on mobile phones, it is the OS that decides whether it should do a service discovery or not. [/quote]

Yes i have tried with desktop it behaves the same way it behaves for mobile. If it was the issue for discovery it should get at lower voltages too.

I get error 8: BLE_HCI_CONNECTION_TIMEOUT when i use 24 volt.

So i referred to THIS link. and changed the PPM to 500 but no luck.

RE: Device not connecting in boot loader mode

Edvin — Fri, 22 Nov 2019 11:41:39 GMT

[quote user="Sarika"]Why BLE do not allow service discovery in bootloader mode.. where it works in application ? [/quote]

It does allow service discovery. Can you try to connect to it with nRF Connect for desktop? It should always do service discovery, while on mobile phones, it is the OS that decides whether it should do a service discovery or not. What are you trying to connect with? A phone? Is it the same behavior if you use nRF Connect for Desktop?

RE: Device not connecting in boot loader mode

ssc — Thu, 21 Nov 2019 17:51:13 GMT

Hello Edvin,

Yes this works on dk but not on custom pcb when given supply of 24volts. For voltages below 22 it works fine. I don't understand why it is so? All logs given in above text file are from custom boards... Is there anything missing or else... Perfectly working log is for 5v supply given.

Why BLE do not allow service discovery in bootloader mode.. where it works in application ? What are electrical requirements for ble connection and service discovery?

RE: Device not connecting in boot loader mode

Edvin — Thu, 21 Nov 2019 16:09:16 GMT

Does this mean that it works on the DK, but not on the custom PCB? Did you have a log from the custom PCB with Voltage = 5v, when it was working? Or is it not working when you have 5v on the custom PCB either?

Also, I didn't understand the DK log. Does the log start in the middle of the DFU process?

RE: Device not connecting in boot loader mode

ssc — Thu, 21 Nov 2019 07:55:04 GMT

[quote userid="26071" url="~/f/nordic-q-a/54435/device-not-connecting-in-boot-loader-mode/221218"]Can you send me the logs from when it is working and when it isn't?[/quote]

devzone.nordicsemi.com/.../Debug_5F00_log_5F00_of_5F00_bootloader_5F00_for_5F00_not_5F00_connecting_5F00_19_5F00_11_5F00_19.txt

[quote userid="26071" url="~/f/nordic-q-a/54435/device-not-connecting-in-boot-loader-mode/221218"]This LDO is external, right?[/quote]

Yes

[quote userid="26071" url="~/f/nordic-q-a/54435/device-not-connecting-in-boot-loader-mode/221218"]That is including external components? Not the nRF?[/quote]

Yes that is including external components. Overall PCB load corrent taken from supply.

RE: Device not connecting in boot loader mode

Edvin — Thu, 21 Nov 2019 07:41:52 GMT

Can you send me the logs from when it is working and when it isn't?

[quote user="Sarika"]So i tested with replacing DCDC to LDO (12 to 5 V)[/quote]

This LDO is external, right?

[quote user="Sarika"]My total PCB Load current takes 50 mA.[/quote]

That is including external components? Not the nRF?

RE: Device not connecting in boot loader mode

ssc — Wed, 20 Nov 2019 13:02:34 GMT

[quote userid="26071" url="~/f/nordic-q-a/54435/device-not-connecting-in-boot-loader-mode/221066"]Have you enabled bonding in the bootloader project?[/quote]

No. for disabling bond i have done:

// <h> BLE DFU security

//==========================================================
// <q> NRF_DFU_BLE_REQUIRES_BONDS - Require bond with peer.

#ifndef NRF_DFU_BLE_REQUIRES_BONDS
#define NRF_DFU_BLE_REQUIRES_BONDS 0
#endif

[quote userid="26071" url="~/f/nordic-q-a/54435/device-not-connecting-in-boot-loader-mode/221066"] These lines indicates that there is no valid application in the memory. Is the application programmed to the nRF? If so, how was it programmed? Via DFU or via programmer? If programmer, did you also program the correct signed bootloader settings?[/quote]

Yes these logs are right there is no application firmware as i have erased whole flash and only flashed boot loader code. I am not able to connect to the device in boot loader mode only.

This issue occurred when Regulator used was DCDC converter for 5 volt input to LDO (3.3V) and then to controller. So i tested with replacing DCDC to LDO (12 to 5 V) converter for 5 volt input to LDO (3.3V) and then to controller. Then also issue remained same.

Then i tested for LM7805 regulator IC and then tested for the Output and then probability of getting failure was reduced. But issue is still there. My total PCB Load current takes 50 mA. and ripples checked at capacitor of LDO is 15mV. Is there any noise or any current related requirements which are failed here for Controller? Or any functionality which i am missing

RE: Device not connecting in boot loader mode

Edvin — Wed, 20 Nov 2019 12:33:12 GMT

Have you enabled bonding in the bootloader project? Maybe the device doesn't do service discovery because it thinks it already knows the services? If you require bonding in the bootloader then it will not increment the BLE address. The address is usually incremented to trigger a service discovery.

[quote user="Sarika"]<info> app: No firmware to activate.
<debug> app: Enter nrf_dfu_app_is_valid
<debug> app: No valid app to boot.[/quote]

These lines indicates that there is no valid application in the memory. Is the application programmed to the nRF? If so, how was it programmed? Via DFU or via programmer? If programmer, did you also program the correct signed bootloader settings?

RE: Device not connecting in boot loader mode

ssc — Tue, 19 Nov 2019 11:56:04 GMT

[quote userid="26071" url="~/f/nordic-q-a/54435/device-not-connecting-in-boot-loader-mode/220603"]Have you tried to debug the bootloader to figure out why the application is not starting? To do so, you should use the pca10040_ble_debug and enable logging and see if you get any sensible output.[/quote]

I tried for ble-debug example code and got following log:

<info> app: Inside main
<debug> app: In nrf_bootloader_init
<debug> nrf_dfu_settings: Calling nrf_dfu_settings_init()...
<debug> nrf_dfu_flash: Initializing nrf_fstorage_nvmc backend.
<debug> nrf_dfu_settings: Settings OK
<debug> app: Enter nrf_bootloader_fw_activate
<info> app: No firmware to activate.
<debug> app: Enter nrf_dfu_app_is_valid
<debug> app: No valid app to boot.
<debug> app: DFU mode because app is not valid.
<info> nrf_bootloader_wdt: WDT is not enabled
<debug> app: in weak nrf_dfu_init_user
<debug> app: timer_stop (0x200057D4)
<debug> app: timer_activate (0x200057D4)
<info> app: Entering DFU mode.
<debug> app: Initializing transports (found: 1)
<debug> nrf_dfu_ble: Initializing BLE DFU transport
<debug> nrf_dfu_ble: Setting up vector table: 0x00072000
<debug> nrf_dfu_ble: Enabling SoftDevice.
<debug> nrf_dfu_ble: Configuring BLE stack.
<debug> nrf_dfu_ble: Enabling the BLE stack.
<debug> nrf_dfu_ble: No advertising name found
<debug> nrf_dfu_ble: Using default advertising name
<debug> nrf_dfu_ble: Advertising...
<debug> nrf_dfu_ble: BLE DFU transport initialized.
<debug> nrf_dfu_flash: Initializing nrf_fstorage_sd backend.
<debug> app: Enter main loop
<debug> nrf_dfu_ble: Connected
<debug> nrf_dfu_ble: Advertising...
<debug> app: timer_stop (0x200057D4)
<debug> app: timer_fire (0x200057D4)
<info> app: Inactivity timeout.
<debug> app: Resetting bootloader.
<info> nrf_dfu_settings: Backing up settings page to address 0x7E000.
<debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.

When i try to connect from mobile device then it gives Connected on debug but mobile is not able to discover the services on device and gets timeout and device gets disconnected . So after timeout device gets reset and again goes in boot loader.

RE: Device not connecting in boot loader mode

ssc — Mon, 18 Nov 2019 14:44:07 GMT

[quote userid="26071" url="~/f/nordic-q-a/54435/device-not-connecting-in-boot-loader-mode/220603"]Try to revert the bootloader settings settings to 0x78000 and 0x6000, and see if that changes anything. But then again, this should not be dependent on the voltage into your external voltage regulator.[/quote]

Yes i do tried it also by changing flash settings . But no luck. I have erased whole flash and then only boot loader is flashed in memory. Same issue persists that device starts advertising but no connection is possible. Debug strings in nRF connect shows Error 22 (0x16) GATT CONN TERMINATE LOCAL HOST.

[quote userid="26071" url="~/f/nordic-q-a/54435/device-not-connecting-in-boot-loader-mode/220603"]What is it that you are trying to update? The app + bl? [/quote]

I am trying to update only application.

RE: Device not connecting in boot loader mode

Edvin — Mon, 18 Nov 2019 13:49:12 GMT

Are you sure this is your settings?

In the Bootloader examples for the nRF52832 examples from the SDK uses the following settings for the Flash:

FLAS_START = 0x78000

FLASH_SIZE = 0x6000

Using these settings the bootloader will use the flash area 0x78000 to 0x7E000. The remaining flash is for the bootloader settings.

In theory, it is possible with the settings you have used as well, but it has to be set several places in the project, so it is easy to do mistakes.

Try to revert the bootloader settings settings to 0x78000 and 0x6000, and see if that changes anything. But then again, this should not be dependent on the voltage into your external voltage regulator.

What is it that you are trying to update? The app + bl? Have you tried to debug the bootloader to figure out why the application is not starting? To do so, you should use the pca10040_ble_debug and enable logging and see if you get any sensible output.

Are there any other changes you have done to the bootloader project that I should know of?

Best regards,

Edvin

RE: Device not connecting in boot loader mode

ssc — Mon, 18 Nov 2019 11:57:29 GMT

[quote userid="26071" url="~/f/nordic-q-a/54435/device-not-connecting-in-boot-loader-mode/220540"]Are you sure that the DFU part is working properly when you use the 5V in?[/quote]

Yes i have tested it for multiple times and Dfu process done successfully with valid FW updates.

[quote userid="26071" url="~/f/nordic-q-a/54435/device-not-connecting-in-boot-loader-mode/220540"]Don't you agree if the input voltage to the nRF doesn't change, and nothing else, as seen from the nRF changes, then the behavior shouldn't change?[/quote]

Yes i do agree to this statement but i am facing issue.. and no clues for why this is so happening.

[quote userid="26071" url="~/f/nordic-q-a/54435/device-not-connecting-in-boot-loader-mode/220540"]Can you successfully update the application?[/quote]

YES I can.

Can it be related to RAM and FLASH memory managements. My application code is modified code of Multiperipheral example . Which has following Section_placement MACRO settings:

FLASH_PH_START=0x0

FLASH_PH_SIZE=0x80000

RAM_PH_START=0x20000000

RAM_PH_SIZE=0x10000

FLASH_START=0x26000

FLASH_SIZE=0x5a000

RAM_START=0x200053F0

RAM_SIZE=0xAC20

Where for secure_bootloader ble example code has following Section_placement MACRO settings:

FLASH_PH_START=0x0

FLASH_PH_SIZE=0x80000

RAM_PH_START=0x20000000

RAM_PH_SIZE=0x10000

FLASH_START=0x72000

FLASH_SIZE=0x8000

RAM_START=0x200057b8

RAM_SIZE=0xa848

Is there anything wrong in this ?

RE: Device not connecting in boot loader mode

Edvin — Mon, 18 Nov 2019 11:31:39 GMT

Are you sure this is related to the input voltage at all? Does everything work when you use 5V? Can you successfully update the application?

Don't you agree if the input voltage to the nRF doesn't change, and nothing else, as seen from the nRF changes, then the behavior shouldn't change?

Are you sure that the DFU part is working properly when you use the 5V in?

RE: Device not connecting in boot loader mode

ssc — Mon, 18 Nov 2019 09:54:19 GMT

I am also facing issue of device not getting reset after firmware update is completed . Mobile application show that firmware updated successfully, but device does not get reset and not even stays in boot loader mode as i don't see any Dfutarg advertising name in mobile application.

RE: Device not connecting in boot loader mode

ssc — Mon, 18 Nov 2019 09:34:54 GMT

[quote userid="26071" url="~/f/nordic-q-a/54435/device-not-connecting-in-boot-loader-mode/220494"]Are you sure the nRF still receive only 3.3V when you try to increase the input voltage to the regulator to 12V? Have you measured?[/quote]

Yes i've measured voltage it is received 3.3 V. I am facing issue after flashing secure boot loader code. Application without boot loader has no complaints in functionality.

[quote userid="26071" url="~/f/nordic-q-a/54435/device-not-connecting-in-boot-loader-mode/220494"]Can you double check that the input voltage to the nRF doesn't change when you increase the voltage into your input regulator?[/quote]

Supply voltage do not change while increasing input voltage. I have crosschecked just now.

[quote userid="26071" url="~/f/nordic-q-a/54435/device-not-connecting-in-boot-loader-mode/220494"]define NRF_BL_DFU_ENTER_METHOD_BUTTON and NRF_BL_DFU_ENTER_METHOD_BUTTON_PIN[/quote]

Both of these methods are already disabled. Still issue remains same.

I wonder what exactly had happend after flashing boot loader code?? and increasing supply get this issue.

Is there any other electrical requirements that need to be fulfilled other than 3.3 V supply. Or any related requirements for boot loader code.

Thanks and regards

RE: Device not connecting in boot loader mode

Edvin — Mon, 18 Nov 2019 08:53:06 GMT

"DfuTarg" means that it is in bootloader mode, yes, as long as you haven't set DfuTarg as the advertising name in your application as well.

I don't see why increasing the input voltage should affect the behavior of the application as long as the nRF always receive 3.3V. Are you sure the nRF still receive only 3.3V when you try to increase the input voltage to the regulator to 12V? Have you measured?

The reasons why the device stays in bootloader mode is usually one of the following:

1: The device doesn't have an application, only a bootloader.

2: The bootloader is set up to enter DFU mode on a button press on restart. If this is the case, and the button is held (the pin is held low) it will stay in DFU mode. Look for the define NRF_BL_DFU_ENTER_METHOD_BUTTON and NRF_BL_DFU_ENTER_METHOD_BUTTON_PIN in sdk_config.h in your bootloader project.

3: The present application isn't signed correctly, or wasn't uploaded correctly, leading to a CRC error when the bootloader checks the application.

None of these should be dependent on the input on your voltage regulator. In fact, nothing should, as long as the regulator works properly, always supplying 3.3V to the nRF.

Can you double check that the input voltage to the nRF doesn't change when you increase the voltage into your input regulator?

RE: Device not connecting in boot loader mode

ssc — Sun, 17 Nov 2019 17:38:32 GMT

Hello Edvin,

Device starts broadcasting with "Dfutarg" name when in bootloader mode. Doesn't that mean it it bootloader mode?

12volt into power supply regulator and nRF gets 3.3 V . Input regulator can be given variable voltage from 5 volts to 30 volt. But as I said earlier it works properly for 5 volt only .. i want to know what are the possibilities that could hamper the function?

RE: Device not connecting in boot loader mode

Edvin — Fri, 15 Nov 2019 14:35:42 GMT

Hello,

[quote user=""]When device is in Application it is connected and operation is fine,but after entering DFU by triggering command from DFU service to enter boot-loader mobile does not get connected but device remains in boot-loader mode. SDK used is 15.2.0 . Secure bootloader example code from DFU section is used.[/quote]

What does that mean? How do you know it is "stuck in bootloader mode" if you are not able to connect? Can you see the advertisements from the bootloader?

[quote user=""]When i use supply input of 5 volt it works perfectly. But for 12 volts it gives me above error behavior. [/quote]

12 volts into the power supply regulator I suppose? What is the input voltage to the nRF at that point?