DFU with a compressed LZ4 file

RE: DFU with a compressed LZ4 file

Markus Arnoldsson — Tue, 26 Apr 2022 20:19:43 GMT

Do you mean that I can remove the call for this function completely or keep the byte array in here? The byte array depends on everything in the function so in that case nothing can be removed.

RE: DFU with a compressed LZ4 file

Aleksander Nowakowski — Tue, 26 Apr 2022 19:54:36 GMT

I don't think you need any of that. Later in the manager only the byte array is sent. Try commenting out everything that's not relevant to byte array with file content.

RE: DFU with a compressed LZ4 file

Markus Arnoldsson — Tue, 26 Apr 2022 19:06:52 GMT

Hi again, I looked into the manager.start function in Firmware Upgrade Manager which looks as follows:

The line in the for loop calls for fromBytes() function, which I belive is the issue, this looks as follows:

As you can see, many function in here for example getHash() will return error.

How should I go by changing this function in order to not ruin the image information being sent through DFU?

RE: DFU with a compressed LZ4 file

Aleksander Nowakowski — Tue, 26 Apr 2022 16:30:04 GMT

Perhaps you need to modify the library as well. Just follow the rabbit. Just check where it crashes and try work around.

RE: DFU with a compressed LZ4 file

Markus Arnoldsson — Tue, 26 Apr 2022 16:23:39 GMT

Hi again!

Were you able to find a solution of how to implement LZ4 on the bootloader?

RE: DFU with a compressed LZ4 file

Markus Arnoldsson — Fri, 22 Apr 2022 13:24:29 GMT

Hello again. I found the other invalids, I removed all checks except one which I am a little bit confused by, maybe you can help me.

In ImageUpgradeViewmodel there are two invalid checks:

https://github.com/NordicSemiconductor/Android-nRF-Connect-Device-Manager/blob/main/sample/src/main/java/io/runtime/mcumgr/sample/viewmodel/mcumgr/ImageUpgradeViewModel.java

They are both in the upgrade() function, in two different try/catch.

The first one I believe can just be removed by the following:

The second one however has a function call at the bottom: manager.start(images, eraseSettings) which needs a catch for exception. In the catch it gives out "Invalid image file.".

I'm not sure how this check shall be removed, or if it has to do with the bootloader of the MCU (we have not implemented decompression in the bootloader yet).

RE: DFU with a compressed LZ4 file

Aleksander Nowakowski — Fri, 22 Apr 2022 08:06:28 GMT

Remove the check everywhere you need. The ImageUploadFragment uploads a single bin file, while ImageUpgradeFragment is able to perform the complete DFU with validating, uploading one or more files, sending test/confirm commands and reset, using the FirmwareUpgradeManager.

RE: DFU with a compressed LZ4 file

Markus Arnoldsson — Thu, 21 Apr 2022 22:37:46 GMT

Hello I am looking into this solution.

I tried removing check from ImageUploadFragment but still invalid.

Noticed now there is also a ImageUpgradeFragment, should I remove check there aswell? Iif so is there a simple way to do it?

https://github.com/NordicSemiconductor/Android-nRF-Connect-Device-Manager/blob/main/sample/src/main/java/io/runtime/mcumgr/sample/fragment/mcumgr/ImageUpgradeFragment.java

https://github.com/NordicSemiconductor/Android-nRF-Connect-Device-Manager/blob/main/sample/src/main/java/io/runtime/mcumgr/sample/fragment/mcumgr/ImageUploadFragment.java

Appreciate the help 🙂

RE: DFU with a compressed LZ4 file

Markus Arnoldsson — Wed, 20 Apr 2022 14:28:12 GMT

Thanks that would be great!

RE: DFU with a compressed LZ4 file

Aleksander Nowakowski — Tue, 12 Apr 2022 21:05:44 GMT

Hello,

The app is checking few first bytes of the binary and it's expecting to find there a Magic value. If your binary is compressed, encrypted, etc, it will fail and return an error.

I recommend downloading the source code of the app and removing the code with the checks.

RE: DFU with a compressed LZ4 file

Sigurd Hellesvik — Tue, 12 Apr 2022 12:20:28 GMT

Hi Markus,

I will check if/how this can be done using the nRF Device Manager.
Since it is Easter, I might not be able to find more until next week. I will return with more information by end of Thrusday next week.

In the meantime, you could try to use mcumgr to send the image over Bluetooth Low Energy instead?
See the SMP Server Sample for how to use this.

Regards,
Sigurd Hellesvik