<?xml-stylesheet type="text/xsl" href="https://community.element14.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/"><channel><title>Renesas RX65 Envision Kit - part 12: RAM Use with GCC ToolChain</title><link>/technologies/embedded/b/blog/posts/renesas-rx65-envision-kit---part-12-ram-use-with-gcc-toolchain</link><description>Goal: This post tries to explain what objects are placed where in RAM when using the GCC toolchain.It&amp;#39;s intended as self-documentation. When using the LCD, you need large continuous chunks of memory for the frame buffers.Memory is limited on controll</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: Renesas RX65 Envision Kit - part 12: RAM Use with GCC ToolChain</title><link>https://community.element14.com/technologies/embedded/b/blog/posts/renesas-rx65-envision-kit---part-12-ram-use-with-gcc-toolchain</link><pubDate>Sat, 04 Jan 2020 18:46:55 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:f316b0cb-0107-4fbf-8ac4-90527e401893</guid><dc:creator>DAB</dc:creator><slash:comments>0</slash:comments><description>&lt;p&gt;It has been a long time since I did this level of detailed work in assembly language.&lt;/p&gt;&lt;p&gt;Memory mapping was very key in the old days as few of us had a fully populated memory space in which to do our software.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;DAB&lt;/p&gt;&lt;img src="https://community.element14.com/aggbug?PostID=8523&amp;AppID=7&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item><item><title>RE: Renesas RX65 Envision Kit - part 12: RAM Use with GCC ToolChain</title><link>https://community.element14.com/technologies/embedded/b/blog/posts/renesas-rx65-envision-kit---part-12-ram-use-with-gcc-toolchain</link><pubDate>Sat, 04 Jan 2020 10:26:22 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:f316b0cb-0107-4fbf-8ac4-90527e401893</guid><dc:creator>Andrew J</dc:creator><slash:comments>1</slash:comments><description>&lt;p&gt;For the LCD ram buffers, it’s worth bearing in mind that when using emWin, you will want two of these buffers (i.e. 2 x 261,120 bytes) to operate the screen without flickering, depending upon the frequency of changes to the screen your app makes.&amp;nbsp; Without using multi-buffering, I found that the screen was not satisfactorily usable with emWin.&amp;nbsp; See &lt;a class="jive-link-blog-small" href="/products/roadtest/b/blog/posts/renesas-envision-kit-rx65n-roadtest-part-6---getting-the-display-working"&gt;post 7&lt;/a&gt; of my review.&amp;nbsp; The alternative is to time the screen updates yourself based on vsync, something I didn’t try!&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;These are really useful follow up posts, thanks.&lt;/p&gt;&lt;img src="https://community.element14.com/aggbug?PostID=8523&amp;AppID=7&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item><item><title>RE: Renesas RX65 Envision Kit - part 12: RAM Use with GCC ToolChain</title><link>https://community.element14.com/technologies/embedded/b/blog/posts/renesas-rx65-envision-kit---part-12-ram-use-with-gcc-toolchain</link><pubDate>Fri, 03 Jan 2020 19:53:42 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:f316b0cb-0107-4fbf-8ac4-90527e401893</guid><dc:creator>clem57</dc:creator><slash:comments>1</slash:comments><description>&lt;p&gt;&lt;span&gt;[mention:acaf6a9338de4eef8f6717d5561ed01d:e9ed411860ed4f2ba0265705b8793d05]&lt;/span&gt;&amp;nbsp; Curious about code space versus SRAM space. On this processor are they different or the same? i.e. do they share the same bus or use unique bus for each. It seems the Max32650 and maybe the Max32660 use separate buses and therefore separate address space.&lt;/p&gt;&lt;p&gt;Clem&lt;/p&gt;&lt;img src="https://community.element14.com/aggbug?PostID=8523&amp;AppID=7&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item><item><title>RE: Renesas RX65 Envision Kit - part 12: RAM Use with GCC ToolChain</title><link>https://community.element14.com/technologies/embedded/b/blog/posts/renesas-rx65-envision-kit---part-12-ram-use-with-gcc-toolchain</link><pubDate>Fri, 03 Jan 2020 19:01:14 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:f316b0cb-0107-4fbf-8ac4-90527e401893</guid><dc:creator>Jan Cumps</dc:creator><slash:comments>0</slash:comments><description>&lt;p&gt;Eclipse has a reasonable good map viewer too:&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;span&gt;[View:/resized-image/__size/620x316/__key/commentfiles/f7d226abd59f475c9d224a79e3f0ec07-f316b0cb-0107-4fbf-8ac4-90527e401893/8132.contentimage_5F00_205595.png:620:316]&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;You can open it via Window -&amp;gt; Show View -&amp;gt; Other -&amp;gt; Memory usage.&lt;/p&gt;&lt;p&gt;It &amp;#39;ll load the map file of the currently active build configuration.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;A particularly useful view is the areas of the hardware (it seems to know the full layout of the RM65N!), and how the program uses those:&lt;/p&gt;&lt;p&gt;&lt;span&gt;[View:/resized-image/__size/621x538/__key/commentfiles/f7d226abd59f475c9d224a79e3f0ec07-f316b0cb-0107-4fbf-8ac4-90527e401893/5078.contentimage_5F00_205596.png:621:538]&lt;/span&gt;&lt;/p&gt;&lt;img src="https://community.element14.com/aggbug?PostID=8523&amp;AppID=7&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item></channel></rss>