How to add 'build-id' for nRF Connect SDK

[loquat]

Please tell me How to add 'build-id' for nRF Connect SDK.

I try to
target_link_libraries(app PUBLIC -Wl,--build-id=sha1)
But, not effect.

The MemFault SDK seems to have this functionality built in, but I don't want to use it.

In zephyr system,
It seems that the bindesc subsystem is trying to achieve equivalent functionality.
Is this feature available in the nRF Connect SDK?

[Raoul]

Hi, thanks for waiting!

Unfortunately I haven't found the answer to this yet - I'll try to give you an answer soon.

Best regards,

Raoul

[loquat]

Do you have any new information?

[Raoul]

Hi,

It seems that the bindesc subsystem is trying to achieve equivalent functionality.

Yes, I wasn't aware of this before, but it seems that this has been under development recently:

https://github.com/zephyrproject-rtos/zephyr/pull/54464

I see that a sample has been added: https://github.com/zephyrproject-rtos/zephyr/commit/0a888db62f6a91b909caa1d5bc9b342814ebad0f

Is this feature available in the nRF Connect SDK?

Since Zephyr is the core RTOS in NCS, most zephyr features will work in NCS. We are not familiar with thie bindesc system yet, but I don't see any reason why it wouldn't work.

But I'm not sure if this does exactly what you wanted yet.

There also seems to be something called GNU Build IDs for gcc, which create a hash of the elf file.

Memfault actually has an article on it: https://interrupt.memfault.com/blog/gnu-build-id-for-firmware. Is this what you were referring to? Note that this is not a memfault specific thing - as this overview shows, the memfault build id and the gnu build id are not the same.

It seems that some work was started to integrate this system with Zephyr: https://github.com/zephyrproject-rtos/zephyr/pull/51532

but I believe the developers have decided to adopt bindesc for this "build id" purpose instead:

https://github.com/zephyrproject-rtos/zephyr/pull/63350

WIth the amount of discussion still going on, I'm not sure if you can trust this for production purposes yet. Please be aware that even if it ends up working, it might not be stable yet.

I'm very sorry for not responding earlier! I made a mistake in handling your case.

Best regards,

Raoul

[loquat]

OK.

Do you have any information regarding the following?

-----------------------------------------------------------------------------------------------------------------------
It seems that the HASH value of the image can be obtained using img_mgmt_read_info().
And the same HASH value seems to be included in app_update.bin.
How can I read this HASH value from app_update.bin?
-----------------------------------------------------------------------------------------------------------------------

[Raoul]

Hi,

Assuming you want to read this hash on a pc, you can use

imgtool verify <binary file>

As described in this case: dfu hash not matching calculated hash from a .bin file 

Note that this will be a hash of both the image (build output) + the image header. So if the header changes but the compiled image stays the same, the hash would change. I think that one of the goals with bindesc is to describe the build itself, and only the build. But it seems that that system is still under development.

Best regards,

Raoul

[loquat]

OK.Thanks!!