NRF52832 Firmware Upgrade using Esp8266

[Vaibhav_Bansal]

Hi Team

I am trying to implement the firmware upgrade for master controller nrf52832 on chip using esp8266 over uart and I am very new with this boot-loader part.

I had gone through many examples and trying to understand the flow from where to start. Code had already implementation of DFU using nrf connect application and working, but now I need to do this using esp8266.

My flow is I will download the hex file from the server and then upgrade the hex file form esp8266 over uart.

I had seen the examples - secure_bootloader_dfu and iot example but still not able to understand the example.

Any help or suggestion in this.

[Matt]

Sounds like your Esp8266 plays the role of DFU controller. I've not touched DFU lately but I do find the DFU documentation back in SDKv11 very detailed and readable. There's also an DFU example using uart instead of ble for transferring the new firmware image. Checkout SDKv11 to see if that example helps with what you plan to do: Software Development Kit > Previous versions of nRF5 SDK > nRF5 SDK v11.0.0 > Examples > DFU bootloader examples > BLE & HCI/UART Bootloader/DFU > Architecture

[Vaibhav_Bansal]

Hi can you suggest me the settings that I should do in bootloader file to enable the serial dfu.

[Vaibhav_Bansal]

Hi,

In SES only after providing the path to the library I am able to compile the code but It is saying slip_encode is not defined even I am able to see that in slip.c library, also I had removed that #ifdef in Slip.c

[Vaibhav_Bansal]

I am using Keil v5 now, and error I am getting is Fail to download  flash - "Cortex-M4"

[Hung Bui]

Please try to do an "nrfjprog.exe --eraseall" in the command line. 
You can also find the .hex file in the build folder and flash it manually using either nrfjprog or use nRF Connect programmer tool.

[Vaibhav_Bansal]

Hi 

I am successful to get the debug logs and I found that after sending the INIT file, what I observed that when device is trying to write the update dfu settings then device got stuck and also it is happening during flash erase only.

But when I do same over BLE its working, code won't stuck and erase successful works.

I am not able to understand the reason behind this, is there any difference between Ble DFU and Serial DFU which makes this happens

[Vaibhav_Bansal]

    if (    ((page_addr & (p_fs->p_flash_info->erase_unit - 1)) != 0)
        ||  !addr_within_bounds(p_fs, page_addr, (len * p_fs->p_flash_info->erase_unit)))
    {
	
        return NRF_ERROR_INVALID_ADDR;
    }
    print(LL_INFO,"333333\n");
    return (p_fs->p_api)->erase(p_fs, page_addr, len, p_context);

This code is not returning during execution of OP command in serial DFU mode but working in BLE DFU .

I am not able to understand the reason, any suggestions please!