With the above settings, external read, external write, internal write and debuging interface will be disabled in the project. This will secure the proprietary firmware. Once you program the WO NVL with the correct 32-bit key, the part cannot be programmed further, and becomes an OTP (One Time Programmable) device. It permanently gates off the ability to erase or alter the contents of the latch. Hence OTP should be exercised with extreme caution considering these effects.
- set flash security to "W" for bootloader portion
- set flash security to R for all other, non-bootloader portion
- Debug Select = GPIO, Enable Device Protection = On
- Miniprog3: Enable Chip Lock in the programmer options and program the device
In this case I can program the device multiple times and with miniprog3 I'm not able to read back the flash content (I get xxxxx instead of actual flash values). I'm asking if these "Programming steps" are enough to protect the code from cloning. If that's enough than I would't use WO NVL to lock the device.
Yes, it will secure the proprietary code.