Nrf52832 ble_app_uart DFU No bootloader found(NRF_ERROR_NO_MEM) | SDK 15.3.0 | Soft device S132 6.1.1

RE: Nrf52832 ble_app_uart DFU No bootloader found(NRF_ERROR_NO_MEM) | SDK 15.3.0 | Soft device S132 6.1.1

Yogeshwaran — Wed, 30 Sep 2020 12:15:42 GMT

Sure Thanks for being Kind and supportive. The issue got solved really fast that i didn't expect. This is why i like to use Nordic chip majorly because of very good support. Good Luck!

RE: Nrf52832 ble_app_uart DFU No bootloader found(NRF_ERROR_NO_MEM) | SDK 15.3.0 | Soft device S132 6.1.1

Einar Thorsrud — Wed, 30 Sep 2020 12:05:38 GMT

Hi,

Ah, yes. I did not spot that. You are right. Please note that if you want a BLE service for enabling DFU that is allready implemented for you in the SDK, with the DFU service. There you can also see how DFU mode is triggered by writing to GPREGRET and resetting using ble_dfu_buttonless_bootloader_start_finalize() implemented like this in ble_dfu.c (for your reference):

uint32_t ble_dfu_buttonless_bootloader_start_finalize(void)
{
    uint32_t err_code;

    NRF_LOG_DEBUG("In ble_dfu_buttonless_bootloader_start_finalize\r\n");

    err_code = sd_power_gpregret_clr(0, 0xffffffff);
    VERIFY_SUCCESS(err_code);

    err_code = sd_power_gpregret_set(0, BOOTLOADER_DFU_START);
    VERIFY_SUCCESS(err_code);

    // Indicate that the Secure DFU bootloader will be entered
    m_dfu.evt_handler(BLE_DFU_EVT_BOOTLOADER_ENTER);

    // Signal that DFU mode is to be enter to the power management module
    nrf_pwr_mgmt_shutdown(NRF_PWR_MGMT_SHUTDOWN_GOTO_DFU);

    return NRF_SUCCESS;
}

RE: Nrf52832 ble_app_uart DFU No bootloader found(NRF_ERROR_NO_MEM) | SDK 15.3.0 | Soft device S132 6.1.1

Yogeshwaran — Wed, 30 Sep 2020 12:02:15 GMT

I am sorry basically resetting the board drives the device into DFU mode not power off and on. So i found some useful things from https://devzone.nordicsemi.com/f/nordic-q-a/30856/invalid-memory-access-when-writing-to-nrf_power--gpregret and https://devzone.nordicsemi.com/f/nordic-q-a/37971/gpregret-clears-on-sd_nvic_systemreset using this the issue got resolved. Actually we should not directly set NRF_POWER->GPREGRET if Softdevice is present. The way we should set by only using below code

err_code = sd_power_gpregret_clr(0, 0xffffffff);
APP_ERROR_CHECK(err_code);
err_code = sd_power_gpregret_set(0,BOOTLOADER_DFU_START);
APP_ERROR_CHECK(err_code);
nrf_pwr_mgmt_shutdown(NRF_PWR_MGMT_SHUTDOWN_GOTO_DFU);

I am right sir?

RE: Nrf52832 ble_app_uart DFU No bootloader found(NRF_ERROR_NO_MEM) | SDK 15.3.0 | Soft device S132 6.1.1

Einar Thorsrud — Wed, 30 Sep 2020 11:54:03 GMT

Hi,

[quote user="Yogeshwaran"]Yeah as you said it not getting Fatal error because of NVIC_SystemReset().[/quote]

Sounds good. Then we can ignore NVIC_SystemReset() itself.

[quote user="Yogeshwaran"] if i add NRF_POWER->GPREGRET = BOOTLOADER_DFU_START before NVIC_SystemReset() then it is happening but if add the NRF_POWER->GPREGRET = BOOTLOADER_DFU_START and restart the device by switch off and on then it goes to DFU mode as excepected and other functionalities are working fine.[/quote]

By turning off and on here do you mean power-cycle? If so, then whatever was in the GPREGRET is lost as it is only retained while the device is powered. It is a bit odd that the device enters DFU mode though, as the BOOTLOADER_DFU_START flag is lost after the reset. It is also strange that you get the error when the flag is set. Some questions:

Do you only get this error when using a high number of FDS pages, or is that unrelated to the issue?
Have you made any modifications in the bootloader? If so, which?
Do you see anything useful if testing with the debug bootloader with RTT logging (example bootloader project ending with "_debug")?

RE: Nrf52832 ble_app_uart DFU No bootloader found(NRF_ERROR_NO_MEM) | SDK 15.3.0 | Soft device S132 6.1.1

Yogeshwaran — Wed, 30 Sep 2020 11:35:59 GMT

Yeah as you said it not getting Fatal error because of NVIC_SystemReset(). if i add NRF_POWER->GPREGRET = BOOTLOADER_DFU_START before NVIC_SystemReset() then it is happening but if add the NRF_POWER->GPREGRET = BOOTLOADER_DFU_START and restart the device by switch off and on then it goes to DFU mode as excepected and other functionalities are working fine.

RE: Nrf52832 ble_app_uart DFU No bootloader found(NRF_ERROR_NO_MEM) | SDK 15.3.0 | Soft device S132 6.1.1

Einar Thorsrud — Wed, 30 Sep 2020 11:03:22 GMT

How have you debugged to verify that you get an error after calling NVIC_SystemReset? The function does not return anything, and really should not fail. For reference, this is the implementation (<SDK>\components\toolchain\cmsis\include\core_cm4.h):

/**
  \brief   System Reset
  \details Initiates a system reset request to reset the MCU.
 */
__STATIC_INLINE void NVIC_SystemReset(void)
{
  __DSB();                                                          /* Ensure all outstanding memory accesses included
                                                                       buffered write are completed before reset */
  SCB->AIRCR  = (uint32_t)((0x5FAUL << SCB_AIRCR_VECTKEY_Pos)    |
                           (SCB->AIRCR & SCB_AIRCR_PRIGROUP_Msk) |
                            SCB_AIRCR_SYSRESETREQ_Msk    );         /* Keep priority group unchanged */
  __DSB();                                                          /* Ensure completion of memory access */

  for (;;)                                                           /* wait until reset */
  {
    __NOP();
  }
}

RE: Nrf52832 ble_app_uart DFU No bootloader found(NRF_ERROR_NO_MEM) | SDK 15.3.0 | Soft device S132 6.1.1

Yogeshwaran — Wed, 30 Sep 2020 10:58:52 GMT

I am using SoftDevice for advertising then it must be enabled i feel, but even i tried NVIC_SystemReset() still same Fatal error. The below is the code which i am using

for(;;)

{

if(go_to_dfu)
{
NRF_LOG_INFO("Going to dfu ");
uint32_t err_code;
err_code = sd_ble_gap_disconnect(m_conn_handle, BLE_HCI_CONN_INTERVAL_UNACCEPTABLE);
APP_ERROR_CHECK(err_code);
sd_ble_gap_scan_stop();
sd_ble_gap_adv_stop(NULL);
while(connected);
NRF_POWER->GPREGRET = BOOTLOADER_DFU_START;
nrf_delay_ms(100);
sd_nvic_SystemReset();
}

if(start_advertise)

{

//starting_advertising

}

RE: Nrf52832 ble_app_uart DFU No bootloader found(NRF_ERROR_NO_MEM) | SDK 15.3.0 | Soft device S132 6.1.1

Einar Thorsrud — Wed, 30 Sep 2020 10:37:43 GMT

Hi,

[quote user="Yogeshwaran"]NRF_DFU_FORCE_DUAL_BANK_APP_UPDATES by setting to 1 now the issue got resolved and DFU successfully updating application and running properly after update.[/quote]

That makes sense. With forced dual bank updates you need more available space, so it makes sense that setting NRF_DFU_FORCE_DUAL_BANK_APP_UPDATES to 0 allows you to reserve more space for user data (FDS pages).

[quote user="Yogeshwaran"]NRF_DFU_APP_DATA_AREA_SIZE to 80 pages then throwing error after update as '11' at fds_init() which denotes NO_PAGES. what is the reason?[/quote]

Do you have an overview of the memory layout of your device? You can refer to the figure at the end of this page and put in your sizes. You cannot use more pages for FDS than what is between the end of the application and the beginning of the bootloader. And even if that fits, it may be too much to allow you to do SoftDevice and updates, as they must be dual bank bootloader.

[quote user="Yogeshwaran"]One more issue is if i call sd_nvic_SystemReset() gives Fatal error in loop(). This function will get called after device receives cmd from ble_client(nRF_Connect app) so can you tell how to reset the device properly to go into DFU.[/quote]

You should not get an error from sd_nvic_SystemReset(), it should just reset and never return. If the SoftDevice is not enabled you should call NVIC_SystemReset(). Are you sure this is the problem?

RE: Nrf52832 ble_app_uart DFU No bootloader found(NRF_ERROR_NO_MEM) | SDK 15.3.0 | Soft device S132 6.1.1

Yogeshwaran — Wed, 30 Sep 2020 07:41:30 GMT

NRF_DFU_APP_DATA_AREA_SIZE 204800 which is 50 pages of FDS and i enabled

NRF_DFU_FORCE_DUAL_BANK_APP_UPDATES by setting to 1 now the issue got resolved and DFU successfully updating application and running properly after update. If i change the NRF_DFU_APP_DATA_AREA_SIZE to 80 pages then throwing error after update as '11' at fds_init() which denotes NO_PAGES. what is the reason? One more issue is if i call sd_nvic_SystemReset() gives Fatal error in loop(). This function will get called after device receives cmd from ble_client(nRF_Connect app) so can you tell how to reset the device properly to go into DFU.

RE: Nrf52832 ble_app_uart DFU No bootloader found(NRF_ERROR_NO_MEM) | SDK 15.3.0 | Soft device S132 6.1.1

Yogeshwaran — Tue, 29 Sep 2020 15:43:47 GMT

I used FDS_VIRTUAL_PAGES as 10 then it is working fine but i need more pages so what should i do. Atleast 30 pages.

RE: Nrf52832 ble_app_uart DFU No bootloader found(NRF_ERROR_NO_MEM) | SDK 15.3.0 | Soft device S132 6.1.1

Yogeshwaran — Tue, 29 Sep 2020 15:11:57 GMT

Do i need to adjust the application flash size in segger Linker script? and 0x2000FF18 denotes to which register location?

RE: Nrf52832 ble_app_uart DFU No bootloader found(NRF_ERROR_NO_MEM) | SDK 15.3.0 | Soft device S132 6.1.1

Yogeshwaran — Tue, 29 Sep 2020 14:44:46 GMT

I am getting the below error if use 327680 for DATA_AREA_SIZE

00> <debug> app: SD_PRESENT: true.
00>
00> <debug> app: Bank contents:
00>
00> <debug> app: Bank 0 code: 0x01: Size: 0xC420
00>
00> <debug> app: Bank 1 code: 0x00: Size: 0x0
00>
00> <error> app: Received a fault! id: 0x00004002, pc: 0x00000000, info: 0x2000FF18

RE: Nrf52832 ble_app_uart DFU No bootloader found(NRF_ERROR_NO_MEM) | SDK 15.3.0 | Soft device S132 6.1.1

Einar Thorsrud — Tue, 29 Sep 2020 13:05:31 GMT

Then there is a clear mismatch. You use 80 FDS pages, but you only reserve 12288 / 0x1000 = 3 pages. So you must increase NRF_DFU_APP_DATA_AREA_SIZE to 0x1000 * 80 = 327680.

RE: Nrf52832 ble_app_uart DFU No bootloader found(NRF_ERROR_NO_MEM) | SDK 15.3.0 | Soft device S132 6.1.1

Yogeshwaran — Tue, 29 Sep 2020 12:52:03 GMT

FDS_VIRTUAL_PAGES in application sdk_config.h was 80 and

NRF_DFU_APP_DATA_AREA_SIZE 12288 in pca10040_ble_debug sdk_config.h

RE: Nrf52832 ble_app_uart DFU No bootloader found(NRF_ERROR_NO_MEM) | SDK 15.3.0 | Soft device S132 6.1.1

Einar Thorsrud — Tue, 29 Sep 2020 12:46:36 GMT

Hi,

If an FDS call returns 11 this is FDS_ERR_NO_PAGES, and this is probably because the FDS pages has been corrupted. As this happens after a DFU operation I suspect this is because the flash area was written to during the DFU update. This can happen if the FDS pages are not properly reserved in the bootloader (i.e. the bootloader does not know it cannot use them for temporary storage). How many FDS pages have you configured in your applications sdk_config.h (FDS_VIRTUAL_PAGES)? And how many FDS pages have you reserved in the bootloader's sdk_config.h (NRF_DFU_APP_DATA_AREA_SIZE)?

RE: Nrf52832 ble_app_uart DFU No bootloader found(NRF_ERROR_NO_MEM) | SDK 15.3.0 | Soft device S132 6.1.1

Yogeshwaran — Tue, 29 Sep 2020 12:33:44 GMT

After Dfu upload i am getting error value 11 at fds_init() function. what does it mean?

RE: Nrf52832 ble_app_uart DFU No bootloader found(NRF_ERROR_NO_MEM) | SDK 15.3.0 | Soft device S132 6.1.1

Yogeshwaran — Tue, 29 Sep 2020 12:08:12 GMT

Yeah my bad i messed up with public and private keys. Now i generated both again and placed into the right directory(this was the mistake) to make it work. The new issue happening here is after successful DFU upload the device restarts and i got Fatal error after some serial prints. I programmed again device with nrfjprog -f nrf52 --program --sectorerase then also Fatal error comes at the same place. If erase full flash that means nrfjprog -f nrf52 -e then nrfjprog -f nrf52 --program --sectorerase, it runs the app properly. Again if do DFU it stucks at Fatal error? After this if i upload using JLink without erasing the full flash the app is not running.

RE: Nrf52832 ble_app_uart DFU No bootloader found(NRF_ERROR_NO_MEM) | SDK 15.3.0 | Soft device S132 6.1.1

Einar Thorsrud — Tue, 29 Sep 2020 11:45:08 GMT

Hi,

Referring to the initial question first, I want to mention that SDK 15.3 introduced a new location for the bootloader start address. It is no longer in the UICR (though some code still incorrectly refers to "uicr" or "UICR"), but instead it is in the end of the first page, the MBR params page. You can see that MBR_BOOTLOADER_ADDR is set to 0xFF8 in nrf_mbr.h, and this is what is used. So the bootloader start address does not need to be in the UICR.

[quote user="Yogeshwaran"]But Now if i upload an app.zip file which i made using nrfutil along with private key i am getting signature failed error in bootloader while uploading app.zip. The bootloader has dfu_public_key.c and i modified the file by using private key. So what could be the issue?[/quote]

Good question. Based on what you wrote it should work, but perhaps there has been a mixup? Can you double check that you build the bootloader with the correct public key and that this is the bootloader you uploaded to the device? And then verify that you signed the DFU image using the correct corresponding private key?

RE: Nrf52832 ble_app_uart DFU No bootloader found(NRF_ERROR_NO_MEM) | SDK 15.3.0 | Soft device S132 6.1.1

Yogeshwaran — Tue, 29 Sep 2020 11:14:17 GMT

Actually this issue is happening because i am using segger and it erases the bootloader if going into debug mode. The issue actually comes when buttonless_service initialization happens. Hence i want to modify the NRF_POWER->GPREGRET = BOOTLOADER_DFU_START and restarted the device so i can able to see Dfu_Targ in nrf_connect app. But Now if i upload an app.zip file which i made using nrfutil along with private key i am getting signature failed error in bootloader while uploading app.zip. The bootloader has dfu_public_key.c and i modified the file by using private key. So what could be the issue?