<?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>Handling resets with HCI SPI</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/89405/handling-resets-with-hci-spi</link><description>For nrf52x, a pin can be dedicated for reset, and this is from my understanding how HCI works in the sample (host line to controller reset pin). However, for the nrf5340, there is no RESET pin possible for the network core from what I&amp;#39;ve researched. Since</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 29 Jun 2022 14:59:13 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/89405/handling-resets-with-hci-spi" /><item><title>RE: Handling resets with HCI SPI</title><link>https://devzone.nordicsemi.com/thread/374785?ContentTypeID=1</link><pubDate>Wed, 29 Jun 2022 14:59:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8cce340a-b929-4a93-8b1a-0c22d1d90814</guid><dc:creator>&amp;#216;ivind</dc:creator><description>&lt;p&gt;I&amp;#39;ve spoken to a developer and I believe modifying the hci spi driver to use NETWORK.FORCEOFF instead should work.&lt;/p&gt;
&lt;p&gt;You can disable uart in the devicetree using an overlay file.&lt;br /&gt;&lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.0.0/zephyr/build/dts/howtos.html"&gt;https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.0.0/zephyr/build/dts/howtos.html&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.0.0/zephyr/build/dts/intro.html#dt-input-files"&gt;https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.0.0/zephyr/build/dts/intro.html#dt-input-files&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Handling resets with HCI SPI</title><link>https://devzone.nordicsemi.com/thread/374617?ContentTypeID=1</link><pubDate>Tue, 28 Jun 2022 19:07:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:03da5f7f-300b-4d53-8ece-2b540b720e73</guid><dc:creator>Abraham Hamidi</dc:creator><description>&lt;p&gt;Thanks. It will probably work now that I see it&amp;#39;s a shared register, but I&amp;#39;ll wait for a response. If that is the case, then I will make a PR to sdk-nrf that checks if CPUNET is enabled. By the way, since ENABLE_CPUNET is required to release FORCEOFF, how can I make that not allocate gpio for UART, since I&amp;#39;m not using UART? I think right now all that can be done is to disable serial and hope the generate stubs don&amp;#39;t interfere with anything. I might patch that code to check CONFIG_SERIAL.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Handling resets with HCI SPI</title><link>https://devzone.nordicsemi.com/thread/374594?ContentTypeID=1</link><pubDate>Tue, 28 Jun 2022 14:57:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:28a200eb-e3b8-473d-a52b-d8aca5bdc99c</guid><dc:creator>&amp;#216;ivind</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;At first glance it looks like using FORCEOFF instead of the reset pin should work. I will ask the developers and get back to you.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>