<?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>nrf51822QFAA   DFU</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/19484/nrf51822qfaa-dfu</link><description>Hi 
 I have worked quite a lot with the nrf51822AC, and some time ago I got the OTA bootloader working in my projects on a custom board. 
 However, now I am trying the same one a board with the nrf51822QFAA (so less RAM), but I do not get the device</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 08 Feb 2017 11:36:01 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/19484/nrf51822qfaa-dfu" /><item><title>RE: nrf51822QFAA   DFU</title><link>https://devzone.nordicsemi.com/thread/75692?ContentTypeID=1</link><pubDate>Wed, 08 Feb 2017 11:36:01 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:07ef2476-d34a-4705-9053-9db94c61eb29</guid><dc:creator>bjorn-spockeli</dc:creator><description>&lt;p&gt;No, you will not be able to fit the UUID of the DFU service &lt;strong&gt;and&lt;/strong&gt; a 16 character name in the 31 byte payload of the  Advertisement package.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf51822QFAA   DFU</title><link>https://devzone.nordicsemi.com/thread/75691?ContentTypeID=1</link><pubDate>Wed, 08 Feb 2017 10:59:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7e214ce3-f8c4-4240-b593-2e627c5bcb74</guid><dc:creator>wim</dc:creator><description>&lt;p&gt;that makes sense, this was my thought as well; so I guess a 16 character name is not feasible&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf51822QFAA   DFU</title><link>https://devzone.nordicsemi.com/thread/75690?ContentTypeID=1</link><pubDate>Tue, 07 Feb 2017 13:40:17 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:893afa25-f4f7-4b18-a78b-1feff74d3e63</guid><dc:creator>bjorn-spockeli</dc:creator><description>&lt;p&gt;@wim: I think is because the advertisement packet is restricted to a payload 31 bytes. The packet already contains the 128bit(16bytes) UUID of the DFU service in additions to some additional bytes so if you set a very long device name, then you will exceed 31 bytes and ble_advdata_set() in dfu_transport_ble.c will return an error which in turn will cause a reset.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf51822QFAA   DFU</title><link>https://devzone.nordicsemi.com/thread/75688?ContentTypeID=1</link><pubDate>Tue, 07 Feb 2017 10:55:02 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ef78ae35-b16d-423e-99f1-b9faf13af655</guid><dc:creator>wim</dc:creator><description>&lt;p&gt;to be honest, I never debugged the bootloader code, just compile and flash, so I am not really sure; what I do know is that it is probably not NRF_SUCCESS, as the reset is explained by the ERROR check;
i just traced it down to the name length: if it is 8 or smaller, all is ok, if it is &amp;gt; 9, I get a reset;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf51822QFAA   DFU</title><link>https://devzone.nordicsemi.com/thread/75689?ContentTypeID=1</link><pubDate>Tue, 07 Feb 2017 10:24:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a2f6d68e-e6cf-4c1b-bd33-40465ef06f83</guid><dc:creator>bjorn-spockeli</dc:creator><description>&lt;p&gt;Yes, that would explain why it did not run properly. Are you able to check if sd_ble_gap_device_name_set() returns NRF_SUCCESS or an error code?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf51822QFAA   DFU</title><link>https://devzone.nordicsemi.com/thread/75687?ContentTypeID=1</link><pubDate>Tue, 07 Feb 2017 09:57:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3c1408a7-7688-4ee2-842f-71e85158e5f4</guid><dc:creator>wim</dc:creator><description>&lt;p&gt;Hi Bjorn,&lt;/p&gt;
&lt;p&gt;I found the issue - my code and memory configurations were ok, but in the JLINKExe command line options I used the wrong device type, so I guess it was written to the wrong position in flash or something; all seems to work now, except for 1 thing: &lt;strong&gt;if I set the device name in the DFU bootloader code (using the sd_ble_gap_device_name_set() function) to a string longer than 8 characters, the bootloader crashes&lt;/strong&gt;; I have been looking for the root cause of that crash, but did not really find it yet; where does this limitation come from? because in my normal application, I use longer names without a problem, and wanted to use more or less the same name if possible&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf51822QFAA   DFU</title><link>https://devzone.nordicsemi.com/thread/75686?ContentTypeID=1</link><pubDate>Mon, 06 Feb 2017 12:44:17 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:438f5eb0-eac8-44b3-a51f-8db83c47614d</guid><dc:creator>bjorn-spockeli</dc:creator><description>&lt;p&gt;Can you post the IRAM1 and IRAM2 sizes and start addresses?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>