Replies: 2 comments 3 replies
-
Looking at the pcap file, it does appear that many packets sent from nRF52840 to CC2652 do not have a corresponding ack message. I would suggest reaching out to TI for support on this. |
Beta Was this translation helpful? Give feedback.
3 replies
-
Hi @ValNyrov. Best Regards, |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello OpenThread community!
My hardware configuration is:
1)One board nRF52840-DK acting as router and commissioner,OS Zephyr 3.3.99,chip speed 64 MHz
2)One board TI CC2652-launchpad, acting as minimal end divice and joiner,OS Zephyr 3.3.99,chip speed 48 MHz
3)Packet sniffer: Wireshark + nrf52840-dongle
In general, everything works and the commissioning process is completed.
But I noticed in the log of the nRF52840-DK board that in the commissioning process there are repetitions of sending some frames, it is highlighted in the screenshot with a red line. This is also visible in the wireshark log (lines 33-50).
Screenshot TI CC2652 log:
Full logs in attachment.
After the completion of the commissioning, I execute the ping command whith 1024 bytes on the side of the nRF52840-DK board, and there are also retries of transmission of some frames.
Since these boards have different chips with different speeds, I assume that the CC2652 board does not always have time to process a frame (this is just my guess).
Perhaps I should correctly set the timeouts for waiting ACK frame from CC2652-launchpad and increase the time between retransmissions of frames? Please tell me how to do it right.
Zephyr logs:
nRF52840.log
ti_cc2652.log
Wireshark:
wireshark.pcapng.tar.gz
What commands in Zephyr did I execute:
zephyr_commands_nRF52840.txt
zephyr_commands_ti_CC2652.txt
Best Regards,
Valeriy
Beta Was this translation helpful? Give feedback.
All reactions