Insufficient resources error while doing Buttonless OTA on NRF52840

RE: Insufficient resources error while doing Buttonless OTA on NRF52840

sne_333 — Thu, 09 Nov 2023 03:57:02 GMT

Hi... I have solved the issue. Same pin was being accessed in bootloader as well as application fw which caused the issue.

RE: Insufficient resources error while doing Buttonless OTA on NRF52840

Hung Bui — Mon, 30 Oct 2023 09:02:27 GMT

Hi Snehal,

Please step in the code and check what cause the problem.

You need to know how to debug to be able to solve the issue.

In the app_usbd.c we used:

ret = nrf_drv_power_init(NULL);
if ((ret != NRF_SUCCESS) && (ret != NRF_ERROR_MODULE_ALREADY_INITIALIZED))
{
/* This should never happen */
APP_ERROR_HANDLER(ret);
}

You may want to consider to do the same.

Have you tried what I suggested ?
Can you confirm that if you flash them separately they worked ?
It they do, I don't see why the code would cause the problem. Why combining hexes have anything to do with nrf_drv_power_init() function.

RE: Insufficient resources error while doing Buttonless OTA on NRF52840

sne_333 — Sun, 29 Oct 2023 17:54:19 GMT

Hi I guess I know what the issue is... The issue is inside "nrf_drv_power.c" file. Something is causing an issue in this file. If i comment this whole file everything works fine, But for USB MSC this file is needed and its causing issue.

I also searched other tickets and did nrf_drv_power_init before ble stack init in the application main file. But still the device seems to hang. This is my code for main.c:-

int main(void)
{
        bool erase_bonds;
    ret_code_t err_code;
    // Initialize modules.
    log_init();
    timers_init();


    err_code = nrf_drv_power_init(NULL);
    APP_ERROR_CHECK(err_code);

    clock_init();
    nrf_drv_clock_lfclk_request(NULL);

    while(!nrf_drv_clock_lfclk_is_running())
    {
        /* Just waiting */
    }
    
    usbd_config_init();

    // Initialize the async SVCI interface to bootloader before any interrupts are enabled.
    // We don't check for error in case bootloader not in place
    ble_dfu_buttonless_async_svci_init();

    err_code = nrf_drv_gpiote_init();
    APP_ERROR_CHECK(err_code);
    
    // Do not start any interrupt that uses system functions before system initialisation.
    // The best solution is to start the OS before any other initalisation.

#if NRF_LOG_ENABLED
    // Start execution.
    m_logger_thread = xTaskCreateStatic(logger_thread, "LOGGER", sizeof(xLoggerStack) / sizeof(xLoggerStack[0]), NULL, LOGGER_TASK_PRIORITY, xLoggerStack, &xLoggerTaskBuffer);
    if (m_logger_thread == NULL) {
        APP_ERROR_HANDLER(NRF_ERROR_NO_MEM);
    }
#endif

NRF_LOG_INFO("TESTING NEW FIRMWARE");
    
      //init_device_storage();

    // Activate deep sleep mode.
    SCB->SCR |= SCB_SCR_SLEEPDEEP_Msk;

    device_storage_init();
    clinitraq_load_settings();
  

    memset(app_fw_version, 0, sizeof(app_fw_version));
    app_version_str(app_fw_version, sizeof(app_fw_version));

    mem_init();

 ///* Enable interrupt for FPU so we can clear it */
 //   NVIC_SetPriority(FPU_IRQn, APP_IRQ_PRIORITY_LOW);
 //   NVIC_EnableIRQ(FPU_IRQn);

    // Configure and initialize the BLE stack.
    ble_stack_init();
    gap_params_init();
    gatt_init();
    services_init();
    advertising_init();
    conn_params_init();
    peer_manager_init();

    // Initialize modules.
    
 
    
    
    application_timers_start();

 /* Set TX Output Power to +4dBm */
    err_code = sd_ble_gap_tx_power_set(BLE_GAP_TX_POWER_ROLE_ADV, m_advertising.adv_handle, 4); 
    APP_ERROR_CHECK(err_code);

    // Create a FreeRTOS task for the BLE stack.
    // The task will run advertising_start() before entering its loop.
    nrf_sdh_freertos_init(advertising_start, &erase_bonds);

    
    init_usb_msc_task();
    init_led_button_task();
    init_system_task();
    //////////init_device_storage();
    init_clinitraq_task();
 

    //err_code = app_usbd_power_events_enable();
    //APP_ERROR_CHECK(err_code);

    NRF_LOG_INFO("CLINITRAQ Starting");
    NRF_LOG_INFO("FW Version: %s", app_fw_version);
    

      

     // Start FreeRTOS scheduler.
    vTaskStartScheduler();

    for (;;) {
        APP_ERROR_HANDLER(NRF_ERROR_FORBIDDEN);
    }
}

can you please suggest me something? I am running out of time.

Thanks & Regards,

Snehal

RE: Insufficient resources error while doing Buttonless OTA on NRF52840

Hung Bui — Fri, 20 Oct 2023 13:47:23 GMT

Hi,

After you have everything working, you may want to copy the content of the flash of your working device and then flash it to other products. You want only one hex file and can flash to all product in production, correct ? I assume that what you want ?

You can do that by having a working device, then do this:

nrfjprog --readcode --readuicr myfirmware.hex

After that nrfjprog will read the flash content of the working device including the UICR, and write it to myfirmware.hex

You can use this myfirmware.hex to flash other device(s) and it should have the exact flash content as the working device.

RE: Insufficient resources error while doing Buttonless OTA on NRF52840

sne_333 — Fri, 20 Oct 2023 11:43:47 GMT

Hi Hung,

>>>- If you do SD + BL and then do DFU update the application. After that you can do as many DFU update as you want , is it correct ?

Yes correct.

>>>If it's the case I think one solution for you to not to have to merge SD + BL + APP + BL setting is that you can do a flash read out and UICR read out :
nrfjprog --readcode --readuicr

Here which files do I need to flash and then read out the code?? Got confused on this one.

Thanks & Regards,

Snehal

RE: Insufficient resources error while doing Buttonless OTA on NRF52840

Hung Bui — Fri, 20 Oct 2023 10:55:32 GMT

Hi Snehal,
It's really strange that with bootloader setting v2 it didn't work

Can you confirm that:

- If you do SD + BL and then do DFU update the application. After that you can do as many DFU update as you want , is it correct ?

If it's the case I think one solution for you to not to have to merge SD + BL + APP + BL setting is that you can do a flash read out and UICR read out :
nrfjprog --readcode --readuicr

so that you can get the hex dump into a hex file. You can then use this hex file to flash your application in production.

RE: Insufficient resources error while doing Buttonless OTA on NRF52840

sne_333 — Fri, 20 Oct 2023 06:23:15 GMT

Hi Hung,

Sorry for the late response. Was out for some days. I tried with --bl-settings-version 2 but still OTA did not work. We got Gatt error as described in above comments. Would it be a hardware issue?? Because everything works fine on development kit nrf52840.

Thanks,

Snehal

RE: Insufficient resources error while doing Buttonless OTA on NRF52840

Hung Bui — Tue, 10 Oct 2023 07:50:41 GMT

Hi Snehal,
It seems that you are using SDK v17.1

But in the bootloader settings script you are using --bl-settings-version 1

This is incorrect. You can see here: https://infocenter.nordicsemi.com/topic/ug_nrfutil/UG/nrfutil/nrfutil_settings_generate_display.html?cp=11_8_6

You should use --bl-settings-version 2

RE: Insufficient resources error while doing Buttonless OTA on NRF52840

sne_333 — Tue, 10 Oct 2023 04:52:47 GMT

Hi Hung,

settings page is generated using following script

nrfutil settings generate --family NRF52840 --application usbmsc.hex --application-version 3 --bootloader-version 2 --bl-settings-version 1 settings_usbmsc.hex

del /s /q jtag_lp
del /s /q dfu_lp
mkdir jtag_lp

mergehex -m s140_nrf52_7.2.0_softdevice.hex usbmsc.hex bootloader.hex -o inter_usbmsc.hex
mergehex -m inter_clinitraq.hex settings_usbmsc.hex -o jtag_lp/usbmsc-merged.hex


mkdir dfu_lp
nrfutil pkg generate --hw-version 52 --application-version 3 --application usbmsc.hex --sd-req 0x0100 --key-file debug.pem dfu_lp/usbmsc-dfu.zip

:end
pause

Is anything wrong with my settings generation or merging of files?

The application firmware is using "fstorage" but why it does not show any issues on development kit?

Thanks & Regards,

Snehal

RE: Insufficient resources error while doing Buttonless OTA on NRF52840

Hung Bui — Mon, 09 Oct 2023 11:21:00 GMT

Hi Snehal,
Then we will need to look at how you generate the bootloader setting and if there is anything special about your application ? Did it write to flash (without using fds or fstorage) that may potential cause a problem to DFU update ?

Please try doing a test with an example in our SDK , ble_app_hrs for example.
Please do bootloader + softdevice test first, DFU update ble_app_hrs and very that it works on your board.

After that do bootloader + softdevice + application + bootloader setting then do DFU update after that to check if it works

RE: Insufficient resources error while doing Buttonless OTA on NRF52840

sne_333 — Mon, 09 Oct 2023 06:46:12 GMT

Hi Hung,

I tried following your steps on our custom device. We flashed the device with bootloader.hex and softdevice file. Then we performed OTA via nrf connect app and I was able to do OTA. Even after doing OTA, I was able to connect again to the device without any issue. Did this multiple times and it is working fine on custom board.

But why the merged files work on development kit and doesn't work on custom device??

Thanks & Regards,

Snehal

RE: Insufficient resources error while doing Buttonless OTA on NRF52840

Hung Bui — Wed, 04 Oct 2023 13:39:09 GMT

Please do what I suggested only flash softdevice + bootloader for step 1(this is how it should be done as in the bootloader documentation)

Please sent us the schematic of your board.

Besides RTT log, you can debug the application (and the bootloader) by step into the code and set a breakpoint. It's the normal debugging process for application development.

RE: Insufficient resources error while doing Buttonless OTA on NRF52840

sne_333 — Wed, 04 Oct 2023 13:22:07 GMT

For debugging rtt logs will be needed right. Currently after doing ota rtt logs are not seen. Before ota we can see rtt logs... but not after ota. Thats my problem. I can't debug in this case.

without ota my application works fine... I am able to connect to device. How to debug ??

RE: Insufficient resources error while doing Buttonless OTA on NRF52840

Hung Bui — Wed, 04 Oct 2023 12:34:56 GMT

Hi Snehal,

Yes I read this reply. I know that everything works on the DK. We need to look into why it doesn't work your board.

I want you test at step 1 only do softdevice + bootloader no application, no bootloader setting.

Also please try to do this:

1. Flash softdevice + bootloader

2. DFU update your application

3. Check if your application start.

If #3 doesn't work, then you can again from step 1 but at step 2 do DFU update a very simple application

If #3 works, you can see your application advertising, then you can try to do DFU update your application again (with minor modification, for example change advertising name).

What I want to say is that you need to narrow down what can be wrong and you need to try debugging it. Step in the code, simplify your application, etc.
Simply say it doesn't work won't help.

RE: Insufficient resources error while doing Buttonless OTA on NRF52840

sne_333 — Wed, 04 Oct 2023 10:56:57 GMT

I guess you missed to read my one reply here. I am attaching that reply here again:-

I tried various combinations. I have found that my code ( USB MSC application) works fine on development kit nrf52840. I am able to do OTA and even after OTA I am able to connect to the device without any GATT error on the development kit nrf52840. But on my custom board after OTA I am not able to connect to the application.
Can you please help us on why it is creating issues on our custom hardware after doing OTA update??

I am following the same steps to test OTA on development kit as well as custom hardware which I had shared

1)Flash the firmware files separately one by one (bootloader, softdevice & application)

2)Device is advertising and visible in NRF connect app.

3) Connect NRF connect with device.

4) Do OTA upgrade

5) Upgrade finishes

6) After upgrading firmware I am no longer able to connect to the device on custom hardware.

Thanks & Regards,

Snehal

RE: Insufficient resources error while doing Buttonless OTA on NRF52840

Hung Bui — Wed, 04 Oct 2023 10:53:24 GMT

Hi Snehal,

Could you please try testing again with only softdevice + bootloader at step 1?
Please try that and update the application to see if the application can run.

If it doesn't run, please try again with a more simple application, blinky for example. You mentioned that if you disable USB MSC code it work ?
If it's the case , this mean the application actually run , but it crash at initializing USB MSC, then you can step in and debug to see what crashes.

RE: Insufficient resources error while doing Buttonless OTA on NRF52840

sne_333 — Wed, 04 Oct 2023 06:54:33 GMT

Hi Hung,

Answering all your queries sequentially:-

1) At step 2 yes the device was advertising properly.

2) At step 1, I flashed bottloader+ softdevice + application + settings. So the device was advertising properly and I was able to do OTA upgrade.

3) If I only flash softdevice + application yes the application works perfectly.

4) At step 6 I am not able to see any logs. I tried to check in RTT logs but nothing was seen.

Please understand I am able to do OTA on custom board but after doing OTA upgrade I am not able to connect to the device, application doesn't seem to be running in this case. Thts the reason I am not observing any logs in RTT viewer.

Regards,

Snehal

RE: Insufficient resources error while doing Buttonless OTA on NRF52840

Hung Bui — Tue, 03 Oct 2023 12:14:58 GMT

Hi Snehal,
Please clarify at #2 the device was advertising as DFUTarg ?
At 1 if you only flash bootloader + softdevice + application, the application won't be able to start because the bootloader will not accept it as a valid application. Please only do bootloader + softdevice.

If you only flash softdevice + application , would the application work ?

At step 6 do you see any log ? We need to know if the application was running and crashed or it never run and the bootloader having trouble

Please be aware that you can debug the application as normal after it's DFUed. Please try to debug it, either by step in the code or by printing log out. It's not a black box.

RE: Insufficient resources error while doing Buttonless OTA on NRF52840

sne_333 — Tue, 03 Oct 2023 10:58:10 GMT

Hi Hung,

I am following the same steps to test OTA on development kit as well as custom hardware which I had shared

1)Flash the firmware files separately one by one (bootloader, softdevice & application)

2)Device is advertising and visible in NRF connect app.

3) Connect NRF connect with device.

4) Do OTA upgrade

5) Upgrade finishes

6) After upgrading firmware I am no longer able to connect to the device on custom hardware.

Thanks & Regards,

Snehal

RE: Insufficient resources error while doing Buttonless OTA on NRF52840

Hung Bui — Wed, 20 Sep 2023 10:55:58 GMT

Hi Snehal,

At step 1 please don't flash the application. You should flash only the bootloader + softdevice.

At step 4, please try testing with:

1 - Simple blinky application

2 - ble_app_hrs

3 - usbd_msc

You may need to modify the usbd_msc application so that it works with the softdevice.
Please make sure all of the application works with application + softdevice before you test with DFU and bootloader.

If the test #3 worked fine, then it must be something wrong with your application that make it doesn't work when DFU updated. You would need to comment out some features of the application until you see that it would run after DFU update.

Please let me know the result of the test #1, #2, #3.

RE: Insufficient resources error while doing Buttonless OTA on NRF52840

sne_333 — Wed, 20 Sep 2023 05:00:15 GMT

Hi Hung,

When I try to debug with segger studio, it is working fine. The Gatt error comes only after updating firmware via DFU. To avoid more confusion please see the steps below which I am following for test.

1)Flash the firmware files separately one by one (bootloader, softdevice & application)

2)Device is advertising and visible in NRF connect app.

3) Connect NRF connect with device.

4) Do OTA upgrade

5) Upgrade finishes

6) After upgrading firmware I am no longer able to connect to the device.

This firmware includes USB MSC code. So is that causing an issue after OTA upgrade? Do we need to set anything after OTA? It seems like device gets stuck after upgrading. I am not even able to see any logs in RTT viewer.

Also one thing to note is in my sdk config "NRF_SDH_DISPATCH_MODEL" is set to "0" which is interrupt based. I had to set this define as I am using USB MSC with FreeRTOS. Is this causing an issue?

Thanks & Regards,

Snehal

RE: Insufficient resources error while doing Buttonless OTA on NRF52840

Hung Bui — Wed, 13 Sep 2023 12:47:42 GMT

Hi,
My understanding is that the device, after DFU, advertised. Then you connect to it and then you get the GATT ERROR ?
It's not that after DFU the device doesn't do anything, correct ?

In that case, please try to debug the application to see if you have any assert. You can debug it as normal like when you flash it directly.

Please also capture a sniffer trace so that we know what exactly happens.

RE: Insufficient resources error while doing Buttonless OTA on NRF52840

sne_333 — Wed, 13 Sep 2023 09:19:13 GMT

Hi Hung,

I already tried DFU without USB MSC code in my application firmware. Without USB MSC code OTA works fine. I am able to upgrade the firmware and connect to device even after OTA. The problem comes only when i add usb msc code in my application firmware.

The error which I get while testing usb msc code is as follows:-

Thanks & Regards,

Snehal

RE: Insufficient resources error while doing Buttonless OTA on NRF52840

Hung Bui — Wed, 13 Sep 2023 08:55:59 GMT

Hi Snehal,

Please keep merge hex out of the scope until you have made DFU works.

From what you described DFU doesn't work. You mentioned "but as soon as application is loaded via DFU, I am no longer able to connect to the device." Does that mean the device is not working after DFU update? Does it advertise as your application ? Please show the error.

Please try to follow the documentation and test doing DFU with a very simple application before you test with your application. For example ble_app_hrs. You can follow my tutorial here: Getting started with Nordic's Secure DFU bootloader, a step by step guide

After you have DFU working for an example, please try testing DFU with a example that uses USB MSC in the SDK.

RE: Insufficient resources error while doing Buttonless OTA on NRF52840

sne_333 — Wed, 13 Sep 2023 08:11:34 GMT

Hi Hung,

I am using "pca10056_s140_ble_debug" bootloader in my project which is BLE bootloader.

If you don't do merge hex and simply DFU the application, would the application works after DFU ?

>> Yes if I don't merge the files and flash it one by one, then DFU upgrade works but as soon as application is loaded via DFU, I am no longer able to connect to the device. It gives GATT error on nrf connect app and no logs are shown on RTT viewer.

you are talking about if you comment out the USB MSC the merged hex file worked fine. If you have the USB MSC in your code the merged hex file doesn't work ?

>> Yes If I comment USB MSC code from project OTA works fine even with merged files. But If I uncomment the USB MSC code then it won't work. Even logs can't be seen on RTT viewer in this case which makes it difficult to debug.

What I'm thinking of is that there could be a chance that the bootloader has initialized USB or write to a register that should be cleaned before you use it in the application.

>> which register should be cleaned here and how to do it?

Also I had one more doubt. I am merging settings.hex also with the firmware file. Does that cause an issue?

Thanks & Regards,
Snehal