USB DFU on a NRF52833

RE: USB DFU on a NRF52833

Marte Myrvold — Thu, 25 Nov 2021 10:43:45 GMT

Hi,

[quote user="Nppn7"]Where do I get the corresponding values for the nRF52833[/quote]

There are multiple ways to get this. The simplest way would be to open a nRF52833 project in SES and look at what these values are set to there.

You can also find it by looking at the memory map you linked. As is stated there, flash memory is divided into 128 pages of 4 kB each. In the figure you see that the last page starts on 0x7F000. Since each page is 4 kB, or 0x1000, the end of flash will be 0x7F000+0x1000=0x80000. You can do the same for RAM.

Another way is to use the size of available flash and RAM to and find the hex address from this. The nRF52833 has 512 kB flash, which is 512 * 1024 = 524 288 bytes. There are multiple converters available that convert from decimal to hex, and using this you find that the hex value is 0x80000.

Best regards,

Marte

RE: USB DFU on a NRF52833

Nppn7 — Wed, 24 Nov 2021 14:59:00 GMT

Hi,

of course you are right. That was a typo. I was using the nRF52840 as a reference.

I followed the guide you proposed and did the reverse things. I have a problem with step 3. Adding NRF52833_XXAA is fine, but adding NRF52 causes trouble:

If I remove it it throws less errors. What I do not understand is step 5. Where do I get the corresponding values for the nRF52833 (nRF52833 memory map)? I couldn't even find the ones for the nRF52820 as a reference (nRF52820 memory map).

This is how it looks like now:

devzone.nordicsemi.com/.../3010.flash_5F00_placement.xml

The error message:

RE: USB DFU on a NRF52833

Marte Myrvold — Wed, 24 Nov 2021 12:21:47 GMT

Hi,

[quote user="Nppn7"]For reference I used the nRF52833. According to the documentation the bootloader should start at 0x000F 8000. But in the working example it starts at 0xF4000.[/quote]

You are looking at the memory layout for nRF52840. The memory layout in my previous reply is for nRF52833, and is what you should look at. This is the same as the two columns at the right in the picture you posted. You see there that the bootloader starts at 0x78000, and not 0xF8000, which is outside of range for the nRF52833, as it has a flash size of 512 kB, so it only goes up to 0x80000.

Pca10010 projects with an e at the end (pca10010e) are nRF52820 projects, so secure_bootloader_usb_mbr_pca10010e is a nRF52820 project, and not nRF52833, which is why the flash and RAM settings do not correspond with the memory layout for nRF52833. The project is still configured as a nRF52820 project, which is causing you to get the errors you get. If you want to transfer this project to nRF52833 you can look at the guide Transferring the project to nRF52820 hardware, and reverse the steps there to transfer the project from nRF52820 to nRF52833, instead of from nRF52833 to nRF52820.

Best regards,

Marte

RE: USB DFU on a NRF52833

Nppn7 — Wed, 24 Nov 2021 10:17:04 GMT

Hi,

thank you for the info. I adjusted the values but get an error:

devzone.nordicsemi.com/.../1172.flash_5F00_placement.xml

I can make it build with FLASH_START=0x75000 or lower.

But this way it won't flash:

For reference I used the nRF52840. According to the documentation the bootloader should start at 0x000F 8000. But in the working example it starts at 0xF4000.

RE: USB DFU on a NRF52833

Marte Myrvold — Tue, 23 Nov 2021 12:38:23 GMT

Hi,

I see that you have made changes to the memory layout in section placement macros. FLASH_START is the start address of the program, so in the bootloader project, secure_bootloader_usb_mbr_pca10100e, this will be the start address of the bootloader. This should be 0x78000, but you have set this to 0x24000, which is too low.

If you look at the memory layout I linked to in one of my previous replies, you will see that for nRF52833 you have the following:

Usage	Memory range nRF52833 (S113 v7.0.x)	Memory range nRF52833 (S140 v7.0.x)
Bootloader settings	0x0007 F000 - 0x0008 0000 (4 kB)	0x0007 F000 - 0x0008 0000 (4 kB)
MBR parameter storage	0x0007 E000 - 0x0007 F000 (4 kB)	0x0007 E000 - 0x0007 F000 (4 kB)
Bootloader	0x0007 8000 - 0x0007 E000 (24 kB)	0x0007 8000 - 0x0007 E000 (24 kB)
Application area (incl. free space)	0x0001 C000 - 0x0007 8000 (368 kB)	0x0002 6000 - 0x0007 8000 (328 kB)
SoftDevice	0x0000 1000 - 0x0001 C000 (112 kB)	0x0000 1000 - 0x0002 6000 (148 kB)
Master Boot Record (MBR)	0x0000 0000 - 0x0000 1000 (4 kB)	0x0000 0000 - 0x0000 1000 (4 kB)

This is with SoftDevice, but even without SoftDevice and MBR the application area is 0x0 to 0x78000. You can also see this in the section placement macros in your application, where FLASH_START is 0x0 and FLASH_SIZE is 0x7e000. Right now you are programming the bootloader at 0x24000 - 0x36000, and then you try to perform DFU with an application that should be located in the area 0x0 - 0x78000, but part of this is already taken by the bootloader. The size of bootloader flash, 0x12000, is also larger than it needs to be. As you can see in the the memory layout, you only need 0x6000.

Best regards,

Marte

RE: USB DFU on a NRF52833

Nppn7 — Mon, 22 Nov 2021 15:21:40 GMT

Hi,

thanks for your quick reply. I get the same error message.

RE: USB DFU on a NRF52833

Marte Myrvold — Mon, 22 Nov 2021 15:09:20 GMT

Hi,

Try to enable single-bank updates by setting NRF_DFU_SINGLE_BANK_APP_UPDATES to 1.

Best regards,

Marte

RE: USB DFU on a NRF52833

Nppn7 — Mon, 22 Nov 2021 13:50:25 GMT

Hi,

single bank would be enough.

#define NRF_DFU_SINGLE_BANK_APP_UPDATES 0

#define NRF_DFU_FORCE_DUAL_BANK_APP_UPDATES 0

RE: USB DFU on a NRF52833

Marte Myrvold — Mon, 22 Nov 2021 13:23:54 GMT

Hi,

Yes, this would be resources regarding memory. Either your application is too large or memory is configured incorrectly. Please see Memory layout to see where different firmware components are located.

Are you using dual-bank or single-bank updates? What are NRF_DFU_SINGLE_BANK_APP_UPDATES and NRF_DFU_FORCE_DUAL_BANK_APP_UPDATES set to in sdk_config.h in the project?

Best regards,

Marte

RE: USB DFU on a NRF52833

Nppn7 — Thu, 18 Nov 2021 15:31:28 GMT

Hi,

I have another question. Since there is no bootloader example for the NRF52833 in the SDK 16.0.0, I downloaded the SDK 17.1.0. Now I am trying to build a bootloader based on the secure_bootloader_usb_mbr_pca10100e because it already has the crypto needed (when migrating from a 10065 example we had to do this manually). I had to download and build uECC. I could flash the bootloader to our custom PCB. Also I could perform

nrfutil dfu usb-serial -pkg blinky_mbr.zip -p COM16

just like before with the dev kit. It worked. Now I want to do the same thing with our custom .zip. I created custom public and private keys and provided the public one to the bootloader. When executing

nrfutil dfu usb-serial -pkg release_package.zip -p COM16

I get following error message:

  [------------------------------------]    0%                                                                                                                                                                                               Traceback (most recent call last):                                                                                                                                                                                                             File "C:\Users\gv9479\AppData\Local\Programs\Python\Python39\lib\runpy.py", line 197, in _run_module_as_main                                                                                                                                   return _run_code(code, main_globals, None,                                                                                                                                                                                                 File "C:\Users\gv9479\AppData\Local\Programs\Python\Python39\lib\runpy.py", line 87, in _run_code                                                                                                                                              exec(code, run_globals)                                                                                                                                                                                                                    File "C:\Users\gv9479\AppData\Local\Programs\Python\Python39\Scripts\nrfutil.exe\__main__.py", line 7, in <module>                                                                                                                           File "C:\Users\gv9479\AppData\Local\Programs\Python\Python39\lib\site-packages\click\core.py", line 1128, in __call__                                                                                                                          return self.main(*args, **kwargs)                                                                                                                                                                                                          File "C:\Users\gv9479\AppData\Local\Programs\Python\Python39\lib\site-packages\click\core.py", line 1053, in main                                                                                                                              rv = self.invoke(ctx)                                                                                                                                                                                                                      File "C:\Users\gv9479\AppData\Local\Programs\Python\Python39\lib\site-packages\click\core.py", line 1659, in invoke                                                                                                                            return _process_result(sub_ctx.command.invoke(sub_ctx))                                                                                                                                                                                    File "C:\Users\gv9479\AppData\Local\Programs\Python\Python39\lib\site-packages\click\core.py", line 1659, in invoke                                                                                                                            return _process_result(sub_ctx.command.invoke(sub_ctx))                                                                                                                                                                                    File "C:\Users\gv9479\AppData\Local\Programs\Python\Python39\lib\site-packages\click\core.py", line 1395, in invoke                                                                                                                            return ctx.invoke(self.callback, **ctx.params)                                                                                                                                                                                             File "C:\Users\gv9479\AppData\Local\Programs\Python\Python39\lib\site-packages\click\core.py", line 754, in invoke                                                                                                                             return __callback(*args, **kwargs)                                                                                                                                                                                                         File "C:\Users\gv9479\AppData\Local\Programs\Python\Python39\lib\site-packages\nordicsemi\__main__.py", line 1022, in usb_serial                                                                                                               do_serial(package, port, connect_delay, flow_control, packet_receipt_notification, baud_rate, serial_number, False,                                                                                                                        File "C:\Users\gv9479\AppData\Local\Programs\Python\Python39\lib\site-packages\nordicsemi\__main__.py", line 978, in do_serial                                                                                                                 dfu.dfu_send_images()                                                                                                                                                                                                                      File "C:\Users\gv9479\AppData\Local\Programs\Python\Python39\lib\site-packages\nordicsemi\dfu\dfu.py", line 127, in dfu_send_images                                                                                                            self._dfu_send_image(self.manifest.application)                                                                                                                                                                                            File "C:\Users\gv9479\AppData\Local\Programs\Python\Python39\lib\site-packages\nordicsemi\dfu\dfu.py", line 95, in _dfu_send_image                                                                                                             self.dfu_transport.send_init_packet(data)                                                                                                                                                                                                  File "C:\Users\gv9479\AppData\Local\Programs\Python\Python39\lib\site-packages\nordicsemi\dfu\dfu_transport_serial.py", line 256, in send_init_packet                                                                                          self.__execute()                                                                                                                                                                                                                           File "C:\Users\gv9479\AppData\Local\Programs\Python\Python39\lib\site-packages\nordicsemi\dfu\dfu_transport_serial.py", line 421, in __execute                                                                                                 self.__get_response(DfuTransportSerial.OP_CODE['Execute'])                                                                                                                                                                                 File "C:\Users\gv9479\AppData\Local\Programs\Python\Python39\lib\site-packages\nordicsemi\dfu\dfu_transport_serial.py", line 504, in __get_response                                                                                            raise NordicSemiException('Response Code {}'.format(                                                                                                                                                                                     pc_ble_driver_py.exceptions.NordicSemiException: Response Code InsufficientResources

Is this related to ressources in a memory sense?

Here is our layout. Please correct if anything is wrong.

Bootloader:

devzone.nordicsemi.com/.../7587.flash_5F00_placement.xml

Application:

devzone.nordicsemi.com/.../7140.flash_5F00_placement.xml

RE: USB DFU on a NRF52833

Marte Myrvold — Thu, 18 Nov 2021 12:30:14 GMT

Hi,

Great that you figured it out! Does this mean the issue can be closed?

Best regards,

Marte

RE: USB DFU on a NRF52833

Nppn7 — Thu, 18 Nov 2021 06:56:38 GMT

Hi,

I could do it the following way:

nrfutil pkg generate --sd-req 0x00 --hw-version 52 --application-version 1 --application out.hex --key-file priv.pem package.zip

As described in the documentation https://infocenter.nordicsemi.com/index.jsp?topic=%2Fsdk_nrf5_v16.0.0%2Flib_bootloader_dfu_validation.html&anchor=lib_dfu_image in the chapter "Updates without a SoftDevice".