REQUEST AN IOS VERSION DFU UPGRADE PROCESS

[ANNY-TAO]

DFU is now implemented on ipads and iphones, as well as on Android phones, and the app platform is nRF Connect. The problem is that the firmware upgrade can be achieved normally with an Android phone; The ipad can connect and read data, but it can't use the DFU function; iPhones can't connect to Bluetooth; Observe the log information in the process of iPad DFU, and observe <debug> nrf_dfu_validation: CRC check of app failed. What is the reason for such a sentence as Return 1? And the IPAD can establish a connection with the firmware bluetooth, but the iphone15 can't establish a connection, what could be the problem?

The version of SDK is 17.0.2；
The following is the information for the wrong printing:

1. 00> <debug> app: Running nrf_bootloader_app_start with address: 0x00001000
   00>
   00> <debug> app: Disabling interrupts. NVIC->ICER[0]: 0x0
   00>
   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: Initializing 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> 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_settings: Destination settings are identical to source, write not needed. Skipping.
   00>
   00> <debug> app: Running nrf_bootloader_app_start with address: 0x00001000
   00>
   00> <debug> app: Disabling interrupts. NVIC->ICER[0]: 0x0
   00>
   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: Initializing 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: App is valid
   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: Running nrf_bootloader_app_start with address: 0x00001000
   00>
   00> <debug> app: Disabling interrupts. NVIC->ICER[0]: 0x0
   00>

[Vidar Berg]

Hello,

00> <debug> nrf_dfu_validation: CRC check of app failed. Return 1

The debug message indicates that the computed checksum of the application does not match the expected checksum stored in the bootloader settings page. However, the bootloader is allowed to boot the image anyway, as you are using the debug variant of the bootloader, which sets the NRF_DFU_DEBUG flag. This suggests that the application image was altered after the DFU was completed. It's strange that this only happens with iOS/ipadOS and not Android. 

Can you read out the flash after completing DFU with Android and iOS to compare the differences? You can do this with nrfjprog.

$ nrfjprog --memrd <application start address> --n <size of application image in bytes> > app_image.txt

Best regards,

Vidar

[ANNY-TAO]

Hello Vidar,thanks a lot for your reply.

As you said it's an issue with the initial jump address, I already found out yesterday.

One of the more strange problems is found at the moment, because the previous version of the iPad version 16.6.1 was used to implement the Bluetooth connection, but when using the iPhone with the iOS version 18, the Bluetooth connection could not be realized. Will the Bluetooth connection of the NRF52832 be related to the system version? Do I need to set any relevant parameters?

Best regards，

Anny