Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

.dat file content from the ZIP packet information

Hi Guys,

I am working on the nrf52840 and using SDK 17.1.0 version.

i am creating the zip file of my application code using "nrfutil pkg generate"

It give .json, .bin and one .dat file.

i want to know the details of the .dat file.

What exact information it passing through nrf app..?

is it storing that information in the flash if yes where i can see those info adn also how can i relate it...?

Regards

R_S

Parents
  • Hello R_S,

    We don't have any good documentation on what the different bytes in the .dat file means, but you can try to generate a packet, and populate the fields differently, and by watching the outcome in the .dat file, you will recognize a few of them. you can also use "nrfutil pkg display pkg.zip.

    You can also look at the implementation of nrfutil on github, as this is probably the closest thing to the documentation that we have. 

    The last way to go about this would be to look at the implementation of the bootloader (SDK\examples\dfu\secure_bootloader\)

    In SDK 17.1.0, there is a function called nrf_dfu_validation_init_cmd_execute() in nrf_dfu_validation.c.

    Is there a particular field you are curious about, or do you plan to edit something? If so, perhaps you are interrested in the "Customizing the init packet" section in the nrfutil documentation on infocenter.

    Best regards,

    Edvin

Reply
  • Hello R_S,

    We don't have any good documentation on what the different bytes in the .dat file means, but you can try to generate a packet, and populate the fields differently, and by watching the outcome in the .dat file, you will recognize a few of them. you can also use "nrfutil pkg display pkg.zip.

    You can also look at the implementation of nrfutil on github, as this is probably the closest thing to the documentation that we have. 

    The last way to go about this would be to look at the implementation of the bootloader (SDK\examples\dfu\secure_bootloader\)

    In SDK 17.1.0, there is a function called nrf_dfu_validation_init_cmd_execute() in nrf_dfu_validation.c.

    Is there a particular field you are curious about, or do you plan to edit something? If so, perhaps you are interrested in the "Customizing the init packet" section in the nrfutil documentation on infocenter.

    Best regards,

    Edvin

Children
No Data
Related