<?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 Anti-Rollback Implementation Options for i.MX6ULZ in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Anti-Rollback-Implementation-Options-for-i-MX6ULZ/m-p/2110699#M237901</link>
    <description>&lt;P&gt;Hi,&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;I'm looking for anti-rollback implementation on i.MX6ulz. My understanding is that I cannot use bootROM for that because it is fixed in silicon and I couldn't find suitable registers I can use to increment versions to compare with. What options do I have?&lt;/P&gt;&lt;P&gt;Key considerations:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Need reliable version tracking mechanism&lt;/LI&gt;&lt;LI&gt;Prevent firmware downgrade&lt;/LI&gt;&lt;LI&gt;Secure method of version comparison&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;While OCOTP Fuse Banks seem promising, they are limited to only 4 version upgrades, which is insufficient for long-term product lifecycle management.&lt;/P&gt;&lt;P&gt;One potential approach could be implementing version checking directly in the bootloader, where the firmware image includes a version identifier that can be compared during the boot process.&lt;/P&gt;&lt;P&gt;Specific questions:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;How can I implement a secure version comparison mechanism?&lt;/LI&gt;&lt;LI&gt;What are the recommended methods for preventing firmware downgrades?&lt;/LI&gt;&lt;LI&gt;Are there any NXP-recommended best practices for version tracking on i.MX6ULZ?&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Any recommendations or best practices would be greatly appreciated.&lt;BR /&gt;&lt;BR /&gt;Thank you.&lt;BR /&gt;Lenny Tochinski&lt;BR /&gt;Amazon&lt;/P&gt;</description>
    <pubDate>Wed, 04 Jun 2025 20:32:19 GMT</pubDate>
    <dc:creator>ltoch</dc:creator>
    <dc:date>2025-06-04T20:32:19Z</dc:date>
    <item>
      <title>Anti-Rollback Implementation Options for i.MX6ULZ</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Anti-Rollback-Implementation-Options-for-i-MX6ULZ/m-p/2110699#M237901</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;I'm looking for anti-rollback implementation on i.MX6ulz. My understanding is that I cannot use bootROM for that because it is fixed in silicon and I couldn't find suitable registers I can use to increment versions to compare with. What options do I have?&lt;/P&gt;&lt;P&gt;Key considerations:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Need reliable version tracking mechanism&lt;/LI&gt;&lt;LI&gt;Prevent firmware downgrade&lt;/LI&gt;&lt;LI&gt;Secure method of version comparison&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;While OCOTP Fuse Banks seem promising, they are limited to only 4 version upgrades, which is insufficient for long-term product lifecycle management.&lt;/P&gt;&lt;P&gt;One potential approach could be implementing version checking directly in the bootloader, where the firmware image includes a version identifier that can be compared during the boot process.&lt;/P&gt;&lt;P&gt;Specific questions:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;How can I implement a secure version comparison mechanism?&lt;/LI&gt;&lt;LI&gt;What are the recommended methods for preventing firmware downgrades?&lt;/LI&gt;&lt;LI&gt;Are there any NXP-recommended best practices for version tracking on i.MX6ULZ?&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Any recommendations or best practices would be greatly appreciated.&lt;BR /&gt;&lt;BR /&gt;Thank you.&lt;BR /&gt;Lenny Tochinski&lt;BR /&gt;Amazon&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 20:32:19 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Anti-Rollback-Implementation-Options-for-i-MX6ULZ/m-p/2110699#M237901</guid>
      <dc:creator>ltoch</dc:creator>
      <dc:date>2025-06-04T20:32:19Z</dc:date>
    </item>
  </channel>
</rss>

