Where is the bootloader used by the serial example progect.

RE: Where is the bootloader used by the serial example progect.

Elfving — Fri, 26 Nov 2021 14:48:33 GMT

Hey Leo! Sorry about the late response.

[quote user="Leo Lin"]

Q1- Do you mean that this example does not have a bootloader FW? Only softdevice FW and application FW are needed?

[/quote]

Yes

[quote user="Leo Lin"]

Q2- So I used the "Interactive PyACI script" to send the "Direct Firmware Upgrade Jump To Bootloader" command. The device only reboots, but does not jump to bootloader mode, because this example does not have a bootloader FW? Right?

[/quote]

Yes, I believe so.

[quote user="Leo Lin"]

And the function nrf_mesh_dfu_jump_to_bootloader has been changed so that when I give instructions, the code that jumps to bootloader mode will be executed.

[/quote][quote user="Leo Lin"]

I entered the command, but the device only reboots, but does not enter the bootloader mode.

[/quote]

I see, now you have found a way to reboot the device, which would reboot it to the bootloader if there was one (but still not necessarily the bootloader mode btw, or that depends on what you mean by it).

I think there might be a misunderstanding about the difference between bootloader, bootloader mode, DFU and DFU mode here. The bootloader is responsible for booting and updating the FW. Updating the FW can be done using a DFU. In order for it to do that, the bootloader needs to trigger the DFU mode. "Bootloader mode" is a term that has been mostly used about the DFU mode on the debugger chip on the DK (not the nRF SoC), and sometimes as something synonymous with DFU mode. It might be confusing, but just make sure that you know the difference between the bootloader and the DFU mode.

In order for something to enter DFU mode, it needs to reboot (in order for it to enter bootloader) and then the GPREGISTER needs to be set. This can be done directly, or using the buttonless DFU service or by simply holding Button 4 when powering it up.

For more of a step by step tutorial on how to incorporate Mesh DFU into your map you could see here. (Though I once again want you to be sure that Mesh DFU is what you want, since you don't have to use Mesh DFU even though you are using a Mesh application. )

And btw, are you using the mesh version of nrfutil?

Best regards,

Elfving

RE: Where is the bootloader used by the serial example progect.

Leo Lin — Sun, 21 Nov 2021 10:00:35 GMT

Hi Elfving

Thank you for your reply！

Q1- Do you mean that this example does not have a bootloader FW? Only softdevice FW and application FW are needed?

Like the instructions on the file

===========================================================================================

The following is the actual practice of my Q2 question.

Here I used this example and changed some things.

First I added "nrf_mesh_dfu.c" to the project.

Below is the content of "serial_nrf52832_xxAA_s132_7_2_0.emProject"

And the function nrf_mesh_dfu_jump_to_bootloader has been changed so that when I give instructions, the code that jumps to bootloader mode will be executed.

Because I think that to use the nrfutil tool to update the FW through the serial interface, the nrf52832 module must be in DFU mode. So I tried to let nrf52832 enter the DFU mode.

I entered the command, but the device only reboots, but does not enter the bootloader mode.

Thanks in advance.

Leo.

RE: Where is the bootloader used by the serial example progect.

Elfving — Fri, 19 Nov 2021 14:04:46 GMT

Hey Leo!

You don't have to use a bootloader to use this example, though for the DFU reasons the mesh bootloader can be found in MeshSDK/examples/dfu/. For more info see here.

Best regards,

Elfving