<?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>Flashing firmware on a new chip</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/105693/flashing-firmware-on-a-new-chip</link><description>Suppose I design a PCB where nRF52810 or a similar chip is used for very simple BLE connectivity. My understanding is that as it is fresh from a factory, there is no firmware on it of any sort, so it needs to be programmed before it can be used for anything</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 15 Nov 2023 12:18:33 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/105693/flashing-firmware-on-a-new-chip" /><item><title>RE: Flashing firmware on a new chip</title><link>https://devzone.nordicsemi.com/thread/455743?ContentTypeID=1</link><pubDate>Wed, 15 Nov 2023 12:18:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7a35fd33-4f6a-42b4-975f-0dc48c65c42a</guid><dc:creator>Jared</dc:creator><description>&lt;p&gt;Yes, that sounds right. I would prefer a programming header because it would make it possible to debug your application if something goes wrong after you&amp;#39;ve deployed your device.&lt;/p&gt;
&lt;p&gt;regards&lt;/p&gt;
&lt;p&gt;Jared&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Flashing firmware on a new chip</title><link>https://devzone.nordicsemi.com/thread/455739?ContentTypeID=1</link><pubDate>Wed, 15 Nov 2023 12:03:42 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:dc458dd6-18bd-4908-98b7-4ae9c8a9e41f</guid><dc:creator>rtvd</dc:creator><description>&lt;p&gt;Thank you, Jared.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;I think I understand&amp;nbsp;what can be done. There are two paths: either I provide a programming header on the board which would allow to reprogram the chips after&amp;nbsp;the board is fully assembled, or I use one of the gang programmers which can program the chip before they are soldered onto a board.&lt;/p&gt;
&lt;p&gt;Superb. Thank you very much!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Flashing firmware on a new chip</title><link>https://devzone.nordicsemi.com/thread/455730?ContentTypeID=1</link><pubDate>Wed, 15 Nov 2023 10:20:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f32383b6-a596-422e-bb67-c2d2890ef8ce</guid><dc:creator>Jared</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
[quote user=""]My understanding is that as it is fresh from a factory, there is no firmware on it of any sort, so it needs to be programmed before it can be used for anything.[/quote]
&lt;p&gt;Correct,&lt;/p&gt;
[quote user=""]&lt;ul&gt;&lt;li&gt;I believe I cannot use a single header to program multiple MCUs (the board already has another MCU), so a single programming header is not an option as unlike JTAG SWD does not support daisy-chaining.&lt;/li&gt;
&lt;li&gt;Flashing the nRF chip via JTAG&amp;nbsp;does not appear to be possible either.&lt;/li&gt;
&lt;li&gt;I suppose I could add a dedicated header connected to nRF&amp;#39;s SWD pins just to program that chip. But that seems wrong as I would end up with multiple programming headers on the PCB, which is error-prone and messy.&lt;/li&gt;
&lt;li&gt;Over-the Air updates are - I think - also impossible even though the &lt;a href="https://www.mouser.co.uk/datasheet/2/297/nRF52810_PB_v1.1-1760340.pdf"&gt;datasheet&lt;/a&gt; says it is supported. My reasoning here is that the chip would&amp;nbsp;likely come entirely empty, so it would not have a bootloader for OTA updates.&amp;nbsp;&lt;/li&gt;
&lt;li&gt;It would not be on a dev board either, where a J-Link is already present. Although had it been present, that would still require extra headers, I suppose.&lt;/li&gt;
&lt;li&gt;Perhaps there is a way to source chips pre-programmed with a bootloader enabling OTA updates but it is not clear where would I get that from.&lt;/li&gt;&lt;/ul&gt;[/quote]
&lt;p&gt;Your understanding here is mostly correct, OTA is not possible as the ICs doesn&amp;#39;t come with pre programmed fw that enables it.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I think most of the answers for your questions are summarized in our &lt;a href="https://infocenter.nordicsemi.com/pdf/nwp_027.pdf"&gt;production programming white paper&lt;/a&gt;.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Can you take a look at that and see if that answers your question?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;regards&lt;/p&gt;
&lt;p&gt;Jared&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>