SDK 15 and Mesh 2.0 Generate a DFU file with nrfutil - ValueError

RE: SDK 15 and Mesh 2.0 Generate a DFU file with nrfutil - ValueError

Arij — Fri, 15 Jun 2018 13:44:11 GMT

I opened a new case about this issue

RE: SDK 15 and Mesh 2.0 Generate a DFU file with nrfutil - ValueError

Bjørn Kvaale — Fri, 15 Jun 2018 13:38:12 GMT

iotlight Like I mentioned in the comment above, I would use nrfjprog --reset -s without the Segger ID. That way, if you have multiple dev kits attached to your pc, you will get a popup where you can select the correct ID.

Another tip: make a script to automate all of the steps. I should have done this from the beginning too, but did not.

In general, it is a good idea to connect all of the dev kits to your computer via usb. That way, you can program & power the DKs via USB. You will need to attach both DKs to the computer via USB. That is the reason you are getting the error.

You will need to program both kits via USB with the softdevice, bootloader & application before you can do a DFU over the mesh network.

There is documentation which shows how to install the nrfutil mesh branch. What happens when you enter the command "nrfutil version" in a command prompt?

RE: SDK 15 and Mesh 2.0 Generate a DFU file with nrfutil - ValueError

Bjørn Kvaale — Fri, 15 Jun 2018 13:21:27 GMT

Hi Arij could you please open a new case regarding this.

RE: SDK 15 and Mesh 2.0 Generate a DFU file with nrfutil - ValueError

Arij — Thu, 14 Jun 2018 13:36:45 GMT

I'm facing a problem in step 4 when i need to generate a hex version of device page, i did this :

dfu$ py device_page_generator.py -d nrf52832_xxAA -sd "s132_6.0.0"

and this is the result

Wrote device page for nrf53832_xxAA with the s132_6.0.0 SoftDevice to bin/device_page_nrf52832_xxAA_s132_5.0.0.hex instead of s132 version 6

here is the bin directory

I don't know why it doesn't generate device page with s132 v6.0.0, help please

RE: SDK 15 and Mesh 2.0 Generate a DFU file with nrfutil - ValueError

Bjørn Kvaale — Wed, 13 Jun 2018 10:41:55 GMT

I used gcc armemb. gcc armemb uses the GCC ARM compiler & armcc uses the compiler provided by keil. You need to add the nrfjprog -s command to all of the nrfjprog commands in this quick start guide.

But what I do instead, which I find easier, is to just write the nrfjprog commands without the -s at the back. That way, you should get a popup with a list of all the segger IDs if you have attached multiple DKs. If you only have one connected, the nrfjprog command will run without any errors. Then, you can choose the segger ID that you want to use.

RE: SDK 15 and Mesh 2.0 Generate a DFU file with nrfutil - ValueError

iotlight — Tue, 12 Jun 2018 23:35:54 GMT

I followed the DFU quick start guide using 2 development kits, where one (682630616) is interfaced over the COM port, which is the one we have been using to check out from Step 1 to Step 10. Now I am using the other development kits (682686733) receives the DFU from the first device (682630616) over the mesh. According to the DFU quick start guide, I specified which device to use in which context, add the -s 682686733 option for each call to the nrfjprog command. Therefore, we started to communicate with 682686733 starting Step 5 to Step 9 as below:

Step 5 Erase all chip memory (including UICR) on all devices
nrfjprog --eraseall -s 682686733

Step 6 Flash the SoftDevice on all devices
nrfjprog --program bin/softdevice/s132_nrf52_6.0.0_softdevice.hex --chiperase -s 682686733

Step 7 Flash the serial bootloader on all devices
nrfjprog --program bin/bootloader/gccarmemb/mesh_bootloader_serial_gccarmemb_nrf52832_xxAA.hex -s 682686733

Step 8 Flash the first application on all devices
nrfjprog --program examples\dfu\build\dfu_nrf52832_xxAA_s132_6.0.0_Release\dfu_nrf52832_xxAA_s132_6.0.0.hex -s 682686733

Step 9 Flash the device page on all devices
nrfjprog --program tools/dfu/bin/device_page_nrf52832_xxAA_s132_6.0.0.hex -s 682686733

nrfjprog --reset -s 682686733

Every Step, I got an error:
ERROR: There is no debugger connected to the PC with the given serial number.

Please see below attached screen shoot.

Do we need to connect the other development kit 682686733 to the PC? How can we do it over the mesh or over the air?

According to the DFU quick start guide, I also downloaded the mesh_dfu branch as shown at below screen shoot, but I don't know how to use it.

Please advise. Thanks.

RE: SDK 15 and Mesh 2.0 Generate a DFU file with nrfutil - ValueError

shubhangir — Tue, 12 Jun 2018 18:47:12 GMT

Opened a new case at https://devzone.nordicsemi.com/f/nordic-q-a/35341/issue-doing-dfu-over-ble-mesh-setup-1-target-board-nrf52840-dev-kit-s140-mesh-2-0-1-nrf-sdk-15-0-0

RE: SDK 15 and Mesh 2.0 Generate a DFU file with nrfutil - ValueError

shubhangir — Tue, 12 Jun 2018 16:25:03 GMT

Hi, yes, unfortunately still see the issue. I will open another case to follow up. thank you.

RE: SDK 15 and Mesh 2.0 Generate a DFU file with nrfutil - ValueError

Bjørn Kvaale — Tue, 12 Jun 2018 15:27:33 GMT

Hi Shubhangi, could you please open a new devzone case regarding this issue? Kind Regards, Bjorn

RE: SDK 15 and Mesh 2.0 Generate a DFU file with nrfutil - ValueError

iotlight — Tue, 12 Jun 2018 06:49:35 GMT

Did you apply

"nrfjprog --reset" on step 9?

RE: SDK 15 and Mesh 2.0 Generate a DFU file with nrfutil - ValueError

iotlight — Tue, 12 Jun 2018 06:47:54 GMT

It worked in my other computer now.

I tried both

C:\Nordic_SES\nrf5_SDK_for_Mesh_v2.0.1_src\bin\bootloader\gccarmemb\ mesh_bootloader_serial_gccarmemb_nrf52832_xxAA.hex

And

C:\Nordic_SES\nrf5_SDK_for_Mesh_v2.0.1_src\bin\bootloader\armcc\ mesh_bootloader_serial_armcc_nrf52832_xxAA.hex

What is the difference between gccarmemb and armcc?

Now it works using serial port, but my goal is updating firmware on mesh devices without using any cable connection as stated in the DFU quick start guide.

I tried to use -s <serial number> on another module, but nothing happened. Please specify which steps I should add -s <serial number>.

Please advise. Thanks.

RE: SDK 15 and Mesh 2.0 Generate a DFU file with nrfutil - ValueError

shubhangir — Mon, 11 Jun 2018 19:21:46 GMT

Hello,

Thank you for the help here.

I tried all the steps mentioned in the post, including the change to flash_placement.xml before flashing to the target board, I still see the issue (Failed to establish connection, after sending the DFU start packet).

I’m following the quick start guide for this, using following setup: one target board – nrf52840 dev kit, softdevice – s140_6.0.0 (I verified in the nRF Go studio that this corresponds to ID 0x00A9), bootloader: mesh_bootloader_serial_gccarmemb_nrf52840_xxAA.hex. I built my dfu application using ninja/cmake, having set the device and softdevice to nrf52840/s140 respectively.

Do I need to flash the host board as well, with the same first application? I assumed that since it is just a carrier, as long as it is recognized as a JLINK device, I should be able to run nrfutil on the serial port connected to the host board.

Please advise,

Thanks and regards,

Shubhangi

RE: SDK 15 and Mesh 2.0 Generate a DFU file with nrfutil - ValueError

Bjørn Kvaale — Mon, 11 Jun 2018 12:21:23 GMT

I have two tips: add some prints (i.e. sys.stdout.write("...")) in the bootloader_verify.py script to see where the error is occurring and/or try the whole dfu getting started process again. Most likely there is some small mistake you are making somewhere that is leading to this issue (e.g. running mesh_bootloader_gccarmemb instead of mesh_bootloader_serial_gccarmemb). I have tested this example again with three nrf52832 dev kits & the blinky dfu worked.

I have had one issue with the COM port, so it might also be worthwhile to try a different usb port or try running the python bootloader_verify.py script on another one of your devices.

RE: SDK 15 and Mesh 2.0 Generate a DFU file with nrfutil - ValueError

iotlight — Sun, 10 Jun 2018 06:43:37 GMT

I successfully built file using cmake. Thank you very much.

Yes, I used the bootloader_verify.py file from mesh sdk v2.0.1, please see attached directory folder of bootloader_verify.py

devzone.nordicsemi.com/.../bootloader_5F00_verify.py

When I ran python bootloader_verify.py 682630616 COM3, it was get stuck in

Resetting device..

and didn't go anywhere. The Command Prompt won't accept any command, please see attached screen shoot.

Please advise. Thanks.

RE: SDK 15 and Mesh 2.0 Generate a DFU file with nrfutil - ValueError

Bjørn Kvaale — Fri, 08 Jun 2018 07:53:52 GMT

Have you tried using the bootloader_verify.py file from mesh sdk v2.0.1? Do you still receive the same error then? Did you make sure to run an nrfjprog --reset running the python script? This may help.

Regarding ninja, I believe you can run the command: pip install Ninja or pip install ninja

As far as I am aware though, for your use case, you will not need to use cmake unless you want a different segger project for a different device.

RE: SDK 15 and Mesh 2.0 Generate a DFU file with nrfutil - ValueError

iotlight — Fri, 08 Jun 2018 05:07:03 GMT

I used other blinky example file and Mesh SDK v2.0.1 & softdevice 6, device was programmed and LEDs were ON. Thanks for the advices. But when I verified the bootloader, it was stuck at “Resetting device ..”, please see attached cmd_script devzone.nordicsemi.com/.../cmd_5F00_script_5F00_bootlarder_5F00_verify.txt

which is difference from DFU quick start guide, please see screen shoot.

For Cmake, I created a Build folder using mkdir and still got the same error.

CMake Error: CMake was unable to find a build program corresponding to "Ninja".

devzone.nordicsemi.com/.../cmd_5F00_script_5F00_cmake_5F00_06072018.txt

Please advise. Thanks.

RE: SDK 15 and Mesh 2.0 Generate a DFU file with nrfutil - ValueError

Bjørn Kvaale — Thu, 07 Jun 2018 12:16:09 GMT

1) Update: I have tried to erase the chip, program the softdevice to the nrf52 & then program the blinky hex file that is updated during the dfu process & no LEDs are blinking. Update2: The precompiled blinky hex file works fine. First off, you must program the softdevice before programming the blinky hex file. Secondly, you must reset the board before it starts working (i.e. nrfjprog --reset). I believe the dfu worked fine, only that I was stupid enough not reset the board at the end of the DFU. I will double check this.

2) The serial number is the number on top of the interface MCU on the dev kit. It's the number on the white sticker on the bottom which I believe always is 9 digits long.

3) The only reason I used Mesh SDK v2.0.0 & SD v5 was because you used this setup in your original question. I would recommend you to use the latest SDK & Softdevice. Not sure exactly why I used the v5 softdevice.

4) If you want to use mesh sdk v2.0.1 & softdevice 6, I do not believe you need to use the cmake command to generate a new SES project (I believe this was only the case because the ses dfu mesh bootloader project used softdevice 5 in mesh sdk v2.0.0, whereas we wanted it to use v6 softdevice.)

To answer your question: Yes, I believe you need the .. at the end of the cmake command. The reason it is not working is because you need to make a build folder inside the root folder of the mesh sdk (i.e. where examples, mesh, models & all other folders are located). Then, inside the build folder, you can run the command you posted in your question. If you look at the cmake infocenter doc, you notice that there is a "build$" in front of the cmake command. This will then build an examples folder inside the build folder which does not contain the SES project files (I do not know why this happens). What you will notice though is that the examples inside the root mesh sdk folder do get updated.

5) Here is more info about building the mesh stack. Normally, you can just open a Segger Embedded Studio project & compile to build the mesh stack. You can use cmake if you cannot find a SES project for your device or softdevice version.

Regarding the question about doing a dfu with sdk 15 & mesh sdk v2.0.1 combined, this should be doable. Would you only need to update the application? If you want to do a dfu of all of the nodes in the mesh network, you could use the dfu bootloader from the dfu example in the mesh sdk.

RE: SDK 15 and Mesh 2.0 Generate a DFU file with nrfutil - ValueError

iotlight — Thu, 07 Jun 2018 06:18:00 GMT

Thank you so much for the answer. I ran the DFU example again using the zipped mesh sdk nrf5_SDK_for_Mesh_v2.0.0_src.zip from your last reply and I named it nrf5_SDK_for_Mesh_v2.0.0_src_support. After I made change to the line 32 of flash_placement.xml, the device was successfully program. Please see line 333 of the attached cmd_script_06062018.txt. devzone.nordicsemi.com/.../cmd_5F00_script_5F00_06062018.txt

Now I have a few more questions:

According to the DFU quick start guide, please see attached screenshot, I supposed to see one user LED start blinking, but I do NOT see any user LED is on or blinking except the LD5 is always ON.
Verifying bootloader with the bootloader_verify.py script
python bootloader_verify.py <serial number> COM3
Please tell me what is <serial number>? I tried 682, NRF52 and nrf52832_xxAAnrf52832_xxAA, all did NOT work. Please see from line 337 to line 356 of the attached cmd_script_06062018.txt above.
I would like to know the reasons you used mesh v2.0.0 and 5.0.0 softdevice instead of mesh v2.0.1 and 6.0.0 softdevice because we are using mesh v2.0.1 and 6.0.0 softdevice for our development. What are the reasons we can NOT use 6.0.0 softdevice?
You suggested to building the mesh stack using cmake (see the subsection "Generating SEGGER Embedded Studio project files). Do you mean below is the only command I need to run in the Command Prompt Window? Do I need to put the two dots “..” at the end?

"cmake -G Ninja -DGENERATE_SES_PROJECTS=ON -DPLATFORM=nrf52832_xxAA -DSOFTDEVICE=s132_6.0.0 .."

I copied the nrf5_SDK_for_Mesh_v2.0.1_src folder to nrf5_SDK_for_Mesh_v2.0.1_src _CMake folder and ran CMake. Please see attached cmd_script_cmake_06062018.txt, I tried with “..” and without “..”, both are NOT working.

devzone.nordicsemi.com/.../cmd_5F00_script_5F00_cmake_5F00_06062018.txt
Please elaborate how to build mesh stack for mesh v2.0.1 and future mesh release. Actually, I need to make DFU to work with SDK 15.0.0 and Mesh v2.0.1 combined together, please advise on how to make it happens.

Thanks.

RE: SDK 15 and Mesh 2.0 Generate a DFU file with nrfutil - ValueError

Bjørn Kvaale — Wed, 06 Jun 2018 08:06:12 GMT

Finally found the answer! Tried the dfu quick start guide using mesh v2.0.0. Used two nrf52832 dev kits & softdevice v5.0.0. I uploaded the blinky hex file located in the bin/blinky/blinky_nrf52832_xxAA_s132_5.0.0.hex. In step 8, I built the segger embedded studio project for the dfu example using the 5.0.0 softdevice (since only the emproject for the 6.0.0 softdevice is available in the mesh sdk). Here is the link to building the mesh stack using cmake (see the subsection "Generating SEGGER Embedded Studio project files).

To make it simpler, I have uploaded the zipped mesh sdk that I used.

devzone.nordicsemi.com/.../nrf5_5F00_SDK_5F00_for_5F00_Mesh_5F00_v2.0.0_5F00_src.zip

The changes you will need to make relate to step 8 in the quick start guide. You will need to make changes to the generated SES project using the v5.0.0 softdevice in the flash_placement.xml file located in examples/dfu/.

The fix for this is relatively simple: In examples/dfu/flash_placement.xml, change line 32 from

After this, follow all of the steps & the dfu should complete without any issues. Hope that helps & sorry for the long time it took in getting this to work!!!

RE: SDK 15 and Mesh 2.0 Generate a DFU file with nrfutil - ValueError

Bjørn Kvaale — Wed, 06 Jun 2018 07:16:08 GMT

I have tried the whole dfu quick start guide again & received this error while trying to do the DFU:

Will talk to the nrfutil developer, ask him to try & get back to you soon.

RE: SDK 15 and Mesh 2.0 Generate a DFU file with nrfutil - ValueError

Bjørn Kvaale — Tue, 05 Jun 2018 08:14:13 GMT

Great! I will let the team know to take a look at the case ASAP.

RE: SDK 15 and Mesh 2.0 Generate a DFU file with nrfutil - ValueError

iotlight — Tue, 05 Jun 2018 04:27:07 GMT

A new issue is open in GitHub

github.com/.../148

RE: SDK 15 and Mesh 2.0 Generate a DFU file with nrfutil - ValueError

Bjørn Kvaale — Mon, 04 Jun 2018 08:48:35 GMT

I believe it might be best if you add a new issue at this github link for nrfutil. They should be quite quick in debugging the issue for you. The mesh developer I have talked to is quite busy & does not have the time currently to debug this issue. If you have found a fix to this problem, could you please update this thread with the solution?

Regarding not being able to upload pictures, we have done a test & found out that it is possible to attach images & files in this thread. Which browser are you using? We tested with Google Chrome & that worked very well.

RE: SDK 15 and Mesh 2.0 Generate a DFU file with nrfutil - ValueError

iotlight — Fri, 01 Jun 2018 15:51:59 GMT

To reply to your suggestions:

"The original issue seems to be an error in the json file. Looks like there is an extra "}" at the end”.
Please specify the name of the json file. If you referred to bootloader_config_default.json which was attached in my last reply, there were two “{“ in the front and two “}” at the end.
is the customer sure that the com port used is the correct com port?
There is only one JLink CDC UART Port (COM46) and please see line 120 of cmd script.txt attached in my last reply “target on COM46”.
(I want to attach my COM port screen shot image here, but I have no problem to attach images and files from my computer for private ticket. Now I converted to public ticket, I cannot attach images and files from my computer for public ticket. Can you help me to convert back to private ticket? We can convert back to public ticket until we have a solution, there is no point to post it public without a solution.)

The SEGGER DFU build had a known issue with the flash_placement.xml file. I would advise the customer to use some of the pre-compiled binaries to test the DFU first."
Please see lines 16 to 19 of the attached cmd script.txt in my last reply
“>nrfutil dfu genpkg --application bin/blinky/blinky_nrf52832_xxAA_s132_6.0.0.hex --company-id 0x00000059 --application-id1 --application-version 2 --key-file private_key.txt --sd-req 0x009D --mesh dfu_test.zip” where bin/blinky/blinky_nrf52832_xxAA_s132_6.0.0.hex was already pre-compiled. If this is not the right file, please specify which step and file name that need to be used.

Please ask your Mesh developer continue working on this until a solution. Thanks

RE: SDK 15 and Mesh 2.0 Generate a DFU file with nrfutil - ValueError

Bjørn Kvaale — Fri, 01 Jun 2018 12:42:36 GMT

I got a few tips from a Mesh developer here at Nordic:

"The original issue seems to be an error in the json file. Looks like there is an extra "}" at the end, maybe.

Next, is the customer sure that the com port used is the correct com port?

The SEGGER DFU build had a known issue with the flash_placement.xml file. I would advise the customer to use some of the pre-compiled binaries to test the DFU first."

But I believe you have fixed the first issue, correct? I also believe you are using the correct com port & I believe you have used the pre-compiled binaries & not your own built hex files.

I am not sure these tips will help all too much, but it's worth giving it a shot!