topic Re: RW612 and Thread FTD in Wi-Fi® + Bluetooth® + 802.15.4

RW612 and Thread FTD

joanou — Sun, 04 May 2025 19:30:02 GMT

Main question - Can I use the RW612 as a Full Thread Device (FTD) sensor node and act as a router eligible end device (REED)?

If so, is this recommended and is there a working example for VSCode? Also, no need for Matter in my application. I need low latency.

I found the firmware binary: rw61x_sb_ble_15d4_combo_a2.bin. Any plans to release the source code that that it can be tuned and optimized? Same question for rw61x_sb_wifi_a2.bin.

Finally, can WiFi and Thread be supported in the same application, even if only one can be used at a time?

Thanks

Re: RW612 and Thread FTD

Ricardo_Zamora — Mon, 05 May 2025 15:56:47 GMT

Hello,

Hope you are doing well. Here you can find the OpenThread examples available for RW612: NXP/ot-nxp · GitHub

Also, I would recommend checking this User Manual: NXP 802.15.4 Demo Applications for RW612.

Hope this helps!

Regards,

Ricardo

Re: RW612 and Thread FTD

joanou — Wed, 07 May 2025 16:38:23 GMT

Hello Ricardo,

Thanks for the links. I am looking to use Zephyr, VSCode MCUXpresso with the included device tree for the FRDM-RW612. Would there be a sample for openthread CLI? If not, any plans... I am stuck otherwise with my current code base?

The error is:

In file included from C:/Zephyr/zephyr_v4_1_0/zephyr/include/zephyr/toolchain/gcc.h:98,
from C:/Zephyr/zephyr_v4_1_0/zephyr/include/zephyr/toolchain.h:52,
from C:/Zephyr/zephyr_v4_1_0/zephyr/include/zephyr/sys/__assert.h:11,
from C:/Zephyr/zephyr_v4_1_0/zephyr/include/zephyr/sys/iterable_sections.h:10,
from C:/Zephyr/zephyr_v4_1_0/zephyr/include/zephyr/logging/log_instance.h:10,
from C:/Zephyr/zephyr_v4_1_0/zephyr/include/zephyr/logging/log.h:10,
from C:/Zephyr/zephyr_v4_1_0/zephyr/modules/openthread/platform/radio.c:17:
C:/Zephyr/zephyr_v4_1_0/zephyr/include/zephyr/device.h:96:41: error: '__device_dts_ord_DT_CHOSEN_zephyr_ieee802154_ORD' undeclared here (not in a function)
96 | #define DEVICE_NAME_GET(dev_id) _CONCAT(__device_, dev_id)
| ^~~~~~~~~

The code lines in zephyr\modules\openthread\platform\radio.c are:

static const struct device *const radio_dev =

DEVICE_DT_GET(DT_CHOSEN(zephyr_ieee802154));

static struct ieee802154_radio_api *radio_api;

I had tried adding this to the device tree, but more is needed.

&nbu_802154_channel {
status = "okay";
};

chosen {
zephyr,ieee802154 = <&nbu_802154_channel>;
};

These were added to prj.conf

CONFIG_CRYPTO=y
CONFIG_MBEDTLS=y
CONFIG_NETWORKING=y
CONFIG_SHELL=y
CONFIG_UART_CONSOLE=y
CONFIG_NET_L2_IEEE802154=y
CONFIG_NET_L2_OPENTHREAD=y
CONFIG_OPENTHREAD_FTD=y
CONFIG_OPENTHREAD_MTD=n
CONFIG_OPENTHREAD_COPROCESSOR_RCP=n
CONFIG_OPENTHREAD_COPROCESSOR_NCP=n
CONFIG_OPENTHREAD_THREAD_VERSION_1_4=y

Thanks

Re: RW612 and Thread FTD

Ricardo_Zamora — Wed, 07 May 2025 20:10:14 GMT

Hello,

I apologize, but currently there is no support for this MCU.

I would recommend checking official channels from OT and Zephyr to check availability and support.

Best Regards,

Ricardo

Re: RW612 and Thread FTD

joanou — Wed, 07 May 2025 21:05:14 GMT

Thanks for this information. So Zephyr (or OT) community is the appropriate organization to implement OT FTD? Anyone else? I would have thought NXP would drive this. I will review the FreeRTOS implementation.

Following up from earlier, will source code for rw61x_sb_ble_15d4_combo_a2.bin be available anytime soon? This could help interface and optimize the implementation for the application?

Regards, Steve

Re: RW612 and Thread FTD

Ricardo_Zamora — Fri, 09 May 2025 17:24:25 GMT

Hello Steve,

NXP works on these repositories, so the support is updated there.

For other wireless protocols, the FW for the radio is used and integrated on the application. We do not offer the source code for these binaries.

Regards,

Ricardo

Re: RW612 and Thread FTD

joanou — Wed, 11 Jun 2025 17:29:16 GMT

Hi,

Most of the code works now except the Openthread running as FTD which is most important.

Would you have an idea when the ieee802.15.4 node will be in the device tree and enabled in Zephyr so that a Openthread FTD can operate? I added the question last month to Zephyr Discord, but there was no response.

https://discord.com/channels/720317445772017664/1032993479061667900

The company project is blocked unfortunately. If I knew how to do this, I would implement it. I am perplexed since this seems so fundamental to the purpose of this part.

Is there someone or group I can work with to get the ieee802.15.4 node into the device tree and into Zephyr for this RW612 part?

Thanks!