<?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 i.MX get microcontroller type in i.MX RT Crossover MCUs</title>
    <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/i-MX-get-microcontroller-type/m-p/1639787#M24798</link>
    <description>&lt;P&gt;Is there any way to determine the microcontroller type, not family or UID, by reading particular register? I would like to separate between i.MX RT1062 and i.MX RT 1064 while being&amp;nbsp;in ROM bootloader using sdphost.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 25 Apr 2023 12:50:59 GMT</pubDate>
    <dc:creator>Litmus1446</dc:creator>
    <dc:date>2023-04-25T12:50:59Z</dc:date>
    <item>
      <title>i.MX get microcontroller type</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/i-MX-get-microcontroller-type/m-p/1639787#M24798</link>
      <description>&lt;P&gt;Is there any way to determine the microcontroller type, not family or UID, by reading particular register? I would like to separate between i.MX RT1062 and i.MX RT 1064 while being&amp;nbsp;in ROM bootloader using sdphost.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 25 Apr 2023 12:50:59 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/i-MX-get-microcontroller-type/m-p/1639787#M24798</guid>
      <dc:creator>Litmus1446</dc:creator>
      <dc:date>2023-04-25T12:50:59Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX get microcontroller type</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/i-MX-get-microcontroller-type/m-p/1640984#M24822</link>
      <description>&lt;P&gt;Dear&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/201484"&gt;@Litmus1446&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;Thanks so much for your patience, the i.MX RT106x don't have a standard register that identify the part.&lt;/P&gt;
&lt;P&gt;but one difference is the 4MB that we have in the internal flash for&amp;nbsp;&lt;SPAN&gt;i.MX RT 1064.&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;Also considering a default XIP memory setup, is to identify if code is being executed at 0x6000_xxxx (&lt;A href="https://www.nxp.com/products/processors-and-microcontrollers/arm-microcontrollers/i-mx-rt-crossover-mcus/i-mx-rt1060-crossover-mcu-with-arm-cortex-m7-core:i.MX-RT1060#richmedia" target="_self"&gt;i.MX RT1060&lt;/A&gt;) or at 0x7000_xxxx (&lt;A href="https://www.nxp.com/products/processors-and-microcontrollers/arm-microcontrollers/i-mx-rt-crossover-mcus/i-mx-rt1064-crossover-mcu-with-arm-cortex-m7-core:i.MX-RT1064#richmedia" target="_self"&gt;i.MX RT1064&lt;/A&gt;).&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;please see this topic for more information&amp;nbsp;&lt;A href="https://community.nxp.com/t5/i-MX-Processors/Device-Identification-Register/m-p/1528156" target="_blank"&gt;Device Identification Register - NXP Community&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;I hope this information help you!&lt;/P&gt;
&lt;P&gt;Kind regards&amp;nbsp;&lt;/P&gt;
&lt;P&gt;-Ramon.&lt;/P&gt;</description>
      <pubDate>Wed, 26 Apr 2023 21:44:13 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/i-MX-get-microcontroller-type/m-p/1640984#M24822</guid>
      <dc:creator>Ramon_Vega</dc:creator>
      <dc:date>2023-04-26T21:44:13Z</dc:date>
    </item>
  </channel>
</rss>

