<?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>SPIM deterministic TX timing control</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/23150/spim-deterministic-tx-timing-control</link><description>Hi fellows, 
 I&amp;#39;m trying to control accurate/deterministic timing of the first bit from MOSI PIN of SPIM, employing EasyDMA. 
 According to Figure 69 SPI master with EsayDMA, SPIM block has &amp;quot;TXD+1&amp;quot;.
That would be double buffer for Tx.
So, for accurate</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 03 Jul 2017 08:03:10 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/23150/spim-deterministic-tx-timing-control" /><item><title>RE: SPIM deterministic TX timing control</title><link>https://devzone.nordicsemi.com/thread/91053?ContentTypeID=1</link><pubDate>Mon, 03 Jul 2017 08:03:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5bddbd7b-85d7-49f4-a49f-2aa269a317ae</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;The reason you see this version as the latest in CMSIS pack installer is that we &lt;a href="https://devzone.nordicsemi.com/blogs/880/deprecating-support-for-cmsis-pack-in-nrf5-sdk/"&gt;deprecated support for CMSIS Pack&lt;/a&gt;. You can download the no-pack version of the latest SDK from &lt;a href="https://developer.nordicsemi.com/nRF5_SDK/nRF5_SDK_v13.x.x/nRF5_SDK_13.0.0_04a0bfd.zip"&gt;this page&lt;/a&gt;. You will find all relevant documentation &lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v13.0.0/index.html?cp=4_0_0"&gt;on our infocenter&lt;/a&gt;.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SPIM deterministic TX timing control</title><link>https://devzone.nordicsemi.com/thread/91057?ContentTypeID=1</link><pubDate>Mon, 03 Jul 2017 00:14:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:261e9717-9844-4860-97fe-a8c365e48ec6</guid><dc:creator>kojima</dc:creator><description>&lt;p&gt;Hi Turbo J,&lt;/p&gt;
&lt;p&gt;I got a small progress.&lt;/p&gt;
&lt;p&gt;In my older code, I was setting HFCLK after SoftDevice is enabled.
( I have seen CLOCK-&amp;gt;HFCLKSTAT.SRC is unexpectedly flipped)
Now, I did set HFCLK far before SoftDevice is enabled.
Then, the most of the cause of the jitter disappeared.&lt;/p&gt;
&lt;p&gt;But, still timing jitter is observed on MOSI pin.
When I connect ide debugger ULINK-Pro (but without Periodic Window update disabled), it works fine.
But when I let it run stand-alone, only at the very limited duration, jitter appears.
Very strange...&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SPIM deterministic TX timing control</title><link>https://devzone.nordicsemi.com/thread/91056?ContentTypeID=1</link><pubDate>Mon, 03 Jul 2017 00:00:03 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0687b9ff-474e-47ca-83b2-b1a7090395f7</guid><dc:creator>kojima</dc:creator><description>&lt;p&gt;Hi Jørgen,&lt;/p&gt;
&lt;p&gt;The only reason is ... my MDK-ARM&amp;#39;s pack installer suggests it is the latest somehow.
Even after executing attached Installer for Keil in nRF5 SDK 13.0.0....&lt;/p&gt;
&lt;p&gt;My module mounts Rev.1, not Engineering A/B/C on it.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SPIM deterministic TX timing control</title><link>https://devzone.nordicsemi.com/thread/91055?ContentTypeID=1</link><pubDate>Fri, 30 Jun 2017 10:46:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:64b52125-a9c7-4d4c-954b-91757fb59e6d</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;Why are you using S132_nrf52_2.0.0-7.alpha softdevice? Are you using &lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.nrf52/dita/nrf52/compatibility_matrix/ic_revision_overview.html?cp=2_1_2_0"&gt;Engineering B revision&lt;/a&gt; of nRF52832, where &lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.nrf52/dita/nrf52/compatibility_matrix/ic_rev_sdk_sd_comp_matrix.html?cp=2_1_2_2"&gt;this version is the last one supported&lt;/a&gt;?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SPIM deterministic TX timing control</title><link>https://devzone.nordicsemi.com/thread/91058?ContentTypeID=1</link><pubDate>Fri, 30 Jun 2017 02:40:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f33c3821-ea10-4f24-a0a3-bd78e07beb30</guid><dc:creator>kojima</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I got another fact that my application is runnig under clock control by SoftDevice....
My target device is nRF52832 and is running on the platform S132_nrf52_2.0.0-7.alpha.
My application is a modified one from a sample code of Central-styled UART supplied by Nordic.
At somewhere and/or by some reasons, the original sample codes specify this dynamic clock switching behavior.
One of the reasons would be poweer-saving... But, In MY case, timing stability is more important than power-saving.
So, I suppose, I should patch the code to prevent this before going into deeper analysis.
But, I have no enough idea that the SoftDeice S132 does/may-do dynamic HC clock switching right now.
Does anyone have suggestions on that ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SPIM deterministic TX timing control</title><link>https://devzone.nordicsemi.com/thread/91054?ContentTypeID=1</link><pubDate>Thu, 29 Jun 2017 23:50:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:71293021-eeef-4c03-8bda-256ea4cf1160</guid><dc:creator>kojima</dc:creator><description>&lt;p&gt;Thank you for your suggestion.&lt;/p&gt;
&lt;p&gt;But, which errata do you doubt ?
I&amp;#39;m driving the chip with HFCLK for stable timing.&lt;/p&gt;
&lt;p&gt;Anyway, I tried to kick TASKS_CONSTLAT manually on-the-fly thru the debugger, no behavior change has been obserbed.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SPIM deterministic TX timing control</title><link>https://devzone.nordicsemi.com/thread/91059?ContentTypeID=1</link><pubDate>Thu, 29 Jun 2017 14:58:34 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ddad54f2-b579-4c58-99c4-7bd5b9843d28</guid><dc:creator>Turbo J</dc:creator><description>&lt;p&gt;Have a look at those processor errata. You may want to use the HFCLK or CONSTLAT mode, and maybe disable power save.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>