<?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>No OTA consistency board to board on the same firmware/layout PCBA</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/74328/no-ota-consistency-board-to-board-on-the-same-firmware-layout-pcba</link><description>Hi, 
 Recently, we have ordered PCBAs using nrf52832 to online PCB manufacturers. 
 During a test, we found that some boards can use OTA firmware update, but some are not. We use the same software/softdevice/bootloader, but the results vary from board</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 23 Apr 2021 06:13:52 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/74328/no-ota-consistency-board-to-board-on-the-same-firmware-layout-pcba" /><item><title>RE: No OTA consistency board to board on the same firmware/layout PCBA</title><link>https://devzone.nordicsemi.com/thread/306464?ContentTypeID=1</link><pubDate>Fri, 23 Apr 2021 06:13:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0d395acf-6b0b-42e8-aa9e-d24857b5d174</guid><dc:creator>Chabose</dc:creator><description>&lt;p&gt;Hi Sigurd,&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;I do appreciate the instructions you&amp;#39;ve given.&lt;br /&gt;You literally saved my day.&lt;/p&gt;
&lt;p&gt;As soon as I use debug bootloader, I found I left LED code for nrf52DK in &amp;quot;dfu_observer()&amp;quot; without modification.&lt;br /&gt;And it was stacked on &amp;quot;nrf_gpio_cfg_output()&amp;quot;.&lt;/p&gt;
&lt;p&gt;After removing unnecessary codes, it works perfectly.&lt;br /&gt;I&amp;#39;m now assuming variation between the board is due to a bad reflowing process that some pads are shorted.&lt;/p&gt;
&lt;p&gt;Thank you sooo much.&lt;/p&gt;
&lt;p&gt;Hiroto&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: No OTA consistency board to board on the same firmware/layout PCBA</title><link>https://devzone.nordicsemi.com/thread/306336?ContentTypeID=1</link><pubDate>Thu, 22 Apr 2021 12:53:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fb01a628-e2db-4943-99d0-49ca8fc1dbef</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Looks like the central device was not able to find the device(It should be advertising as &amp;quot;DfuTarg#your number&amp;nbsp;after going into bootloader mode).&lt;/p&gt;
&lt;p&gt;1)&lt;/p&gt;
&lt;p&gt;Are you able to get the nrf_log output from the bootloader, either via UART or Segger RTT viewer as log backend? The _debug prefix projects have logging enabled.&amp;nbsp;So use the&amp;nbsp;pca10040_ble_debug&amp;nbsp;secure_bootloader project. Maybe the log from the nRF52 might reveal something about why it&amp;#39;s failing.&lt;/p&gt;
&lt;p&gt;2) Do you see this issue when testing with different phones as well?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>