How to block FOTA between different nRF SoC families?

[djgj]

Hello,

   I am using NCS 1.9.1 and nRF5340 for our current product development. We also have a product which uses nRF52840. We are using MCUboot, mcumgr and all tools relevant for firmware update from zephyr and NCS world. 

Now i have the following situation which needs some support from Nordic. 

Is there any way to identify which SoC a particular firmware file is targetting? i want to avoid updating nRF53 firmware on nRF52 hardware and viceversa.

Is there any solution either on MCUboot, NCS that can avoid this situation. we are using UPGRADE_ONLY option and so we don't want bricked devices on the field due to accidentally uploading firmware for different SoC.

Thank you,

DJ

[djgj]

i am already changing signing keys for mcuboot and it solves the purpose.
I am interested if there is any other Nordic specific solution in NCS that can block during uploading stage itself. 

[Sigurd Hellesvik]

Hi

No, we do not have any built-in method for finding which nRF chip is used when doing DFU.

I agree that using different signing keys for the chips is a solution.

As an alternative, If you are doing FOTA, you already have Bluetooth Low Energy running, and could maybe have a service from which you can read the nRF chip version from as well.

Regards,
Sigurd Hellesvik