<?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>Migration from nrf5 to nrf Connect SDK</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/101652/migration-from-nrf5-to-nrf-connect-sdk</link><description>Hello, 
 I have a software architecture based on nrf 5 SDK. I want to port it to nrf Connect SDK. To proceed step by step I want to port first single tasks (for example temperature handling). I have read here in the forum that nrf Connect SDK is fundamentally</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 11 Jul 2023 08:16:29 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/101652/migration-from-nrf5-to-nrf-connect-sdk" /><item><title>RE: Migration from nrf5 to nrf Connect SDK</title><link>https://devzone.nordicsemi.com/thread/435637?ContentTypeID=1</link><pubDate>Tue, 11 Jul 2023 08:16:29 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cea95451-72cc-46be-a2e7-d58e0cc90b73</guid><dc:creator>Sigurd Hellesvik</dc:creator><description>&lt;p&gt;One of my colleguas have an &lt;a href="https://github.com/Rallare/fw-nrfconnect-nrf/tree/nrf9160_samples/samples/nrf9160/nrfx/rtc"&gt;unofficial sample for the RTC&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Also, see this more complicated offiical sample for &lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/samples/boards/nrf/nrf53_sync_rtc/README.html"&gt;Synchronized RTC&lt;/a&gt;.&lt;/p&gt;
[quote user="Tal."](for nrf 52832DK[/quote]
&lt;p&gt;One of the nice things about the nRF Connect SDK is that you can use one project for different boards, because the board differences are handeled by the configuration system (Kconfig and DeviceTree).&lt;br /&gt;So this one should work for the nRF52DK also. Just build for nrf52dk_nrf52832.&lt;/p&gt;
&lt;p&gt;PS: I think I forgot to mention our great getting started tutorials at &lt;a href="https://academy.nordicsemi.com/"&gt;https://academy.nordicsemi.com/&lt;/a&gt;.&lt;br /&gt;If you need a good starting point to learn the nRF Connect SDK, that is it.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Migration from nrf5 to nrf Connect SDK</title><link>https://devzone.nordicsemi.com/thread/435544?ContentTypeID=1</link><pubDate>Mon, 10 Jul 2023 15:39:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ef9a7d5e-b092-42b1-84fa-710b7a6a2573</guid><dc:creator>Tal.</dc:creator><description>&lt;p&gt;Hello, I just try to port the RTC function in nrf Connect SDK. I want to use the RTC_get_time function. Are there any examples using RTC (for nrf 52832DK)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Migration from nrf5 to nrf Connect SDK</title><link>https://devzone.nordicsemi.com/thread/435480?ContentTypeID=1</link><pubDate>Mon, 10 Jul 2023 12:02:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:93f03346-a2a2-40d0-befe-829cead40989</guid><dc:creator>Tal.</dc:creator><description>&lt;p&gt;Thank you for your answer. That helps me. I will try porting some functions. If I had&amp;nbsp; questions, I would contact you again.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Migration from nrf5 to nrf Connect SDK</title><link>https://devzone.nordicsemi.com/thread/435462?ContentTypeID=1</link><pubDate>Mon, 10 Jul 2023 11:23:03 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e1d0fd9b-03dc-482a-9f34-c5f49ba026fb</guid><dc:creator>Sigurd Hellesvik</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Yes, you have understood that correctly.&lt;br /&gt;See &amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/nrf-connect-sdk-and-nrf5-sdk-statement"&gt;nRF Connect SDK and nRF5 SDK statement&lt;/a&gt; for some info.&lt;br /&gt;The nRF Connect SDK is built on Zephyr RTOS, while the nRF5 SDK is closer to bare-metal.&lt;/p&gt;
&lt;p&gt;Generally, we advice customers to start from scratch when moving to the nRF Connect SDK.&lt;br /&gt;Migrating the full project as-is is usually more time consuming.&lt;/p&gt;
&lt;p&gt;That being said, it is still written in C, so you can take parts of your code and move them over.&lt;/p&gt;
&lt;p&gt;In the end, it depends on your project.&lt;br /&gt;If you want some more specific advice, you can list your features, and I will let you know how/if they can be migrated or give you new starting points/samples for said features (As far as my knowledge goes).&lt;br /&gt;If you evt prefer the ticket to be private for something like that, I can convert it.&lt;/p&gt;
&lt;p&gt;Maybe the biggest thing that is different is that we now use the Zephyr drivers instead of the nrfx drivers you know from the nRF5 SDK. &lt;br /&gt;You still can use the nrfx drivers (for example for SPI), but it is no longer the default way. &lt;br /&gt;For example, the nRF Connect SDK use the DeviceTree to keep track of peripherals. If you use the nrfx drivers without the devicetree, you may get conflicts with other parts of the nRF Connect SDK which use the devicetree, for example related to GPIO initialization.&lt;/p&gt;
&lt;p&gt;Let me know if you got any more questions&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Sigurd Hellesvik&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>