<?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>PCA10040  SEGGER J-Link OB Code Customization</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/25730/pca10040-segger-j-link-ob-code-customization</link><description>Hi, 
 I would like to know if anyone ever tried to alter the SEGGER J-Link OB Code that goes on the ATSAM3U2CA-AU IC (this is the IC that controls de PCA10040). 
 I&amp;#39;m asking because I would like to create a programming central for my devices but I would</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 05 Oct 2017 23:15:11 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/25730/pca10040-segger-j-link-ob-code-customization" /><item><title>RE: PCA10040  SEGGER J-Link OB Code Customization</title><link>https://devzone.nordicsemi.com/thread/101374?ContentTypeID=1</link><pubDate>Thu, 05 Oct 2017 23:15:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:be26b575-a367-426a-a201-07bb090c68f6</guid><dc:creator>Felipe Gabardo</dc:creator><description>&lt;p&gt;Thank you, that variant was what I was looking for.&lt;/p&gt;
&lt;p&gt;Actually the idea of this board is not for mass production, we have those bed of nails for that. It&amp;#39;s a way to make the firmware developers life easier when debugging and programming the board, so they won&amp;#39;t have to keep worrying about conecting a lot of cables to a bunch of peripherals an some of them may be damaged. And the PCB really doesn&amp;#39;t seems that complex. I may have to do a multiplexer to program one by one, I&amp;#39;ll make that test before continue with PCB design. But if a parallel connection with pull-up resistors works that would be awesome.&lt;/p&gt;
&lt;p&gt;Thank you for your response, lot of usefull links.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: PCA10040  SEGGER J-Link OB Code Customization</title><link>https://devzone.nordicsemi.com/thread/101373?ContentTypeID=1</link><pubDate>Thu, 05 Oct 2017 19:36:20 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:eafc7d72-bfc0-4b2c-abdc-79c46ad161ae</guid><dc:creator>endnode</dc:creator><description>&lt;p&gt;As the name suggest SEGGER J-Link OB firmware is product of SEGGER company and it&amp;#39;s closed source (actually it&amp;#39;s one of the biggest products of that company, not surprising they are not giving the source for free;). However there exist MBED variant which has &lt;a href="https://github.com/NordicSemiconductor/CMSIS-DAP/"&gt;open source FW on GitHub&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Side note: doing this yourself looks like a lot of work and unless you are really good and fast embedded developer it will be most probably cheaper and more effective to purchase some of already existing solutions. You are not the first guy solving parallel FW flashing configuration for HW production, see &lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.gs/dita/gs/prod_test_prog.html?cp=1_6"&gt;solutions listed at Nordic Infocenter&lt;/a&gt; and &lt;a href="https://devzone.nordicsemi.com/blogs/search/?query=program+swd"&gt;various blog posts&lt;/a&gt;.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>