dfu upgrade failed

RE: dfu upgrade failed

Simonr — Wed, 24 Aug 2022 07:19:22 GMT

I see, that should be fine. Since the Advertising Interval here recommends using the advertising interval of 20 ms for 30 seconds before moving to either of the longer advertising intervals. Many of our example projects have different advertising intervals. One FAST and one SLOW, and with different advertising durations for these. Reference below:

#define APP_ADV_FAST_INTERVAL          40                                     /**< The advertising interval (in units of 0.625 ms). The default value corresponds to 25 ms. */
#define APP_ADV_SLOW_INTERVAL          3200                                   /**< Slow advertising interval (in units of 0.625 ms). The default value corresponds to 2 seconds. */

#define APP_ADV_FAST_DURATION          3000                                   /**< The advertising duration of fast advertising in units of 10 milliseconds. */
#define APP_ADV_SLOW_DURATION          18000                                  /**< The advertising duration of slow advertising in units of 10 milliseconds. */

NRF_BLE_GATT_MTU_EXCHANGE_INITIATION_ENABLED should not affect the DFU as far as I know.

Best regards,

Simon

RE: dfu upgrade failed

Mikey — Tue, 23 Aug 2022 12:09:30 GMT

According to the design parameters of ios, we choose 546.25ms, so 874*0.265 = 546.25ms. (I hope I am not wrong).

Does the parameter "NRF_BLE_GATT_MTU_EXCHANGE_INITIATION_ENABLED" affect the upgrade?

RE: dfu upgrade failed

Simonr — Tue, 23 Aug 2022 10:56:33 GMT

Okay, your advertising parameters look good, just the APP_ADV_INTERVAL being set to 874 seems a little off, although it shouldn't cause any issues. Any specific reason it is set to 874?

If it's not too hard to reproduce, it would be great if we could confirm whether this was a flash timeout or not. You can place a breakpoint or blink a LED in bootloader-> nrf_dfu_scvi_handler.c-> nrf_dfu_set_adv_name_on_sys_evt->NRF_EVT_FLASH_OPERATION_ERROR for example to verify this.

Best regards,

Simon

RE: dfu upgrade failed

Mikey — Tue, 23 Aug 2022 00:45:24 GMT

My product looks more like this.

RE: dfu upgrade failed

Mikey — Mon, 22 Aug 2022 15:20:02 GMT

Hi,

This is some current configuration and I don't know how to analyze it.

#define APP_ADV_INTERVAL                874                                 

#define APP_ADV_DURATION                0//18000                            

#define MIN_CONN_INTERVAL               MSEC_TO_UNITS(30, UNIT_1_25_MS)     
#define MAX_CONN_INTERVAL               MSEC_TO_UNITS(75, UNIT_1_25_MS)     
#define SLAVE_LATENCY                   0                                   
#define CONN_SUP_TIMEOUT                MSEC_TO_UNITS(4000, UNIT_10_MS)     

#define FIRST_CONN_PARAMS_UPDATE_DELAY  APP_TIMER_TICKS(5000)

The broadcast channel has not been modified, and the data channel is currently set to BLE_GAP_PHY_AUTO.

RE: dfu upgrade failed

Simonr — Mon, 22 Aug 2022 13:18:36 GMT

Is this reproducible with the buttonless_DFU example project in SDK 17.1.0 or has the customer made any changes to it to trig these errors?

The error you're seeing indicates that the bootloader failed to store the new advertisement name to flash, possibly due to a flash timeout.

A flash timeout means that the SoftDevicewas unable to schedule a flash operation which was successfully requested by the application/bootloader. This should not happen unless there is a lot of BLE activity in parallel with the flash writes. Please have a look at table 1 in the Flash memory API chapter and see if your application meets any of the criteria for low to medium probability of success.

Best regards,

Simon