<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Help about SPI of Omega2+]]></title><description><![CDATA[<p dir="auto">Hi,<br />
I try to use SPI to communicate with TI RF chip. But the first byte(register address) of a packet is not what I expected.<br />
For example, I send 0x40 will become 0xC0, I send 0x80 will become 0x00.<br />
The MSB is not correct, it become the same with bit 6.<br />
Anyone know how to solve this?<br />
Please!<br />
Regards,<br />
Max.</p>
]]></description><link>http://community.onion.io/topic/2027/help-about-spi-of-omega2</link><generator>RSS for Node</generator><lastBuildDate>Mon, 11 May 2026 20:57:34 GMT</lastBuildDate><atom:link href="http://community.onion.io/topic/2027.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 05 May 2017 07:09:02 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Help about SPI of Omega2+ on Fri, 05 May 2017 07:09:02 GMT]]></title><description><![CDATA[<p dir="auto">Hi,<br />
I try to use SPI to communicate with TI RF chip. But the first byte(register address) of a packet is not what I expected.<br />
For example, I send 0x40 will become 0xC0, I send 0x80 will become 0x00.<br />
The MSB is not correct, it become the same with bit 6.<br />
Anyone know how to solve this?<br />
Please!<br />
Regards,<br />
Max.</p>
]]></description><link>http://community.onion.io/post/12969</link><guid isPermaLink="true">http://community.onion.io/post/12969</guid><dc:creator><![CDATA[Max Peng]]></dc:creator><pubDate>Fri, 05 May 2017 07:09:02 GMT</pubDate></item><item><title><![CDATA[Reply to Help about SPI of Omega2+ on Thu, 07 Sep 2017 08:08:04 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="http://community.onion.io/uid/1895">@Max-Peng</a><br />
Are you fixed this problem?? I got same problem..</p>
]]></description><link>http://community.onion.io/post/14398</link><guid isPermaLink="true">http://community.onion.io/post/14398</guid><dc:creator><![CDATA[JinGyu Lee]]></dc:creator><pubDate>Thu, 07 Sep 2017 08:08:04 GMT</pubDate></item><item><title><![CDATA[Reply to Help about SPI of Omega2+ on Mon, 18 Sep 2017 09:36:43 GMT]]></title><description><![CDATA[<p dir="auto">No, they just give me a link to a 6 months ago post, nothing fixed, nothing released, no updated, no comment, no reply</p>
]]></description><link>http://community.onion.io/post/14529</link><guid isPermaLink="true">http://community.onion.io/post/14529</guid><dc:creator><![CDATA[Max Peng]]></dc:creator><pubDate>Mon, 18 Sep 2017 09:36:43 GMT</pubDate></item><item><title><![CDATA[Reply to Help about SPI of Omega2+ on Tue, 26 Sep 2017 08:37:34 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="http://community.onion.io/uid/1895">@Max-Peng</a><br />
At least you got something to work.  I've been fighting this SPI thing for weeks, on and off.  There seems to be no way to do SPI from a C program, and no good way to develop anything in C due to lack of kernel repo or at least config.  I'm binning my three Omega2+s, without SPI they're useless to me. A pity, I like these things but without access to the stuff I need there's no point.</p>
<p dir="auto">I have seen discussions about your problem with the first byte being corrupted, <a href="https://community.onion.io/topic/1560/spi-pins-for-the-omega2" rel="nofollow">in the forum here</a> but there doesn't seem to any resolution.</p>
]]></description><link>http://community.onion.io/post/14581</link><guid isPermaLink="true">http://community.onion.io/post/14581</guid><dc:creator><![CDATA[Lindsay Wright]]></dc:creator><pubDate>Tue, 26 Sep 2017 08:37:34 GMT</pubDate></item><item><title><![CDATA[Reply to Help about SPI of Omega2+ on Tue, 26 Sep 2017 18:52:15 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="http://community.onion.io/uid/4591">@Lindsay-Wright</a> Theoretically you could put variation of the Linkit Smart OpenWrt build on them which should have the patch to switch SPI to half-duplex mode and thus avoid the bit corruption due to a hardware issue with full duplex.   But that is obviously a bit of a non-trivial project - ultimately, it just resemphasizes the problem pointed out long ago, that <strong>Onion's persistent refusal to release sources which build to a system with working wifi</strong> means that the community can't fix little problems for them, and all the work of fixing everything falls on their overstretched team.</p>
<p dir="auto">Another approach you could consider would be to bit-bang SPI, or use a small MCU to bridge to it from I2C or a spare UART.</p>
]]></description><link>http://community.onion.io/post/14584</link><guid isPermaLink="true">http://community.onion.io/post/14584</guid><dc:creator><![CDATA[Chris Stratton]]></dc:creator><pubDate>Tue, 26 Sep 2017 18:52:15 GMT</pubDate></item></channel></rss>