<?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>Programming nRF51822</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/2866/programming-nrf51822</link><description>Good morning,
I have been playing with the EV-Kit and now I want to design my own application. I would like to know if is it necessary to include Segger (J-Link) IC in order to program and debug the nRF51822 device.
What I really need is to find a solution</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 09 Aug 2016 18:04:31 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/2866/programming-nrf51822" /><item><title>RE: Programming nRF51822</title><link>https://devzone.nordicsemi.com/thread/10951?ContentTypeID=1</link><pubDate>Tue, 09 Aug 2016 18:04:31 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6d7e2ca9-0a64-42d5-b7bc-2e6f02b3d605</guid><dc:creator>saiteja</dc:creator><description>&lt;p&gt;plz help : &lt;a href="https://devzone.nordicsemi.com/question/90085/undefined-reference-to-softdevice_handler_initnrf_clock_lf_cfg_t-void-unsigned-short-unsigned-long/"&gt;devzone.nordicsemi.com/.../&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Programming nRF51822</title><link>https://devzone.nordicsemi.com/thread/10948?ContentTypeID=1</link><pubDate>Tue, 09 Aug 2016 18:04:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0e9e92f2-fdc8-482f-9856-103c9896c0cc</guid><dc:creator>saiteja</dc:creator><description>&lt;p&gt;plz help:&lt;a href="https://devzone.nordicsemi.com/question/90085/undefined-reference-to-softdevice_handler_initnrf_clock_lf_cfg_t-void-unsigned-short-unsigned-long/"&gt;devzone.nordicsemi.com/.../&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Programming nRF51822</title><link>https://devzone.nordicsemi.com/thread/10946?ContentTypeID=1</link><pubDate>Tue, 09 Aug 2016 18:03:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8f0599ba-805a-4fb6-a66c-7e0c2319496f</guid><dc:creator>saiteja</dc:creator><description>&lt;p&gt;plz help:&lt;a href="https://devzone.nordicsemi.com/question/90085/undefined-reference-to-softdevice_handler_initnrf_clock_lf_cfg_t-void-unsigned-short-unsigned-long/"&gt;devzone.nordicsemi.com/.../&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Programming nRF51822</title><link>https://devzone.nordicsemi.com/thread/10944?ContentTypeID=1</link><pubDate>Tue, 09 Aug 2016 18:03:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4595a237-6fc4-4746-874e-03d6402eb565</guid><dc:creator>saiteja</dc:creator><description>&lt;p&gt;plz help :&lt;a href="https://devzone.nordicsemi.com/question/90085/undefined-reference-to-softdevice_handler_initnrf_clock_lf_cfg_t-void-unsigned-short-unsigned-long/"&gt;devzone.nordicsemi.com/.../&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Programming nRF51822</title><link>https://devzone.nordicsemi.com/thread/10953?ContentTypeID=1</link><pubDate>Wed, 09 Jul 2014 07:55:02 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1c24ec97-9db7-47d0-b6cc-aab8fefe49b0</guid><dc:creator>Dani</dc:creator><description>&lt;p&gt;As seen in the documentation, DFU/Bootloader is different if it applies via UART or via BLE. It is possible to allow a device be updated both via UART and BLE?
Furthermore, and with relation to the first step, when a device is bare: is it possible to flash it (at least, bootloader and/or Softdevice) without the Segger tool or any other tool, and just flash it via serial port?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Programming nRF51822</title><link>https://devzone.nordicsemi.com/thread/10952?ContentTypeID=1</link><pubDate>Wed, 25 Jun 2014 21:28:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7fe71e30-5247-41d1-a8fc-9b44dc23426d</guid><dc:creator>Mihail</dc:creator><description>&lt;p&gt;You can use bootloader to upload the code via UART (you can check the bootloader project in the sdk, single(dual)_banl_hci) , but without debug possibility. We also experimented with  &lt;a href="http://www.mommosoft.com/blog/2014/01/06/ble-dev-n-with-st-linkv2/"&gt;STM32F3DISCOVERY (ST Link/v2)&lt;/a&gt; like a programmer.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Programming nRF51822</title><link>https://devzone.nordicsemi.com/thread/10950?ContentTypeID=1</link><pubDate>Wed, 25 Jun 2014 11:56:45 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:93980c51-2dd6-4e5d-83c2-097ebba2b537</guid><dc:creator>John</dc:creator><description>&lt;p&gt;Yes, by default the chips come blank from Nordic so an initial programming step is needed. An alternative would be to arrange for them to be pre-programmed by your distributor, but they do charge for that.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Programming nRF51822</title><link>https://devzone.nordicsemi.com/thread/10949?ContentTypeID=1</link><pubDate>Wed, 25 Jun 2014 08:38:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1ce9bc90-a334-41d2-8639-56dc927f45e7</guid><dc:creator>Dani</dc:creator><description>&lt;p&gt;Thank you very much John and Nils.
Furthermore, I have read that SD110-v7 includes the possibility to use OTA also with the SoftDevice. But, I suppose that this can be done once the device is not bear, isn&amp;#39;t it? So, first step is to flash device with the tool John suggested, for instance. Right?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Programming nRF51822</title><link>https://devzone.nordicsemi.com/thread/10947?ContentTypeID=1</link><pubDate>Fri, 20 Jun 2014 17:39:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3a0317cf-2e3d-4de9-adfe-4dd9678b9345</guid><dc:creator>John</dc:creator><description>&lt;p&gt;DFU does work very well for already programmed parts. But Dani may have to deal with bare parts that were just purchased and built onto their design. One solution that I believe our production people are planning to use is something like this:&lt;/p&gt;
&lt;p&gt;&lt;a href="http://www.segger.com/flasher-portable.html"&gt;Segger Flasher&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;I provide them with a hex file containing the stack, DFU bootloader and our application. The load it onto the Segger Flasher and then can program our boards quickly. All it requires is that the proper pins be brought out to someplace on the board that the Segger can connect to. We bring them out to a small header, but you could even use bare pads on the board if you wanted to.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Programming nRF51822</title><link>https://devzone.nordicsemi.com/thread/10945?ContentTypeID=1</link><pubDate>Fri, 20 Jun 2014 12:42:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d6ac772e-c41e-456e-a421-bc2ad618f3da</guid><dc:creator>Nils Minor</dc:creator><description>&lt;p&gt;Hi,
i think the easiest way to copy a new firmware to your applications memory is to use the DFU OTA (Device firmware update over the air) functionality. I would use it for my application because if you use an nrf51822 with BLE then it is the easiest way nordic provides for developers :)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>