USB Dfu cause hash not match issue.

[weizhen]

hi,

I am working on nrf52833 dfu. right now I received an error 

raise NordicSemiException('Extended Error 0x{:02X}: {}'.format(resp[3], data))
pc_ble_driver_py.exceptions.NordicSemiException: Extended Error 0x0C: The hash of the received firmware image does not match the hash in the init packet.

it happened when 96% finished.

my dfu memory settings is :

FLASH (rx) : ORIGIN = 0x74000, LENGTH = 0xA000
RAM (rwx) : ORIGIN = 0x20002ae8, LENGTH = 0x1d518
uicr_bootloader_start_address (r) : ORIGIN = 0x10001014, LENGTH = 0x4
bootloader_settings_page (r) : ORIGIN = 0x0007F000, LENGTH = 0x1000
uicr_mbr_params_page (r) : ORIGIN = 0x10001018, LENGTH = 0x4
mbr_params_page (r) : ORIGIN = 0x0007E000, LENGTH = 0x1000

and my application is :

FLASH (rx) : ORIGIN = 0x27000, LENGTH = 0x4D000
RAM (rwx) : ORIGIN = 0x20000000, LENGTH = 0x20000

[weizhen]

I have not change the bootloader code, the only thing I change is makefile and config file, due to there is no example for pca10100 usb with softdevice s140.and also I change the public_key
I use nrfutil dfu usb-serial -pkg <.zip file> -p <serial port> -fc 0 to flash, and use nrfutil pkg generate --hw-version 52 --sd-req 0xCA --application-version 1 -- application <hex file> --key-file <priv.pen file> <output> to generate the package

[Edvin]

So what bootloader project did you start with? I suggest you look into starting with the SDK17\examples\dfu\secure_bootloader\pca10056_usb,

But you need to change the memory settings. 

Does your bootloader and/or application support BLE as well as USB?

Your dfu memory settings suggests that you have a softdevice, but your application does not.

Let's assume you have a softdevice:

You should change your application's ram to the same as your bootloader's to account for the softdevice.

There are some other things you should change in the makefile as well. What does your preprocessor definitions and assembly flags look like? (CFLAGS and ASMFLAGS). Perhaps there are some of those that suggests you are using a different chip?

Also, make sure to set the TARGETS := nrf52833_xxaa_s140.

I assume you have checked, but are you 100% sure that you used the same key to generate the dfu image as you used in the bootloader? (that you are using the matching private key for the bootloader's public key).

[weizhen]

from the debug version print, I get "app: Inside main" at the end, which means it should enter the application mode, but the application is not really run, and the code seems stopped.

[Marjeris Romero]

Hi weizhen,

Hung is currently out of office on vacation but he will be back next week. Thanks for your patience.

[Hung Bui]

Hi Weizhen, 
I'm sorry for late response I was on vacation last week.

Could you send us the bootloader that you made for the nRF52833 ? Are you using open bootloader or the secure one ? From which project did you modify the bootloader to ? Was it the one for nRF52832 or nRF52840 ? 

The address 0xFF8 is used to store the start address of the bootloader in the MBR.  This is optional as the start address of the bootloader is also stored in the UICR.

[weizhen]

pca10100_usb_debug.zippca10100_s140_ble_debug_usb.zip

I also post my info here. https://devzone.nordicsemi.com/f/nordic-q-a/64101/nrf52833-usb-dfu-bootloader-does-not-go-to-the-application 

the pca10100_usb_debug is the one I start from pca10100e_usb_debug, this one, I can flash, and the application and bootloader can be writed into memory, but the application is not run. then the pca10100_s140_ble_debug_usb is the one I start from pca10100_s140_ble_debug, this one the nrfutil do not give any problems, but after flash, the application is not on memory.

[Hung Bui]

Hi Weizhen, 
I have made an example for USB DFU on nRF52833. I attached the project (pca10100_usb_debug_833.zip) here. 
It's made on SES and was modified from pca10100e_usb_debug. But should be straight forward to port to gcc. I would suggest to compare the .emProject file and the flash_placement.xml file to see my modification and apply the same to your gcc Makefile. Main changes were flash size and address, ram address and size, hard floating point. 

I also attached the .hex file I used (mbr, bootloader and the dfu .zip file) so you can test on your side. 

Before you test, please make sure to do a chip erase.
 833DFU.zip

[weizhen]

hi Hung Bui,

I tested with the bootloader file you give me, it can flash the blink flash, and it can runned. but for usb debug package, it cannot flash, and return an error message.

Traceback (most recent call last):
File "/usr/local/bin/nrfutil", line 8, in <module>
sys.exit(cli())
File "/usr/local/lib/python3.7/site-packages/click/core.py", line 829, in __call__
return self.main(*args, **kwargs)
File "/usr/local/lib/python3.7/site-packages/click/core.py", line 782, in main
rv = self.invoke(ctx)
File "/usr/local/lib/python3.7/site-packages/click/core.py", line 1259, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/usr/local/lib/python3.7/site-packages/click/core.py", line 1259, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/usr/local/lib/python3.7/site-packages/click/core.py", line 1066, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/usr/local/lib/python3.7/site-packages/click/core.py", line 610, in invoke
return callback(*args, **kwargs)
File "/usr/local/lib/python3.7/site-packages/nordicsemi/__main__.py", line 1015, in usb_serial
timeout)
File "/usr/local/lib/python3.7/site-packages/nordicsemi/__main__.py", line 964, in do_serial
dfu = Dfu(zip_file_path = package, dfu_transport = serial_backend, connect_delay = connect_delay)
File "/usr/local/lib/python3.7/site-packages/nordicsemi/dfu/dfu.py", line 69, in __init__
self.manifest = Package.unpack_package(zip_file_path, self.unpacked_zip_path)
File "/usr/local/lib/python3.7/site-packages/nordicsemi/dfu/package.py", line 650, in unpack_package
with open(os.path.join(target_dir, Package.MANIFEST_FILENAME), 'r') as f:
FileNotFoundError: [Errno 2] No such file or directory: '/var/folders/m9/th1fg8h54d33zsz93rypyvdc0000gn/T/nrf_dfu_6dmao_5m/unpacked_zip/manifest.json'

also with serial window open, I have not see any debug message print out, are you using uart debug or rtt debug?

[Hung Bui]

Hi Weizhen, 
Could you explain what you meant by "but for usb debug package, it cannot flash, and return an error message" ? 

You supposed to unzip pca10100_usb_debug_833.zip put that into the bootloader example in SDK and then compile the bootloader using Segger Embedded Studio . Do that you will get the bootloader .hex file. 

If you want to compile using gcc you would need to modify your make file according to what I did in the .emProject  file and flash_placement.xml file. 

[weizhen]

hi Hung Bui,

after check the pca10100_usb_debug_833.zip you send to me. I switch the log mode I used from uart to rtt, and it works. then I do more test and found maybe there is some issues with uart log. based on my result, turn off the log or using rtt log both works, but using uart log causes the issue.

[Hung Bui]

Hi Weizhen, 
I'm sorry for the late response. 
I have tested here and reproduced the issue. I dig a little bit more and I think I found the bug. 
In nrf_bootloader_app_start() in nrf_bootloader_app_start.c we disable all interrupts and then we call NRF_LOG_FLUSH();

This will cause a dead loop inside serial_tx() if you use  UART for logging. Resulting the app never executed. 
if you call  NRF_LOG_FLUSH(); before disabling interrupts

NVIC->ICER[0]=0xFFFFFFFF;
NVIC->ICPR[0]=0xFFFFFFFF;

it should work. 

[weizhen]

Thanks, Bui, I think this fix works for me. but we also found another bug, which feels the usb dfu in this version do not clear NRF_POWER->GPREGRET after flash or time out. used when we working on nrf52832 with gpregret enter mode, the chip can go back to application after flash and time out, but now it stay in bootloader mode until power off the chip, which will reset the NRF_POWER->GPREGRET