<?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>NUVOTON + NRF24L01 Software Development. (SPI Communication)</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/120985/nuvoton-nrf24l01-software-development-spi-communication</link><description>Hello Everyone, 
 I try to develop Nuvoton + NRF24L01 SPI communicate each other. And I don&amp;#39;t understand why MISO bus has 0x0E after I send Write_Command 0x20? 
 
 void NRF24_AdressTX(uint8_t reg, uint8_t *dataa) { SPI_send_byte(0x20 | reg); SPI_send_byte</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 05 May 2025 15:55:14 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/120985/nuvoton-nrf24l01-software-development-spi-communication" /><item><title>RE: NUVOTON + NRF24L01 Software Development. (SPI Communication)</title><link>https://devzone.nordicsemi.com/thread/533969?ContentTypeID=1</link><pubDate>Mon, 05 May 2025 15:55:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:575d1899-7dcc-4e03-9ad8-294801084e15</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I am sorry to say, but we do not provide any technical support for the nRF24L01 anymore. Please consider using newer nRF devices, such as the nRF54L15.&lt;/p&gt;
&lt;p&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NUVOTON + NRF24L01 Software Development. (SPI Communication)</title><link>https://devzone.nordicsemi.com/thread/533911?ContentTypeID=1</link><pubDate>Mon, 05 May 2025 12:48:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:433f203a-8fe5-4260-8756-e277855c1c00</guid><dc:creator>electric eye</dc:creator><description>&lt;p&gt;&lt;img style="max-height:234px;max-width:706px;" height="234" src="https://devzone.nordicsemi.com/resized-image/__size/1412x468/__key/communityserver-discussions-components-files/4/pastedimage1746449222365v1.png" width="706" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;This is the new singals that I sent data to MOSI line. &lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NUVOTON + NRF24L01 Software Development. (SPI Communication)</title><link>https://devzone.nordicsemi.com/thread/533909?ContentTypeID=1</link><pubDate>Mon, 05 May 2025 12:45:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:74f51583-414d-486d-b5f3-296890866a6e</guid><dc:creator>electric eye</dc:creator><description>&lt;p&gt;Actually I checked many times that document. But I didn&amp;#39;t find anything that another I need to do. How can reach inside of NRF24L01 single chip spi commands? Are there any table of it?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NUVOTON + NRF24L01 Software Development. (SPI Communication)</title><link>https://devzone.nordicsemi.com/thread/533246?ContentTypeID=1</link><pubDate>Mon, 28 Apr 2025 15:40:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5ef5518c-45f2-4327-a957-2d278e6dd00d</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Please refer to Figure 26 and 27:&lt;br /&gt;&lt;a href="https://docs.nordicsemi.com/bundle/nRF24L01P_PS_v1.0/resource/nRF24L01P_PS_v1.0.pdf"&gt;https://docs.nordicsemi.com/bundle/nRF24L01P_PS_v1.0/resource/nRF24L01P_PS_v1.0.pdf&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NUVOTON + NRF24L01 Software Development. (SPI Communication)</title><link>https://devzone.nordicsemi.com/thread/533191?ContentTypeID=1</link><pubDate>Mon, 28 Apr 2025 12:45:20 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7e6b344e-bff3-403a-b356-77ccdf132bc5</guid><dc:creator>electric eye</dc:creator><description>&lt;p&gt;So is the corret way to do? Or not?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NUVOTON + NRF24L01 Software Development. (SPI Communication)</title><link>https://devzone.nordicsemi.com/thread/533188?ContentTypeID=1</link><pubDate>Mon, 28 Apr 2025 12:29:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4cc9ace0-8c82-4b16-8db3-a7976f246fdc</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;First byte for each spi transfer the&amp;nbsp;STATUS byte will be written (typically 0x0E) from the nRF24L01.&lt;/p&gt;
&lt;p&gt;I notice in the screenshot you shared the chip select pin toggle between the two bytes, which means this is then two commands, hence why you see STATUS byte for each byte.&lt;/p&gt;
&lt;p&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>