<?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 Re: How to access the i.MX6 unique ID/serial number in Linux in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/How-to-access-the-i-MX6-unique-ID-serial-number-in-Linux/m-p/622148#M94342</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the answer!&lt;/P&gt;&lt;P&gt;As a result of finding a solution to this problem, the following thought arose.&lt;BR /&gt;At the stage of loading in &lt;STRONG&gt;U-Boot&lt;/STRONG&gt;, you can read the "&lt;STRONG&gt;unique&amp;nbsp;ID&lt;/STRONG&gt;" (addr. 0x021bc410, 0x021bc420 ) with the "md" command, and then put the result as a parameter in the &lt;STRONG&gt;*.dts&lt;/STRONG&gt; file. After loading Linux, parameters from the &lt;STRONG&gt;*.dts&lt;/STRONG&gt; file can be read from the path /sys/bus/soc/devices/soc0 /&lt;EM&gt;parameters&lt;/EM&gt;, where they are stored as files.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 27 Jun 2019 08:12:31 GMT</pubDate>
    <dc:creator>titggtu</dc:creator>
    <dc:date>2019-06-27T08:12:31Z</dc:date>
    <item>
      <title>How to access the i.MX6 unique ID/serial number in Linux</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/How-to-access-the-i-MX6-unique-ID-serial-number-in-Linux/m-p/622143#M94337</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am working with the 4.1.15 bsp release 1.1.1 for the i.MX6. &amp;nbsp;I am trying to obtain the unique ID/serial number that is available in the processor's fuses at address 0x410 and 0x420 in Linux. &amp;nbsp;I realize that I can enable the /sys/fsl_otp interface, but I don't want that exposed in production runtime images because accidental writes could cause the processor to stop functioning correctly. &amp;nbsp;What I would really like is for the /proc/cpuinfo output to populate the Serial line with the unique number from the fuses.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It appears u-boot is capable of passing the serial number off to the Linux kernel through ATAGS, but with the use of device trees now I don't know if this is possible anymore. &amp;nbsp;In u-boot, my board .h file has the "#define&amp;nbsp;CONFIG_SERIAL_TAG" which is supposed to pass off CPU serial information to Linux.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Additionally it would be nice if the revision of the processor (fuse address&amp;nbsp;0x430[19:16]) could also be supported in the /proc/cpuinfo data too.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does anyone have any idea why this doesn't work and how to fix this?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 Sep 2016 15:15:12 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/How-to-access-the-i-MX6-unique-ID-serial-number-in-Linux/m-p/622143#M94337</guid>
      <dc:creator>compmas2</dc:creator>
      <dc:date>2016-09-15T15:15:12Z</dc:date>
    </item>
    <item>
      <title>Re: How to access the i.MX6 unique ID/serial number in Linux</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/How-to-access-the-i-MX6-unique-ID-serial-number-in-Linux/m-p/622144#M94338</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can read these fuses from sysfs:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;# cat /sys/fsl_otp/HW_OCOTP_CFG0&lt;BR /&gt;0xd72d7394&lt;BR /&gt;# cat /sys/fsl_otp/HW_OCOTP_CFG1&lt;BR /&gt;0xf1361d4&lt;BR /&gt;#&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have a great day,&lt;BR /&gt;Victor&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Sep 2016 06:13:28 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/How-to-access-the-i-MX6-unique-ID-serial-number-in-Linux/m-p/622144#M94338</guid>
      <dc:creator>b36401</dc:creator>
      <dc:date>2016-09-16T06:13:28Z</dc:date>
    </item>
    <item>
      <title>Re: How to access the i.MX6 unique ID/serial number in Linux</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/How-to-access-the-i-MX6-unique-ID-serial-number-in-Linux/m-p/622145#M94339</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Victor,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is what I stated in the original post as something I was aware of but that I did not want to expose the fuses in my runtime environment because of the risk of setting fuses which could break functionality or prevent booting. &amp;nbsp;I am mainly looking for if there is a native way to pass the serial number from the bootloader to the Linux kernel so the kernel interfaces for obtaining the CPU serial number work.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Matt&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 19 Sep 2016 13:24:10 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/How-to-access-the-i-MX6-unique-ID-serial-number-in-Linux/m-p/622145#M94339</guid>
      <dc:creator>compmas2</dc:creator>
      <dc:date>2016-09-19T13:24:10Z</dc:date>
    </item>
    <item>
      <title>Re: How to access the i.MX6 unique ID/serial number in Linux</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/How-to-access-the-i-MX6-unique-ID-serial-number-in-Linux/m-p/622146#M94340</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Matthew, did you manage to get access to a unique processor ID from under the Linux kernel?&amp;nbsp; Would you share a solution to this problem?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Jun 2019 07:15:46 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/How-to-access-the-i-MX6-unique-ID-serial-number-in-Linux/m-p/622146#M94340</guid>
      <dc:creator>titggtu</dc:creator>
      <dc:date>2019-06-26T07:15:46Z</dc:date>
    </item>
    <item>
      <title>Re: How to access the i.MX6 unique ID/serial number in Linux</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/How-to-access-the-i-MX6-unique-ID-serial-number-in-Linux/m-p/622147#M94341</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;&lt;P&gt;Alexey, I did not get the processor serial number passing through the kernel working without the &lt;SPAN&gt;fsl_otp&lt;/SPAN&gt; driver enabled.&lt;SPAN style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/SPAN&gt;I ended up implementing my own serial numbering system used by my company for uniqueness.&lt;/P&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Jun 2019 15:18:20 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/How-to-access-the-i-MX6-unique-ID-serial-number-in-Linux/m-p/622147#M94341</guid>
      <dc:creator>compmas2</dc:creator>
      <dc:date>2019-06-26T15:18:20Z</dc:date>
    </item>
    <item>
      <title>Re: How to access the i.MX6 unique ID/serial number in Linux</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/How-to-access-the-i-MX6-unique-ID-serial-number-in-Linux/m-p/622148#M94342</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the answer!&lt;/P&gt;&lt;P&gt;As a result of finding a solution to this problem, the following thought arose.&lt;BR /&gt;At the stage of loading in &lt;STRONG&gt;U-Boot&lt;/STRONG&gt;, you can read the "&lt;STRONG&gt;unique&amp;nbsp;ID&lt;/STRONG&gt;" (addr. 0x021bc410, 0x021bc420 ) with the "md" command, and then put the result as a parameter in the &lt;STRONG&gt;*.dts&lt;/STRONG&gt; file. After loading Linux, parameters from the &lt;STRONG&gt;*.dts&lt;/STRONG&gt; file can be read from the path /sys/bus/soc/devices/soc0 /&lt;EM&gt;parameters&lt;/EM&gt;, where they are stored as files.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Jun 2019 08:12:31 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/How-to-access-the-i-MX6-unique-ID-serial-number-in-Linux/m-p/622148#M94342</guid>
      <dc:creator>titggtu</dc:creator>
      <dc:date>2019-06-27T08:12:31Z</dc:date>
    </item>
  </channel>
</rss>

