<?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>How to convert Arduino libraries</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/115818/how-to-convert-arduino-libraries</link><description>Hello, 
 I have several sketches from prototyping my project but It&amp;#39;s occurred to me that the libraries used for some sensors are unique. I want to use the SDK connect examples for development purposes but I do not know how to port the Ardiuno libraries</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 25 Oct 2024 13:35:33 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/115818/how-to-convert-arduino-libraries" /><item><title>RE: How to convert Arduino libraries</title><link>https://devzone.nordicsemi.com/thread/507966?ContentTypeID=1</link><pubDate>Fri, 25 Oct 2024 13:35:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d55f1832-6ee6-4c16-817b-28ef7bb06850</guid><dc:creator>Menon</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;Porting Arduino libraries to the nRF Connect SDK will likely be challenging because the two platforms are quite different in their architecture. Arduino libraries are usually designed for a simple, single-threaded environment, while the nRF Connect SDK is based on Zephyr RTOS, which supports multi-threading, interrupts, and various advanced features.&lt;/p&gt;
&lt;p&gt;Zephyr has a more complex hardware abstraction layer that communicates with devices using device trees and driver APIs, while Arduino uses simpler APIs and straightforward calls.&lt;/p&gt;
&lt;p&gt;If there are no existing drivers available, a better approach might be to write your own wrapper libraries that connect directly to the sensor hardware. This way, you can customize the library to meet your specific needs while maintaining control over the hardware interaction.&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;br /&gt;Abhijith&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>