https://community.nxp.com/t5/NFC/SL3S40X1-Read-Protection/m-p/1375191#M9011 <P>When read protect is enabled the IC will only allow this information to be read when in the “secured” state. However, the I²C interface always has this “secured” privilege. Please check this in section 12&nbsp;RF interface/I2C interface arbitration.</P><P>"I2C access to the chip memory is possible regardless if it is in the EPC Gen2 secured<BR />state or not"</P><P>This means that whenever you need to disable the UCODE memory protection you can do this securely by I2C.</P> Mon, 22 Nov 2021 19:12:01 GMT Fabian_R 2021-11-22T19:12:01Z https://community.nxp.com/t5/NFC/SL3S40X1-Read-Protection/m-p/1370010#M8994 <P>Hello,</P><P>I'd like to know what are the SL3S40X1 capabilities for user memory protection. After reading the datasheet, I still have following questions:</P><P>- After activation of the read protection, the user memory cannot be read via: RF, I2C or both?</P><P>- How could this read protection be disabled?</P><P>&nbsp;</P><P>Thanks in advance</P> Thu, 11 Nov 2021 14:42:54 GMT https://community.nxp.com/t5/NFC/SL3S40X1-Read-Protection/m-p/1370010#M8994 MCU_0X55 2021-11-11T14:42:54Z https://community.nxp.com/t5/NFC/SL3S40X1-Read-Protection/m-p/1375191#M9011 <P>When read protect is enabled the IC will only allow this information to be read when in the “secured” state. However, the I²C interface always has this “secured” privilege. Please check this in section 12&nbsp;RF interface/I2C interface arbitration.</P><P>"I2C access to the chip memory is possible regardless if it is in the EPC Gen2 secured<BR />state or not"</P><P>This means that whenever you need to disable the UCODE memory protection you can do this securely by I2C.</P> Mon, 22 Nov 2021 19:12:01 GMT https://community.nxp.com/t5/NFC/SL3S40X1-Read-Protection/m-p/1375191#M9011 Fabian_R 2021-11-22T19:12:01Z