<?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 Cryto driver not working in S32K</title>
    <link>https://community.nxp.com/t5/S32K/Cryto-driver-not-working/m-p/2072854#M47409</link>
    <description>&lt;P&gt;&lt;SPAN&gt;HI ,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;One of our BMS customer using S32k344 has the following issue&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;I am using the crypto_1 mcal to do hashing. For some reason, when I run the job, the hash buffer is does not get filled in at all and just stays with whatever was in it before.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 02 Apr 2025 11:47:59 GMT</pubDate>
    <dc:creator>adijoshi</dc:creator>
    <dc:date>2025-04-02T11:47:59Z</dc:date>
    <item>
      <title>Cryto driver not working</title>
      <link>https://community.nxp.com/t5/S32K/Cryto-driver-not-working/m-p/2072854#M47409</link>
      <description>&lt;P&gt;&lt;SPAN&gt;HI ,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;One of our BMS customer using S32k344 has the following issue&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;I am using the crypto_1 mcal to do hashing. For some reason, when I run the job, the hash buffer is does not get filled in at all and just stays with whatever was in it before.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 02 Apr 2025 11:47:59 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Cryto-driver-not-working/m-p/2072854#M47409</guid>
      <dc:creator>adijoshi</dc:creator>
      <dc:date>2025-04-02T11:47:59Z</dc:date>
    </item>
    <item>
      <title>Re: Cryto driver not working</title>
      <link>https://community.nxp.com/t5/S32K/Cryto-driver-not-working/m-p/2072907#M47412</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/198922"&gt;@adijoshi&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is the hash buffer forced to non-cacheable RAM? All data objects used for communication with HSE must be forced to non-cacheable RAM. HSE can't see the cache. Or you can simply turn off the data cache to see if it makes a difference. &lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Lukas&lt;/P&gt;</description>
      <pubDate>Wed, 02 Apr 2025 13:44:20 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Cryto-driver-not-working/m-p/2072907#M47412</guid>
      <dc:creator>lukaszadrapa</dc:creator>
      <dc:date>2025-04-02T13:44:20Z</dc:date>
    </item>
  </channel>
</rss>

