<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title><![CDATA[wolfSSL - Embedded SSL Library — Xilinx Complie Error]]></title>
		<link>https://www.wolfssl.com/forums/topic1944-xilinx-complie-error.html</link>
		<atom:link href="https://www.wolfssl.com/forums/feed-rss-topic1944.xml" rel="self" type="application/rss+xml" />
		<description><![CDATA[The most recent posts in Xilinx Complie Error.]]></description>
		<lastBuildDate>Thu, 06 Mar 2025 15:31:24 +0000</lastBuildDate>
		<generator>PunBB</generator>
		<item>
			<title><![CDATA[Re: Xilinx Complie Error]]></title>
			<link>https://www.wolfssl.com/forums/post8248.html#p8248</link>
			<description><![CDATA[<p>I am writing here because I have confronted the same problem and I am wondering if you were able to find a solution.</p><p>I am trying to compile wolfSSL from scratch in Vitis 2023.1 for a Standalone OS running on psu_cortexa53_0. I initially faced the &quot;define versal&quot; issue, but I managed to resolve it. However, now I am stuck with this error:</p><p>C:\wolfssl/wolfssl/wolfcrypt/port/xilinx/xil-versal-glue.h:29:10: fatal error: xsecure_mailbox.h: No such file or directory<br />&nbsp; &nbsp;29 | #include &lt;xsecure_mailbox.h&gt;<br />&nbsp; &nbsp; &nbsp; |&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ^~~~~~~~~~~~~~~~~~~<br />compilation terminated.<br />make: *** [src/wolfcrypt/test/subdir.mk:20: src/wolfcrypt/test/test.o] Error 1<br />I have already enabled the xsecure library in the BSP settings, but I still get the same error.. I also tried regenerating the BSP, manually adding include paths.<br />If you found a solution to this issue, I would really appreciate it if you could share how you fixed it.</p>]]></description>
			<author><![CDATA[null@example.com (vusall.novruzov)]]></author>
			<pubDate>Thu, 06 Mar 2025 15:31:24 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post8248.html#p8248</guid>
		</item>
		<item>
			<title><![CDATA[Re: Xilinx Complie Error]]></title>
			<link>https://www.wolfssl.com/forums/post6886.html#p6886</link>
			<description><![CDATA[<p>Eric,</p><p>Thanks for the support. You were correct. It was the lack of &quot;define versal&quot;. This has advanced me to the next error:</p><p>&nbsp; &nbsp; make: *** [src/wolfssl/wolfcrypt/src/port/xilinx/subdir.mk:29: src/wolfssl/wolfcrypt/src/port/xilinx/xil-aesgcm.o] Error 1</p><p>The help files state a similar error could be caused by the failure to include xilmailbox. However, I have done that and when looking at the makefile can see its inclusion as noted below. </p><p>&nbsp; &nbsp; psu_cortexa53_0/libsrc/xilmailbox_v1_2/src/Makefile psu_cortexa53_0/libsrc/xilsecure_v4_3/src/Makefile</p><br /><p>Additionally, I have noted a few other issues. </p><p>1)&nbsp; When using the standalone as the OS and attempt to change the lwip211 setting api_mode from RAW to socket it receive the following error:</p><p>&nbsp; &nbsp; Error occurred while generating bsp sources for the domain &#039;standalone_domain&#039;.<br />&nbsp; &nbsp; Failed to generate the bsp sources for domain.standalone_domain</p><p>&nbsp; &nbsp; Details: ERROR: lwIP with Sockets requires &quot;xilkernel or freertos&quot; OS</p><p>&nbsp; &nbsp; ERROR: [Hsi 55-1545] Problem running tcl command ::sw_lwip211_v1_3::lwip_drc : ERROR: lwIP with Sockets requires&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&quot;xilkernel or freertos&quot; OS<br />&nbsp; &nbsp; while executing<br />&nbsp; &nbsp; &quot;error &quot;ERROR: lwIP with Sockets requires \&quot;xilkernel or freertos\&quot; OS&quot; &quot;&quot; &quot;mdt_error&quot;&quot;<br />&nbsp; &nbsp; (procedure &quot;lwip_sw_drc&quot; line 10)<br />&nbsp; &nbsp; invoked from within<br />&nbsp; &nbsp; &quot;lwip_sw_drc $libhandle $emac_names_list&quot;<br />&nbsp; &nbsp; (procedure &quot;::sw_lwip211_v1_3::lwip_drc&quot; line 82)<br />&nbsp; &nbsp; invoked from within<br />&nbsp; &nbsp; &quot;::sw_lwip211_v1_3::lwip_drc lwip211&quot;</p><p>&nbsp; &nbsp; ERROR: [Hsi 55-1440] Error(s) while running DRCs.</p><p>2) If I switch the OS from standalone to FreeROTS (because standalone is proving so troublesome) the xilmailbox is not provided as a library to include and the build fails because it is missing.</p><p>I have tried to build the wolfssl code as s static library instead of including it in my primary application, but receive similar errors. I am using Vitis 2020.2 as my IDE and there is a lack of help for that specific version, but it seems like I should be able to work around it.</p><p>That said my primary concern is that neither FreeRTOS nor the standalone OS appear to be viable solutions because of errors 1 and 2 noted above, but I have been, perhaps foolishly, trying to get a build of the standalone OS using the api_mode of raw just to see if I could.</p><p>Thanks for sticking with the long post. Thoughts?</p><p>-Hodge</p>]]></description>
			<author><![CDATA[null@example.com (Gamblestein12)]]></author>
			<pubDate>Wed, 21 Dec 2022 13:10:40 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post6886.html#p6886</guid>
		</item>
		<item>
			<title><![CDATA[Re: Xilinx Complie Error]]></title>
			<link>https://www.wolfssl.com/forums/post6881.html#p6881</link>
			<description><![CDATA[<p>Hi Hodge,</p><p>Check out the project instructions from the readme:<br /><a href="https://github.com/wolfSSL/wolfssl/tree/master/IDE/XilinxSDK#steps-for-creating-project-from-scratch">https://github.com/wolfSSL/wolfssl/tree … om-scratch</a></p><p>In particular, confirm that the preprocessor macro &quot;WOLFSSL_USER_SETTINGS&quot; is set, per step 15</p><p>Thanks,<br />Eric</p>]]></description>
			<author><![CDATA[null@example.com (embhorn)]]></author>
			<pubDate>Fri, 16 Dec 2022 17:24:53 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post6881.html#p6881</guid>
		</item>
		<item>
			<title><![CDATA[Re: Xilinx Complie Error]]></title>
			<link>https://www.wolfssl.com/forums/post6880.html#p6880</link>
			<description><![CDATA[<p>Greetings Eric,</p><p>Versal shouldn&#039;t be defined, but just to be certain I undef&#039;ed it. Below is the current configuraiton of User_settings.h.</p><p>/* Xilinx SDK */<br />#define WOLFSSL_XILINX<br />#define WOLFSSL_ARMASM<br />#undef WOLFSSL_XILINX_CRYPT<br />#undef WOLFSSL_XILINX_CRYPT_VERSAL<br />#if defined(versal) &amp;&amp; defined(WOLFSSL_XILINX_CRYPT)<br />#define WOLFSSL_XILINX_CRYPT_VERSAL<br />#endif<br />#ifndef FREERTOS<br />#define SINGLE_THREADED<br />#endif<br />#define NO_FILESYSTEM<br />#define HAVE_UINTPTR_T</p><p>/* Platform - remap printf */<br />#include &quot;xil_printf.h&quot;<br />#define XPRINTF xil_printf</p><p>#if !defined(WOLFSSL_XILINX_CRYPT_VERSAL)<br />/* Enable ARMv8 (Aarch64) assembly speedups - SHA256 / AESGCM */<br />/* Note: Requires CFLAGS=&quot;-mcpu=generic+crypto -mstrict-align&quot; */<br />#define WOLFSSL_ARMASM<br />#endif</p><br /><p>It appears the user_settings.h file is not being utilized by the complier; however, the compile time options appear correct:</p><p>06:16:56 **** Build of configuration Debug for project refdes ****<br />make all <br />&#039;Building file: C:/wolfssl/wolfcrypt/src/port/xilinx/xil-aesgcm.c&#039;<br />&#039;Invoking: ARM v8 gcc compiler&#039;<br />aarch64-none-elf-gcc -DWOLFSSL_USER_SETTINGS -Wall -O0 -g3 -I&quot;C:\reg\test_a53\src&quot; -I&quot;C:\wolfssl&quot; -I&quot;C:\wolfssl\IDE\XilinxSDK&quot; -IC:/Users/g41150/workspace/refdes_platform/export/refdes_platform/sw/refdes_platform/standalone_domain/bspinclude/include -I&quot;C:\Users\g41150\workspace\refdes\src\drv&quot; -c -fmessage-length=0 -MT&quot;src/wolfssl/wolfcrypt/src/port/xilinx/xil-aesgcm.o&quot; -fPIC -mstrict-align -mcpu=generic+crypto -v -MMD -MP -MF&quot;src/wolfssl/wolfcrypt/src/port/xilinx/xil-aesgcm.d&quot; -MT&quot;src/wolfssl/wolfcrypt/src/port/xilinx/xil-aesgcm.o&quot; -o &quot;src/wolfssl/wolfcrypt/src/port/xilinx/xil-aesgcm.o&quot; &quot;C:/wolfssl/wolfcrypt/src/port/xilinx/xil-aesgcm.c&quot;<br />Using built-in specs.<br />COLLECT_GCC=C:\Xilinx\Vitis\2020.2\gnu\aarch64\nt\aarch64-none\bin\\..\x86_64-oesdk-mingw32\usr\bin\aarch64-xilinx-elf\aarch64-xilinx-elf-gcc.exe<br />Target: aarch64-xilinx-elf</p><p>I assume I am doing something foolish, but I don&#039;t know how best to identify what that might be. I appreciate the help.</p><p>-Hodge</p>]]></description>
			<author><![CDATA[null@example.com (Gamblestein12)]]></author>
			<pubDate>Fri, 16 Dec 2022 14:27:22 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post6880.html#p6880</guid>
		</item>
		<item>
			<title><![CDATA[Re: Xilinx Complie Error]]></title>
			<link>https://www.wolfssl.com/forums/post6878.html#p6878</link>
			<description><![CDATA[<p>Hi Hodge,</p><p>Is &quot;versal&quot; defined? Otherwise it looks like &quot;WOLFSSL_ARMASM&quot; is being defined at the end:</p><div class="codebox"><pre><code>#if !defined(WOLFSSL_XILINX_CRYPT_VERSAL)
/* Enable ARMv8 (Aarch64) assembly speedups - SHA256 / AESGCM */
/* Note: Requires CFLAGS=&quot;-mcpu=generic+crypto -mstrict-align&quot; */
#define WOLFSSL_ARMASM
#endif</code></pre></div>]]></description>
			<author><![CDATA[null@example.com (embhorn)]]></author>
			<pubDate>Thu, 15 Dec 2022 14:23:10 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post6878.html#p6878</guid>
		</item>
		<item>
			<title><![CDATA[Re: Xilinx Complie Error]]></title>
			<link>https://www.wolfssl.com/forums/post6875.html#p6875</link>
			<description><![CDATA[<p>Greetings Eric,</p><p>I have toggled the defines both ways in the user_settings.h file. I am editing the file located IDE/XiLinxSDK folder. Perhaps this is the wrong file to edit.</p><p>Here the current contents are:</p><p>/* Xilinx SDK */<br />#define WOLFSSL_XILINX<br />#undef WOLFSSL_ARMASM<br />#define WOLFSSL_XILINX_CRYPT<br />#if defined(versal) &amp;&amp; defined(WOLFSSL_XILINX_CRYPT)<br />#define WOLFSSL_XILINX_CRYPT_VERSAL<br />#endif<br />#ifndef FREERTOS<br />#define SINGLE_THREADED<br />#endif<br />#define NO_FILESYSTEM<br />#define HAVE_UINTPTR_T</p><p>/* Platform - remap printf */<br />#include &quot;xil_printf.h&quot;<br />#define XPRINTF xil_printf</p><p>#if !defined(WOLFSSL_XILINX_CRYPT_VERSAL)<br />/* Enable ARMv8 (Aarch64) assembly speedups - SHA256 / AESGCM */<br />/* Note: Requires CFLAGS=&quot;-mcpu=generic+crypto -mstrict-align&quot; */<br />#define WOLFSSL_ARMASM<br />#endif</p><p>Thanks,<br />Hodge</p>]]></description>
			<author><![CDATA[null@example.com (Gamblestein12)]]></author>
			<pubDate>Wed, 14 Dec 2022 23:22:12 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post6875.html#p6875</guid>
		</item>
		<item>
			<title><![CDATA[Re: Xilinx Complie Error]]></title>
			<link>https://www.wolfssl.com/forums/post6867.html#p6867</link>
			<description><![CDATA[<p>Hello Hodge,</p><p>Thanks for joining the wolfSSL Forums. In your configuration, please ensure that either WOLFSSL_ARMASM or WOLFSSL_XILINX_CRYPT is defined, but not both. </p><p>Thanks,<br />Eric - wolfSSL Support</p>]]></description>
			<author><![CDATA[null@example.com (embhorn)]]></author>
			<pubDate>Tue, 13 Dec 2022 17:53:00 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post6867.html#p6867</guid>
		</item>
		<item>
			<title><![CDATA[Xilinx Complie Error]]></title>
			<link>https://www.wolfssl.com/forums/post6866.html#p6866</link>
			<description><![CDATA[<p>Greetings,</p><p>I am attempting to compile WolfSSL within the Xilinx Vitis IDE for execution on a Xilinx board. I have followed the steps in the README under the IDE/XilinxSDK folder; however, at compile time I receive the following error.</p><p>&quot;#Error can not use both ARMv8 and instructions and XILINX hardened crypto&quot;</p><p>I have attempted to modify the user_settings.h defines to resolve this error, but have been unsuccessful.</p><p>Thanks,<br />Hodge</p>]]></description>
			<author><![CDATA[null@example.com (Gamblestein12)]]></author>
			<pubDate>Tue, 13 Dec 2022 17:36:35 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post6866.html#p6866</guid>
		</item>
	</channel>
</rss>
