nrf52832 buttonless DFU with fstorage

RE: nrf52832 buttonless DFU with fstorage

Coder_hope — Thu, 27 Aug 2020 09:41:43 GMT

This problem is solved. here is my solution:

#define SN_HW_EXIST_MASK (uint32_t)0x12345678u
#define FIRMWARE_EXIST_MASK (uint32_t)0x87654321u

#define FSTORAGE_START_ADDR (uint32_t)0x3EE00
#define FSTORAGE_END_ADDR (uint32_t)0x78000
uint32_t Hardware_VerAddr __attribute__ ((at(0x74400)));
uint32_t Serial_NumAddr __attribute__ ((at(0x74300)));
uint32_t SN_HW_EXIST_Addr __attribute__ ((at(0x74100)));

uint32_t Firmware_VerAddr __attribute__ ((at(0x3EE10)));
uint32_t Firmware_EXIST_Addr __attribute__ ((at(0x3EE00)));

I changed FW version addr and exist addr, fstorage start addr changed too,In my app,when dfu command comes, device prepare to enter bootloader,I reset the FW version exist addr`s value in ble_dfu_evt_handler, add Reset_FIRMWARE_EXIST_MASK();

void Reset_FIRMWARE_EXIST_MASK(void)
{
uint32_t data=0xFFFFFFFF;
ret_code_t rc;
rc = nrf_fstorage_write(&fstorage, (uint32_t )(&Firmware_EXIST_Addr),&data,sizeof(uint32_t), NULL);//写入标志
APP_ERROR_CHECK(rc);
}

static void ble_dfu_evt_handler(ble_dfu_buttonless_evt_type_t event)
{
    switch (event)
    {
        case BLE_DFU_EVT_BOOTLOADER_ENTER_PREPARE:
            NRF_LOG_INFO("Device is preparing to enter bootloader mode.");
            // YOUR_JOB: Disconnect all bonded devices that currently are connected.
            //           This is required to receive a service changed indication
            //           on bootup after a successful (or aborted) Device Firmware Update.
			Reset_FIRMWARE_EXIST_MASK();
		    nrf_gpio_pin_set(LED_RED);
            break;

        case BLE_DFU_EVT_BOOTLOADER_ENTER:
            // YOUR_JOB: Write app-specific unwritten data to FLASH, control finalization of this
            //           by delaying reset by reporting false in app_shutdown_handler
			Reset_FIRMWARE_EXIST_MASK();
		    nrf_gpio_pin_set(LED_RED);
            NRF_LOG_INFO("Device will enter bootloader mode.");
            break;

        case BLE_DFU_EVT_BOOTLOADER_ENTER_FAILED:
            NRF_LOG_ERROR("Request to enter bootloader mode failed asynchroneously.");
            // YOUR_JOB: Take corrective measures to resolve the issue
            //           like calling APP_ERROR_CHECK to reset the device.
            break;

        case BLE_DFU_EVT_RESPONSE_SEND_ERROR:
            NRF_LOG_ERROR("Request to send a response to client failed.");
            // YOUR_JOB: Take corrective measures to resolve the issue
            //           like calling APP_ERROR_CHECK to reset the device.
            APP_ERROR_CHECK(false);
            break;

        default:
            NRF_LOG_ERROR("Unknown event from ble_dfu_buttonless.");
            break;
    }
}

tell app that firmware information does not exist,when dfu is finished,app reboot and rewrite firmware data and exist value .

may this be helpful for others!

RE: nrf52832 buttonless DFU with fstorage

Coder_hope — Thu, 27 Aug 2020 08:24:13 GMT

Thanks for response,

with device information,the app.bin file`s size is 100KB,without device information ,the app.bin file`s size is 99kb, almost the same.

My app.hex size is 279kb,is it too big for dual bank dfu,and it automaticly choose single bank and erase flash?

the FW version is selfdifined,so we can read it and show..

RE: nrf52832 buttonless DFU with fstorage

Vidar Berg — Thu, 27 Aug 2020 07:59:34 GMT

Hi,

The DFU image will become too big if variables are placed inside the preserved app data region at link time. You may check the size difference by comparing the size of the *.bin file inside the generated DFU package with and without these device information variables included.

Also, you may want to consider using the UICR registers for one-time configurations such as the serial number and device type. And the app FW version is already stored in the bootloader settings page (s_dfu_settings @0x7F000).

RE: nrf52832 buttonless DFU with fstorage

Coder_hope — Thu, 27 Aug 2020 03:05:50 GMT

new progress：

I regenerate public key and privete key，DFU and device information work well ,but when i change the Firmware_Version,and run dfu, the reported frimware is still old one ,not new one.

I guess this is because the DFU uses dual bank ,the Firmware_VerAddr is not erased during OTA,so it remain the same,So how to set the edge address of bank0 and bank1,to make the code of Firmware_Version work as I wash?