https://devzone.nordicsemi.com/f/nordic-q-a/89050/how-to-block-fota-between-different-nrf-soc-familiesHello, 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 situationen-USTelligent Community 13Fri, 17 Jun 2022 13:52:28 GMThttps://devzone.nordicsemi.com/thread/373064?ContentTypeID=1Fri, 17 Jun 2022 13:52:28 GMT137ad170-7792-4731-bb38-c0d22fbe4515:f0b86827-91a1-4e78-b7f2-218c8111cabcSigurd Hellesvik<p>Hi</p> <p>No, we do not have any built-in method for finding which nRF chip is used when doing DFU.</p> <p>I agree that using different signing keys for the chips is a solution.</p> <p>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.</p> <p>Regards,<br />Sigurd Hellesvik</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/372996?ContentTypeID=1Fri, 17 Jun 2022 11:22:09 GMT137ad170-7792-4731-bb38-c0d22fbe4515:e7bb62cb-20e6-4f03-8652-d12fff4b6277djgj<p>i am already changing signing keys for mcuboot and it solves the purpose. <br />I am interested if there is any other Nordic specific solution in NCS that can block during uploading stage itself.&nbsp;</p><div style="clear:both;"></div>