From: Jeff Chen <jeff.chen_1@nxp.com>
To: Martyn Welch <martyn.welch@collabora.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"briannorris@chromium.org" <briannorris@chromium.org>,
"johannes@sipsolutions.net" <johannes@sipsolutions.net>,
"francesco@dolcini.it" <francesco@dolcini.it>,
Pete Hsieh <tsung-hsien.hsieh@nxp.com>,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
Brian Hsu <brian.hsu@nxp.com>
Subject: RE: [EXT] Re: [PATCH v5 00/22] wifi: nxpwifi: create nxpwifi to support iw61x
Date: Mon, 13 Oct 2025 18:18:45 +0000 [thread overview]
Message-ID: <DBBPR04MB7740C33F56C41373CE6641109CEAA@DBBPR04MB7740.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <7c3e9c5a-2f1f-44e7-9c99-2f0a173bd8eb@collabora.com>
Hi Martyn,
Thanks again for your detailed feedback and testing.
From what you've described, this issue doesn't appear to be caused by the
nxpwifi driver itself. The Wi-Fi side seems to be functioning correctly.
To simplify things and avoid firmware loading conflicts, I recommend using
the Wi-Fi-only firmware with the nxpwifi driver, and letting the btnxpuart
driver handle its own Bluetooth firmware loading.
Also, I've looped in Neeraj and Amit, who are the maintainer of the btnxpuart
driver.
From your BT-only scenario logs:
We can confirm that the host-to-chip communication is working correctly, and the
firmware download completes successfully. This rules out hardware issues and
confirms that the UART link is functional. The problem seems to occur during HCI initialization,
where the btnxpuart driver reports repeated Frame reassembly failed (-84) errors.
We suggest that to debug this quickly, it would be very helpful if you could capture the UART
lines (TX/RX/CTS/RTS) using a logic analyzer (e.g., Saleae) and share the trace. This would allow
us to inspect what's happening on the wire and identify the root cause of the
"Frame Reassembly Failed" error. There are affordable logic analyzers compatible with Saleae
software, such as:
https://www.amazon.in/Robodo-Electronics-USBLA24M-Analyser-Compatible/dp/B07B8KHYDD?source=ps-sl-shoppingads-lpcontext&ref_=fplfs&psc=1&smid=AJ6SIZC8YQDZX
best regards,
Jeff
> -----Original Message-----
> From: Martyn Welch <martyn.welch@collabora.com>
> Sent: Saturday, October 11, 2025 12:22 AM
>
> On 09/10/2025 17:01, Jeff Chen wrote:
> > On Tue, Oct 07, 2025 at 05:49:59 PM +0100, Martyn Welch wrote:
> >> This seems to be working well for me, at least for Wifi. I'd like to
> >> get Bluetooth up as well. The bluetooth driver (btnxpuart) doesn't
> >> seem happy loading the bluetooh firmware:
> >
>
> Yes, I'm currently using the wifi only firmware. If I'm not mistaken, that's the
> only firmware that the NXPWifi driver will currently use. It appears that it
> should be able to load `firmware_sdiouart`, but that doesn't appear to be set
> anywhere and thus it's not considered. I tried to rename the combo firmware
> to have the name used for the wifi only firmware, but that was failing for me
> (more about that in a moment).
>
> > To help us reproduce and investigate further, could you please share:
> > - Your test platform (SoC, board, etc.)
>
> Custom board based on Renesas RZ-G2L, using Ezurio Sona NX611 M.2 1216
> module.
>
> Kernel is 6.17 with an added custom DT, a few patches for other hardware and
> the NXPWifi patch series.
>
> Both btnxpuart and nxpwifi are built as modules.
>
> The firmware itself is what Ezurio provide in their Yocto layer:
>
> $ md5sum *
> 6a9307d27c3bdb3bde800265056ab217 sd_w61x_v1.bin.se
> 8a28ec7f1b77dbde0ac7568d0426c669 sduart_nw61x_v1.bin.se
> d38935f03dbe6da7a9ac3daf58e640bf uartspi_n61x_v1.bin.se
>
>
> Looking a bit deeper, if I try and load the combined firmware, the bluetooth
> modules attempts to load before the WiFi driver has had a chance to complete
> loading the firmware which is resulting in the firmware failing.
>
> If I blacklist the btnxpuart module (and rename the combo firmware), it loads:
>
> > - Your test steps
>
> At the moment, booting and checking to see if the hardware has probed.
> If it has, ensure I can connect to my wifi network and ensure that I can pass a
> little bit of traffic.
>
> > - The exact firmware version you're using
>
> As above.
>
> > Also, have you tried running Bluetooth in a BT-only scenario (without
> > loading the Wi-Fi driver)? Does that work correctly?
> >
>
> I hadn't. Just gave that a go and I seem to be getting the same failure (though :
>
> $ sudo dmesg | grep hci0
> [ 40.859055] Bluetooth: hci0: ChipID: 7601, Version: 0
> [ 40.889487] Bluetooth: hci0: Request Firmware:
> nxp/uartspi_n61x_v1.bin.se
> [ 42.850682] Bluetooth: hci0: FW Download Complete: 396444 bytes
> [ 42.850736] Bluetooth: hci0: Frame reassembly failed (-84)
> [ 44.222243] Bluetooth: hci0: Frame reassembly failed (-84)
> [ 44.230226] Bluetooth: hci0: Frame reassembly failed (-84)
> [ 44.237480] Bluetooth: hci0: Frame reassembly failed (-84)
> [ 44.247567] Bluetooth: hci0: Frame reassembly failed (-84)
> [ 44.254188] Bluetooth: hci0: Frame reassembly failed (-84)
> [ 44.263459] Bluetooth: hci0: Frame reassembly failed (-84)
> [ 44.269814] Bluetooth: hci0: Frame reassembly failed (-84)
> [ 46.280494] Bluetooth: hci0: Opcode 0x1002 failed: -110
> [ 46.285835] Bluetooth: hci0: command 0x1002 tx timeout
>
> Are there any BT patches that I'm missing?
>
> Martyn
>
> > Thanks,
> > Jeff
next prev parent reply other threads:[~2025-10-13 18:18 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-04 15:39 Jeff Chen
2025-08-04 15:39 ` [PATCH v5 01/22] wifi: nxpwifi: add 802.11n files Jeff Chen
2025-09-04 11:22 ` Johannes Berg
2025-08-04 15:39 ` [PATCH v5 02/22] wifi: nxpwifi: add 802.11ac files Jeff Chen
2025-08-04 15:39 ` [PATCH v5 03/22] wifi: nxpwifi: add 802.11ax files Jeff Chen
2025-08-04 15:40 ` [PATCH v5 04/22] wifi: nxpwifi: add 802.11h file Jeff Chen
2025-08-04 15:40 ` [PATCH v5 05/22] wifi: nxpwifi: add WMM files Jeff Chen
2025-08-04 15:40 ` [PATCH v5 06/22] wifi: nxpwifi: add scan.c Jeff Chen
2025-08-04 15:40 ` [PATCH v5 07/22] wifi: nxpwifi: add join.c Jeff Chen
2025-08-04 15:40 ` [PATCH v5 08/22] wifi: nxpwifi: add cfp.c Jeff Chen
2025-08-04 15:40 ` [PATCH v5 09/22] wifi: nxpwifi: add configuration files Jeff Chen
2025-08-04 15:40 ` [PATCH v5 10/22] wifi: nxpwifi: implement cfg80211 ops Jeff Chen
2025-08-04 15:40 ` [PATCH v5 11/22] wifi: nxpwifi: add host command file Jeff Chen
2025-08-04 15:40 ` [PATCH v5 12/22] wifi: nxpwifi: add command and event files Jeff Chen
2025-08-04 15:40 ` [PATCH v5 13/22] wifi: nxpwifi: add data path files Jeff Chen
2025-08-04 15:40 ` [PATCH v5 14/22] wifi: nxpwifi: add debugfs file Jeff Chen
2025-08-04 15:40 ` [PATCH v5 15/22] wifi: nxpwifi: add ethtool.c Jeff Chen
2025-08-04 15:40 ` [PATCH v5 16/22] wifi: nxpwifi: add utility files Jeff Chen
2025-08-04 15:40 ` [PATCH v5 17/22] wifi: nxpwifi: add initialization file Jeff Chen
2025-08-04 15:40 ` [PATCH v5 18/22] wifi: nxpwifi: add core files Jeff Chen
2025-09-04 11:37 ` Johannes Berg
2025-09-19 18:06 ` Jeff Chen
2025-10-01 10:17 ` Jeff Chen
2025-10-01 10:19 ` Johannes Berg
2025-08-04 15:40 ` [PATCH v5 19/22] wifi: nxpwifi: add sdio bus driver files Jeff Chen
2025-08-04 15:40 ` [PATCH v5 20/22] wifi: nxpwifi: modify sdio_ids.h Jeff Chen
2025-08-04 15:40 ` [PATCH v5 21/22] wifi: nxpwifi: add makefile and kconfig files Jeff Chen
2025-08-04 15:40 ` [PATCH v5 22/22] wifi: nxpwifi: modify MAINTAINERS file Jeff Chen
2025-09-04 11:39 ` [PATCH v5 00/22] wifi: nxpwifi: create nxpwifi to support iw61x Johannes Berg
2025-10-07 16:49 ` Martyn Welch
2025-10-09 16:01 ` Jeff Chen
2025-10-10 16:22 ` Martyn Welch
2025-10-13 18:18 ` Jeff Chen [this message]
2025-10-14 10:20 ` [EXT] " Martyn Welch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DBBPR04MB7740C33F56C41373CE6641109CEAA@DBBPR04MB7740.eurprd04.prod.outlook.com \
--to=jeff.chen_1@nxp.com \
--cc=brian.hsu@nxp.com \
--cc=briannorris@chromium.org \
--cc=francesco@dolcini.it \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=martyn.welch@collabora.com \
--cc=s.hauer@pengutronix.de \
--cc=tsung-hsien.hsieh@nxp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®