nrf52810 Not jumping Bootloader from BLE Application

[NikhilVV]

Hi,

Chip : NRF52810

Soft Device : s132_nrf52_5.1.0

SDK : nrf5_sdk_for_thread_and_zigbee_v4.2.0_af27f76 (BLE BootLoader) 

IDE : Segger Embedded Studio

SDK : nRF5_SDK_14.2.0_17b948a (BLE Application) 

IDE : IAR Embedded Workbench

in BLE Application i am trying to reboot and enter to bootloader for serial DFU. 

i have checked in nrf devzone and did some changed as suggested but still it reboot and enter to BLE Application.  

BLE application main.c has been added following codes to set start bootloader 

 sd_power_gpregret_set(1,BOOTLOADER_DFU_START);     // to enable dfu_check true

nrf_nvmc_write_word(0x00022000, (uint32_t) dfu_flag);   // to enable dfu_check true

nrf_pwr_mgmt_shutdown(NRF_PWR_MGMT_SHUTDOWN_GOTO_DFU);     //

NVIC_SystemReset();.   //reboot to jump to bootloader

in Application sdkconfig did following changes.

#define BLE_DFU_ENABLED 1

#define NRF_DFU_BLE_BUTTONLESS_SUPPORTS_BONDS 1

#define NRF_PWR_MGMT_CONFIG_AUTO_SHUTDOWN_RETRY 1

#define NRF_SDH_BLE_VS_UUID_COUNT 2

#define NRF_SDH_BLE_SERVICE_CHANGED 1

#define NRF_SDH_BLE_SERVICE_CHANGED 1

From bootloader dfu_enter_check() nrf_power_gpregret_get() but it never returns true.

also tries to read nvic memory to read flag to make dfu_enter_check true.

uint32_t DFU_Flag_data  = 0;

uint32_t* dfu_flag_mem2 = (uint32_t*) 0x00022000;
DFU_Flag_data = (uint32_t)*dfu_flag_mem2 ;

if(DFU_Flag_data  != 0xFFFFFFFF) dfu_enter = true;

but after NVIC_SystemReset(); the application restart without entering to dfu_check.

how can i verify and enter to bootloader after systemreset().

Both BLE Application and BLE Bootloader is tested individually and works fine.

 

[Vidar Berg]

Hello,

Please verify that the bootloader start address is correctly stored at address 0x10001014 when both bootloader and app is loaded to your device. If not, the bootloader will not be included in the boot sequence: https://docs.nordicsemi.com/bundle/sds_s132/page/SDS/s1xx/mbr_bootloader/mbr_sd_reset_behavior.html 

Also, nrf5_sdk_for_thread_and_zigbee_v4.2.0_af27f76 and nRF5_SDK_14.2.0_17b948a are not compatible with the same Softdevices. Is there a particular reason for using this combination? Normally you would want to base the application and bootloader on the same SDK version. There should also not be any reason to use the Thread & Zigbee SDK when targeting the nRF52810 which does not have a 15.4 RADIO needed for thread and zigbee.

Best regards,

Vidar

[NikhilVV]

Hi,

>nrfjprog --memrd 0x10001014
0x10001014: 00029000 |....|

>nrfjprog --memrd 0x10001018
0x10001018: 0002E000 |....|

i have checked by writing memory using nrf_nvmc_write_word() from bootloader it is writting the memory location while booting before jump to BLE Application.

#include "nrf_nvmc.h"

ret_code_t nrf_bootloader_init(nrf_dfu_observer_t observer)
{
    NRF_LOG_DEBUG("In nrf_bootloader_init");

   ....

    switch (activation_result)
    {
        case ACTIVATION_NONE:

            nrf_nvmc_write_word(0x00022100,0x12341234);
            initial_timeout = NRF_BOOTLOADER_MS_TO_TICKS(NRF_BL_DFU_INACTIVITY_TIMEOUT_MS);
            dfu_enter       = dfu_enter_check();
            
            ...
            break;

Also i read the memory while running application and received following result.

>nrfjprog --memrd 0x00022100
0x00022100: 12341234 |4.4.|

and here is the result which i written from BLE Application

>nrfjprog --memrd 0x00022000
0x00022000: 12341234  

from bootloader am reading the same memory and used to enter DFU mode which is getting fail or not reading proper value similarly  with gpregister also.

how to read nvmc proper ? 

BLE Application is developed in nRF5_SDK_14.2.0_17b948a which is developed long back ago and we do not want to disturb right now.

where Bootloader developing in nrf5_sdk_for_thread_and_zigbee_v4.2.0_af27f76 currently where we want to add OTA in our coming BLE products.

lately we will move both Application and Bootloader into one SDK.

[Vidar Berg]

Hi,

Thanks for confirming that the UICR registers were set. 

The application and bootloader running on your device must always be compatible with the same softdevice. You can't have the bootloader built for one major version and the application for another. So first the first step is to make sure both are compatible with the same softdevice version.

NikhilVV said:

i have checked by writing memory using nrf_nvmc_write_word() from bootloader it is writting the memory location while booting before jump to BLE Application.

I'm not sure I understand what you are trying to test with this or why you are writing to this address. If the bootloader changes any of the data in the application region (or the app writes to itself), then the boot validation  of the app will fail.

[NikhilVV]

HI,

I was trying to verify that while booting whether the control goes to bootloader or not. 

By writing memory from bootloader i confirmed that device is rebooting and control goes to bootloader but it fails to enter dfu mode or dfu_enter getting failed. so it start running APP.

i understand i have to make bootloader and Application have to make compatible with same softdevice version.

But i individually checked the application and bootloader which was working fine so i thought to merge the both.

Q. Why memory read function getting failed from bootloader ?

 i have tried 2 methods to read memory as follows but all methods are got failed.

can u tell why it is getting failed.

uint32_t* dfu_flag_mem2 = (uint32_t*) 0x00022000;
DFU_Flag_data = (uint32_t)*dfu_flag_mem2 ;


memcpy(&dfu_flag_mem1,(uint32_t*) 0x00022000,sizeof(uint32_t));

[Vidar Berg]

NikhilVV said:

But i individually checked the application and bootloader which was working fine so i thought to merge the both.

But did you test them individually with the same Softdevice version?

NikhilVV said:

By writing memory from bootloader i confirmed that device is rebooting and control goes to bootloader but it fails to enter dfu mode or dfu_enter getting failed. so it start running APP.

To debug the bootloader, I recommend either using the *_debug variant or start a debug session in your bootloader project and place breakpoints in the dfu enter check function.

NikhilVV said:

Q. Why memory read function getting failed from bootloader ?

 i have tried 2 methods to read memory as follows but all methods are got failed.

It is not a problem with the read function. 

[NikhilVV]

Q But did you test them individually with the same Softdevice version?

Yes. Application and bootloader checked with same Softdevice  (s132_nrf52_5.1.0) and working well. 

i hope by it will work together with BLE APP and Bootloader.

Am not debugging bootloader. i am verifying that whether it hit or enter into bootloader or not by writting memory using nvmc_write.

If it is not a problem with read function why did the read function is not reading the correct data from  memory location. I read the same memory using nrfjprog --memrd  and returning 12341234. 

 

[Vidar Berg]

Please remove your nvmc writes and  try debug the bootloader to find out why the DFU flag in the GPREGRET register is being cleared without the device entering DFU mode.

[NikhilVV]

Hi,

I have removed all nvmc writes from bootloader and tried to enter DFU mode in run mode.

But the bootloader not entering to DFU, GPREGRET Register is setting from ble App and ble app getting rebooted .. But after rebooting it fails to enter DFU mode and jumps to Application. 

After rebooting i rechecked the GPREGRET data and it says,

C:\Users\DELL>nrfjprog --memrd 0x4000051c      //before 
0x4000051C: 00000000 |....|

C:\Users\DELL>nrfjprog --memrd 0x4000051c     //after reboot
0x4000051C: 000000B1

It is not clearing the data.

[Vidar Berg]

Hi,

I would begin with starting a debug session with the Bootloader project and verify that main() is reached after the enter DFU command has been issued to the application.