Help with nrf24l01+ not seeing air traffic

RE: Help with nrf24l01+ not seeing air traffic

ulao — Tue, 07 Apr 2020 21:06:39 GMT

Success!

side note for anyone reading, Arduino code sets a few presets. For example the channel is not default its set to 0x4c in the code. So for a minimal set up set it back to 2. Also the RF_SETUP on my chip is defaulted to 0x0f but in the Arduino codes its 7.

Tif for the nordic team, may want to do an Arduino minimal set pu guide as most everyone plays with them stupid things. Take note the mentioned.

So that out the way, I get a reply ! Kenneth, thx for all the assume help! Ticket good to close!

RE: Help with nrf24l01+ not seeing air traffic

Kenneth — Tue, 07 Apr 2020 07:38:44 GMT

Please refer to the datasheet on ???. In short EN_RXADDR = 2 enable RX pipe0 and 1. Also make sure that TX_ADDRESS is equal the RX address you want to transmit to.

Best regards,
Kenneth

RE: Help with nrf24l01+ not seeing air traffic

ulao — Tue, 07 Apr 2020 01:35:52 GMT

UPDATE: so after changing the clocking edge I apparently bumped out the MOSI wire and that cause the condition above. After plugging it back in I see my register data.

Still nothing on the receiving end but now I have a path to fallow down. That arduino library is really hard to use but I like the GUI debug.

not that its a nordic concern but I see no way to set the payload width unless you set an addres. So the minimum I can do is this.
STATUS       = 0x0e RX_DR=0 TX_DS=0 MAX_RT=0 RX_P_NO=7 TX_FULL=0
RX_ADDR_P0-1   = 0x0101010101 0xc2c2c2c2c2
RX_ADDR_P2-5   = 0xc3 0xc4 0xc5 0xc6
TX_ADDR       = 0xe7e7e7e7e7
RX_PW_P0-6   = 0x03 0x00 0x00 0x00 0x00 0x00
EN_AA       = 0x3f
EN_RXADDR   = 0x03 (???)
RF_CH       = 0x4c
RF_SETUP   = 0x07
CONFIG       = 0x0f
DYNPD/FEATURE   = 0x00 0x00
Data Rate   = 1MBPS
Model       = nRF24L01+
CRC Length   = 16 bits
PA Power   = PA_MAX

and as for the sender I only set
sendCommand(0x20);sendCommand(0x0e);
_delay_ms(2)
sendCommand(0x23);sendCommand(3);
sendCommand(0x30);sendCommand(1);sendCommand(1);sendCommand(1);sendCommand(1);sendCommand(1);

I then verify all of that.

then I try sending a growing payload (pulsing after each)

1
1,2
1,2,3

and on up to about 21 bytes. Nothing responds to any of these.

I'm pretty sure I can fix this on my own now if I knew the ???'s I marked in the print out above. Because I can match everything up as I know what that all means. What is EN_RXADDR with two bits on?

RE: Help with nrf24l01+ not seeing air traffic

ulao — Mon, 06 Apr 2020 19:10:04 GMT

Here is read and write, the next read is after 1.5 ms suggestion and the pulse. So too big to fit in one image. but I woudl expect the first read to get 0x08, everything I read is 0 no matter the register.

pulse then read again.

RE: Help with nrf24l01+ not seeing air traffic

Kenneth — Mon, 06 Apr 2020 15:55:31 GMT

Can you show write and then readback? E.g. of CONFIG register (0x00).

write: 0x20 0x0A

read: 0x00 0x00

Best regards,
Kenneth

RE: Help with nrf24l01+ not seeing air traffic

ulao — Mon, 06 Apr 2020 13:03:40 GMT

Ok I believe that is now corrected but no change in my issue.

RE: Help with nrf24l01+ not seeing air traffic

ulao — Mon, 06 Apr 2020 12:49:31 GMT

I was sure it was 0,0?

I may have my i/o lines swapped but this is my analyzer set up. If this is not right what should it be?

EDIT: oh I see its clocking on the rising, should be falling.

RE: Help with nrf24l01+ not seeing air traffic

Kenneth — Mon, 06 Apr 2020 09:37:59 GMT

Looking at your trace and comparing with the datasheet, I can find that your MOSI is changing on rising CLK, while the datasheet specify data should be changed on falling CLK:

I believe you are using wrong SPI mode.

RE: Help with nrf24l01+ not seeing air traffic

ulao — Sun, 05 Apr 2020 18:32:33 GMT

Ok I have finally found my issue but now I can not fix it.

Problem is that what I set, is ignored. Or ats least I'm pretty sure.

ex: read config get:0x00 (should be a 8 for default) , wright config with 0x0a, read config get 0x00.

Or at least I would assume a read does return info? the first clocked out byte is the status register and the data on the second clock byte is the returning data, then 0 is wrong.

I also tried sending a NOP after my read request instead of a 0 but no luck.

RE: Help with nrf24l01+ not seeing air traffic

ulao — Thu, 02 Apr 2020 18:44:47 GMT

// Power up radio   
hal_nrf_set_power_mode(HAL_NRF_PWR_UP); //gives me a 0xe7  on second byte received from spi. 

// Add a delay of 1.5ms
    
// Write payload to radio TX FIFO
hal_nrf_write_tx_payload(payload, 3U);
    
// Toggle radio CE signal to start transmission
CE_PULSE();

RE: Help with nrf24l01+ not seeing air traffic

ulao — Thu, 02 Apr 2020 15:29:43 GMT

Gave that a try but still seeing the 0xe7 I noted on my second question. Surly that is noted in the data sheet somewhere?

RE: Help with nrf24l01+ not seeing air traffic

Kenneth — Thu, 02 Apr 2020 10:15:18 GMT

The problem here may be just about anything, my recommendation is to setup a receiver and transmitter with minimum configuration (e.g. use the default configuration for most registers).

https://devzone.nordicsemi.com/f/nordic-q-a/13766/minimal-nrf24l01-setup-problem/52611#52611