Extend the default img_mgr handlers with custom implementation

RE: Extend the default img_mgr handlers with custom implementation

Einar Thorsrud — Fri, 27 Oct 2023 13:55:46 GMT

I see your point, but unfortunately I don't see another way with the current nRF Connect SDK.

RE: Extend the default img_mgr handlers with custom implementation

george232 — Thu, 26 Oct 2023 17:51:04 GMT

Hi Einar, yes, we can remove static, but any modification of the nRF Connect SDK in NCS manifest based projects (like https://github.com/nrfconnect/ncs-example-application) is problematic. This would require either action from Nordic to remove statics of aforementioned functions or to create sdk-nrf fork that requires maintenance and synchronization with upstream repository. I thought that there was yet another solution which I didn't see (like some Kconfig options to make the img_mgmt more flexible).

RE: Extend the default img_mgr handlers with custom implementation

Einar Thorsrud — Mon, 23 Oct 2023 13:16:13 GMT

These functions are static, so you will need to remove static in order to be able to call from your code. I am not able to see any reason why that should cause problems or how these differs from img_mgmt_state_write() img_mgmt_state_read(), but I have not tested myself.