<?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>Custom non-nordic semiconductor host chip for nRF7002</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/113139/custom-non-nordic-semiconductor-host-chip-for-nrf7002</link><description>Hi team, 
 We tested the nRF7002 with the nRF5340 as the host. Now, our application needs to connect the nRF7002 Wi-Fi module with a custom microcontroller other than Nordic. However, we have no information on which microcontrollers support the nRF7002</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 17 Jul 2024 11:59:33 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/113139/custom-non-nordic-semiconductor-host-chip-for-nrf7002" /><item><title>RE: Custom non-nordic semiconductor host chip for nRF7002</title><link>https://devzone.nordicsemi.com/thread/494346?ContentTypeID=1</link><pubDate>Wed, 17 Jul 2024 11:59:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fe16e143-ddde-4cd1-a556-f90a3b7231ab</guid><dc:creator>runsiv</dc:creator><description>&lt;p&gt;Hi&amp;nbsp;&lt;span&gt;Chandrasekaran&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;In general I would recommend contacting your &lt;a href="https://www.nordicsemi.com/About-us/Contact-Us#projectdetails"&gt;RSM &lt;/a&gt;when you planning a project and considering which chip to&amp;nbsp;use&lt;/p&gt;
&lt;p&gt;Regarding your questions&lt;/p&gt;
&lt;p&gt;1. There is experimental linux support for the 7002, you could in theory also use another device running Zephyr.However we have not tested the 7002 on other devices then Nordic devices.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;2. The 7002 do not support thread, to run thread you would need for example an&amp;nbsp;&lt;span&gt;nRF54L series,&amp;nbsp;&lt;/span&gt;&amp;nbsp;&lt;span&gt;nRF&lt;/span&gt;5340 or&amp;nbsp; nRF52840. As I mentioned we have not tested the 7002, I will just copy in a reply from a similar question below&lt;/p&gt;
&lt;p&gt;&lt;em&gt;The drivers are present in nrf space, and as you mention; the agnostic low-level code is in nrfxlib.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;&lt;a href="https://github.com/nrfconnect/sdk-nrf/tree/main/drivers/wifi/nrf700x/src"&gt;https://github.com/nrfconnect/sdk-nrf/tree/main/drivers/wifi/nrf700x/src&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;&lt;a href="https://github.com/nrfconnect/sdk-nrfxlib/tree/main/nrf_wifi"&gt;https://github.com/nrfconnect/sdk-nrfxlib/tree/main/nrf_wifi&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;OS agnostic, ie. nrfxlib, docs is present here:&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;&lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrfxlib/nrf_wifi/README.html"&gt;https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrfxlib/nrf_wifi/README.html&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;&amp;quot;Running 7002 on a non nordic host&amp;quot;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;This is an untested scenario from our side, and it is hard to state exactly what issues/problems that will occur when porting.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;The obvious one is the (Q)SPI transport that needs to be in-place, based on how the transport is described in our datasheet:&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;&lt;a href="https://infocenter.nordicsemi.com/topic/ps_nrf7002/chapters/functional/doc/qspi_command_description.html?cp=3_0_0_6_0"&gt;https://infocenter.nordicsemi.com/topic/ps_nrf7002/chapters/functional/doc/qspi_command_description.html?cp=3_0_0_6_0&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;If their host controller runs zephyr, it will be easier for them, but we have not mapped any dependency tree (kconfig/dts wise) where this can&amp;nbsp;potentially be&amp;nbsp;problematic.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;If you look into the CMakeLists.txt file in the driver path, you will see that this needs to be expanded and patched to support other MCUs:&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;&lt;a href="https://github.com/nrfconnect/sdk-nrf/blob/main/drivers/wifi/nrf700x/CMakeLists.txt"&gt;https://github.com/nrfconnect/sdk-nrf/blob/main/drivers/wifi/nrf700x/CMakeLists.txt&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;div&gt;&lt;em&gt;Where is supplicant? Is it also included / part of these files, or another directory that needs to be pulled?&lt;/em&gt;&lt;/div&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;em&gt;That is here:&amp;nbsp;&lt;a href="https://github.com/nrfconnect/sdk-hostap"&gt;https://github.com/nrfconnect/sdk-hostap&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;The drivers are present in nrf space, and as you mention; the agnostic low-level code is in nrfxlib.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;&lt;a href="https://github.com/nrfconnect/sdk-nrf/tree/main/drivers/wifi/nrf700x/src"&gt;https://github.com/nrfconnect/sdk-nrf/tree/main/drivers/wifi/nrf700x/src&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;&lt;a href="https://github.com/nrfconnect/sdk-nrfxlib/tree/main/nrf_wifi"&gt;https://github.com/nrfconnect/sdk-nrfxlib/tree/main/nrf_wifi&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;3. My general understand is that must ESP32 has wifi, why would you run a 7002 in addition?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Regards&lt;/p&gt;
&lt;p&gt;Runar&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>