<?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>S32K中的主题 Re: S32K14X CSEC pram data fillling problem</title>
    <link>https://community.nxp.com/t5/S32K/S32K14X-CSEC-pram-data-fillling-problem/m-p/2249231#M54835</link>
    <description>&lt;P&gt;hello, thanks for your&amp;nbsp;response.&lt;/P&gt;&lt;P&gt;in s32RM_rel14, like&amp;nbsp;the picture below。&lt;/P&gt;</description>
    <pubDate>Wed, 26 Nov 2025 09:56:59 GMT</pubDate>
    <dc:creator>1113240626</dc:creator>
    <dc:date>2025-11-26T09:56:59Z</dc:date>
    <item>
      <title>S32K14X CSEC pram data fillling problem</title>
      <link>https://community.nxp.com/t5/S32K/S32K14X-CSEC-pram-data-fillling-problem/m-p/2246257#M54734</link>
      <description>&lt;P&gt;as demo(cesc_keyconfig) say:&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;plaintext = 00112233445566778899aabbccddeeff&lt;BR /&gt;ciphertext = 69c4e0d86a7b0430d8cdb78070b4c55a&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;why data is&amp;nbsp; 32bit reversed when filling in pram ?&lt;/P&gt;&lt;P&gt;link&amp;nbsp;plaintext&amp;nbsp; = 0x00112233 0x44556677&lt;/P&gt;&lt;P&gt;ciphertext=0x69c4e0d8 0x6a7b0430.&lt;/P&gt;&lt;P&gt;Do you have any document to explain this ?&lt;/P&gt;</description>
      <pubDate>Sun, 23 Nov 2025 01:40:12 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K14X-CSEC-pram-data-fillling-problem/m-p/2246257#M54734</guid>
      <dc:creator>1113240626</dc:creator>
      <dc:date>2025-11-23T01:40:12Z</dc:date>
    </item>
    <item>
      <title>回复： S32K14X CSEC pram data fillling problem</title>
      <link>https://community.nxp.com/t5/S32K/S32K14X-CSEC-pram-data-fillling-problem/m-p/2246617#M54738</link>
      <description>&lt;P&gt;Is csec subsystem big endian?&lt;/P&gt;</description>
      <pubDate>Mon, 24 Nov 2025 01:49:35 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K14X-CSEC-pram-data-fillling-problem/m-p/2246617#M54738</guid>
      <dc:creator>1113240626</dc:creator>
      <dc:date>2025-11-24T01:49:35Z</dc:date>
    </item>
    <item>
      <title>回复： S32K14X CSEC pram data fillling problem</title>
      <link>https://community.nxp.com/t5/S32K/S32K14X-CSEC-pram-data-fillling-problem/m-p/2246620#M54739</link>
      <description>&lt;P&gt;I saw PRAM description&amp;nbsp; that the pram interface is Big Endian in s32kRM_r9, and&amp;nbsp;&amp;nbsp;pram interface is Little Endian in s32kRM_r14. what happened? The chip‘s design had been changed？or is s32kRM_r9&amp;nbsp; error?&lt;/P&gt;</description>
      <pubDate>Mon, 24 Nov 2025 01:58:21 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K14X-CSEC-pram-data-fillling-problem/m-p/2246620#M54739</guid>
      <dc:creator>1113240626</dc:creator>
      <dc:date>2025-11-24T01:58:21Z</dc:date>
    </item>
    <item>
      <title>Re: S32K14X CSEC pram data fillling problem</title>
      <link>https://community.nxp.com/t5/S32K/S32K14X-CSEC-pram-data-fillling-problem/m-p/2247998#M54786</link>
      <description>&lt;P&gt;Hi@&lt;SPAN&gt;1113240626&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Senlent_1-1764050023677.png" style="width: 685px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/367082iDECA40B691517E29/image-dimensions/685x320?v=v2" width="685" height="320" role="button" title="Senlent_1-1764050023677.png" alt="Senlent_1-1764050023677.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 25 Nov 2025 05:54:03 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K14X-CSEC-pram-data-fillling-problem/m-p/2247998#M54786</guid>
      <dc:creator>Senlent</dc:creator>
      <dc:date>2025-11-25T05:54:03Z</dc:date>
    </item>
    <item>
      <title>Re: S32K14X CSEC pram data fillling problem</title>
      <link>https://community.nxp.com/t5/S32K/S32K14X-CSEC-pram-data-fillling-problem/m-p/2249231#M54835</link>
      <description>&lt;P&gt;hello, thanks for your&amp;nbsp;response.&lt;/P&gt;&lt;P&gt;in s32RM_rel14, like&amp;nbsp;the picture below。&lt;/P&gt;</description>
      <pubDate>Wed, 26 Nov 2025 09:56:59 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K14X-CSEC-pram-data-fillling-problem/m-p/2249231#M54835</guid>
      <dc:creator>1113240626</dc:creator>
      <dc:date>2025-11-26T09:56:59Z</dc:date>
    </item>
    <item>
      <title>Re: S32K14X CSEC pram data fillling problem</title>
      <link>https://community.nxp.com/t5/S32K/S32K14X-CSEC-pram-data-fillling-problem/m-p/2249943#M54856</link>
      <description>&lt;P&gt;Hi@&lt;SPAN&gt;1113240626&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;You don't need to waste your time on this. &lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;You can check how the API "CSEC_WriteCommandBytes()" fills the PRAM. &lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Senlent_0-1764211862291.png" style="width: 525px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/367472i04E46A6868EDD1CF/image-dimensions/525x572?v=v2" width="525" height="572" role="button" title="Senlent_0-1764211862291.png" alt="Senlent_0-1764211862291.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 27 Nov 2025 02:51:22 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K14X-CSEC-pram-data-fillling-problem/m-p/2249943#M54856</guid>
      <dc:creator>Senlent</dc:creator>
      <dc:date>2025-11-27T02:51:22Z</dc:date>
    </item>
  </channel>
</rss>

