Device not connecting in boot loader mode

[ssc]

Hello ,

I am using nRF52832 controller in peripheral role. I have integrated Secure boot loader code. I am facing issue of mobile device is not getting connected to the DFU service in boot-loader.

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.

I am using Custom board with ready module integrated  of nrf52832 from RAYTAC (MDBT42Q-512KV2). Board has Power supply regulator on board. Input supply voltage 10 v to 30 v with 500 mA current rating. When i use supply input of 5 volt it works perfectly. But for 12 volts it gives me above error behavior. This issue is been faced after flashing secure boot-loader code. Without boot-loader code simple application works totally fine.

Thanks in advance.

[Edvin]

Hello,

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.

 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?

 

When i use supply input of 5 volt it works perfectly. But for 12 volts it gives me above error behavior.

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

[ssc]

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?

[Edvin]

"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?

[ssc]

Edvin said:

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?

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. 

Edvin said:

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

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

Edvin said:

define NRF_BL_DFU_ENTER_METHOD_BUTTON and NRF_BL_DFU_ENTER_METHOD_BUTTON_PIN

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

[ssc]

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.