UART DFU for nRF52833

RE: UART DFU for nRF52833

Vidar Berg — Tue, 27 Oct 2020 09:58:46 GMT

Yes. And you can call NVIC_SystemReset() to perform the reset. The bootloader will check the GPREGRET on subsequent boot.

RE: UART DFU for nRF52833

rcerati — Mon, 26 Oct 2020 17:19:06 GMT

> The bootloader will enter DFU mode only if GPREGRET contain the value 0xB1

Ok, but how to switch from application program to bootloader ?

Is it needed to force a soft reset ? and how ?

nRF52833 DS refers to SYSRESETREQ (5.3.6.4 Soft reset), but it is not clear for me.

Best Regards

RE: UART DFU for nRF52833

Vidar Berg — Mon, 26 Oct 2020 10:56:53 GMT

[quote user="rcerati"]The project includes also ses_startup_nrf52.s;[/quote]

That means your project is configured for the 52832 (pca10040 board), not the 52833 (pca10100). You should go over the linker settings as well as the startup files to verify it matches your device.

[quote user="rcerati"]NRF_POWER->GPREGRET = (uint8_t val) 0x1;[/quote]

The bootloader will enter DFU mode only if GPREGRET contain the value 0xB1 (BOOTLOADER_DFU_START)

Best regards,

Vidar

RE: UART DFU for nRF52833

rcerati — Fri, 23 Oct 2020 17:00:31 GMT

The project was built with 'system_nrf52.c': I changed it with 'system_nrf52833.c' and now reset button works.

I also checked

nrfjprog --memrd 0x10001200
0x10001200: 00000012 |....|

The project includes also ses_startup_nrf52.s;

should I change it with ses_startup_nrf52833.s ?

If I want to test NRF_BL_DFU_ENTER_METHOD_GPREGRET:

I'm adding

NRF_POWER->GPREGRET = (uint8_t val) 0x1;

in an application program.

Is it all needed to enter in DFU mode or it is needed to force a soft reset ?

Thank you

Best Regards

RE: UART DFU for nRF52833

Vidar Berg — Fri, 23 Oct 2020 13:42:57 GMT

It appears to be mismatch between your project configuration and chip target. Make sure the project is built with 'system_nrf52833.c' and not system_nrf52.c

RE: UART DFU for nRF52833

rcerati — Fri, 23 Oct 2020 08:56:00 GMT

nrfjprog --memrd 0x10001200
0x10001200: 00000015 |....|

and

nrfjprog --memrd 0x10001204
0x10001204: 00000015 |....|

It seems not setted the right pin

shuld I reprogram the register with

nrfjprog --memwr 0x10001200 --val 0x12 --verify

and

nrfjprog --memwr 0x10001204 --val 0x12 --verify

RE: UART DFU for nRF52833

Vidar Berg — Fri, 23 Oct 2020 06:39:35 GMT

[quote user="rcerati"]About the other question, reset seems to have no effect while application firmware is running: with reset button is not possible to enter in bootloader mode.[/quote]

Sounds like the pinreset is not working then. Please double check that the reset button on your board is connected to P0.18 and also read out UICR.PSELRESET[n] to verify that the register is set. E.g., nrfjprog --memrd 0x10001200.

RE: UART DFU for nRF52833

rcerati — Thu, 22 Oct 2020 15:38:46 GMT

For heart_rate_demo, the smartphone Bluetooth had a problem I suppose, because

I tried

nrfjprog -f NRF52 --chiperase --program ..\..\tools\heart_rate_demo\heart_rate_demo\heart_rate_demo.hex
Parsing hex file.
Erasing user available code and UICR flash areas.
Applying system reset.
Checking that the area to write is not protected.
Programming device.

and it is ok.

About the other question, reset seems to have no effect while application firmware is running: with reset button is not possible to enter in bootloader mode.

Best Regards

RE: UART DFU for nRF52833

Vidar Berg — Thu, 22 Oct 2020 12:25:59 GMT

Please try to erase the chip, then re-program the FW with either the Programmer app in nRF Connect for Desktop, or nrfjprog.

RE: UART DFU for nRF52833

rcerati — Thu, 22 Oct 2020 07:19:40 GMT

There is blinky firmware running: if I press reset button nothing happens, blinky continues to work.

By the way, if I copy heart_rate_demo on the disk of interface MCU, the heart_rate_demo seems not to works because the DK doesn't connect to the smartphone. The demo worked some days ago (see previous message), I'm following the readme instructions.

RE: UART DFU for nRF52833

Vidar Berg — Thu, 22 Oct 2020 06:34:34 GMT

Is the board reset when you press the reset button?

RE: UART DFU for nRF52833

rcerati — Wed, 21 Oct 2020 15:22:55 GMT

Now I'm able to merge MBR, bootloader, application, bootloader settings in a single file for production, and it starts and enter in bootloader mode when I press Button 4 at power-on.

However if I set NRF_BL_DFU_ENTER_METHOD_PINRESET instead of NRF_BL_DFU_ENTER_METHOD_BUTTON I'm not able to enter in bootloader mode (LED 1 and 3 on): the program never enters in bootloader mode with reset button also if I use nrfjprog and nrfutil or Jlink programmer and program the board in "old style" manner.

CONFIG_GPIO_AS_PINRESET is defined in bootloader project and also in application program project.

Which checks can I perform ?

Thanks

RE: UART DFU for nRF52833

Vidar Berg — Wed, 21 Oct 2020 07:39:46 GMT

The bootloader will not be aware of the application if it was programmed directly through the debug interface and will thus as a result fall back to DFU mode. Please read the "Combine application, bootloader and softdevice image - Bootloader setting" section at the end of this post: https://devzone.nordicsemi.com/nordic/short-range-guides/b/software-development-kit/posts/getting-started-with-nordics-secure-dfu-bootloader. It goes through the necessary steps to make the bootloader aware of the app after it has been programmed with the Jlink.

RE: UART DFU for nRF52833

rcerati — Tue, 20 Oct 2020 16:23:05 GMT

Returning on how to load an application program on a board with DFU/bootloader

if I use

nrfutil dfu serial -pkg blinky_pca10100_mbr.zip -p COM6 -b 115200

[####################################] 100%

the bootloader run the application program,

if I download the application program with the jlink debugger from "Segger Embedded Studio" the bootloader is running but doesn't load the application program.

Is it correct ?

Best Regards

RE: UART DFU for nRF52833

Vidar Berg — Tue, 20 Oct 2020 11:26:12 GMT

The flash placement file was copied from the bootloader project. It's generic and used across all configurations. The MBR_PRESENT flag is used in the bootloader configurations that don't include the Softdevice.

RE: UART DFU for nRF52833

rcerati — Tue, 20 Oct 2020 09:22:58 GMT

Is MBR_PRESENT for DFU program or for application program ?

> flash_placement.xml file ... from nRF5 SDK 17.

From which project was flash_placement.xml copied ?

Thanks

RE: UART DFU for nRF52833

Vidar Berg — Mon, 19 Oct 2020 07:45:32 GMT

You can search the project for "MBR_PRESENT" to see where it's used.

[quote user="rcerati"]

FLASH_SIZE=0x7F000

are Bootloader settings and MBR parameter storage sections preserved ?

[/quote]

They are supposed to be preserved, but due to a problem with the way the SES project is set up in SDK 16, the linker will not actually prevent you from letting your code grow into the reserved MBR and bootloader settings page. However, you can easily fix this potential problem by replacing the flash_placement.xml file in your project folder with the one below which I copied from nRF5 SDK 17.

devzone.nordicsemi.com/.../7416.flash_5F00_placement.xml

RE: UART DFU for nRF52833

rcerati — Thu, 15 Oct 2020 16:33:35 GMT

It works, thank you

What is preprocessor definition MBR_PRESENT for ?

I want to go in deep with sections definition:

with

FLASH_START=0x1000

MBR section is preserved

but with

FLASH_SIZE=0x7F000

are Bootloader settings and MBR parameter storage sections preserved ?

RE: UART DFU for nRF52833

Vidar Berg — Wed, 14 Oct 2020 11:05:52 GMT

It should be sufficient to adjust the linker settings as shown below:

RE: UART DFU for nRF52833

rcerati — Wed, 14 Oct 2020 10:41:52 GMT

About point 3,

I want to modify the examples\peripheral\blinky_freertos\pca10100 in order to download it by DFU update:

Which are the needed steps ?

RE: UART DFU for nRF52833

Vidar Berg — Wed, 14 Oct 2020 06:15:49 GMT

1) I've seen reports of this when other non-Jlink serial bridges are being used. Please try the workaround suggested in this thread: https://devzone.nordicsemi.com/f/nordic-q-a/55803/nrfutil-takes-34-seconds-before-starting-dfu

2) The heart_rate_demo.hex is merged with a Softdevice, and the problem with that is that you must specify the Softdevice and Application image separately when you generate the dfu packages (Memory layout). Othwerwise the bootloader will treat the merged softdevice+app image as one application image.

[quote user="rcerati"]When I copy heart_rate_demo on the disk of interface MCU, the heart_rate_demo works fine and the DK connects to the smartphone. [/quote]

Then it's programmed directly through the debug interface and not through the bootloader.

3) Yes, it's required. You can read more about its function here: Master boot record and bootloader.

RE: UART DFU for nRF52833

rcerati — Tue, 13 Oct 2020 17:06:34 GMT

With nrfjprog I've programmed a DFU that uses an UART on P1 pins, and then dowloaded a program

nrfutil dfu serial -pkg blinky_pca10100_mbr.zip -p COM5 -b 115200
[####################################] 100%
Device programmed.

Three questions:

1) PC UART waits 30 seconds before to lower RTS signal and start download, is it correct ?

2) I tried to download heart_rate_demo.hex,

nrfutil dfu serial -pkg heart_rate_demo.zip -p COM5 -b 115200
[####################################] 100%
Device programmed.

but the program seems not work because LED1 and LED3 are lit on the DK (the DK has bootloader mode active).

When I copy heart_rate_demo on the disk of interface MCU, the heart_rate_demo works fine and the DK connects to the smartphone.

What's wrong ?

3) it is not clear for me the use of mbr: is it necessary include it with DFU bootloader ?

Best Regards

RE: UART DFU for nRF52833

Vidar Berg — Thu, 01 Oct 2020 05:15:47 GMT

Glad to hear that it works. It should be sufficient to to change the UART pinout in the bootloader FW to support the external serial bridge.

RE: UART DFU for nRF52833

rcerati — Wed, 30 Sep 2020 15:53:31 GMT

Now interface chip works !

With PCA10100 board connected to PC with a usb cable on j2 connector, I programmed fw with MSD functionality, then I tried to use virtual com with nrfutil but it didn't work.

All changes if I program the board with

nrfjprog -f NRF52 --sectorerase --program NORDIK_SDK_v4\examples\dfu\secure_bootloader\pca10100_uart\ses\Output\Release\Exe\secure_bootloader_uart_mbr_pca10100.hex --reset

Now nrfutil is able to program the chip

nrfutil dfu serial -pkg blinky_pca10100_mbr.zip -p COM6 -b 115200

[####################################] 100%

Device programmed.

I want to perform another test with the PCA10100 board:

move nRF52833 UART on other pins, using pins P1.01/02/03/04, and connect the UART to the PC with an external USB-UART serial bridge.

RE: UART DFU for nRF52833

Vidar Berg — Tue, 29 Sep 2020 07:48:30 GMT

Hi,

Attached below is the Jlink FW for the interface chip. You can drag&drop the file to the "Bootloader" drive when the board is in bootloader mode.

[quote user="rcerati"]I want to avoid conflict on nRF52833 UART pins P0.5/6/7/8.[/quote]

Do you want to use a different USB-UART serial bridge? If not, you can just use the default pins which are connected to the Jlink.

Best regards,

Vidar

Jlink OB FW:

devzone.nordicsemi.com/.../5706.J_2D00_Link-OB_2D00_SAM3U128_2D00_V2_2D00_NordicSemi-170724.bin