nrf 802.15.4 Sniffer Dongle doesn't sniff custom protocol

[Elia_pell]

Dear All,

I'm using nrf52840-DK for development purpose of IEEE 802.15.4 standard. One is used as transmitter, while other as receiver. I'm using nrf_radio_driver inside SDK for Thread and Zigbee. I would like to use a nrf52840-dongle for sniffing and debugging purpose,but it does not seem to work (the frequency channel is set correctly). What I notice, if that I use the example inside the SDK the sniffer just works perfectly, while with my stack it doesn't show anything: what could be the reason? My idea is that calling nrf_802154_transmit_raw(...), it doesn't set correclty the total on-air packet and so the sniffer couldn't detect the packet and show it in Wireshark (i "navigate" inside the function, reaching the lower layer where there is the line NRF_RADIO->PACKETPTR = (uint32_t)p_packet, where p_packet is the pointer to the packet containing the pakcet from PHR field, but preamble and access-address are not set). Moreover, the fact that the .hex file for the sniffer is not readable, made impossible other sort of debugging.

Am I correct or there is something else in your opinion?

Thanks to everyone,

Elia

[Kenneth]

What I notice, if that I use the example inside the SDK the sniffer just works perfectly, while with my stack it doesn't show anything: what could be the reason?

Does your stack work end-to-end? Just trying to figure out of the problem is that the packet is not correctly formatted to be received by the sniffer or if the problem is that there is no data sent at all.

[Elia_pell]

I forgot to mention it: yes, of course the data is correctly exchanged between tx and rx.

[Kenneth]

Maybe you can set a breakpoint when calling TASKS_TXEN when using the example as-is and your stack, and compare the various register in the RADIO for any apparent difference, if they are identical, then it must be the packet content you must look at. Could be some bits that should be specific value.

Best regards,
Kenneth