NRF Connect app stuck on "VALIDATING" when performing DFU

RE: NRF Connect app stuck on "VALIDATING" when performing DFU

Simon — Tue, 23 Feb 2021 12:08:27 GMT

Jon: It seems like your initial issue is solved: performing BLE DFU on the nRF52840 using the mcumgr protocol. Right?

Could you open a new ticket about "maximize throughput on DFU from IOS and Android". This way we can keep the forum more organized and easier to navigate for other developers. By the way, I recommend you to check out the nRF Connect Device Manager App, which is made for your usecase; updating and managing devices running nRF Connect SDK (using the mcumgr protocol).

Mike Hibbett: Your case will be assigned to a Nordic engineer today, which will take a look at you issue.

Best regards,

Simon

RE: NRF Connect app stuck on "VALIDATING" when performing DFU

Mike Hibbett — Tue, 23 Feb 2021 10:22:37 GMT

I too am experiencing this issue. I reported it here:

devzone.nordicsemi.com/.../fota-with-nordic-connect-sdk-ncs-not-working

RE: NRF Connect app stuck on "VALIDATING" when performing DFU

Simon — Sun, 21 Feb 2021 10:35:35 GMT

Sorry for the delay on this, I'll look into this the next week

Best regards,

Simon

RE: NRF Connect app stuck on "VALIDATING" when performing DFU

Jon — Sat, 20 Feb 2021 19:01:45 GMT

Yet another update:

I added the following configs and was able to get a DFU to work from the NRF Connect app (note that I am still unsuccessful from the NRF Toolbox app, as I still get the same 'DFU Init packet required' error):

CONFIG_BT_RX_BUF_LEN=86
CONFIG_BT_L2CAP_RX_MTU=75
CONFIG_BT_L2CAP_TX_MTU=75
CONFIG_MCUMGR_SMP_BT_AUTHEN=n

With said configuration, I see a throughput of about 0.5KB/sec from my Android phone.

Then I made the following changes to increase MTU:

CONFIG_BT_RX_BUF_LEN=258
CONFIG_BT_L2CAP_RX_MTU=247
CONFIG_BT_L2CAP_TX_MTU=247
CONFIG_BT_CTLR_TX_BUFFER_SIZE=251
CONFIG_BT_CTLR_DATA_LENGTH_MAX=251

With this configuration, I see an average throughput of about 2.3KB/sec. I tried further increasing the MTU to 517 as follows:

CONFIG_BT_RX_BUF_LEN=528
CONFIG_BT_L2CAP_RX_MTU=517
CONFIG_BT_L2CAP_TX_MTU=517

...but with this configuration I get an assert:"ASSERTION FAIL [net_buf_simple_tailroom(buf) >= len] @ WEST_TOPDIR/zephyr/subsys/net/buf.c:793"

Can you provide information on the ideal configuration to maximize throughput on DFU from IOS and Android (I realize that some issues cannot be controlled since they are handled by the mobile OS).

Thanks!

Jon

RE: NRF Connect app stuck on "VALIDATING" when performing DFU

Jon — Fri, 19 Feb 2021 16:26:51 GMT

Another update: I traced the DFU process to the point where the first upload message is sent to the device from the NRF Connect app. The CBOR message includes the MCUBoot header. The message includes the CBOR payload as follows:

{"data": h'3DB8F3960000000000020000344B0800000000000000', "len": 544203, "sha": h'034862', "off": 0}

As you can see, the MCUBoot magic is correct (0x96f3b83d). However, this data is rejected in the function img_mgmt_impl_upload_inspect() in 'modules/lib/mcumgr/cmd/img_mgmt/port/zephyr/src/zephyr_img_mgmt.c' of the NRFConnect SDK because the header sent by the app only contains 22 bytes of data, whereas the MCUBoot header is defined as 32 bytes in length. The line which checks this is:

    if (req->off == 0) {
        /* First upload chunk. */
        if (req->data_len < sizeof(struct image_header)) {
            /*
             * Image header is the first thing in the image.
             */
            *errstr = img_mgmt_err_str_hdr_malformed;
            return MGMT_ERR_EINVAL;
        }

RE: NRF Connect app stuck on "VALIDATING" when performing DFU

Jon — Fri, 19 Feb 2021 01:41:31 GMT

An update: I disabled CONFIG_MCUMGR_SMP_BT_AUTHEN, and now Nrf Connect app gets a little bit further: Instead of getting hung on the 'Validating' message. it quickly flashes "Starting DFU" and then exits back to the characteristics screen.

Thanks,

Jon