Mesh DFU Example 52840 - No CMD handler

RE: Mesh DFU Example 52840 - No CMD handler

Hung Bui — Thu, 06 Feb 2020 09:43:50 GMT

Armcc is provided by Keil (belong to ARM) and gcc is from gnu.org. It's hard to tell which one is better. But I don't see a big difference in performance or code size.

SES use GCC as the compiler. But it's not a problem if you use the bootloader compiled with armcc and the application compiled with gcc. They are independent binaries.

RE: Mesh DFU Example 52840 - No CMD handler

pkoenig — Wed, 05 Feb 2020 17:10:39 GMT

OK, got it loaded and running. Switched to 832DK, since we will be running on 52832

Still not clear why you put both (gcc and non-gcc) bootloaders in the SDK. I want to push to our SVN just one of those, and selected armcc

Is the ses using gcc compiler, or arm version? And from your experience, which one is better?

So next will be testing of the DFU operation, but first need to do the first mesh, start with serial example ...

Thanks, Piotr

<t: 0>, main.c, 194, ----- Bluetooth Mesh DFU Example -----
<t: 18213>, serial_handler_prov.c, 267, Generating encryption keypair...
<t: 22949>, main.c, 200, Initialization complete!
<t: 27594>, main.c, 221, Enabling serial interface...
<t: 27597>, mesh_app_utils.c, 65, Device UUID (raw): 2DADD3BED4C6C847A870788934617ADD
<t: 27600>, mesh_app_utils.c, 66, Device UUID : BED3AD2D-C6D4-47C8-A870-788934617ADD
<t: 27609>, nrf_mesh_dfu.c, 538, RADIO TX! SLOT 0, count 255, interval: periodic, handle: FFFE
<t: 27614>, nrf_mesh_dfu.c, 576, SERIAL TX!
<t: 27620>, main.c, 229, DFU example started!

RE: Mesh DFU Example 52840 - No CMD handler

Hung Bui — Wed, 05 Feb 2020 16:06:01 GMT

They are the same code, just compiled using different toolchain gccarmemb or armcc. You can use either of them.
The softdevice is the same as in the nRF5 SDK. No difference.

The serial bootloader is the bootloader that support serial interface. This mean this bootloader when running without app (or if the app switch to the bootloader) it can receive data via UART.

The non serial bootloader can be used with serial dfu application and also with non serial dfu application. But when it has to run standalone it can't receive data via UART. When it's used with serial interface

Please follow this guide strictly to test the mesh DFU feature:

https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.meshsdk.v4.0.0/md_doc_libraries_dfu_dfu_quick_start.html?cp=7_2_2_2_3

RE: Mesh DFU Example 52840 - No CMD handler

pkoenig — Wed, 05 Feb 2020 14:54:07 GMT

And following one, the serial bootloader is for the examples using serial, correct?

It wold be serial and dfu with serial. The "nonserial" bootloaders are for all other ones, dfu w/o serial, beacon, etc.

I do not want to get into cmake if possible, prefer to stay within SES, since I have a lot to debug.

RE: Mesh DFU Example 52840 - No CMD handler

pkoenig — Wed, 05 Feb 2020 14:50:54 GMT

Good, some progress...

2 questions:

Which bootloader is "better": gccarmemb or armcc?

Are the softdevices the same as in the sdk16? Why are those duplicated here?

RE: Mesh DFU Example 52840 - No CMD handler

Hung Bui — Wed, 05 Feb 2020 14:38:25 GMT

Hi Piotr,

You would need to flash the bootloader in addition to the DFU application and the device page.

So 4 things need to be flashed:

- softdevice

- bootloader

- dfu application (\examples\dfu)

- device page.

The bootloader binary file can be found at \Mesh_v4.0.0\bin\bootloader

You can compile the bootloader as well, to compile the bootloader you do this on the commandline:

cmake -G Ninja .. -DSDK_ROOT=[path to your nRF5 SDK] -DCMAKE_BUILD_TYPE=MinSizeRel -DBUILD_BOOTLOADER=ON

RE: Mesh DFU Example 52840 - No CMD handler

pkoenig — Wed, 05 Feb 2020 07:55:52 GMT

Questions would be:

at what address the bootloader should be loaded at?

how do you set the UICR value after uploading the bootloader?

RE: Mesh DFU Example 52840 - No CMD handler

pkoenig — Wed, 05 Feb 2020 07:43:32 GMT

Trying to load and execute: dfu_nrf52832_xxAA_s132_7_0_1.emProject

Current steps:

use nrfjprog to load bin/app_green_s132.hex - it loads at address 0x1F000

C:\work\svn\produkte\WIRELESS\mesh\nrf5_SDK_for_Mesh_v4.0.0_src\examples\dfu\bin>nrfjprog --program app_green_s132.hex
Parsing hex file.
Reading flash area to program to guarantee it is erased.
Checking that the area to write is not protected.
Programming device.

C:\work\svn\produkte\WIRELESS\mesh\nrf5_SDK_for_Mesh_v4.0.0_src\examples\dfu\bin>nrfjprog --memrd 0x1eff0 --w 8 --n 0x20
0x0001EFF0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF |................|
0x0001F000: 00 F0 00 20 B1 F5 01 00 D9 F5 01 00 DB F5 01 00 |... ............|

load app through SES - it owerwrites the bootloader. Read back after app load:

C:\work\svn\produkte\WIRELESS\mesh\nrf5_SDK_for_Mesh_v4.0.0_src\examples\dfu\bin>nrfjprog --memrd 0x1eff0 --w 8 --n 0x20
0x0001EFF0: 62 FA A0 68 00 78 C0 F3 80 11 60 68 01 27 90 F8 |b..h.x....`h.'..|
0x0001F000: 4D 20 00 2A 18 BF 00 29 04 D0 6A 79 02 F0 C0 02 |M .*...)..jy....|

RE: Mesh DFU Example 52840 - No CMD handler

pkoenig — Tue, 04 Feb 2020 16:24:20 GMT

Tried to upload bootloader, generated with python script, but this is too small for the bootloader, you call it device page. It looks like below. Is it correct?

Looking for the image for the bootloader for the 52832, I want to use it with dfu example - I would need one with serial I/F for my controller device, and one without UART for the emergency lights.

Piotr

C:\work\svn\produkte\WIRELESS\mesh\nrf5_SDK_for_Mesh_v4.0.0_src\tools\dfu\bin>nrfjprog --program device_page_nrf52832_xxAA_s132_7.0.1.hex
Parsing hex file.
Reading flash area to program to guarantee it is erased.
Checking that the area to write is not protected.
Programming device.

C:\work\svn\produkte\WIRELESS\mesh\nrf5_SDK_for_Mesh_v4.0.0_src\tools\dfu\bin>nrfjprog --memrd 0xfeff0 --w 8 --n 0x80
0x000FEFF0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF |................|
0x000FF000: 04 01 08 08 03 00 12 00 00 70 02 00 00 00 0D 00 |.........p......|
0x000FF010: 03 00 10 00 00 10 00 00 00 70 02 00 03 00 11 00 |.........p......|
0x000FF020: 00 80 0F 00 00 60 00 00 05 00 02 00 CA 00 01 01 |.....`..........|
0x000FF030: 59 00 00 00 01 00 01 00 00 00 FF FF 02 00 04 00 |Y...............|
0x000FF040: FF FF FF FF FF FF FF 7F FF FF FF FF FF FF FF FF |................|
0x000FF050: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF |................|
0x000FF060: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF |................|