SDK Version?

[richardpike]

Hi,
Thanks for this.
Attempting to build gives me "ETH_P_IEEE802154" undeclared
I assume you must be using a nrF connect build that hasn't been released yet? Looks like the latest official version uses zephyr 3.1.99 - hopefully a new official release comes out soon as workwise I can't try that right now.

Just for your potential interest: using the 5340DK I was able to send some messages on their raw transmit function - very heavily stripped down version here (apologies for the huge files, inexperienced with the newer SDK and wasn't sure what files should be ignored).

I got the non stripped down version communicating with a legacy coordinator on another chip using 802.15.4 but unfortunately the messages get dropped. Hoping nordic get back to me soon enough.

[dberliner]

I was using plain Zephyr OS, no nrf SDK. As far as I can tell there is no adaptation of Zephyr 3.2.0 with the SDK at this time. Unfortunately this feature is so new they havent integrated it yet, I have no idea when that is expected.

[dberliner]

@richardpike FYI it looks like Nordics sdk-nrf v2.2.0 is going to use a zephyr base with these changes. It's currently in the RC stages.

[richardpike]

@richardpike FYI it looks like Nordics sdk-nrf v2.2.0 is going to use a zephyr base with these changes. It's currently in the RC stages.

Thank you, I meant to update this and say that myself. Your code compiles and runs in it.
Not had a chance to fully look into it yet (boss has requested I focus on a different part of the same project) but I'll try and get this going on a 5340 at some point - although historically I've always taken complete control of the packets rather than using DGRAM.