Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
We wish to protect our embedded PSoC1 code against attempts to read the code out of programmed chips and reverse engineer it and copy it to other devices. Can anyone point me to documentation describing the level of code protection and any settings that may be required during device programming in order to ensure that code cannot be read out of programmed PSoC1 devices?