<?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>Getting started with spi and i2c on nrf connect sdk</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/74136/getting-started-with-spi-and-i2c-on-nrf-connect-sdk</link><description>Hi, 
 
 I have been working with nrf5 sdk for my projects and now i am trying to port it into the nrfconnect sdk. 
 It looks a bit confusing and not able to find the proper documentation channels to add spi communication to my sample project. I have seen</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 21 Apr 2021 15:23:01 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/74136/getting-started-with-spi-and-i2c-on-nrf-connect-sdk" /><item><title>RE: Getting started with spi and i2c on nrf connect sdk</title><link>https://devzone.nordicsemi.com/thread/306172?ContentTypeID=1</link><pubDate>Wed, 21 Apr 2021 15:23:01 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9d74d9c3-81d0-4db7-b8c1-3b44442f073a</guid><dc:creator>Albrecht Markus Schellenberger</dc:creator><description>&lt;p&gt;In general, I recommend you switching over to the NCS since we are not adding any new features to the SDK anymore.&lt;/p&gt;
&lt;p&gt;You can check out &lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/index.html"&gt;this link&lt;/a&gt; for available examples and documentation.&lt;/p&gt;
&lt;p&gt;Regarding the time for porting your code: It is of course hard to give you exact numbers, but I do not expect it to take too much time. The API’s are quite similar in general.&lt;/p&gt;
&lt;p&gt;A good way to start would be letting the NCS compiler run through the ported code.&lt;/p&gt;
&lt;p&gt;Cheers,&lt;/p&gt;
&lt;p&gt;Markus&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Getting started with spi and i2c on nrf connect sdk</title><link>https://devzone.nordicsemi.com/thread/306046?ContentTypeID=1</link><pubDate>Wed, 21 Apr 2021 10:12:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f4938244-e431-447f-b4ca-4d67222d9ce5</guid><dc:creator>madblue</dc:creator><description>&lt;p&gt;Thanks Markus,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;it was helpful, i am able read/write data using the zephyr apis.&lt;/p&gt;
&lt;p&gt;I am still a bit confused about the spi data structures for read/write and also the &amp;#39;patch_spi_read&amp;#39; api.&lt;/p&gt;
&lt;p&gt;It doesn&amp;#39;t seem to work but i&amp;nbsp;can figure that out.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;I will try out the i2c in the same way.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;I have a general question regarding the nrfconnect sdk and zephyr,&lt;/p&gt;
&lt;p&gt;As I have mentioned in the initial question, i am trying to port my application code to nrf connect sdk from nrf5 sdk14.00. i am a bit worried about the time required to completely port the code.&lt;/p&gt;
&lt;p&gt;My application requirements are,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;dfu bootloader, 2 spi, a flash file system(little fs), extended BLE mtu size(&amp;gt;150), low BLE connection interval (&amp;lt;50 ms), 2 timers, 1 i2c and a watchdog.&lt;/p&gt;
&lt;p&gt;Is the nrfconnect sdk drivers&amp;nbsp;required for my application is mature enough? Is there enough examples/documentation available to make the process as quick as possible ?&lt;/p&gt;
&lt;p&gt;Just to make sure it is the right time to port the code to nrfconnect sdk.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;I am adding my code here.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Hope this would be helpful for someone.&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;/*
 * Copyright (c) 2012-2014 Wind River Systems, Inc.
 *
 * SPDX-License-Identifier: Apache-2.0
 */

#include &amp;lt;zephyr.h&amp;gt;
#include &amp;lt;sys/printk.h&amp;gt;
#include &amp;lt;zephyr/types.h&amp;gt;
#include &amp;lt;stddef.h&amp;gt;
#include &amp;lt;string.h&amp;gt;
#include &amp;lt;errno.h&amp;gt;
#include &amp;lt;drivers/spi.h&amp;gt;
#include &amp;lt;drivers/gpio.h&amp;gt;


#if !DT_NODE_EXISTS(DT_NODELABEL(spi1))
#error &amp;quot;0oops&amp;quot;
#endif
#define SPI1 DT_NODELABEL(spi1)

int spi_cs_pin = 15;
int led_pin = 14;

static struct spi_config spi_cfg = {
	.operation = SPI_WORD_SET(8) | SPI_TRANSFER_MSB,
	.frequency = 4000000,
	.slave = 0,
};
struct device * spi_dev = NULL;
struct device * gpio0_dev = NULL;
struct device * gpio1_dev = NULL;

bool patch_spi_read(uint8_t * tx_ptr, uint8_t * rx_ptr, uint8_t tx_len, uint8_t rx_len){

	int err;

	struct spi_buf tx_buf[2];
	struct spi_buf rx_buf[2];
	struct spi_buf_set tx;
	struct spi_buf_set rx;

	tx_buf[0].buf = tx_ptr;
	tx_buf[0].len = 1;

	rx_buf[0].buf = rx_ptr;
	rx_buf[0].len = 1;

	rx_buf[1].buf = &amp;amp;rx_ptr[1];
	rx_buf[1].len = 4;

	tx.buffers = tx_buf;
	tx.count = 1;
	rx.buffers = rx_buf;
	rx.count = 2;

	gpio_pin_set(gpio0_dev, spi_cs_pin, 0);
	//err = spi_transceive(spi_dev, &amp;amp;spi_cfg, &amp;amp;tx, &amp;amp;rx);k_sleep(K_MSEC(30));
	err = spi_write(spi_dev, &amp;amp;spi_cfg, &amp;amp;tx);

	if (err) {
		printk(&amp;quot;spi write error: %d\n&amp;quot;, err);
		return false;
	}
	k_sleep(K_MSEC(3));
	err = spi_read(spi_dev, &amp;amp;spi_cfg, &amp;amp;rx);
	if (err) {
		printk(&amp;quot;spi read error: %d\n&amp;quot;, err);
		return false;
	}else {
		printk(&amp;quot;tx data %x\n&amp;quot;, tx_ptr[0]);

		for (size_t i = 0; i &amp;lt; 4; i++) {
			printk(&amp;quot;RX recv: %d \n&amp;quot;, rx_ptr[i]);
		}
	}
	//gpio_pin_set(gpio0_dev, spi_cs_pin, 1);
	return true;
}

void main(void)
{
	printk(&amp;quot;Hello World! %s\n&amp;quot;, CONFIG_BOARD);

	gpio0_dev= device_get_binding(&amp;quot;GPIO_0&amp;quot;);

	gpio_pin_configure(gpio0_dev, spi_cs_pin, GPIO_OUTPUT); //p0.03 == led_pin2
	gpio_pin_configure(gpio0_dev, led_pin, GPIO_OUTPUT); //p0.03 == LED2
	gpio_pin_set(gpio0_dev, spi_cs_pin, 0);


	printk(&amp;quot; SPI init\n&amp;quot;);
	spi_dev = device_get_binding(DT_LABEL(SPI1));
	if (spi_dev == NULL) {
		printk(&amp;quot;Could not find SPI driver\n&amp;quot;);
		return;
	}else printk(&amp;quot;spi init success\n&amp;quot;);

	k_sleep(K_MSEC(50));

	static uint8_t tx_buffer[16] = {0x1f, 00, 00, 00};
	static uint8_t rx_buffer[16];
	patch_spi_read(tx_buffer, rx_buffer, 1, 4);

	while(true){
		gpio_pin_set(gpio0_dev, led_pin, 0xff);
		k_sleep(K_MSEC(2000));

		gpio_pin_set(gpio0_dev, led_pin, 0);
		k_sleep(K_MSEC(30));
	}

}
&lt;/pre&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Getting started with spi and i2c on nrf connect sdk</title><link>https://devzone.nordicsemi.com/thread/305885?ContentTypeID=1</link><pubDate>Tue, 20 Apr 2021 13:42:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c98426bb-34ec-40b5-8675-f9a3fdc54238</guid><dc:creator>Albrecht Markus Schellenberger</dc:creator><description>&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/nordic/nrf-connect-sdk-guides/b/getting-started/posts/nrf-connect-sdk-tutorial---part-2-ncs-v1-4-0#h183sjwm5829mbs21y3111ulj6et5ph1"&gt;Chapter 3.4&lt;/a&gt;&amp;nbsp;of Simons tutorial gives you a basic introduction on how to create an overlay file. I hope this will be useful for you.&lt;/p&gt;
&lt;p&gt;Cheers!&lt;/p&gt;
&lt;p&gt;Markus&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Getting started with spi and i2c on nrf connect sdk</title><link>https://devzone.nordicsemi.com/thread/305855?ContentTypeID=1</link><pubDate>Tue, 20 Apr 2021 12:49:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5d7d7cd5-3c57-4c2a-aa45-56d48c08f1c2</guid><dc:creator>madblue</dc:creator><description>&lt;p&gt;I am using a custom board based on nrf52840.&lt;/p&gt;
&lt;p&gt;I have not created a new board but edited the existing .dts file according my custom board specifications.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;I have ran it on a dk also but getting the same error.&lt;/p&gt;
&lt;p&gt;i have chosen a ble code as my base, let me get back to you after trying it out with simple example.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;This how the zephyr.dts file looks like,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;		};
		spi0: spi@40003000 {
			#address-cells = &amp;lt; 0x1 &amp;gt;;
			#size-cells = &amp;lt; 0x0 &amp;gt;;
			reg = &amp;lt; 0x40003000 0x1000 &amp;gt;;
			interrupts = &amp;lt; 0x3 0x1 &amp;gt;;
			status = &amp;quot;disabled&amp;quot;;
			label = &amp;quot;SPI_0&amp;quot;;
			compatible = &amp;quot;nordic,nrf-spi&amp;quot;;
			sck-pin = &amp;lt; 0x1f &amp;gt;;
			mosi-pin = &amp;lt; 0x1e &amp;gt;;
			miso-pin = &amp;lt; 0x28 &amp;gt;;
		};
		spi1: spi@40004000 {
			#address-cells = &amp;lt; 0x1 &amp;gt;;
			#size-cells = &amp;lt; 0x0 &amp;gt;;
			reg = &amp;lt; 0x40004000 0x1000 &amp;gt;;
			interrupts = &amp;lt; 0x4 0x1 &amp;gt;;
			status = &amp;quot;okay&amp;quot;;
			label = &amp;quot;SPI_1&amp;quot;;
			compatible = &amp;quot;nordic,nrf-spi&amp;quot;;
			sck-pin = &amp;lt; 0xd &amp;gt;;
			mosi-pin = &amp;lt; 0xe &amp;gt;;
			miso-pin = &amp;lt; 0x10 &amp;gt;;
		};
		spi2: spi@40023000 {
			#address-cells = &amp;lt; 0x1 &amp;gt;;
			#size-cells = &amp;lt; 0x0 &amp;gt;;
			reg = &amp;lt; 0x40023000 0x1000 &amp;gt;;
			interrupts = &amp;lt; 0x23 0x1 &amp;gt;;
			status = &amp;quot;disabled&amp;quot;;
			label = &amp;quot;SPI_2&amp;quot;;
			compatible = &amp;quot;nordic,nrf-spi&amp;quot;;
			sck-pin = &amp;lt; 0x13 &amp;gt;;
			mosi-pin = &amp;lt; 0x14 &amp;gt;;
			miso-pin = &amp;lt; 0x15 &amp;gt;;
		};&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;How do i create an overlay file ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Getting started with spi and i2c on nrf connect sdk</title><link>https://devzone.nordicsemi.com/thread/305847?ContentTypeID=1</link><pubDate>Tue, 20 Apr 2021 12:28:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:517f109b-cf19-4bec-b61d-13c0c1f5cdcf</guid><dc:creator>Albrecht Markus Schellenberger</dc:creator><description>&lt;p&gt;There are no silly questions, only silly answers. Right? ;-)&lt;/p&gt;
&lt;p&gt;Are you using your own board together with the nRF52840 or a DK? I am asking because if you work with the nRF52840 DK for instance, you do not need an overlay file to get SPI1 to work. It is already part of the device tree, which you can check via a file called &lt;em&gt;zephyr.dts&lt;/em&gt; located in: &lt;em&gt;../&amp;lt;your build folder&amp;gt;/zephyr/&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;pre class="ui-code" data-mode="text"&gt;spi1: spi@40004000 {
	#address-cells = &amp;lt; 0x1 &amp;gt;;
	#size-cells = &amp;lt; 0x0 &amp;gt;;
	reg = &amp;lt; 0x40004000 0x1000 &amp;gt;;
	interrupts = &amp;lt; 0x4 0x1 &amp;gt;;
	status = &amp;quot;okay&amp;quot;;
	label = &amp;quot;SPI_1&amp;quot;;
	compatible = &amp;quot;nordic,nrf-spi&amp;quot;;
	sck-pin = &amp;lt; 0x1f &amp;gt;;
	mosi-pin = &amp;lt; 0x1e &amp;gt;;
	miso-pin = &amp;lt; 0x28 &amp;gt;;
};&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;I ran your C-snippet through a simple “Hello World” application on the nRF52840 DK and the binding worked fine.&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Markus&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Getting started with spi and i2c on nrf connect sdk</title><link>https://devzone.nordicsemi.com/thread/305632?ContentTypeID=1</link><pubDate>Mon, 19 Apr 2021 15:54:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e3954e07-4c19-4aa1-881b-11803d492440</guid><dc:creator>madblue</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;That is pretty good, thanks.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I have tried a simple test code for spi but i am not able to get the device_get_binding().&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;prj.config&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;CONFIG_NCS_SAMPLES_DEFAULTS=y

CONFIG_BT=y
CONFIG_BT_PERIPHERAL=y
CONFIG_BT_DEVICE_NAME=&amp;quot;Nordic_Blinky&amp;quot;

# Enable the LBS service
CONFIG_BT_LBS=y
CONFIG_BT_LBS_POLL_BUTTON=y
CONFIG_DK_LIBRARY=y

CONFIG_GPIO=y
CONFIG_SPI=y
CONFIG_I2C=n
CONFIG_NRFX_SPIM=n
CONFIG_NRFX_SPIM1=n


CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=2048&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;#if !DT_NODE_EXISTS(DT_NODELABEL(spi1))
#error &amp;quot;whoops&amp;quot;
#endif
#define SPI1 DT_NODELABEL(spi1)

    struct device * spi_dev;
    spi_dev = device_get_binding(DT_LABEL(SPI1));   


	const char* const spiName = &amp;quot;SPI_1&amp;quot;;
	//spi_dev = device_get_binding(spiName);
    spi_dev = device_get_binding(MYSPI);
	if (spi_dev == NULL) {
		printk(&amp;quot;Could not find SPI driver\n&amp;quot;);
		return;
	}else printk(&amp;quot;spi success&amp;quot;);
	
	
	uint8_t tx_buf[4]={(0x0F&amp;lt;&amp;lt;1 ) | 0x01};
	uint8_t rx_buf[4]={0};
	struct spi_buf spi_tx_buf_struct;
	spi_tx_buf_struct.buf = tx_buf;
	spi_tx_buf_struct.len = 4;

	struct spi_buf spi_rx_buf_struct;
	spi_tx_buf_struct.buf = rx_buf;
	spi_tx_buf_struct.len = 4;

	struct spi_buf_set spi_bufs;
	spi_bufs.buffers = &amp;amp;spi_tx_buf_struct;
	spi_bufs.count = 4;
	struct spi_buf_set spi_bufs_rx;
	spi_bufs.buffers = &amp;amp;spi_rx_buf_struct;
	spi_bufs.count = 4;
	//


	spi_transceive(spi_dev, &amp;amp;spi_cfg, &amp;amp;spi_bufs, &amp;amp;spi_bufs_rx);
	//spi_write(spi_dev, &amp;amp;spi_cfg, &amp;amp;spi_bufs);
	k_sleep(K_MSEC(100));
	printk(&amp;quot;read %d %d %d \n\n&amp;quot;, rx_buf[1], rx_buf[2], rx_buf[3]);
&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;I have also had a look at the &amp;quot;&lt;a href="https://docs.zephyrproject.org/2.4.0/guides/dts/api-usage.html#dt-node-identifiers"&gt;device tree how to &lt;/a&gt;&amp;nbsp;&amp;quot;,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;

my .dts for 52840,

&amp;amp;spi1 {
	compatible = &amp;quot;nordic,nrf-spi&amp;quot;;
	/* Cannot be used together with i2c0. */
	/* status = &amp;quot;okay&amp;quot;; */
	sck-pin = &amp;lt;13&amp;gt;;
	mosi-pin = &amp;lt;14&amp;gt;;
	miso-pin = &amp;lt;16&amp;gt;;
};

zephyr.dts, 

spi1: spi@40004000 {
	#address-cells = &amp;lt; 0x1 &amp;gt;;
	#size-cells = &amp;lt; 0x0 &amp;gt;;
	reg = &amp;lt; 0x40004000 0x1000 &amp;gt;;
	interrupts = &amp;lt; 0x4 0x1 &amp;gt;;
	status = &amp;quot;disabled&amp;quot;;
	label = &amp;quot;SPI_1&amp;quot;;
	compatible = &amp;quot;nordic,nrf-spi&amp;quot;;
	sck-pin = &amp;lt; 0xd &amp;gt;;
	mosi-pin = &amp;lt; 0xe &amp;gt;;
	miso-pin = &amp;lt; 0x10 &amp;gt;;
};&lt;/pre&gt;&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;
&lt;p&gt;I think It initializes the spi, my&amp;nbsp;i am getting this error,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;*** Booting Zephyr OS build v2.4.99-ncs1  ***␍␊
Starting Bluetooth Peripheral LBS example␍␊
 SPI init␍␊
spi successI: CS control inhibited (no GPIO device)␍␊
E: ***** BUS FAULT *****␍␊
E:   Precise data bus error␍␊
E:   BFAR Address: 0x20040000␍␊
E: r0/a1:  0x40004000  r1/a2:  0x20002e1c  r2/a3:  0x0003dbb8␍␊
E: r3/a4:  0x20002448 r12/ip:  0x20002e28 r14/lr:  0x0001da9b␍␊
E:  xpsr:  0x21000014␍␊
E: Faulting instruction address (r15/pc): 0x00024216␍␊
E: &amp;gt;&amp;gt;&amp;gt; ZEPHYR FATAL ERROR 0: CPU exception on CPU 0␍␊
E: Fault during interrupt handling␍␊&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;I have tied the cs pin low always.&lt;/p&gt;
&lt;p&gt;Do i have to specify the pin numbers elsewhere other than the .dts file ? does it get override from somewhere else ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Getting started with spi and i2c on nrf connect sdk</title><link>https://devzone.nordicsemi.com/thread/305599?ContentTypeID=1</link><pubDate>Mon, 19 Apr 2021 14:17:20 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:991fdfcf-cf58-4bc4-be20-caa969c8230d</guid><dc:creator>Albrecht Markus Schellenberger</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;I can recommend a tutorial written by my colleague Simon. Chapter 1.2 should be of special interest for you:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/nordic/nrf-connect-sdk-guides/b/getting-started/posts/nrf-connect-sdk-tutorial---part-3-ncs-v1-4-0#h79sk0f70607qwcyitkx2xn61bmh9mo"&gt;https://devzone.nordicsemi.com/nordic/nrf-connect-sdk-guides/b/getting-started/posts/nrf-connect-sdk-tutorial---part-3-ncs-v1-4-0#h79sk0f70607qwcyitkx2xn61bmh9mo&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Note that the tutorial is not up to date anymore, so instead of using&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;CONFIG_I2C_1=y&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;in prj.conf, you have to use this option instead:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;CONFIG_I2C=y&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;I hope this will help you! Let me know if you have any more questions.&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Markus&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>