topic Re: FRDM-RW612 - Zephyr connection management of Ethernet/Wifi in Wi-Fi® + Bluetooth® + 802.15.4

FRDM-RW612 - Zephyr connection management of Ethernet/Wifi

adrianburns1 — Sun, 12 Oct 2025 18:28:58 GMT

Hi,

Im looking to create a Zephyr application (on or chip) to connect to a server (mqtt or coap) over Ethernet or Wifi. When Eth (primary comms) is plugged IN, it should use Eth and when Eth is plugged OUT, it should fallback to Wifi (secondary comms). I have a FRDM-RW612 now and a ublox EVK-IRIS-W106-RW612 (with RW612 inside module). I was looking for a Zephyr sample app that would be the best starting point. Its looking like i need to use the conn_mgr component in Zephyr but is there a good starting app (or appnote) in either Zephyr or MCUXpresso SDK that does this already ? uhttps://docs.zephyrproject.org/latest/connectivity/networking/conn_mgr/main.h

When i get the Eth/Wifi done, i will add LTE/4G as another network interface.

thanks

Re: FRDM-RW612 - Zephyr connection management of Ethernet/Wifi

Christine_Li — Mon, 13 Oct 2025 02:34:31 GMT

Hi, @adrianburns1

Please see this user guide:

UM12035: Getting Started with RW61x Running Zephyr OS

Hope it can help you somehow.

Best regards,

Christine.

Re: FRDM-RW612 - Zephyr connection management of Ethernet/Wifi

adrianburns1 — Mon, 13 Oct 2025 08:02:32 GMT

Hi @Christine_Li ,

Had gone through that alright and its a good start for getting zephyr running. But i was looking for more demo apps for multi-connectivity (eth/wifi/ble) and secure OTA of app, wifi and ble cpu's as the multi-radio aspect is whats attractive about this chip. Maybe im better using the mcuxpresso sdk examples on FreeRTOS to start as its more mature than zephyr?

Thanks for your quick response

Re: FRDM-RW612 - Zephyr connection management of Ethernet/Wifi

adrianburns1 — Mon, 13 Oct 2025 15:53:43 GMT

Also, @Christine_Li ,

when going through the doc (page 23) https://www.nxp.com/docs/en/user-manual/UM12035.pdf

the "nxp_wifi add" command says unknown command, same for all other nxp_wifi commands apart from the scan command

using the standard "wifi" commands rather than the "nxp_wifi" commands seems to work ok but i couldnt get the nxp_wifi ones to work as per the document, see below the serial terminal output and the version of zephyr im using (tip of tree as per today)

uart:~$ nxp_wifi version
WLAN Driver Version : v1.3.r52.z_up.p4
WLAN Firmware Version : rw610w-V2, IMU, FP99, 18.99.6.p41, PVE_FIX 1
Command wlan-version
uart:~$ nxp_wifi add test1 ssid xxxxxxxxxx psk xxxxxxxxxx
Unknown comamnd add
uart:~$

My version of zephyr is as follows (just mainline tip of tree as of today):

(.venv) ado@ado:~/zephyrproject/zephyr$ git status
On branch main
Your branch is up to date with 'origin/main'.

nothing to commit, working tree clean
(.venv) ado@ado:~/zephyrproject/zephyr$ git log
commit 4b3cb736d5fb6de21b614c833a65a99700b61594 (HEAD -> main, tag: help, origin/main, origin/HEAD)
Author: Firas Sammoura <fsammoura@google.com>
Date: Mon Oct 6 23:46:46 2025 +0000

Re: FRDM-RW612 - Zephyr connection management of Ethernet/Wifi

Christine_Li — Wed, 15 Oct 2025 09:08:04 GMT

Hi， @adrianburns1

I setup Zephyr environment on my Windows, and tried to import an example from repository, I found that currently it only support rd_rw612_bga, but not support FRDM_RW612.

Sorry for the inconvenience to you.

If you want to use RW612 on Zephyr OS, you can think about our rd_rw612_bga board.

Best regards,

Christine.

Re: FRDM-RW612 - Zephyr connection management of Ethernet/Wifi

adrianburns1 — Wed, 15 Oct 2025 10:19:37 GMT

Hi @Christine_Li

Not sure i understand, I can build samples onto the board with upstream zephyr v4.2.1 (on linux command line or mcuxpresso extension in VS code). Ethernet and Wifi works on frdm_rw612 board with zephyr release v4.2.1 (there are issues with Ethernet on mainline latest code)

Here is supported board info

https://docs.zephyrproject.org/latest/boards/nxp/frdm_rw612/doc/index.html

And ublox modue containing rw612

https://docs.zephyrproject.org/latest/boards/u-blox/ubx_evk_iris_w1/doc/index.html

Re: FRDM-RW612 - Zephyr connection management of Ethernet/Wifi

Christine_Li — Thu, 16 Oct 2025 09:49:56 GMT

Hi, @adrianburns1

Thanks for reply.

Oh, I think the difference between us is because of the Zephyr version.

You are using Zephyr v4.2.1 is newer than me.

Let me update version, then check further and share with you.

Best regards,

Christine.

Re: FRDM-RW612 - Zephyr connection management of Ethernet/Wifi

Christine_Li — Wed, 22 Oct 2025 07:45:51 GMT

Hi， @adrianburns1

Yes, you are right. After I update my Zephyr version, I can choose FRDM-RW612.

Thanks for providing me your Zephyr version.

Which example do you import?

Best regards,

Christine.

Re: FRDM-RW612 - Zephyr connection management of Ethernet/Wifi

Christine_Li — Wed, 22 Oct 2025 09:37:19 GMT

Hi， @adrianburns1

Are you using shell example?

When I compile it, it reports: could not find Firmware.

I think our git log is different.

PS C:\Zephyr\zephyr> git log commit 64e98eb5278d790f3b3e5279ca8b39b45097bbc0 (HEAD, tag: v4.2.1) Author: Daniel DeGrasse <ddegrasse@tenstorrent.com> Date: Fri Oct 3 14:02:58 2025 -0500 release: Zephyr v4.2.1 Set the version to v4.2.1 Signed-off-by: Daniel DeGrasse <ddegrasse@tenstorrent.com> Signed-off-by: Dan Kalowsky <dkalowsky@amperecomputing.com>

Can you please share to me your firmware, from: Zephyr\modules\hal\nxp\zephyr\blobs\rw61x\rw61x_sb_wifi_a2.bin

So that I can reproduce your issue and debug further?

On my side, here, there is no rw61x_sb_wifi_a2.bin, so I could not load firmware successfully even I copy one FW from our MCUXpresso IDE SDK 25.09.

uart:~$ [wifi_io] Error: Download firmware failed [wifi] Error: imu_wifi_init failed. status code -1 [wlcm] Error: wifi init/reinit failed. status code -1 [00:12:44.509,098] <err> nxp_wifi: wlan initialization failed *** Booting Zephyr OS build v4.2.1 *** uart:~$ uart:~$ uart:~$ uart:~$ wifi version Failed to get Wi-Fi versions [00:13:22.304,348] <err> nxp_wifi: Failed to get Wi-Fi driver/firmware version uart:~$

Best regards,

Christine.

Re: FRDM-RW612 - Zephyr connection management of Ethernet/Wifi

Christine_Li — Wed, 22 Oct 2025 09:35:30 GMT

Hi, @adrianburns1

Maybe i'm better using the mcuxpresso sdk examples on FreeRTOS to start as its more mature than zephyr?

==>Yes, you are right. Mcuxpresso sdk examples on FreeRTOS is more mature than Zephyr.

Best regards,

Christine.

Re: FRDM-RW612 - Zephyr connection management of Ethernet/Wifi

Christine_Li — Thu, 23 Oct 2025 09:47:06 GMT

Hi, @adrianburns1

Even I did "west blobs fetch hal_nxp", I still could not get firmware.

Please help to share your firmware, then I can have a try on my side.

Or you can share the whole "Zephyr\modules\hal\nxp" nxp directory to me.

C:\Zephyr420>west blobs fetch hal_nxp Fetching blob hal_nxp: C:\Zephyr420\modules\hal\nxp\zephyr\blobs\iw612\uart_nw61x_se.h Fetching blob hal_nxp: C:\Zephyr420\modules\hal\nxp\zephyr\blobs\rw61x\rw61x_sb_ble_15d4_combo_a2.bin ERROR: An error occurred: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))

And for your information, if it is not necessary for you to choose Zephyr, I will strongly recommend you to use the mcuxpresso sdk examples on FreeRTOS. It is more mature than zephyr.

Please let me know your decisions.

Best regards,

Christine.

Re: FRDM-RW612 - Zephyr connection management of Ethernet/Wifi

Christine_Li — Wed, 29 Oct 2025 07:04:26 GMT

Hello, @adrianburns1

Finally, I do "west blobs fetch hal_nxp" successfully.

Now I can reproduce you issue locally.

And yes, you are right, it says unknown command for "nxp_wifi add".

Thank you for pointing this, we will take your concerns and escalate it to our internal team for correcting this in our https://www.nxp.com/docs/en/user-manual/UM12035.pdf.

But if you want to connect to an AP, please use "wifi connect" command.

I give you an example for your reference as below:

uart:~$ wifi connect -s Christine -k 1 -p Aa_123456 Connection requested board_type: 2, board_type mapping: Connected 0----QFN 1----CSP 2----BGA [00:xx:xx.xxx,936] <inf> net_dhcpv4: Received: 192.168.xx.xx uart:~$ wifi status Status: successful ================== State: COMPLETED Interface Mode: STATION Link Mode: WIFI 6 (802.11ax/HE) SSID: Christine BSSID: xx:xx:xx:xx:xx:xx Band: 2.4GHz Channel: 6 Security: WPA2-PSK MFP: Optional RSSI: -30 Beacon Interval: 100 DTIM: 0 TWT: Not supported Current PHY TX rate (Mbps) : 86 uart:~$

Below is the parameter's explanation for wifi connect:

connect - Connect to a Wi-Fi AP <-s --ssid "<SSID>">: SSID. [-c --channel]: Channel that needs to be scanned for connection. 0:any channel. [-b, --band] 0: any band (2:2.4GHz, 5:5GHz, 6:6GHz] [-p, --passphrase]: Passphrase (valid only for secure SSIDs) [-k, --key-mgmt]: Key Management type (valid only for secure SSIDs) 0:None, 1:WPA2-PSK, 2:WPA2-PSK-256, 3:SAE-HNP, 4:SAE-H2E, 5:SAE-AUTO, 6:WAPI,7:EAP-TLS, 8:WEP, 9: WPA-PSK, 10: WPA-Auto-Personal, 11: DPP 12: EAP-PEAP-MSCHAPv2, 13: EAP-PEAP-GTC, 14: EAP-TTLS-MSCHAPv2, 15: EAP-PEAP-TLS, 20: SAE-EXT-KEY [-w, --ieee-80211w]: MFP (optional: needs security type to be specified) : 0:Disable, 1:Optional, 2:Required. [-m, --bssid]: MAC address of the AP (BSSID). [-t, --timeout]: Timeout for the connection attempt (in seconds). [-a, --anon-id]: Anonymous identity for enterprise mode. [-K, --key1-pwd for eap phase1 or --key2-pwd for eap phase2]: Private key passwd for enterprise mode. Default no password for private key. [-S, --wpa3-enterprise]: WPA3 enterprise mode: Default 0: Not WPA3 enterprise mode. 1:Suite-b mode, 2:Suite-b-192-bit mode, 3:WPA3-enterprise-only mode. [-T, --TLS-cipher]: 0:TLS-NONE, 1:TLS-ECC-P384, 2:TLS-RSA-3K. [-A, --verify-peer-cert]: apply for EAP-PEAP-MSCHAPv2 and EAP-TTLS-MSCHAPv2 Default 0. 0:not use CA to verify peer, 1:use CA to verify peer. [-V, --eap-version]: 0 or 1. Default 1: eap version 1. [-I, --eap-id1]: Client Identity. Default no eap identity. [-P, --eap-pwd1]: Client Password. Default no password for eap user. [-R, --ieee-80211r]: Use IEEE80211R fast BSS transition connect.[-h, --help]: Print out the help for the connect command. [-i, --iface=<interface index>] : Interface index.

Hope it can help you somehow.

Any way, Mcuxpresso sdk examples on FreeRTOS is more mature than Zephyr. If Zephyr is not a must choice, you can think about Mcuxpresso sdk examples on FreeRTOS.

Please let me know whether have any other concerns on this ticket.

Best regards,

Christine.

Re: FRDM-RW612 - Zephyr connection management of Ethernet/Wifi

adrianburns1 — Wed, 29 Oct 2025 14:41:20 GMT

thanks Christine