nRF5340 - DFU over serial mission impossible

RE: nRF5340 - DFU over serial mission impossible

Gabriele — Wed, 30 Dec 2020 09:08:18 GMT

Hello Smile

I didn't use the API you are mentioning.
You have to rebuild the MyApp with mcuboot and smp-srv child applications.
Take a look of image, a shrinked version of MyApp, just to make you figuring out.
In the first part of MyApp you retrieve the flag stored in the LittleFS.
Thereafter you check the flag to switch either to the application loop or to DFU related MCUMgr APIs.
If you run through a DFU (dfumode=1), you will erase the Flash (slot-1), write the new image (slot-1) and swap (slot-0 <- slot-1).
But the LittleFS's content is not touched by that, because it is safely stored on a different partition of the Flash (see memory map)

Hope this helps.

Gabriele

RE: nRF5340 - DFU over serial mission impossible

Smile Jiang — Wed, 30 Dec 2020 03:27:30 GMT

Hi,Gabriele,

My understanding is that your application normally running in "MyApp" , and the step "On next reboot the flag state is read (to set the current mode of operation) and then immediately cleared in flash (for next reboot)." also done on "MyApp", So after erased the flash, how do you step into dfu mode??? I also checked your another ticket, you mentioned these two APIs:

int boot_set_pending(int permanent);
int boot_set_confirmed(void);

Did you finally use the APIs to step into DFU mode??

Or your application always step into "MyApp", but by checking a flag on "MyApp" to decide the different operations??

I also met some issues about DFU on nrf5340, Looking forward to your reply.

Smile

RE: nRF5340 - DFU over serial mission impossible

Simon — Mon, 28 Sep 2020 14:11:44 GMT

I'm happy to help and that you found a working solution 🙂

RE: nRF5340 - DFU over serial mission impossible

Gabriele — Fri, 25 Sep 2020 14:49:16 GMT

Hi,
I think I've fixed all major issues.
When the application is running the init_uart is executed. The user can instruct the application to set a DFUMODE flag into flash (storage partition, NVS mode).
On next reboot the flag state is read (to set the current mode of operation) and then immediately cleared in flash (for next reboot). When in dfu mode, the init_uart is skipped and the smp_srv management calls get executed, allowing mcumgr messages to be parsed and permitting the user to upload-test-confirm new images at will.
Thank you for support.

RE: nRF5340 - DFU over serial mission impossible

Gabriele — Thu, 24 Sep 2020 17:02:59 GMT

Dear Simon
I've followed your hint and now I'm glad to announce you that it works!
Now I have a different issue.
It seems I cannot use UART-0 simultaneously for smp_srv and for user data exchange.
This is a simplified version of my code.
The init_uart() stuff does prevent smp_srv from working.

int main(void)
{
    int err;
    static boot foo = true;

    /* Enabling SMP Server functionalities */
	err = STATS_INIT_AND_REG(smp_svr_stats, STATS_SIZE_32, "smp_svr_stats");
	if (err < 0) {
		printk("Error initializing stats system [%d]\n", err);
		return -1;
	}

	os_mgmt_register_group();
	img_mgmt_register_group();
	stat_mgmt_register_group();

    /* Enabling UART-0 for user data exchange */
	err = init_uart();
	if (err) {
        printk("UART init failed [%d]\n", err);
		return -1;
	}

    while (1) {
        STATS_INC(smp_svr_stats, ticks); //<<<<<<<<<<<<<<<<<<<<<<< smp_srv

        /* wait for data from rx fifo */
        struct uart_data_t *buf = k_fifo_get(&fifo_uart_rx_data, K_FOREVER);  //<<<<<<<<< user data exchange

        /* parse user data */
        if (buf->data[0] = 3) {
                foo = !foo;
        }

        k_free(buf);
    }
}

RE: nRF5340 - DFU over serial mission impossible

Simon — Wed, 23 Sep 2020 20:39:56 GMT

Can't you solve this by merging the smp_svr sample with your application? By that, I don't mean to merge the hex files, but do it on the code level. Put all the relevant functions from the smp_svr into your application. When you update the chip with a new application, make sure that contains the smp_svr related functions as well.

Best regards,

Simon

RE: nRF5340 - DFU over serial mission impossible

Gabriele — Wed, 23 Sep 2020 14:19:14 GMT

Since the first image (different hash) is successfully uploaded, tested and confirmed in slot-0, I cannot run mcumgr commands remotely anymore.

The application takes control over the UART. Nobody can repeat DFU a second time via UART.

RE: nRF5340 - DFU over serial mission impossible

Simon — Wed, 23 Sep 2020 13:42:43 GMT

[quote user=""]To finish the job I have to re-initiate DFU from within MyApp, passing control to smp_srv again, otherwise all this stuff makes no sense, really.[/quote]

Why do you need to do this? Can't you just follow the procedure from here?

Test the image
- On next reset the uploaded image will remain in slot 0
Reset the device
- This can be done by clicking the reset button, or remotely
Confirm the image
- This is to avoid the uploaded image to get swapped back into slot 1

You should be aware of the following:

"Note that if you try to send the very same image that is already flashed in slot-0 then the procedure will not complete successfully since the hash values for both slots will be identical."

So don't upload the same image as is already present on the device

Best regards,

Simon