Good point from Valon. If we develop a system using your modules/processors etc and the use your secure encryption to send the update to the client, what stops them making the same hardware by reverse engineering it and then using the encrypted code to programme them with?
Is there something in the encryption of the update files that prevents them being deployed to other hardware that is not ours?
In the past, I have used the processor unique ID but that means I have to track every single ID and who has what and then create a unique installer for each system.
Are we talking about a key that is input to TinyCLR Config as I assume you are talking about giving the client an encrypted file to load with that over the USB port?
We would not need a key if the update was provided via a FLASH disk and handled by the software already on the device. I’ve used that method before with the G400D.