Inquiry about Matter commissioning failure with FRDM-RW612 and chip-tool

[Nokhysh]

Dear NXP Support,

I am currently testing Matter with the FRDM-RW612 board and NXP Matter SDK. However, I encountered an issue where commissioning fails when using chip-tool.

Environment

• Hardware: FRDM-RW612, USB Type-C cable, Windows 11 (64bit) PC

• Software:

  • WSL2 (Ubuntu 22.04.5 LTS)

  • SEGGER J-Link (Windows, Linux)

  • Matter source: project-chip/connectedhomeip (latest release)

• Build:

  • Built examples/all-clusters-app/nxp/rt/rw61x with chip_enable_wifi=true

  • Programmed the board via JLink + GDB

Steps performed

• Flashed FRDM-RW612 successfully and confirmed it boots

• Executed chip-tool pairing ble-wifi <node_id> <SSID> <PASS> <pin_code> <discriminator>

Issue

• The commissioning fails with the following error:

src/platform/Linux/BLEManagerImpl.cpp:695: Ble Error 0x00000401: BLE adapter unavailable

• Running bluetoothctl also shows that Bluetooth is not available inside WSL2.

Questions

1. Is it correct that commissioning with chip-tool is not possible under WSL2 because BLE is not available?

2. If I switch to a native Linux (Ubuntu) environment instead of WSL2, will it be possible to use chip-tool with BLE commissioning from the PC?

I would greatly appreciate your confirmation and guidance on this matter.

Best regards,
Naoki　Hayashi

[Nokhysh]

Hi, @Christine_Li 

Thank you for your update.

I would like to send you the executable binary, but unfortunately, the file is too large to attach to this email.

Would it be possible for you to provide an email address to which I can send it directly, perhaps via a file-sharing service?

Also, please note that I have not generated the .srec file. Please let me know if this is required.

Thank you for your understanding.

Best regards,
Naoki.

[Christine_Li]

Hi, @Nokhysh 

Thanks for your updates.

I have tried on my side, with Android phone(install CHIP-Tool application) and FRDM-RW612 (flash the chip-rw61x-all-cluster-example.srec with J-Link Commander V7.96) and I can commission successfully.

Where are you using chip-tool? on WSL? or Linux? or on RW612?

What do you input for this command:

chip-tool pairing ble-wifi <node_id> <SSID> <PASS> <pin_code> <discriminator>

In this command:

• <node_id> is the user-defined ID of the node being commissioned.
• <ssid> and <password> are credentials of Wi-Fi
• <pin_code> and <discriminator> are device-specific keys 

I just feel confused, because I am using Chip Tool application on my Android phone.

If you want to do commissioning on FRDMRW612, you need to use one Android phone(install CHIP Tool App)to help.

This chip-tool is used on Linux which support matter such as our IW612(on Linux platform), and I think the error showing in your side: it means the BLE adapter is unavailable on your WSL, but not mean the BLE is unavailable on FRDM-RW612 side.

Best regards,

Christine.

[Nokhysh]

Hi, @Christine_Li 

Thank you for your support with the commissioning process.

Can commissioning only be done with the chip-rw61x-all-cluster-example.srec file?
My build process only produced chip-rw61x-all-cluster-example.bin and chip-rw61x-all-cluster-example.hex files.

For my reference, could you please share the procedure you used for flashing the board with J-Link Commander?

I am running chip-tool in a WSL environment. The command I'm using is as follows: ./out/chip-tool/chip-tool pairing ble-wifi 0x11 <SSID> <PASS> 20202021 3840

I also tried to verify the process with an Android smartphone that has the CHIP Tool app installed, but commissioning failed. I will try again with a different RW612 board that is known to be working.

I understand now that the BLE adapter is unavailable in the WSL environment.
Thank you for clarifying.

Best regards,
Naoki.

[Christine_Li]

Hi, @Nokhysh 

Thanks for your reply.

To use J-Link to flash, below is my steps:

reset
halt
loadfile chip-rw61x-all-cluster-example.srec
reset
go

Please see below screenshot for better understanding my steps:

And：

My build process only produced chip-rw61x-all-cluster-example and chip-rw61x-all-cluster-example.hex files.

For chip-rw61x-all-cluster-example.hex， to use it in a different format, change the file extension from .hex to .srec, resulting in the new file name: chip-rw61x-all-cluster-example.srec

Then use loadfile command to flash it through j-Link to our FRDM-RW612 board.

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

Best regards,

Christine.

[Nokhysh]

Hi, @Christine_Li 

Sorry for the follow-up question.

After reviewing Part 1 of the video at the link below, this video is trying to commission the device by scanning the QR code output in TeraTerm with the CHip-tool app on an Android device.
Is this the correct commissioning method?

https://www.nxp.jp/company/about-nxp/smarter-world-blog/BL-MATTER-ECOSYSTEM-FRDM-RW612-FRDM-MCXW71

In my environment, when I press the RESET button, nothing is output to the UART.

I believe the settings I'm using are correct.

Best Regards,
Naoki.

[Christine_Li]

Hi, @Nokhysh 

For your question 1: could not find device 3840:

Have you ever do matterfactoryreset before commission?

Can you please try to  do matterfactoryreset before commission, then try to commission again to see whether still repro this issue?

Connect the RW612 FRDM evaluation board console and enter the command to reset.
> matterfactoryreset
This command can help FRDM-RW612 do saved parameters reset.

2.For your question 2: could not see QR code:

The output is in another UART.

Please see the testing the example part in the link:

matter/docs/platforms/nxp/nxp_rw61x_guide.md at v1.4.0.2.1 · NXP/matter · GitHub

Testing the example 

UART details

Testing the example with the CLI enabled will require connecting to UART1 and UART2, here are more details to follow for RW61x platform :

• UART1 : Flexcomm3. To view output on this UART, a USB cable could be plugged in.
• UART2 : Flexcomm0. To view output on this UART, a pin should be plugged to an USB to UART adapter.
  • For [NXP RD-RW612-BGA] board, use connector HD2 pin 03.
  • For [NXP FRDM-RW612] board, use J5 pin 4 (mikroBUS: TX).

I tested it locally, and it can output, also if i copy it to the browser, i can see the QR code.

Best regards,

Christine.

[Nokhysh]

Hi, @Christine_Li 

Thank you for your advice.

I have configured the Matter CLI to use the matterfactoryreset command.
However, I am unable to input commands into the CLI from Tera Term.
(I am not getting the ">" prompt either.)

Could there be an error in my connection or configuration?

RW612: TX, GND
USB to UART: RXD, GND
https://www.amazon.co.jp/dp/B01CYBHM26?

Also, after successfully commissioning with chip-tool, is it possible to debug the source code to check its behavior?
https://github.com/NXP/matter/tree/v1.4.0.1.1/examples/all-clusters-app/nxp/rt/rw61x

Best Regards,
Naoki.

[Christine_Li]

Hi， @Nokhysh 

Please check my previous reply, there is a photo showing how to connect USB to UART adapter with FRDM-RW612.

And you can input command in UART1: this port is directly connected with TYPE-C cable with your PC. And also you are using J-LINK Commander with this port. With this port, you can see ">", and also using this port to input "matterfactoryreset" command.

You can see outputs in UART2: this port is connecting to USB-TO-UART with dupont line， then connect to your PC.

I paster the photo here again for your reference.

USB-TO-UART side:          FRDM-RW612 side:

VCC-------------------J5 PWM

TX ---------------------RX 

RX----------------------TX

GND--------------------GND

If still there is no any output in UART2 port, you can reset FRDM-RW612 board by pressing SW1 button(Reset Button).

After reset board, if still failed, you can have a try with my .srec file. It can help you to check whether the issue is from your compiling side, or from connecting side.

Also, after successfully commissioning with chip-tool, is it possible to debug the source code to check its behavior?

==>The examples are given for your reference, and you build it on WSL or Linux, so if you want to debug, it is better to use MCUxpresso for VS code or directly use MCUXpresso like the link you paste.

Best regards,

Christine.

[Nokhysh]

Hi, @Christine_Li .

I connected the board with the configuration you provided and performed a reset,
but nothing is being output to the UART.

When I tried to write the SREC file you sent using J-Link, it failed with the following error:

****** Error: Verification failed @ address 0x08000000 Error while programming flash: Verify failed.

I attempted to resolve the error by following the steps on the site below, but it seems I am unable to erase the flash.
https://community.nxp.com/t5/Wi-Fi-Bluetooth-802-15-4/How-to-solve-flashing-problems-in-FRDM-RW612-f...

I will create a separate post regarding this issue.
Could you please provide a solution?
https://community.nxp.com/t5/MCUXpresso-Secure-Provisioning/quot-Write-Image-quot-fails-at-quot-Eras...

Best Regards,
Naoki.

[Christine_Li]

Hi, @Nokhysh 

The new issue ""Write Image" fails at "Erase Flash" step in FRDM-RW612" is dealing by our colleague. I believe he can provide a solution to you.

Once that issue is resolved, please continue to verify this current case.

Please let me know if you still need my help on this case.

Best regards,

Christine.

[Nokhysh]

Hi, @Christine_Li

Thank you for showing me the steps to flash the device.

Following the procedure, I renamed chip-rw61x-all-cluster-example.hex to chip-rw61x-all-cluster-example.srec and was able to load it using J-Link Commander v8.54 (J-Link).

After pressing the SW2 button on the RW612 to enable advertising, I started the commissioning process on an Android tablet with Chip-Tool installed. However, it fails with the message "BLE Device 3840 not found."

Are there any errors or missing steps in my procedure?

Best Regards,
Noaki.

[Nokhysh]

Hi, @Christine_Li 

Apologies, I'm having difficulty verifying the RW612 at the moment.
While testing the BLE sample with the RW612, I encountered an issue where I cannot write to the flash.
This problem also occurs with other samples, preventing me from proceeding.

Regarding the MCUXpresso IDE repository, I was unable to select the Matter repository, so I flashed the device using J-Link instead.

The method described on the following site does not work in a WSL environment,
so I did some research and used the following procedure to flash the device.

matter/docs/platforms/nxp/nxp_rw61x_guide.md at v1.4.0.2.1 · NXP/matter · GitHub

On Windows

1. Connect the FRDM-RW612 to the PC with a USB-Type C cable.

2. Launch the J-Link Remote Server.

3. Check the USB option.

4. The server will now be waiting for a connection.

On WSL2 (Windows Subsystem for Linux 2)

The following steps are performed in the WSL2 terminal.

1. Find your Windows host's IP address (e.g., using ipconfig in CMD or by checking your network settings).

2. Launch the JLinkGDBServer. By using the -select ip startup option, it will connect to the J-Link Remote Server running on the host IP address, rather than a J-Link connected via USB.

   JLinkGDBServer -select ip=<IP_ADDRESS> -if swd -device RW612

3. The J-Link Remote Server on the host will now indicate that a client has connected. You will see the following output:

   SEGGER J-Link GDB Server V8.54 Command Line Version
   
   JLinkARM.dll V8.54 (DLL compiled Jul 23 2025 12:23:37)
   
   Command line: -select ip=<IP_ADDRESS> -if swd -device RW612
   -----GDB Server start settings-----
   GDBInit file:                   none
   GDB Server Listening port:      2331
   SWO raw output listening port:  2332
   Terminal I/O port:              2333
   Accept remote connection:       yes
   Generate logfile:               off
   Verify download:                off
   Init regs on start:             off
   Silent mode:                    off
   Single run mode:                off
   Target connection timeout:      0 ms
   ------J-Link related settings------
   J-Link Host interface:          IP
   J-Link script:                  none
   J-Link settings file:           none
   ------Target related settings------
   Target device:                  RW612
   Target device parameters:       none
   Target interface:               SWD
   Target interface speed:         4000kHz
   Target endian:                  little
   
   Connecting to J-Link...
   J-Link is connected.
   Firmware: J-Link MCU-Link V1 compiled Jul  8 2025 10:15:43
   Hardware: V1.00
   S/N: 1060644884
   Checking target voltage...
   Target voltage: 3.30 V
   Listening on TCP/IP port 2331
   Connecting to target...
   Halting core...
   Core security extensions: Implemented
   Connected to target
   Waiting for GDB connection...

Connecting and Flashing with GDB

1. Connect to the JLinkGDBServer from GDB. Specify the output file generated by your build as an argument.

   cd ~/connectedhomeip/examples/all-clusters-app/nxp/rt/rw61x/out/debug/
   arm-none-eabi-gdb chip-rw61x-all-cluster-example

2. In the GDB prompt, execute the following command to connect to the server (the listening port is 2331 as shown in the log).

   (gdb) target remote localhost:2331

   This will connect GDB to J-Link and allow for debugging.

3. To flash the application using GDB, run the following commands:

(gdb) load
(gdb) info files​

Best Ragards,

Noaki.

[Nokhysh]

Hi, @Christine_Li 

I will use another RW612 to check the operation of the BLE sample.

Best Ragards,
Noaki.

[Christine_Li]

Hi, @Nokhysh 

Thanks for your reply.

These days I finished compiling and started to test.

But after loadfile my: chip-rw61x-all-cluster-example.srec to the FRDM-RW612, I could not see any prints in the console. I suspect that there is something wrong on my side.

Could you please share your chip-rw61x-all-cluster-example.srec file and chip-rw61x-all-cluster-example file to me, so that I can have a try on my side?

I am still tracking what happened on my side. The compiling is successful and flashed successfully also.

Best regards,

Christine.

[Nokhysh]

Hi, @Christine_Li 

I have confirmed the operation by following the GitHub ReadMe at the link below: https://github.com/NXP/matter/tree/v1.4.0.1.1/examples/all-clusters-app/nxp/rt/rw61x

Understood. I will test your company's BLE sample on the FRDM-RW612 board.
I apologize for the trouble, but I would appreciate your confirmation.

Best regards,
Naoki Hayashi.

[Christine_Li]

Hi， @Nokhysh 

Can the BLE example work on your side?

I tried on my side and prefer to know what repo do you choose, when you refer to this step:
“

• Import the connectedhomeip repo in MCUXpresso IDE as Makefile Project. Use none as Toolchain for Indexer Settings:

”

Best regards，

Christine.

[Christine_Li]

Hi， @Nokhysh 

By the way, are you using J-Link to flash the example app? Or using MCUXpresso IDE to flash?

You can refer to below guide to flash with JLink to have a try. To see whether still have this issue.

matter/docs/platforms/nxp/nxp_rw61x_guide.md at v1.4.0.2.1 · NXP/matter · GitHub

If still have same issue, please let me know. 

Best regards,

Christine.

[Christine_Li]

Hi， @Nokhysh 

Sorry for my delay reply. I am dealing case with priority.

What is your SDK version? I will check it on my side.

At the same time, would you please firstly check the BLE feature whether work? 

Matter will reply on BLE feature, if BLE doesn't work, Matter could not commissioning successfully.

You can check with our BLE examples firstly on FRDM-RW612 to confirm BLE works fine. 

If BLE could not work as expected, please let me know which example could not work and share to me the failed logs.

Best regards,

Christine.

[Christine_Li]

Hi, @Nokhysh 

I will check and reply to you ASAP.

Best regards,

Christine.