<?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>nrf5340 + nrf7002 as multi-protocol (Wifi + BLE + Thread / Zigbee) controller solution of Linux host</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/114115/nrf5340-nrf7002-as-multi-protocol-wifi-ble-thread-zigbee-controller-solution-of-linux-host</link><description>I am looking for a solution of a multi-protocol controller for Linux host. 
 
 1. Coexistence of Wifi &amp;amp; BLE &amp;amp; Thread / Zigbee 
 The ble-coex / thread-coex example has the WiFi stacks on the 5340. If the W iFi stack is on the Linux host (nrf70-linux-driver</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 23 Aug 2024 07:29:03 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/114115/nrf5340-nrf7002-as-multi-protocol-wifi-ble-thread-zigbee-controller-solution-of-linux-host" /><item><title>RE: nrf5340 + nrf7002 as multi-protocol (Wifi + BLE + Thread / Zigbee) controller solution of Linux host</title><link>https://devzone.nordicsemi.com/thread/499480?ContentTypeID=1</link><pubDate>Fri, 23 Aug 2024 07:29:03 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1039caab-ecfa-4184-ae8f-3d0dedfe37e3</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;We discussed this in my team, and it seems like this is a bit too much to ask for, given what we currently have.&lt;/p&gt;
&lt;p&gt;If you take WiFi out of the equation, then it is still a big ask to make the nRF53 work as a generic BLE &lt;strong&gt;and&lt;/strong&gt; Zigbee&amp;nbsp;&lt;strong&gt;or&lt;/strong&gt; Thread device. (As you say, you can&amp;#39;t do both Zigbee and Thread in parallel, so let us assume we only do one at the time. The challenge is that there is no built in way to determine where the serial commands should go. To the Bluetooth stack or the Zigbee/Thread.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Now, I haven&amp;#39;t worked too much with WiFi and our nRF7002, but I don&amp;#39;t think it is possible to run a generic BLE HCI device in combination with the equivalent on WiFi.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;The closest that I can think of, is a way that you can get it to work with all protocols, but only one at the time. You would have to include a bootloader, and have the host update the firmware on the device every time you want to switch protocol. This would, however, mean that if you wanted to support all 3 (4) protocols at the same time, you would need 3 (4) nRF5340s (and the nRF7002).&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Edvin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>