<?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>Why is beacon.c in the firmware 0 bytes long?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/5086/why-is-beacon-c-in-the-firmware-0-bytes-long</link><description>When I run the nRF51822_beacon_firmware_1.1.0.msi to install the Nordic beacon firmware, the file &amp;quot;beacon.c&amp;quot; under C:\Nordic Semiconductor\nRF51822 Beacon v1.1.0\Source Code\nrf51_beacon\common\beacon is 0 bytes long. It&amp;#39;s accompanying header file &amp;quot;beacon</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 12 Jan 2015 23:37:01 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/5086/why-is-beacon-c-in-the-firmware-0-bytes-long" /><item><title>RE: Why is beacon.c in the firmware 0 bytes long?</title><link>https://devzone.nordicsemi.com/thread/17891?ContentTypeID=1</link><pubDate>Mon, 12 Jan 2015 23:37:01 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:34f74b5f-a306-480e-972c-425fc2bbe055</guid><dc:creator>EdCubic</dc:creator><description>&lt;p&gt;Upon closer inspection, I see that beacon.h contains only typedefs and no function signatures - so it could be that we don&amp;#39;t need a beacon.c - but it might be better if that file were not included at all in the example. Thanks.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>