About the manifest after packaging in the security boot

[wyang0824]

When I package the firmware with nrfutil v7.12.0 version， I pack with a command like this

nrfutil nrf5sdk-tools pkg generate --hw-version 52  --application app.bin --sd-req 0xA9 --key-file ./private.key --application-version-string "2.0.0"  app.zip

I got the right app.zip，manifest file 

{
    "manifest": {
        "application": {
            "bin_file": "app.bin",
            "dat_file": "app.dat"
        }
    }
}

My question is: In nrfutilV7.12.0, can I get the manifest file with the following content? 

{
    "manifest": {
        "application": {
            "bin_file": "application.bin",
            "dat_file": "application.dat",
            "init_packet_data": {
                "application_version": 4294967295,
                "device_revision": 65535,
                "device_type": 65535,
                "firmware_crc16": 4837,
                "softdevice_req": [
                    65534
                ]
            }
        }
    }
}

[Sigurd]

Hi!

My question is: In nrfutilV7.12.0, can I get the manifest file with the following content? 

If this was created for legacy DFU solution(ie everything pre-nRF5-SDK version 12), then you need to use nrfutil version 0.5.x, see this post:  RE: custom DFU package 

[wyang0824]

We have used the latest version of nrfutil to build a non-rollback, I know that we can get the version information by parsing the protobuf antisequence app.dat, I want to know that Nordic's Android SDK can be parsed with a function similar to nrfutil display app.dat So as to get the version number information?

[Sigurd]

On the PC side you can do this: nrfutil nrf5sdk-tools pkg display app.zip

wyang0824 said:

Nordic's Android SDK

What SDK are you referring to here?

[wyang0824]

this URL

https://github.com/NordicSemiconductor/Android-DFU-Library 

If Android-DFU-Library doesn't integrate tools like nrfutil nrf5sdk-tools pkg display app.zip, I can implement it myself in Android to get nrfutil nrf5sdk-tools pkg generate --hw-version 52 --application app.bin --sd-req 0xA9 -- key-file ./private.key --application-version-string "2.0.0" app.zip the function of the --application-version-string message in the command? By inverting the app.dat

[Sigurd]

I don't see any parsing of the app version, we do parse e.g. sizes in https://github.com/NordicSemiconductor/Android-DFU-Library/blob/main/lib/dfu/src/main/java/no/nordicsemi/android/dfu/internal/ArchiveInputStream.java#L63 , so maybe you can extend that to read the app version.