nRF52832 buttonless DFU without bonds failed

RE: nRF52832 buttonless DFU without bonds failed

Amanda Hsieh — Thu, 04 Aug 2022 14:30:23 GMT

Hi,

The latest issue is far away from the original scope, and my colleague answered it in this thread.

-Amanda

RE: nRF52832 buttonless DFU without bonds failed

snowuyl — Thu, 04 Aug 2022 04:06:54 GMT

devzone.nordicsemi.com/.../advertising.c devzone.nordicsemi.com/.../8308.ota.c

RE: nRF52832 buttonless DFU without bonds failed

snowuyl — Thu, 04 Aug 2022 01:32:13 GMT

RE: nRF52832 buttonless DFU without bonds failed

snowuyl — Thu, 04 Aug 2022 01:31:51 GMT

I try to use iOS nRF Connect APP to perform DFU. But it failed with "scanning timeout returning no matching peripheral". Why no bootloader log messages after BLE_DFU_EVT_BOOTLOADER_ENTER_PREPARE event?

The following is log messages of nRF52832 device.

00> <info> app: Version 1.2.1
00>
00>
00> <info> app: ========| flash info |========
00>
00> <info> app: erase unit: 4096 bytes
00>
00> <info> app: program unit: 4 bytes
00>
00> <info> app: end address: 0x72000
00>
00> <info> app: ==============================
00>
00> <info> app_timer: RTC: initialized.
00>
00> <info> app: Setting vector table to bootloader: 0x00072000
00>
00> <info> app: Setting vector table to main app: 0x00026000
00>
00> <debug> app: bleDfuInit() return 0
00>
00>
00> <debug> app: NOR_DATA_PERIOD=819
00>
00>
00> <debug> app: NOR_RECORD_PERIOD=8192
00>
00>
00> <info> app: bsp_button_longkey_handler 0.
00>
00> <warning> app: Battery volage 0mV is too low
00>
00>
00> <warning> app: Battery volage 3374mV is too low
00>
00>
00> <info> app: POWER_ON.
00>
00> <info> app: External devices initializing start
00> <info> app: External devices initializing finish
00>
00> <info> app: bsp_button_longkey_handler 1.
00>
00> <debug> nrf_ble_gatt: Requesting to update ATT MTU to 185 bytes on connection 0x0.
00>
00> <info> app: BLE_GAP_EVT_CONNECTED
00>
00>
00> <debug> app: state=1
00>
00>
00> <info> app: BLE_GAP_EVT_PHY_UPDATE_REQUEST
00>
00>
00> <debug> nrf_ble_gatt: Peer on connection 0x0 requested a data length of 251 bytes.
00>
00> <debug> nrf_ble_gatt: Updating data length to 27 on connection 0x0.
00>
00> <debug> nrf_ble_gatt: Data length updated to 27 on connection 0x0.
00>
00> <debug> nrf_ble_gatt: max_rx_octets: 27
00>
00> <debug> nrf_ble_gatt: max_tx_octets: 27
00>
00> <debug> nrf_ble_gatt: max_rx_time: 2120
00>
00> <debug> nrf_ble_gatt: max_tx_time: 2120
00>
00> <debug> nrf_ble_gatt: ATT MTU updated to 185 bytes on connection 0x0 (response).
00>
00> <debug> app: _securityRequestHandler
00>
00>
00> <info> app: BLE_GAP_EVT_SEC_PARAMS_REQUEST
00>
00>
00> <info> app: PM_EVT_CONN_SEC_SUCCEEDED
00>
00>
00> <info> app: Connection secured: role: 1, conn_handle: 0x0, procedure: 1.
00>
00> <info> app: BLE_GAP_EVT_AUTH_STATUS
00>
00>
00> <info> app: BLE_DFU_EVT_BOOTLOADER_ENTER_PREPARE

RE: nRF52832 buttonless DFU without bonds failed

Amanda Hsieh — Tue, 02 Aug 2022 06:18:03 GMT

Hi,

Do you write opcode 0x01 to get into DFU mode?

Have a look at this Buttonless Secure DFU Service without bonds doc.

-Amanda

RE: nRF52832 buttonless DFU without bonds failed

snowuyl — Mon, 01 Aug 2022 13:45:00 GMT

Which event will be received in nRF52832 device when I press "Button DFU without bonds" soft key? I can't see any BLE_DFU_EVT_BOOTLOADER_xxx events in log messages. But ble_dfu_buttonless_init() return 0.:

log messages:

00> <info> app_timer: RTC: initialized.
00>
00> <info> app: Setting vector table to bootloader: 0x00072000
00>
00> <info> app: Setting vector table to main app: 0x00026000
00> <debug> app:bleDfuInit() return 0
00>
00> <debug> app: NOR_DATA_PERIOD=819
00>
00>
00> <debug> app: NOR_RECORD_PERIOD=8192
00>
00>
00> <info> app: bsp_button_longkey_handler 0.
00>
00> <debug> nrf_ble_gatt: Requesting to update ATT MTU to 185 bytes on connection 0x0.
00>
00> <info> app: PM_EVT_BONDED_PEER_CONNECTED
00>
00>
00> <info> app: BLE_GAP_EVT_CONNECTED
00>
00>
00> <debug> app: state=1
00>
00>
00> <info> app: PM_EVT_CONN_SEC_SUCCEEDED
00>
00>
00> <info> app: Connection secured: role: 1, conn_handle: 0x0, procedure: 0.
00>
00> <debug> nrf_ble_gatt: ATT MTU updated to 185 bytes on connection 0x0 (response).
00>
00> <debug> app: _securityRequestHandler
00>
00>
00> <info> app: PM_EVT_CONN_SEC_CONFIG_REQ
00>
00>
00> <info> app: BLE_GAP_EVT_SEC_PARAMS_REQUEST
00>
00>
00> <info> app: PM_EVT_CONN_SEC_SUCCEEDED
00>
00>
00> <info> app: Connection secured: role: 1, conn_handle: 0x0, procedure: 1.
00>
00> <info> app: BLE_GAP_EVT_AUTH_STATUS
00>

source code related to BLE_DFU_EVT_BOOTLOADER_xxx event handling.
static void _bleDfuEvtHandler(ble_dfu_buttonless_evt_type_t event) {
    switch (event) {
        case BLE_DFU_EVT_BOOTLOADER_ENTER_PREPARE:
        {
            NRF_LOG_INFO("BLE_DFU_EVT_BOOTLOADER_ENTER_PREPARE");

            // Prevent device from advertising on disconnect.
            advertisingModesConfigSet();

            // Disconnect all other 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.
            uint32_t conn_count = ble_conn_state_for_each_connected(_bleDfuDisconnect, NULL);
            NRF_LOG_INFO("Disconnected %d links.", conn_count);
        }
        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
            NRF_LOG_INFO("BLE_DFU_EVT_BOOTLOADER_ENTER\n");
        }
        break;

        case BLE_DFU_EVT_BOOTLOADER_ENTER_FAILED:
        {
            NRF_LOG_ERROR("BLE_DFU_EVT_BOOTLOADER_ENTER_FAILED\n");
            // 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("BLE_DFU_EVT_RESPONSE_SEND_ERROR\n");
            // YOUR_JOB: Take corrective measures to resolve the issue
            //           like calling APP_ERROR_CHECK to reset the device.
        }
        break;

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

int bleDfuInit(void) {
    ret_code_t errCode = ble_dfu_buttonless_async_svci_init();
    if (errCode != NRF_SUCCESS) {
        NRF_LOG_WARNING("ble_dfu_buttonless_async_svci_init() failed, errCode=0x%x\n", errCode);
        return ERROR_OTA_INITIALIZE_FAIL;
    }

    ble_dfu_buttonless_init_t init = {0};
    init.evt_handler = _bleDfuEvtHandler;
    errCode = ble_dfu_buttonless_init(&init);
    if (errCode != NRF_SUCCESS) {
        NRF_LOG_WARNING("ble_dfu_buttonless_init() failed, errCode=0x%x\n", errCode);
        return ERROR_OTA_INITIALIZE_FAIL;
    }

    NRF_LOG_DEBUG("bleDfuInit() return 0\n");
    return 0;
}

RE: nRF52832 buttonless DFU without bonds failed

Amanda Hsieh — Mon, 01 Aug 2022 12:00:22 GMT

Hi,

It has the buttonless DFU service, so it doesn't need to trigger to get into DFU again.

-Amanda

RE: nRF52832 buttonless DFU without bonds failed

snowuyl — Mon, 01 Aug 2022 10:15:54 GMT

RE: nRF52832 buttonless DFU without bonds failed

snowuyl — Mon, 01 Aug 2022 10:14:46 GMT

After I restart nRF Connect, it can connect to nRF52832 device. How can I trigger nRF52832 device to enter DFU mode from nRF Connect?

10> <debug> nrf_ble_gatt: Requesting to update ATT MTU to 185 bytes on connection 0x0.
10>
10> <info> app: BLE_GAP_EVT_CONNECTED
10>
10>
10> <debug> app: state=1
10>
10>
10> <debug> nrf_ble_gatt: ATT MTU updated to 185 bytes on connection 0x0 (response).
10>
10> <info> app: BLE_GATTS_EVT_SYS_ATTR_MISSING

10>

RE: nRF52832 buttonless DFU without bonds failed

snowuyl — Mon, 01 Aug 2022 10:06:02 GMT

I have solved CRC check of app failed issue by regenerating bootloader_setting.hex by nrfutil and reprogramming bootloader_setting.hex, bootloader.hex, softdevice_s132.hex, and nrf52832_xxaa.hex.

But I encounter another problem. nRF Connect can't connect nRF52832 with "Faield to secure connection with handle 00".

log messages of nRF52832 device.
10> <info> app: Version 1.2.1
10>
10>
10> <info> app: ========| flash info |========
10>
10> <info> app: erase unit: 4096 bytes
10>
10> <info> app: program unit: 4 bytes
10>
10> <info> app: end address: 0x72000
10>
10> <info> app: ==============================
10>
10> <info> app_timer: RTC: initialized.
10>
10> <info> app: Setting vector table to bootloader: 0x00072000
10>
10> <info> app: Setting vector table to main app: 0x00026000
10>
10> <debug> app: NOR_DATA_PERIOD=819
10>
10>
10> <debug> app: NOR_RECORD_PERIOD=8192
10>
10>
10> <info> app: bsp_button_longkey_handler 0.
10>
10> <debug> nrf_ble_gatt: Requesting to update ATT MTU to 185 bytes on connection 0x0.
10>
10> <info> app: BLE_GAP_EVT_CONNECTED
10>
10>
10> <debug> app: state=1
10>
10>
10> <info> app: PM_EVT_CONN_SEC_FAILED
10>
10> <info> app: Faield to secure connection with handle 00
10>
10>
10> <info> app: BLE_GAP_EVT_DISCONNECTED
10>
10>
10> <debug> app: state=0
10>
10>
10> <debug> app: _securityRequestHandler
10>

log messages of nRF Connect.

nRF5x
DA:73:F1:2C:90:6A
Generic Access
Generic Attribute
17:32:10.097   Using nrf-device-lib-js version: 0.4.11
17:32:10.097   Using nrf-device-lib version: 0.11.8
17:32:10.097   Using nrfjprog DLL version: 10.15.4
17:32:10.097   Using JLink version: JLink_V7.66a
17:32:10.120   Installed JLink version does not match the provided version (V7.58b)
17:32:10.601   Updated list of uuids with data from github.com/.../v1
17:32:12.762   Selected device with s/n DA73F12C906A
17:32:12.770   Device setup completed
17:32:12.770   Connectivity firmware version: ble-connectivity 4.1.4+Mar-11-2021-08-36-04. SoftDevice API version: 5. Baud rate: 1000000.
17:32:12.771   Opening adapter connected to COM10
17:32:13.719   Successfully opened COM10. Baud rate: 1000000. Flow control: none. Parity: none.
17:32:13.722   Reset performed on adapter COM10
17:32:14.805   Adapter connected to COM10 opened
17:32:18.734   Scan started
17:33:18.739   Scanning timed out on adapter COM10
17:33:23.212   Connecting to device
17:33:29.327   Connected to device E8:20:9F:75:90:08: interval: 7.5ms, timeout: 4000ms, latency: 0
17:33:29.347   ATT MTU updated for device E8:20:9F:75:90:08, new value is 185
17:33:29.592   Attribute value read, handle: 0x03, value (0x): 41-4E-43-53-32
17:33:34.381   Connection parameters updated for device E8:20:9F:75:90:08: interval 15ms, timeout 3000ms, latency: 0
17:33:37.026   Security updated, mode:1, level:3
17:33:37.079   Storing bond info for device E8:20:9F:75:90:08
17:33:56.976   Attribute value changed, handle: 0x0E, value (0x): 02-00
17:33:56.981   Attribute value written, handle: 0x0E, value (0x): 02-00
17:34:13.688   Disconnected from device E8:20:9F:75:90:08, reason: BLE_HCI_CONNECTION_TIMEOUT
17:34:38.597   Scan started
17:34:40.480   Connecting to device
17:35:00.489   Connection to device timed out
17:36:02.463   Scan started
17:36:29.017   Connecting to device
17:36:29.529   Connected to device E8:20:9F:75:90:08: interval: 7.5ms, timeout: 4000ms, latency: 0
17:36:29.541   ATT MTU updated for device E8:20:9F:75:90:08, new value is 185
17:36:29.580   Security updated, mode:1, level:3
17:36:29.844   Attribute value read, handle: 0x03, value (0x): 41-4E-43-53-32
17:36:34.587   Connection parameters updated for device E8:20:9F:75:90:08: interval 15ms, timeout 3000ms, latency: 0
17:36:37.127   Security updated, mode:1, level:3
17:36:37.179   Storing bond info for device E8:20:9F:75:90:08
17:37:43.881   Disconnected from device E8:20:9F:75:90:08, reason: BLE_HCI_CONNECTION_TIMEOUT
17:37:51.202   Connecting to device
17:38:11.212   Connection to device timed out
17:40:41.743   Connecting to device
17:41:01.750   Connection to device timed out
17:56:41.236   Scan started
17:56:47.402   Connecting to device
17:56:47.557   Connected to device E8:20:9F:75:90:08: interval: 7.5ms, timeout: 4000ms, latency: 0
17:56:47.576   ATT MTU updated for device E8:20:9F:75:90:08, new value is 185
17:56:47.600   Disconnected from device E8:20:9F:75:90:08, reason: BLE_HCI_REMOTE_USER_TERMINATED_CONNECTION

RE: nRF52832 buttonless DFU without bonds failed

snowuyl — Mon, 01 Aug 2022 09:49:50 GMT

devzone.nordicsemi.com/.../6116.nrfjprog.rar

RE: nRF52832 buttonless DFU without bonds failed

snowuyl — Mon, 01 Aug 2022 09:48:14 GMT

Now I encounter another issue, that is "nrf_dfu_validation: CRC check of app failed". Do I need enable CRC16 or CRC32?

00> <info> app: Inside main
00>
00> <debug> app: In nrf_bootloader_init
00>
00> <debug> nrf_dfu_settings: Calling nrf_dfu_settings_init()...
00>
00> <debug> nrf_dfu_flash: Initialiúing nrf_fstorage_nvmc backend.
00>
00> <debug> nrf_dfu_settings: Using settings page.
00>
00> <debug> nrf_dfu_settings: Copying forbidden parts from backup page.
00>
00> <debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
00>
00> <info> nrf_dfu_settings: Backing up settings page to address 0x7E000.
00>
00> <debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
00>
00> <debug> app: Enter nrf_bootloader_fw_activate
00>
00> <info> app: No firmware to activate.
00>
00> <debug> app: crc_on_valid_app_required() return 0x1
00>
00>
00> <debug> nrf_dfu_validation: CRC check of app failed. Return 1
00>
00> <debug> app: App is valid
00>
00> <info> nrf_dfu_settings: Backing up settings page to address 0x7E000.
00>
00> <debug> nrf_dfu_segs: Destination settings are identical to source, write not +'Ã
14> d. Skip.
14>
14> +Ãug> app: Running nrf_bootloader_app_start with address: 0x00001000
14>
14> <debug> app: Disabling interrupts. NVIC->ICER[0]: 0x0
14>
14> <info> app: Inside main
14>
14> <debug> app: In nrf_bootloader_init
14>
14> <debug> nrf_dfu_settings: Callinï îru_settings_init()...
14>
14> <debug> nrf_dfu_flash: Initializing nrf_fstorage_nvmc backend.
14>
14> <debug> nrf_dfu_settings: Using settings page.
14>
14> <debug> nrf_dfu_settings: Copying forbidden parts from backup page.
14>
14> <debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
14>
14> <info> nrf_dfu_sett: Backing up settings page to address 0x7E000.
14>
14> <debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
14>
14> <debug> app: Enter nrf_bootloader_fw_activate
14>
14> <info> app: No firmware to activate.
14>
14> <debug> app: crc_on_valid_app_«ûired() return 0x1
14>
14>
14> <debug> nrf_dfu_validation: CRC check of app failed. Return 1
14>
14> <debug> app: App is valid
14>
14> <info> nrf_dfu_settings: Backing up settings page to address 0x7E000.
14>
14> <debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
14>
14> <debug> app: Running nrf_booder_app_t with address: 0x00001000
14>
14> <debug> app: Disabling interrupts. NVIC->ICER[0]: 0x0
14>
14> <info> app: Inside main
14>
14> <debug> app: In nrf_bootloader_init
14>
14> <debug> nrf_dfu_settingsllinf_dfu_segs_init()...
14>
14> <debug> nrf_dfu_flash: Initializing nrf_fstorage_nvmc backend.
14>
14> <debug> nrf_dfu_settings: Using settings page.
14>
14> <debug> nrf_dfu_settings: Copying forbidden parts from backup page.
14>
14> <debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
14>
14> <info> nrf_dfu_settings: Bag uptings page to address 0x7E000.
14>
14> <debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
14>
14> <debug> app: Enter nrf_bootloader_fw_activate
14>
14> <info> app: No firmware to activate.
14>
14> <debug> app: crc_on_valid_app_required() return 0x1
14>
14>
14> <debug> nrf_dfu_validation: CRC check of app failed. Return 1
14>
14> <debug> app: App is valid
14>
14> <info> nrf_dfu_settings: Backing up settings page to address 0x7E000.
14>
14> <debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
14>
14> <debug> app: Running nrf_bootloader_app_start with address: 0x00001000
14>
14> <debug> app: Disabling interrupts. NVIC->ICER[0]: 0x0
14>
14> <info> app: Inside main
14>
14> <debug> app: In nrf_bootloader_init
14>
14> <debug> nrf_dfu_settings: Calling nrf_dfu_settings_init()...
14>
14> <debug> nrf_dfu_flash: Initializing nrf_fstorage_nvmc backend.
14>
14> <debug> nrf_dfu_settings: Using settings page.
14>
14> <debug> nrf_dfu_settings: Copying forbidden parts from backup page.
14>
14> <debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
14>
14> <info> nrf_dfu_settings: Backing up settings page to address 0x7E000.
14>
14> <debug> nrf_dfu_settings: Destinatiettings are identical to source, write not needed. Skipping.
14>
14> <debug> app: Enter nrf_bootloader_fw_activateinfop: Nrmware to activate.
14>
14> <debug> app: crc_on_valid_app_required() return 0x1
14>
14>
14> <debug> nrf_dfu_validation: CReck of app failed. Return 1
14>
14> <debug> app: App is valid
14>
14> <info> nrf_dfu_settings: Backing up settings page to addrex7E000.
14>
14> <debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. ping<debug> app: Running nrf_bootloader_app_start with address: 0x00001000
14>
14> <debug> app: Disabling interrupts. NVIC->ICER[0]: 0x0
14>
14> <info> app: Inside main
14>
14> <debug> app: In nrf_bootloader_init
14>
14> <debug> nrf_dfu_settings: Calling nrf_dfu_settings_init()...
14>
14> <debug> nrf_dfu_flash: Initializing nrf_fstorage_nvmc backend.
14>
14> <debug> nrf_dfu_settings: Using settings page.
14>
14> <debug> nrf_dfu_settings: Copying forbidden parts from backup page.
14>
14> <debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
14>
14> <info> nrf_dfu_settings: Backing up settings page to addres7E000.
14>
14> <de nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
14>
14> <debug> app: Enter nrf_bootloader_fw_activate
14>
14> <info> app: No firmware to activate.
14>
14> <debug> app: crc_on_valid_app_required() return 0x1
14>
14>
14> <debug> nrf_dfu_validation: CRC check of app fd. Return 1
14>
14> <debug> app: App is valid
14>
14> <info> nrf_dfu_settings: Backing up settings page to address 0x7E000.
14>
14> <debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
14>
14> <debug> app: Running nrf_bootloader_app_start with address: 0x00001000
14>
14> <debug> app: Disabling interrupts. NVIC->ICER[0]: 0x0
14>
14> <info> app: Inside main
14>
14> <debug> app: In nrf_bootloader_init
14>
14> <debug> nrf_dfu_settings: Calling nrf_dfu_settings_init()...
14>
14> <debug> nrf_dfu_flash: Initializing nrf_fstorage_nvmc backend.
14>
14> <debug> nrf_dfu_settings: Using settings page.
14>
14> <debug> nrf_dfu_settings: Copying forbidden parts from backup page.
14>
14> <debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
14>
14> <info~ dfu_settings: Backing up settings page to address 0x7E000.
14>
14> <debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
14>
14> <debug> app: Enter nrf_boadåòactivate
14>
14> <info> apo firmware to activate.
14>
14> <debug> app: crc_on_valid_app_required() return 0x1
14>
14>
14> <debug> nrf_dfu_validation: CRC check of app failed. Return 1
14>
14> <debug> app: App is valid
14>
14> <info> nrf_dfu_settings: Backing up settings page to address 0x7E000.
14>
14> <debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
14>
14> <debug> app: Run_bootloader_app_start with address: 0x00001000
14>
14> <debug> app: Disabling interrupts. NVIC->ICER[0]: 0x0
14>
14> o> app: Inside main
14>
14> <debug> app: In nrf_bootloader_init
14>
14> <debug> nrf_dfu_settings: Calling nrf_dfu_settings_init()...
14>
14> <debug> nrf_dfu_flash: Initializing nrf_fstorage_nvmc backend.
14>
14> <debug> nrf_dfu_settings: Using settings page.
14>
14> <debug> nrf_dfu_settings: Copying forbidden parts from backup page.
14>
14> <debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
14>
14> <info> nrf_dfu_settings: Backing up settings page to address 0x7E000.
14>
14> <debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
14>
14> <debug> app: Enter nrf_bootloader_fw_activate
14>
14> <info> app: No firmware to activate.
14>
14> <debug> app: crc_on_valid_app_required() return 0x1
14>
14>
14> <debug> nrf_dfu_validation: CRC check of app failed. Return 1
14>
14> <debug> app: App is valid
14>
14> <info> nrf_dfu_settings: B_KÃng up settings page to address 0x7E000.
14>
14> <debug> nrf_dfttings: Destination settings are identical to source, write not needed. Skipping.
14>
14> <debug> app: Running nrf_bootloader_app_start with address: 0x00001000
14>
14> <debug> app: Disabling interrupts. NVIC->ICER[0]: 0x0
14>
14> <iîfpp: Inside main
14>
14> <debug> app: In nrf_bootloader_init
14>
14> <debug> nrf_dfu_settings: Calling nrf_dfu_settings_init()...
14>
14> <debug> nrf_dfu_flash: Initializing nrf_fstorage_nvmc backend.
14>
14> <debug> nrf_dfu_settings: Using settings page.
14>
14> <debug> nrf_dfu_settings: Copying forbidden parts from backup page.
14>
14> <debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
14>
14> <info> nrf_dfu_sett: Backing up settings page to address 0x7E000.
14>
14> <debug> nrf_dfu_settingestination settings are identical to sou/gù write not needed. Skipping.
14>
14> <«ûg> app: Enter nrf_bootloader_fw_acti
14>
14> <info> app: No firmware to activate.
14> ebugp: crc_on_valid_app_required() return 0x1
14>
14>
14> <debug> nrf_dfu_validation: CRC check of app failed. Return 1
14>
14> <debug> app: App is valid
14>
14> <info> nrf_dfu_settings: Backing up settings page to address 0x7E000.
14>
14> <debugf_dfu_settings: Destination settings are identical turce, write not needed. Skipping.
14>
14> <debapp: Running nrf_bootloader_app_start with address: 0x00001000
14>
14> <debug> app: Disabling interrupts. NVIC->ICER[0]: 0x0
14>
14> Ú<info> app: Inside main
14>
14> <debug> app: In nrf_bootloader_init
14>
14> <debug> nrf_dfu_settings: Calling nrf_dfu_segs_init()...
14>
14> <debug> nrf_dfu_flash: Initializing nrf_fstorage_nvmc backend.
14>
14> <debug> nrf_dfu_settings: Using settings page.
14>
14> <debug> nrf_dfu_settings: Copying forbidden parts from backup page.
14>
14> <debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
14>
14> <info> nrf_dfu_settings: Backing up settings page to address 0x7E000.
14>
14> <debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
14>
14> <debug> app: Enter nrf_bootloader_fw_activate
14>
14> <info> app: No firmware ttivate.
14> íæo> aprc_on_valid_app_required() return 0x1
14>
14>
14> <debug> nrf_dfu_validation: CRC check of app failed. Return 1
14>
14> <debugp: App is valid
14>
14> <info> nrf_dfu_settings: Backing up settings page to address 0x7E000.
14>
14> <debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
14>
14> <debug> app: Running nrf_bootloader_app_start with address: 0x00001000
14>
14> <debug> app: Disabling interrupts. NVIC->ICER[0]: 0x0
14>
14> <info> app: Inside main
14>
14> <debug> app: In nrf_bootloader_init
14>
14> <debug> nrf_dfu_settings: Calling nrf_dfu_settings_init()...
14>
14> <debug> nrf_dfu_flash: Initializing nrf_fstorage_nvmc backend.
14>
14> <debug> nrf_dfu_settings: Using settings page.
14>
14> <debug> nrf_dfu_settings: Copying forbidden parts from backup page.
14>
14> <debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
14>
14> <info> nrf_dfu_settings: Backing up settinoge to address 0x7E000.
14>
14> <debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
14>
14> <debug> app: Enter nrf_bootloader_fw_acti
14>
14> <info> app: No firmware to activasiø
14> <debug> app: crc_on_valid_app_required() return 0x1
14>
14>
14> <debug> nrf_dfu_validation: CRC check of app failed. Return 1
14>
14> <debug> app: App is valid
14>
14> <info> nrf_dfu_settings: Backing up settings page to address 0x7E000.
14>
14> <debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
14>
14> <debug> app: Running nrf_bootloader_app_start with address: 0x00001000
14>
14> <debug> app: Disabling interrupts. NVIC->ICER[0]: 0x0
14>
14> <info> app: Inside main
14>
14> <debug> apn nrf_bootloader_init
14>
14> <debug> nrf_dfu_settings: Calling nrf_dfu_settings_init()...
14>
14> <debug> nrf_dfu_flash: Initializing nrf_fstorage_nvmc backend.
14>
14> <debug> nrfßsettings: Using settings page.
14>
14> <debug> nrf_dfu_settingopying forbidden parts from backup page.
14>
14> <debug> nrf_dfu_settings:tination settings are identical to source, write not needed. Skipping.
14>
14> <info> nrf_dfu_settings: Backing up settings page to address 0x7E000.
14>
14> <debug> nrf_dfu_settings: Destination settings are identical to source, write needed. Skipping.
14>
14> <debug> app: r nrf_boader_fw_activate
14>
14> <info> app: No firmware to activate.
14>
14> <debug> app: crc_on_valid_app_required() return 0x1
14>
14>
14> <debug> nrf_dfu_validation: CRC check of app failed. Return 1
14>
14> <debug> app: App is valid
14>
14> <info> nrf_dfu_settings: Backing up settings page to address 0x7E000.
14>
14> <debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
14>
14> <debug> app: Running nrf_bootloader_app_start with address: 0x00001000
14>
14> <debug> app: Disabling interrupts. NVIC->ICER[0]: 0x0
14>
14> o> app: Inside main
14>
14> <debug> app: In nrf_bootloader_init
14>
14> <debug> nrf_dfu_settings: Calling nrf_dfu_settings_init()...
14>
14> <debug> nrf_dfu_flash: Initializing nrf_fstorage_nvmc backend.
14>
14> <debug> nrf_dfu_settings: Using settings page.
14>
14> <debug> nrf_dfu_settings: Copying forbidden parts from backup page.
14>
14> <debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
14>
14> <info> nrf_dfu_££ûings: Backing up settings page to address 0x7E000.
14>
14> <debug> nrf_dfu_settingó~ Änation settings are identical to source, write not needed. Skipping.
14>
14> <debug> app: Enter nrf_booôìk³Ã_fw_£Kûvateéîîïp: No firmware to activate.
14>
14> <debug> app: crc_on_valid_app_required() return 0x1
14>
14>
14> <debug> nrf_dfu_vation: CRC check of app failed. Return 1
14>
14> <debug> app: App is valid
14>
14> <info> nrf_dfu_settings: Backing up settings page to address 0x7E000.
14>
14> <debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
14>
14> <debug> app: Running nrf_bootloader_app_start with address: 0x00001000
14>
14> <debug> app: Disabling interrupts. NVIC->ICER[0]: 0x0
14>
14> o> app: Inside main
14>
14> <debug> app: In nrf_bïader_init
14>
14> <debug> nrf_«ûÂsett: Calling nrf_dfu_settings_init()...
14>
14> <debug> nrf_dfu_flash: Initializing nrf_fstorage_nvmc backend.
14>
14> <debug> nrf_dfu_settings: Using settings page.
14>
14> <debug> nrf_dfu_settings: Copying forbidden parts from backup page.
14>
14> <debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
14>
14> <info> nrf_dfu_settings: Backing up settings page to address 0x7E000.
14>
14> <debug> nrf_dfu_settings: Destination settings are identical to source, write not needed.`SÜing.
14>
14> <debug> app: Enter nrf_bootloader_fw_activate
14>
14> <info> app: No firmware to activate.
14>
14> <debug> app: crc_on_valid_app_required() return 0x1
14>
14>
14> <debug> nrf_dfu_validation: CRC check of app failed. Return 1
14>
14> <debug> app: App is valid
14>
14> <info> nrf_dfu_settings: Backing up settings page to address 0x7E000.
14>
14> <debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
14>
14> <debug> app: Running nrf_bootüïaûú
10> pp_start with address: 0x00001000
10>
10> <debug> app: Disabling interrupts. NVIC->ICER[0]: 0x0
10>
10> <infpp: Inside main
10>
10> <debug> app: In nrf_bootloader_init
10>
10> <debug> nrf_dfu_settings: Calling nrf_dfttinnit()...
10>
10> <debug> nrf_dfu_flash: Initializing nrf_fstor+ûÂnvmc backend.
10>
10> <debug> nrf_dfu_settings: Using settings page.
10>
10> <debug> nrf_dfu_settings: Copying forbidden parts from backup page.
10>
10> <debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
10>
10> <info> nrf_dfu_settings: Backing up settings page to address 0x7E000.
10>
10> <debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
10>
10> <debug> app: Enter nrf_bootloader_fw_activate
10>
10> <info> app: No fire to activate.
10>
10> <debug> app: crc_on_valid_app_required() reôuv1
10>
10>
10> <debug> nrf_dfu_validation: CRC check of app failed. Return 1
10>
10> <debug> app: App is valid
10>
10> <info> nrf_dfu_settings: Backing up settings page to address 0x7E000.
10>
10> <debug> nrf_dfu_settinDestination settings are identical to source, write not k#Ã
14> d. Skipping.
14>
14> <debug> app: Run nrf_bootloader_app_start with address: 0x00001000
14>
14> <debug> app: Disabling interrupts. NVIC->ICER[0]: 0x0
14>
14> <info> app: Inside main
14>
14> <debug> app: In nrf_bootloader_init
14>
14> <debug> nrf_dfu_settings: Calling nrf_dfu_settings_init()...
14>
14> <debug> nrf_dfu_flash: Initializing nrf_fstorage_nvmc backend.
14>
14> <debug> nrf_dæu_££ûings: Using settings page.
14>
14> <debug> nrf_dfu_settings: Copying forbidden parts from backup page.
14>
14> <debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
14>
14> <info> nrf_dfu_settings: Backing up settings page to address 0x7E000.
14>
14> <debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
14>
14> <debug> app: Enter nrf_bootloader_fw_activate
14>
14> <info> app: No firmware to activate.
14>
14> <debug> app: crc_on_valid_app_required() return 0x1
14>
14>
14> <debug> nrf_dfu_validation: CRC check of app failed. Return 1
14>
14> <debug> app: App is valid
14>
14> <info> nrf_dfu_sets: Backing up settings page to address 0x7E000.
14>
14> <debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
14>
14> <debug> app: Running nrf_bootloader_app_start wéddress: 0x00001000
14>
14> <debug> app: Disabling interrupts. NVIC->ICER[0]: 0x0
14>
14> <info> app: Inside main
14>
14> <debug> app: In nrf_bootloader_init
14>
14> <debug> nrf_dfu_settings: Calling nrf_dfu_settings_init()...
14>
14> <debug> nrf_dfu_flash: Initializing nrf_fstorage_nvmc backend.
14>
14> <debug> nrf_dfu_settings: Using settings page.
14>
14> <debug> nrf_dfu_settings: Copying forbidden parts from backup page.
14>
14> <debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
14>
14> fo> nrf_dfu_settings: Bag up settings page to address 0x7E000.
14>
14> <debug> nrf_dfu_settingestination settings are identical to source, write not needed. Skipping.
14>
14> <debug> app: Enter nrf_bootloader_fw_activate> app: No firmware to activate.
14>
14> <debug> app: crc_on_valid_app_required() retur1
14>
14> ebug> nrf_dfu_validation: CRC check of app failed. Return 1
14>
14> <debug> app: App is valid
14>
14> <info> nrf_dfu_settings: Backing up settkngs page to address 0x7E000.
14>
14> <debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
14>
14> <debug> app: Running nrf_bootloader_app_start with address: 0x00001pppbug>: Disabling interrupts. NVIC->ICER[0]: 0x0
14>
(Connection lost)

RE: nRF52832 buttonless DFU without bonds failed

Amanda Hsieh — Mon, 01 Aug 2022 08:05:21 GMT

Hi,

The secure_bootloader supports buttonless DFU without other modifications. When the device enters DFU mode, DFU mode is indicated by LED 3 being lit. From the log, the secure_bootloader seems to go into the buttonless DFU. It should advertise "DfuTarg" as the name. You can check with the nRFConnect mobile app.

-Amanda

RE: nRF52832 buttonless DFU without bonds failed

snowuyl — Mon, 01 Aug 2022 06:40:48 GMT

I use nRF5_SDK_16.0.0\examples\dfu\secure_bootloader\pca10040_s132_ble_debug. But it enter DFU mode since "Boot validation failed. No valid app to boot". But since I would like nRF connect to trigger nRF52832 enter DFU. What should I change in secure_bootloader for supporting buttonless DFU OTA?

0> <info> app: Inside main
0> <debug> app: In nrf_bootloader_init
0> <debug> nrf_dfu_settings: Calling nrf_dfu_settings_init()...
0> <debug> nrf_dfu_flash: Initializing nrf_fstorage_nvmc backend.
0> <debug> nrf_dfu_settings: Using settings page.
0> <debug> nrf_dfu_settings: Copying forbidden parts from backup page.
0> <debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
0> <info> nrf_dfu_settings: Backing up settings page to address 0x7E000.
0> <debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
0> <debug> app: Enter nrf_bootloader_fw_activate
0> <info> app: No firmware to activate.
0> <info> app: Boot validation failed. No valid app to boot.
0> <debug> app: DFU mode because app is not valid.
0> <info> nrf_bootloader_wdt: WDT is not enabled
0> <debug> app: in weak nrf_dfu_init_user
0> <debug> app: timer_stop (0x20005980)
0> <debug> app: timer_activate (0x20005980)
0> <info> app: Entering DFU mode.
0> <debug> app: Initializing transports (found: 1)
0> <debug> nrf_dfu_ble: Initializing BLE DFU transport
0> <debug> nrf_dfu_ble: Setting up vector table: 0x00072000
0> <debug> nrf_dfu_ble: Enabling SoftDevice.
0> <debug> nrf_dfu_ble: Configuring BLE stack.
0> <debug> nrf_dfu_ble: Enabling the BLE stack.
0> <debug> nrf_dfu_ble: No advertising name found
0> <debug> nrf_dfu_ble: Using default advertising name
0> <debug> nrf_dfu_ble: Advertising...
0> <debug> nrf_dfu_ble: BLE DFU transport initialized.
0> <debug> nrf_dfu_flash: Initializing nrf_fstorage_sd backend.
0> <debug> app: Enter main loop

RE: nRF52832 buttonless DFU without bonds failed

snowuyl — Fri, 29 Jul 2022 15:15:39 GMT

Thanks for your reply! I will add BLE_GATTS_EVT_SYS_ATTR_MISSING event handler on next monday.

RE: nRF52832 buttonless DFU without bonds failed

Amanda Hsieh — Fri, 29 Jul 2022 12:06:23 GMT

Hi,

You will receive BLE_GATTS_EVT_SYS_ATTR_MISSING if the peer tries to read a CCCD that hasn't been set. When the BLE_GATTS_EVT_SYS_ATTR_MISSING event is received the application should do a sd_ble_gatts_sys_attr_set() function call, potentially giving back a set of previously set values. However, when not being bonded, it is expected to just pass NULL for the pointer, to reset the values.

Take a look at this and this post from Devzone, it might be helpful.

The erasse issue is handled by https://devzone.nordicsemi.com/f/nordic-q-a/90510/nrfjprog-failed-to-erase-nrf52832-device

-Amanda

RE: nRF52832 buttonless DFU without bonds failed

snowuyl — Fri, 29 Jul 2022 01:55:56 GMT

D:\Nordic>nrfjprog --log --family nRF52 --eraseall
[error]: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".

[error]: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".

[error]: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".

[error]: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".

ERROR: Unable to connect to a debugger.
[error]: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".

ERROR: JLinkARM DLL reported an error. Try again. If error condition
ERROR: persists, run the same command again with argument --log, contact Nordic
ERROR: Semiconductor and provide the generated log.log file to them.

D:\Nordic>nrfjprog --version
nrfjprog version: 10.17.0 external
JLinkARM.dll version: 7.66a

RE: nRF52832 buttonless DFU without bonds failed

snowuyl — Thu, 28 Jul 2022 12:22:16 GMT

Thanks for your reply! I am using custom board with jlink and connect to laptop through USB port. I will try command line tool tomorrow. Since nrf52832 device received BLE_GATTS_EVT_SYS_ATTR_MISSING event, I think it should not receive this event.

RE: nRF52832 buttonless DFU without bonds failed

Amanda Hsieh — Thu, 28 Jul 2022 11:56:41 GMT

Hi,

The segger seems not to connect to your target.

Are you using nRF52832DK or a custom board?

Could you download the latest version of the Command line tool and try again?

From the device and nRF Connect logs, I don't see any fail or error. How do you know it failed?

-Amanda

RE: nRF52832 buttonless DFU without bonds failed

snowuyl — Thu, 28 Jul 2022 10:03:03 GMT

RE: nRF52832 buttonless DFU without bonds failed

snowuyl — Thu, 28 Jul 2022 09:59:32 GMT

I can't erase the kit through nrfjprog or SEGGER Embedded Studio.

nrfjprog --log --family nRF52 --eraseall
WARNING: Logging is unavailable. nrfjprog.exe does not have write
WARNING: permission for the log file
ERROR: Unable to connect to a debugger.
ERROR: JLinkARM DLL reported an error. Try again. If error condition
ERROR: persists, run the same command again with argument --log, contact Nordic
ERROR: Semiconductor and provide the generated log.log file to them.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.

RE: nRF52832 buttonless DFU without bonds failed

snowuyl — Thu, 28 Jul 2022 09:28:54 GMT

17:18:47.101   Using nrf-device-lib-js version: 0.4.11
17:18:47.102   Using nrf-device-lib version: 0.11.8
17:18:47.102   Using nrfjprog DLL version: 10.15.4
17:18:47.102   Using JLink version: JLink_V7.66a
17:18:47.125   Installed JLink version does not match the provided version (V7.58b)
17:18:47.283   Updated list of uuids with data from github.com/.../v1
17:25:24.417   Selected device with s/n F092AF29DAF8
17:25:24.426   Device setup completed
17:25:24.427   Connectivity firmware version: ble-connectivity 4.1.4+Mar-11-2021-08-36-04. SoftDevice API version: 5. Baud rate: 1000000.
17:25:24.428   Opening adapter connected to COM5
17:25:25.374   Successfully opened COM5. Baud rate: 1000000. Flow control: none. Parity: none.
17:25:25.376   Reset performed on adapter COM5
17:25:26.443   Adapter connected to COM5 opened
17:25:31.554   Scan started
17:25:33.110   Connecting to device
17:25:38.231   Connected to device E8:20:9F:75:90:08: interval: 7.5ms, timeout: 4000ms, latency: 0
17:25:38.258   ATT MTU updated for device E8:20:9F:75:90:08, new value is 185
17:25:38.512   Attribute value read, handle: 0x03, value (0x): 41-4E-43-53-32
17:25:43.285   Connection parameters updated for device E8:20:9F:75:90:08: interval 15ms, timeout 3000ms, latency: 0
17:25:46.516   Security updated, mode:1, level:3
17:25:46.566   Storing bond info for device E8:20:9F:75:90:08
17:25:55.708   Attribute value changed, handle: 0x0E, value (0x): 02-00
17:25:55.713   Attribute value written, handle: 0x0E, value (0x): 02-00

RE: nRF52832 buttonless DFU without bonds failed

snowuyl — Thu, 28 Jul 2022 09:18:11 GMT

nRF5_SDK_16.0.0

RE: nRF52832 buttonless DFU without bonds failed

Amanda Hsieh — Thu, 28 Jul 2022 09:12:09 GMT

Hi,

What SDK version are you using?

[quote user=""]I use nRF Connect to test buttonless DFU without bonds failed.[/quote]

Can you provide the log from the nRF Connect?

Please try to erase the kit before programming.

Regards,
Amanda

RE: nRF52832 buttonless DFU without bonds failed

snowuyl — Thu, 28 Jul 2022 05:13:16 GMT

devzone.nordicsemi.com/.../ota.c devzone.nordicsemi.com/.../ota.h