<?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: S32G2 OCOPT programming in S32G</title>
    <link>https://community.nxp.com/t5/S32G/S32G2-OCOPT-programming/m-p/1837127#M6449</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/205137"&gt;@Daniel-Aguirre&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;thank you for your quick response. It made me understand the underlying logic.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;How do we map from 0x234 to 0x384? That is, the way going from BOOT_CFG1 to GP6[127:96] ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
    <pubDate>Thu, 28 Mar 2024 08:42:24 GMT</pubDate>
    <dc:creator>Fergani</dc:creator>
    <dc:date>2024-03-28T08:42:24Z</dc:date>
    <item>
      <title>S32G2 OCOPT programming</title>
      <link>https://community.nxp.com/t5/S32G/S32G2-OCOPT-programming/m-p/1836355#M6421</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;We don't have any configuration switch in our hardware to burn the eFUSE configurations. For this reason we want to burn it via software and found OCOTP peripheral module and we are checking if it is right for our hardware since it is a one time operation and cannot be taken back.&lt;/P&gt;&lt;P&gt;Our confusion comes from the register addresses defined in the software;&lt;/P&gt;&lt;P&gt;#define OCOTP_GP6_127_96 0x384U&lt;BR /&gt;#define OCOTP_GP6_159_128 0x388U&lt;BR /&gt;#define OCOTP_GP6_127_96_SHADOW_REGISTER 97U&lt;BR /&gt;#define OCOTP_GP6_159_128_SHADOW_REGISTER 98U&lt;BR /&gt;#define CRC0_EFUSE_ADD 0x2DCU&lt;BR /&gt;#define CRC0_SHADOW_REGISTER 55U&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What does&amp;nbsp;OCOTP_GP6_127_96&amp;nbsp; mean in the register? We want to program the field BOOT_CFG1[31:0] - ADDR=0x234 field. Which shadow register value corresponds to this?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 27 Mar 2024 12:47:09 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/S32G2-OCOPT-programming/m-p/1836355#M6421</guid>
      <dc:creator>Fergani</dc:creator>
      <dc:date>2024-03-27T12:47:09Z</dc:date>
    </item>
    <item>
      <title>Re: S32G2 OCOPT programming</title>
      <link>https://community.nxp.com/t5/S32G/S32G2-OCOPT-programming/m-p/1836549#M6431</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;Below will be some comments on regards of your questions:&lt;/P&gt;
&lt;P&gt;Q1 &amp;gt;&amp;nbsp;&lt;SPAN&gt;What does&amp;nbsp;OCOTP_GP6_127_96&amp;nbsp; mean in the register?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;[NXP]: This is related to the mapping of that specific FUSE address. We can see that under the&amp;nbsp;&lt;EM&gt;S32G2_Fuse_Map_Table.xlsx&lt;/EM&gt; file embedded under the S32G2 RM the following address is provided for GP6[127:96]:&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="DanielAguirre_0-1711554553669.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/270765i3D6156B2CFF60AE0/image-size/medium?v=v2&amp;amp;px=400" role="button" title="DanielAguirre_0-1711554553669.png" alt="DanielAguirre_0-1711554553669.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;For which 0x384 is the address of GP6[127:96].&lt;/P&gt;
&lt;P&gt;Q2 &amp;gt;&amp;nbsp;&lt;SPAN&gt;We want to program the field BOOT_CFG1[31:0] - ADDR=0x234 field. Which shadow register value corresponds to this?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;[NXP]: Seeing the file mentioned before, the address should be the one you are mentioning (0x234). For the shadow register, we understand that the calculation is as follows:&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;Shadow Register = (Address - 0x200) / 4;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;We can verify this by using the registers you are showing:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;EM&gt;&lt;SPAN&gt;GP6_127_96&amp;nbsp;&lt;/SPAN&gt;Shadow Register = (0x384 - 0x200) / 4 = 0x184 / 4 = 0x61 = 97&lt;/EM&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;EM&gt;&lt;SPAN&gt;GP6_159_128 &lt;/SPAN&gt;Shadow Register = (0x388 - 0x200) / 4 = 0x188 / 4 = 0x62 = 98&lt;/EM&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Don't know if this helps.&lt;/P&gt;
&lt;P&gt;Also, as you are mentioning this&amp;nbsp;&lt;SPAN&gt;is a one-time operation and cannot be taken back, for which care should be taken with the configuration being chosen. We can recommend contacting your local NXP FAE/DFAE/representative for confirmation on these settings.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;Please, let us know.&lt;/P&gt;</description>
      <pubDate>Wed, 27 Mar 2024 16:03:13 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/S32G2-OCOPT-programming/m-p/1836549#M6431</guid>
      <dc:creator>Daniel-Aguirre</dc:creator>
      <dc:date>2024-03-27T16:03:13Z</dc:date>
    </item>
    <item>
      <title>Re: S32G2 OCOPT programming</title>
      <link>https://community.nxp.com/t5/S32G/S32G2-OCOPT-programming/m-p/1837127#M6449</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/205137"&gt;@Daniel-Aguirre&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;thank you for your quick response. It made me understand the underlying logic.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;How do we map from 0x234 to 0x384? That is, the way going from BOOT_CFG1 to GP6[127:96] ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Thu, 28 Mar 2024 08:42:24 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/S32G2-OCOPT-programming/m-p/1837127#M6449</guid>
      <dc:creator>Fergani</dc:creator>
      <dc:date>2024-03-28T08:42:24Z</dc:date>
    </item>
    <item>
      <title>Re: S32G2 OCOPT programming</title>
      <link>https://community.nxp.com/t5/S32G/S32G2-OCOPT-programming/m-p/1837951#M6470</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;Thanks for your feedback. We don't seem to understand this last request. Can you help us elaborate more on the following comment:&lt;/P&gt;
&lt;P&gt;"&lt;SPAN&gt;How do we map from 0x234 to 0x384? That is, the way going from BOOT_CFG1 to GP6[127:96] ?&lt;/SPAN&gt;"&lt;/P&gt;
&lt;P&gt;Why are you trying to map BOOT_CF1 to GP6?&lt;/P&gt;
&lt;P&gt;Please, let us know.&lt;/P&gt;</description>
      <pubDate>Fri, 29 Mar 2024 15:24:14 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/S32G2-OCOPT-programming/m-p/1837951#M6470</guid>
      <dc:creator>Daniel-Aguirre</dc:creator>
      <dc:date>2024-03-29T15:24:14Z</dc:date>
    </item>
  </channel>
</rss>

