<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Using Tamper Pin on i.MX7ULP in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Using-Tamper-Pin-on-i-MX7ULP/m-p/2260228#M242830</link>
    <description>&lt;P&gt;I’ve enabled SECVIO in the kernel to handle tamper events using the tamper pin on the i.MX7ULP.&lt;BR /&gt;Do I also need to modify anything in the device tree (DTS) or in U-Boot for proper tamper pin configuration and detection?&lt;BR /&gt;Additionally, is there any accessible example or application demonstrating how to use the tamper handler in userspace?&lt;/P&gt;</description>
    <pubDate>Thu, 11 Dec 2025 12:27:09 GMT</pubDate>
    <dc:creator>stl123</dc:creator>
    <dc:date>2025-12-11T12:27:09Z</dc:date>
    <item>
      <title>Using Tamper Pin on i.MX7ULP</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Using-Tamper-Pin-on-i-MX7ULP/m-p/2260228#M242830</link>
      <description>&lt;P&gt;I’ve enabled SECVIO in the kernel to handle tamper events using the tamper pin on the i.MX7ULP.&lt;BR /&gt;Do I also need to modify anything in the device tree (DTS) or in U-Boot for proper tamper pin configuration and detection?&lt;BR /&gt;Additionally, is there any accessible example or application demonstrating how to use the tamper handler in userspace?&lt;/P&gt;</description>
      <pubDate>Thu, 11 Dec 2025 12:27:09 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Using-Tamper-Pin-on-i-MX7ULP/m-p/2260228#M242830</guid>
      <dc:creator>stl123</dc:creator>
      <dc:date>2025-12-11T12:27:09Z</dc:date>
    </item>
    <item>
      <title>Re: Using Tamper Pin on i.MX7ULP</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Using-Tamper-Pin-on-i-MX7ULP/m-p/2261300#M242856</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;For proper tamper pin configuration and detection on the i.MX7ULP:&lt;BR /&gt;&lt;BR /&gt;1. Device Tree Configuration:&lt;BR /&gt;You don't necessarily need to modify the device tree (DTS) specifically for tamper functionality when SECVIO is already enabled in the kernel. The tamper pins are typically handled by the SNVS (Secure Non-Volatile Storage) module and its driver rather than through standard GPIO configurations in the device tree.&lt;BR /&gt;&lt;BR /&gt;2. U-Boot Configuration:&lt;BR /&gt;If you're planning to use tamper detection in U-Boot as well, you would need to add "CONFIG_IMX_TAMPER=y" to your U-Boot defconfig and rebuild it. This enables the tamper detection functionality in the bootloader.&lt;BR /&gt;&lt;BR /&gt;3. Tamper Handler in Userspace:&lt;BR /&gt;For userspace applications, there isn't a standardized example application specifically for i.MX7ULP. However, you can adapt implementations from similar platforms like i.MX6UL or i.MX7D as the tampering mechanism is fundamentally similar across these platforms.&lt;BR /&gt;&lt;BR /&gt;For implementation guidance, refer to:&lt;BR /&gt;- Section 3.1.4.2 (Tamper Detection) in the i.MX7 Reference Manual&lt;BR /&gt;- Application note "Tampering Application for i.MX7Dsabresd" (AN12210.pdf)&lt;BR /&gt;&lt;BR /&gt;The SECVIO driver in the kernel should handle the tamper events and can be configured to trigger appropriate security measures when tampering is detected. You can monitor these events through the SNVS_LP Status Register (LPSR) and manage them through the SNVS_LP Tamper Detectors Configuration Register (LPTDCR).&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 12 Dec 2025 14:12:01 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Using-Tamper-Pin-on-i-MX7ULP/m-p/2261300#M242856</guid>
      <dc:creator>Bio_TICFSL</dc:creator>
      <dc:date>2025-12-12T14:12:01Z</dc:date>
    </item>
  </channel>
</rss>

