<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Strings on Bald Engineer</title><link>https://www.baldengineer.com/tag/strings</link><description>Recent content in Strings on Bald Engineer</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 24 Mar 2015 22:18:45 +0000</lastBuildDate><atom:link href="https://www.baldengineer.com/tag/strings/index.xml" rel="self" type="application/rss+xml"/><item><title>The hidden Arduino Macro F() fixes random lock ups</title><link>https://www.baldengineer.com/arduino-f-macro.html</link><pubDate>Wed, 20 Nov 2013 12:25:33 +0000</pubDate><guid isPermaLink="false">https://www.baldengineer.com/?p=1995</guid><description>&lt;p&gt;It&amp;rsquo;s 3am but you are not going to bed until you squash this last bug. You sprinkle Serial.print() statements everywhere you can think of, and then that&amp;rsquo;s when all hell breaks loose:  Your code randomly locks up, the LEDs go crazy, and you&amp;rsquo;ve had it. What&amp;rsquo;s going on?  You&amp;rsquo;ve run out of RAM!&lt;/p&gt;&#10;&lt;p&gt;All of those Serial.print() statements are composed of c-style strings. Which are &amp;ldquo;constant character arrays.&amp;rdquo;  In order for those arrays to work properly, they get loaded into the ATmega&amp;rsquo;s RAM before your code starts running. Which can be a problem because 2,048 bytes of RAM doesn&amp;rsquo;t allow for much.&lt;/p&gt;</description></item></channel></rss>