<?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: wolfssl on s32k144 in S32K</title>
    <link>https://community.nxp.com/t5/S32K/wolfssl-on-s32k144/m-p/2319009#M56859</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/253255"&gt;@Chandrakant&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;wolfSSL is not supported directly by NXP. Issues such as RSA configuration, build flags, memory model problems, or stack usage errors are outside of NXP’s supported scope.&lt;/P&gt;
&lt;P&gt;For wolfSSL‑specific help, please use:&lt;/P&gt;
&lt;P&gt;wolfSSL Community Support &lt;A href="https://www.wolfssl.com/forums/" target="_blank"&gt;https://www.wolfssl.com/forums/&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Lukas&lt;/P&gt;</description>
    <pubDate>Tue, 17 Feb 2026 12:01:01 GMT</pubDate>
    <dc:creator>lukaszadrapa</dc:creator>
    <dc:date>2026-02-17T12:01:01Z</dc:date>
    <item>
      <title>wolfssl on s32k144</title>
      <link>https://community.nxp.com/t5/S32K/wolfssl-on-s32k144/m-p/2318500#M56825</link>
      <description>&lt;P&gt;Hello team, I am trying to use &lt;STRONG&gt;RSA-2048 based&lt;/STRONG&gt; Signature generation &amp;amp; Verification using wolfssl on s32k144EVB. So I used wolfssl source files from NXP folder found under design studio installation &amp;amp; built it as static library. I have attached the user_settings.h file for which i'm building the application. I'm getting &lt;STRONG&gt;stack smashing error&lt;/STRONG&gt; when generating signature for data. "unsigned char* privKey" is &lt;STRONG&gt;der pkcs1 key 2048bit&lt;/STRONG&gt; , "size_t privKeyLen" is the sizeof privKey byte array is 1218 bytes. Also i've attached the test application source file here. Requesting your help with this issue.&lt;/P&gt;</description>
      <pubDate>Mon, 16 Feb 2026 09:39:11 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/wolfssl-on-s32k144/m-p/2318500#M56825</guid>
      <dc:creator>Chandrakant</dc:creator>
      <dc:date>2026-02-16T09:39:11Z</dc:date>
    </item>
    <item>
      <title>Re: wolfssl on s32k144</title>
      <link>https://community.nxp.com/t5/S32K/wolfssl-on-s32k144/m-p/2319009#M56859</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/253255"&gt;@Chandrakant&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;wolfSSL is not supported directly by NXP. Issues such as RSA configuration, build flags, memory model problems, or stack usage errors are outside of NXP’s supported scope.&lt;/P&gt;
&lt;P&gt;For wolfSSL‑specific help, please use:&lt;/P&gt;
&lt;P&gt;wolfSSL Community Support &lt;A href="https://www.wolfssl.com/forums/" target="_blank"&gt;https://www.wolfssl.com/forums/&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Lukas&lt;/P&gt;</description>
      <pubDate>Tue, 17 Feb 2026 12:01:01 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/wolfssl-on-s32k144/m-p/2319009#M56859</guid>
      <dc:creator>lukaszadrapa</dc:creator>
      <dc:date>2026-02-17T12:01:01Z</dc:date>
    </item>
    <item>
      <title>Re: wolfssl on s32k144</title>
      <link>https://community.nxp.com/t5/S32K/wolfssl-on-s32k144/m-p/2319142#M56866</link>
      <description>OK &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/37795"&gt;@lukaszadrapa&lt;/a&gt;, Thanks will check with wolfssl&lt;BR /&gt;</description>
      <pubDate>Tue, 17 Feb 2026 16:48:13 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/wolfssl-on-s32k144/m-p/2319142#M56866</guid>
      <dc:creator>Chandrakant</dc:creator>
      <dc:date>2026-02-17T16:48:13Z</dc:date>
    </item>
  </channel>
</rss>

