<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.cadence.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Welcome and Introduce - Recent Threads</title><link>https://community.cadence.com/cadence_technology_forums/c-sup/f/c-sup-welcome</link><description>Welcome and Introduce</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 01 Oct 2026 14:37:13 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://community.cadence.com/cadence_technology_forums/c-sup/f/c-sup-welcome" /><item><title>HiFi5 NatureDSP RFFT output scaling issue for different FFT sizes</title><link>https://community.cadence.com/thread/74684?ContentTypeID=0</link><pubDate>Thu, 01 Oct 2026 14:37:13 GMT</pubDate><guid isPermaLink="false">75bcbcf9-38a3-4e2e-b84b-26c8c46a9500:0478eb88-d1f3-4a23-8e6e-82031260b78e</guid><dc:creator>BR202501213237</dc:creator><slash:comments>0</slash:comments><comments>https://community.cadence.com/thread/74684?ContentTypeID=0</comments><wfw:commentRss>https://community.cadence.com/cadence_technology_forums/c-sup/f/c-sup-welcome/74684/hifi5-naturedsp-rfft-output-scaling-issue-for-different-fft-sizes/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p class="PDq2pG_selectionAnchorContainer" dir="auto" data-start="338" data-end="341"&gt;Hi,&lt;span class="PDq2pG_selectionAnchor"&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p dir="auto" data-start="343" data-end="431"&gt;I am working on &lt;strong data-start="359" data-end="402"&gt;standalone RFFT testing on Xtensa HiFi5&lt;/strong&gt; using the NatureDSP library.&lt;/p&gt;
&lt;p dir="auto" data-start="433" data-end="539"&gt;I am testing different FFT sizes and comparing the &lt;code data-start="484" data-end="501"&gt;fft_real32x32()&lt;/code&gt; output against my reference FFT data.&lt;/p&gt;
&lt;p dir="auto" data-start="541" data-end="576"&gt;I am seeing the FFT output matches for &lt;strong data-start="771" data-end="799"&gt;128, 512 and 2048 points&lt;/strong&gt;, but does not match for &lt;strong data-start="824" data-end="851"&gt;64, 256 and 1024 points&lt;/strong&gt;.&lt;/p&gt;
&lt;p class="PDq2pG_selectionAnchorContainer" dir="auto" data-start="1284" data-end="1299"&gt;My question is:&lt;span class="PDq2pG_selectionAnchor"&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p dir="auto" data-start="1301" data-end="1425"&gt;&lt;strong data-start="1301" data-end="1425"&gt;How should I correctly interpret/compensate the RFFT output for different FFT sizes and the returned &lt;code data-start="1404" data-end="1416"&gt;fft_shifts&lt;/code&gt; value?&lt;/strong&gt;&lt;/p&gt;
&lt;p dir="auto" data-start="1427" data-end="1571"&gt;Is there any additional normalization or scaling required when comparing the HiFi5 &lt;code data-start="1510" data-end="1527"&gt;fft_real32x32()&lt;/code&gt; output with a floating-point/reference FFT?&lt;/p&gt;
&lt;p dir="auto" data-start="1573" data-end="1627"&gt;Also, has anyone observed this kind of behavior where:T&lt;span&gt;he FFT output matches for &lt;/span&gt;&lt;strong data-start="771" data-end="799"&gt;128, 512 and 2048 points&lt;/strong&gt;&lt;/p&gt;
&lt;p class="PDq2pG_selectionAnchorContainer" dir="auto" data-start="1735" data-end="1788"&gt;with &lt;code data-start="1740" data-end="1757"&gt;fft_real32x32()&lt;/code&gt; / &lt;code data-start="1760" data-end="1778"&gt;ifft_real32x32()&lt;/code&gt; on HiFi5?&lt;span class="PDq2pG_selectionAnchor"&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p dir="auto" data-start="1790" data-end="1875"&gt;Any guidance on the correct &lt;strong data-start="1818" data-end="1853"&gt;FFT/IFFT scaling interpretation&lt;/strong&gt; would be appreciated.&lt;/p&gt;
&lt;p dir="auto" data-start="1877" data-end="2014"&gt;&lt;strong data-start="1877" data-end="1890"&gt;Platform:&lt;/strong&gt; Xtensa HiFi5&lt;br data-start="1903" data-end="1906" /&gt; &lt;strong data-start="1906" data-end="1918"&gt;Library:&lt;/strong&gt; NatureDSP HiFi5&lt;br data-start="1934" data-end="1937" /&gt; &lt;strong data-start="1937" data-end="1951"&gt;Functions:&lt;/strong&gt; &lt;code data-start="1952" data-end="1969"&gt;fft_real32x32()&lt;/code&gt; / &lt;code data-start="1972" data-end="1990"&gt;ifft_real32x32()&lt;/code&gt;&lt;br data-start="1990" data-end="1993" /&gt; &lt;strong data-start="1993" data-end="2012"&gt;Scaling option:&lt;/strong&gt; 3&lt;/p&gt;
&lt;p dir="auto" data-start="2016" data-end="2023"&gt;Thanks.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Grid Settings</title><link>https://community.cadence.com/thread/66139?ContentTypeID=0</link><pubDate>Tue, 07 Jul 2026 07:17:24 GMT</pubDate><guid isPermaLink="false">75bcbcf9-38a3-4e2e-b84b-26c8c46a9500:2505cb3f-9111-418c-9d01-2bfab4ee44dd</guid><dc:creator>JE202605133419</dc:creator><slash:comments>0</slash:comments><comments>https://community.cadence.com/thread/66139?ContentTypeID=0</comments><wfw:commentRss>https://community.cadence.com/cadence_technology_forums/c-sup/f/c-sup-welcome/66139/grid-settings/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Currently, in my Allegro X, even after changing and applying grid settings for different layers and checking again, the intended settings are not reflected. Only the &amp;quot;All Etch&amp;quot; setting applies to all layers. However, this is changeable other&amp;nbsp;versions such as 17.4.&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:480px;max-width:640px;" src="https://community.cadence.com/resized-image/__size/1280x960/__key/communityserver-discussions-components-files/159/pastedimage1783408457570v1.png" alt=" " /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Welcome to the Community - introduce yourself!</title><link>https://community.cadence.com/thread/64985?ContentTypeID=0</link><pubDate>Tue, 22 Jul 2025 06:49:09 GMT</pubDate><guid isPermaLink="false">75bcbcf9-38a3-4e2e-b84b-26c8c46a9500:1a512c27-4518-4e5e-b3c3-50f8538db637</guid><dc:creator>Renu Vibha</dc:creator><slash:comments>4</slash:comments><comments>https://community.cadence.com/thread/64985?ContentTypeID=0</comments><wfw:commentRss>https://community.cadence.com/cadence_technology_forums/c-sup/f/c-sup-welcome/64985/welcome-to-the-community---introduce-yourself/rss?ContentTypeId=0</wfw:commentRss><description>&lt;p&gt;Welcome to the Cadence Community Forums! We are thrilled to have you here!&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;We want you to know that this community has been created with you in mind to build professional connections, explore new ideas, discover alternative solutions, and stay updated on&amp;nbsp;Cadence&amp;nbsp;products, and much more.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;To kickstart, what better way than introducing yourselves, right? Please feel free to use the questions, we&amp;rsquo;ve provided below (or a style all your own) and tell us a little about yourself!&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Technology Interest/ areas of expertise, and what motivates you to actively participate in our forum discussions?&lt;/li&gt;
&lt;li&gt;What are you hoping to learn from other members?&amp;nbsp;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Once again, a warm welcome and we look forward to your contribution and success stories.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>