<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.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>bootloader with gcc too large</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/12550/bootloader-with-gcc-too-large</link><description>Hi, 
 in SDK v9, i tried to compile the bootloader example, but: 
 /usr/lib/gcc/arm-none-eabi/5.3.0/../../../../arm-none-eabi/bin/ld: region `FLASH&amp;#39; overflowed by 6944 bytes 
 why does the bootloader need so much stuff in the first place? like scheduler</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 16 Mar 2016 11:21:14 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/12550/bootloader-with-gcc-too-large" /><item><title>RE: bootloader with gcc too large</title><link>https://devzone.nordicsemi.com/thread/47643?ContentTypeID=1</link><pubDate>Wed, 16 Mar 2016 11:21:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5801fe90-67dc-4595-877e-413779ed320d</guid><dc:creator>aep</dc:creator><description>&lt;p&gt;-flto made it small enough for me. (its still not working, so not sure if flto is a good thing to do)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: bootloader with gcc too large</title><link>https://devzone.nordicsemi.com/thread/47641?ContentTypeID=1</link><pubDate>Tue, 15 Mar 2016 17:20:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bf13135b-c57b-4605-ac7a-a7617e5b4f12</guid><dc:creator>Dave_couling</dc:creator><description>&lt;p&gt;It sounds like you are compiling under DEBUG.    You can account for this by offsetting the start of the Bootloader section when you compile under DEBUG.  I set it to 0x32000 when I&amp;#39;m debugging, then to 0x35000 under release.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: bootloader with gcc too large</title><link>https://devzone.nordicsemi.com/thread/47642?ContentTypeID=1</link><pubDate>Tue, 15 Mar 2016 15:31:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5cf26b10-fca7-45da-bfdd-3315acf6a7eb</guid><dc:creator>ioannis</dc:creator><description>&lt;p&gt;It doesn&amp;#39;t fit for me too, try increasing the space allocated for the bootloader in your linker script. origin, length and also in dfu_types.h in libraries/dfu_bootloader
It has been answered before.&lt;/p&gt;
&lt;p&gt;What I think is the cause, is the newer gcc version. 4.9 for example outputs a smaller binary than 5.2. If you don&amp;#39;t want to change the size in the linker, stick with an older version.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: bootloader with gcc too large</title><link>https://devzone.nordicsemi.com/thread/47640?ContentTypeID=1</link><pubDate>Tue, 15 Mar 2016 07:08:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0001646e-6cd4-47c7-8b72-af7b4e54e2b9</guid><dc:creator>RK</dc:creator><description>&lt;p&gt;What optimisation level did you compile it with? I use -Os and it fits in the space allocated, compiled with anything less than that, it doesn&amp;#39;t.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>