<?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/"><channel><title>Serial Wire Debug Port Interface for nRF52832</title><link>/nordic/nordic-blog/b/blog/posts/serial-wire-debug-port-interface-for-nrf52832</link><description>1.1 Description
This documentation describes the use and initialization of the Serial Wire Debug Port (SWDP) interface when writing to or reading from Flash and SRAM of the nRF52832 Rev 1. See http://infocenter.nordicsemi.com/ for more information o</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><item><title>RE: Serial Wire Debug Port Interface for nRF52832</title><link>https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/serial-wire-debug-port-interface-for-nrf52832</link><pubDate>Thu, 07 Feb 2019 17:36:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:01c56e85-8877-441a-a87c-420060b698e5</guid><dc:creator>DanielK_GarminEng</dc:creator><slash:comments>0</slash:comments><description>&lt;p&gt;One of the things I found really confusing in ARM IHI 0031C (the official ARM spec) was the representation of the ACK bits.&amp;nbsp; They&amp;#39;re presented as a number in the reverse order from how you would see them on a scope trace.&amp;nbsp; It is REALLY easy to miss that the ack bits are transmitted LSB first.&lt;/p&gt;&lt;img src="https://devzone.nordicsemi.com/aggbug?PostID=1015&amp;AppID=4&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item><item><title>RE: Serial Wire Debug Port Interface for nRF52832</title><link>https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/serial-wire-debug-port-interface-for-nrf52832</link><pubDate>Wed, 21 Jun 2017 16:13:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:01c56e85-8877-441a-a87c-420060b698e5</guid><dc:creator>daguro</dc:creator><slash:comments>0</slash:comments><description>&lt;p&gt;ARM CMSIS code at &lt;a rel="nofollow" target="_blank" href="https://github.com/ARM-software/CMSIS/releases"&gt;github.com/.../releases&lt;/a&gt;&lt;/p&gt;
&lt;img src="https://devzone.nordicsemi.com/aggbug?PostID=1015&amp;AppID=4&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item><item><title>RE: Serial Wire Debug Port Interface for nRF52832</title><link>https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/serial-wire-debug-port-interface-for-nrf52832</link><pubDate>Sat, 03 Jun 2017 00:19:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:01c56e85-8877-441a-a87c-420060b698e5</guid><dc:creator>RK</dc:creator><slash:comments>0</slash:comments><description>&lt;p&gt;Nice article - rarely does anyone dive into what SWD actually does and how it works.&lt;/p&gt;
&lt;p&gt;For anyone writing their own I always suggest starting with, or at least looking at, the ARM CMSIS-DAP code. That&amp;#39;s designed to implement the whole CMSIS protocol with a USB front end however it does contain the full implementation of a bitbanging SWD driver, which deals with all the timing and turnaround and other details. It&amp;#39;s easy to take that piece out and use it driven by your own code, or use it as a reference.&lt;/p&gt;
&lt;img src="https://devzone.nordicsemi.com/aggbug?PostID=1015&amp;AppID=4&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item></channel></rss>