nRF Connect SDK DFU

[lCannon]

After reviewing the add DFU support to your application guide

 Add DFU support to your application 

i have several questions:

1)What modifications are required for the nRF5340 with an app core and net core?  This example shows using Device Manager to upload a .bin file but that is only one of the app core or net core, not both.  Can Device Manager accept a the generated .zip with the manifest to update both at once?  Could a similar guide be generated for updating both the app and net cores at the same time?  When trying to upload the zip of both, Device Manager shows the hash of both bin files, but when started with confirm only, the state shows VALIDATING… for a while then “Sending the request timed out.”  When using the advanced page, I can manually select the app core and download the bin for it – not the zip.

2)In Device Manger, the read, test, confirm, and erase options do not work.  How can they be activated?

3)The guide said that Device Manager will reset the device after the transfer but watching the debug output on the device, this is not the case.  I need to manually press the advanced button to get the reset command to show then issue it.  Is this correct?

4)I have read about encryption and updating keys but in other places it appears it is not supported to encrypt an image:

 Please add/enable support for encrypted images with MCUBOOT 

Is it correct to say signing is supported but encryption is not?  Is there a step by step guide to generate new encryption keys (or signing keys) and update the MCUboot and app for both the app core and net core?

5)If singing is working correctly, is it still possible for a user to upload an image that is not correctly signed, but that the MCUboot will just not swap to it?

Thank you

[Simon]

lCannon said:

Could this documentation be updated or expanded on and instruction given to use mcumgr in windows?

I don't think the mcumgr commands are any different in Windows than in Linux. The only thing I could think of was the serial port name used with --connstring. However, in the tutorial I added the following note: "Get the development kit’s serial port name (for example, "/dev/ttyACM0"), by running nrfjprog --com" (see Serial DFU -->Testing), which should help you get the serial port name when using both Windows and Linux. 

lCannon said:

Also could the instructions be updated to build with VS Code?

To keep the tutorial concise, short and to the point I just used west. I added the following note in the start:  "The west command is used to build and flash the samples, but if you're not familiar with the command line, you can build and flash the sample using nRF Connect for VS Code instead.". So I added some links that demonstrated how to build and flash usin VS Code.

Does this seem reasonable? Please let me know if not.

Best regards,

Simon

[CW]

Hi Simon,
    I am also encountering this symptom, may I know any progress of the question "Sending the request timed out." ?
    Thank you
Jason

[Simon]

I've asked internally about the progress of this. I will keep you updated.

Best regards,

Simon