Skip to main content
Arduino

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

5
  • 1
    what is your question? ... you provided a solution to the problem of preventing the copying of flash memory ... the handshake can only be protected by preventing physical access to the windows pc Commented Aug 18, 2021 at 5:46
  • I need to known if this is a good idea and would it work. I have one attempt to get it right. And if anyone has any better solutions. Commented Aug 18, 2021 at 5:51
  • So you are developing your own protection dongle. Well, why don't you simply use a proven product? Commented Aug 18, 2021 at 9:00
  • 2
    Note that setting the lock bits is pointless, while the Arduino bootloader is installed. The bootloader can still read out the program, even with the lock bits set. You'd have to remove the bootloader and upload the code using the ISP interface (ArduinoAsISP). Commented Aug 18, 2021 at 11:43
  • 1
    You could save a GUID in EEPROM that matches one in the compiled file. The sketch reads EEPROM, and compares the saved value, quitting if they don't match. This might require flashing a simple stand-alone sketch that only writes the EEPROM before flashing your main program. It's not skilled hacker-proof, but it would stop the unaltered sketch from running anywhere but the original MCU. Commented Aug 18, 2021 at 21:03