Dual Bank DFU CRC computation failed after copy to bank 0

RE: Dual Bank DFU CRC computation failed after copy to bank 0

tyana — Tue, 04 May 2021 11:54:48 GMT

Hello,

have you found a solution to this problem in the end?

RE: Dual Bank DFU CRC computation failed after copy to bank 0

tesc — Thu, 12 Apr 2018 16:14:41 GMT

Hi,

It is hard to change bootloader size during DFU, mainly because the bootloader start address is written to a UICR register. Also because bank size and location calculations (for where to download and move firmware images to and from) depend on where the bootloader begins, so that extra care must be taken if changing bootloader size during DFU. While possible, it does require a lot of effort.

It is much easier to stick to the same bootloader size. That size may be larger than the one we provide with the SDK, as long as you set the project settings flash start and flash size values correctly. In addition, the BOOTLOADER_START_ADDR define should also get this value, and it should be written to UICR. This should happen automatically for the various toolchains, as the value is fetched from the project settings for flash, but double checking never hurts.

I suspect that you get two separate errors. One when adding debug (related to changed bootloader size), and one when not adding debug (hard to tell what happens there). I found your private thread and will look into the files that you provided there.

Regards,
Terje

RE: Dual Bank DFU CRC computation failed after copy to bank 0

Bart Cerneels — Wed, 11 Apr 2018 16:31:07 GMT

Is it possible the CRC calculation while receiving the DFU data and the one after the copy from bank1 to bank0 is using different sizes? It's difficult to trace with bootloader_settings. Could the 2nd CRC be using a value it got from the DFU init packet?

I believe this is generated by nrfutil, but perhaps there is something wrong there.

RE: Dual Bank DFU CRC computation failed after copy to bank 0

Bart Cerneels — Wed, 11 Apr 2018 07:49:52 GMT

I just reduced our bootloader size to 24k using the value from the secure_dfu_ble_gcc_nrf52.ld

FLASH (rx) : ORIGIN = 0x78000, LENGTH = 0x6000

In fact, our ld is exactly the same.

Now that debugging is disabled it's difficult to know for sure but it reboots in DFU mode, so I'll assume the CRC check failed again.

I will try with my J-Link plus in monitor mode later, but have not gotten that to work yet, hence the need for print debugging.

RE: Dual Bank DFU CRC computation failed after copy to bank 0

Bart Cerneels — Wed, 11 Apr 2018 07:09:17 GMT

I indeed had to increase the bootloader size. I included NRF_LOG_BACKEND_RTT and a bit more debugging. The dfu_request_handling() is copied directly from the 14.2.0 examples/dfu/dfu_req_handling with some debugging and a change of hardware version.

Could you explain why changing the bootloader location and size can cause the CRC issue I'm seeing?
I've found this ancient document explaining relocating the bootloader:
https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.sdk52.v0.9.0%2Fbledfu_memory_relocating.html
Is any of this info still valid? Is relocating bootloader still possible with non-modified libraries?

RE: Dual Bank DFU CRC computation failed after copy to bank 0

tesc — Wed, 04 Apr 2018 16:09:41 GMT

Hi,

I am sorry for the delay. We have been out-of-office due to Easter holidays.

Note that you may experience some trouble if you increase the size of the bootloader itself past the flash page boundary, so check that you have not done so.

The crc field of the nrf_dfu_settings_t structure is the crc of the rest of that structure itself. The crc of the bank image is in the nrf_dfu_bank_t structures, e.g. bank_0.image_crc and bank_1.image_crc.

In nrf_dfu_app_continue(), after copying the application is done, the crc of the copied data is checked and then written to bank_0.image_crc. That way, when the data has been copied over (from bank 1 to bank 0) the crc should be the correct one.

Perhaps you can do a diff between the original bootloader from the SDK and your version, to see if anything stands out?

Regards,
Terje

RE: Dual Bank DFU CRC computation failed after copy to bank 0

Bart Cerneels — Thu, 29 Mar 2018 09:17:03 GMT

When flashing the application with a JLink I'm generating the bootloader settings with CRC = 0 and flashing it along with my application. The --debug-mode bootloader boots this as expected.

RE: Dual Bank DFU CRC computation failed after copy to bank 0

Bart Cerneels — Thu, 29 Mar 2018 09:15:02 GMT

I was mistaken about the device being bricked. I was under the assumption the peer data would be removed if this error happened. Since it's still there the bootloader will indeed go into DFU

RE: Dual Bank DFU CRC computation failed after copy to bank 0

Bart Cerneels — Thu, 29 Mar 2018 09:13:38 GMT

I've shared those files in a private thread.

RE: Dual Bank DFU CRC computation failed after copy to bank 0

tesc — Tue, 27 Mar 2018 16:56:43 GMT

Hi,

I do not quite understand what you are seeing here. The bootloader either

reads in the bootloader settings page that there is an applicaiton, reads the alleged application from flash and calculates the CRC, and if it matches the application CRC stored in the bootloader settings file it starts the application

or, if the above fails,

enters DFU mode.

If you can not get the device into bootloader mode again then that suggests that you have actually jumped to the application, but that the application fails. Have you tested the application by programming it directly with a programmer? In order to test it together with the bootloader you must also generate the bootloader settings file using nrfutil. Then you should also be able to run a debug session for the application.

I see from the make target that you use --debug-mode and that there is no application version (only application version string). Are you using the debug version of the bootloader?

I would like to get the bootloader hex file and the DFU zip file in order to reproduce, or flash dumps from before and after the upgrade ("nrfutil --readcode filename.hex" for dumping the nRF flash contents to a hex file.) If you do not want to share that here on the open forum then we can make the thread private first or you can create a private ticket and refer to this thread.

Regards,
Terje

Dual Bank DFU CRC computation failed *after* copy to bank 0

RE: Dual Bank DFU CRC computation failed *after* copy to bank 0

RE: Dual Bank DFU CRC computation failed *after* copy to bank 0

RE: Dual Bank DFU CRC computation failed *after* copy to bank 0

RE: Dual Bank DFU CRC computation failed *after* copy to bank 0

RE: Dual Bank DFU CRC computation failed *after* copy to bank 0

RE: Dual Bank DFU CRC computation failed *after* copy to bank 0

RE: Dual Bank DFU CRC computation failed *after* copy to bank 0

RE: Dual Bank DFU CRC computation failed *after* copy to bank 0

RE: Dual Bank DFU CRC computation failed *after* copy to bank 0

RE: Dual Bank DFU CRC computation failed *after* copy to bank 0

Dual Bank DFU CRC computation failed after copy to bank 0

RE: Dual Bank DFU CRC computation failed after copy to bank 0

RE: Dual Bank DFU CRC computation failed after copy to bank 0

RE: Dual Bank DFU CRC computation failed after copy to bank 0

RE: Dual Bank DFU CRC computation failed after copy to bank 0

RE: Dual Bank DFU CRC computation failed after copy to bank 0

RE: Dual Bank DFU CRC computation failed after copy to bank 0

RE: Dual Bank DFU CRC computation failed after copy to bank 0

RE: Dual Bank DFU CRC computation failed after copy to bank 0

RE: Dual Bank DFU CRC computation failed after copy to bank 0

RE: Dual Bank DFU CRC computation failed after copy to bank 0