Colibri Imx8x - AP Mode - Firmware Dump

Technical Support
, , ,
1

While testing the Toradex Colibri IMX8 WB IT 1 GB AP mode on the NXP W8997 WiFi chip, we encountered a command timeout followed by a firmware dump. You can verify this in the attached logging.

Environment

  • Device: Toradex Colibri IMX8 WB IT 1 GB
  • WiFi Chip: NXP W8997
  • ID=tdx-xwayland
  • NAME=“TDX Wayland with XWayland”
  • VERSION=“5.7.5-devel-20240220153133+build.0 (dunfell)”
  • VERSION_ID=5.7.5-devel-20240220153133-build.0
  • PRETTY_NAME=“TDX Wayland with XWayland 5.7.5-devel-20240220153133+build.0 (dunfell)”
  • DISTRO_CODENAME=“dunfell”
    • Driver Version PCIE-WLAN-USB-BT-8997-U16-X86-W16.88.10.p173-16.26.10.p173-C4X16698_V4-MGPL (proprietary NXP driver version supplied by Toradex support)

Application Usage

  • Function: Using NXP W8997 as a Soft AP
  • Device Connection Maximum of 3 devices connected
  • Bluetooth LE Hosting Used for exchanging WiFi credentials during initial setup via a mobile cross-platform tablet app (Android and iOS)
  • Testing Scenario Reconnect attempts by going out of range and then back in range using iPads and or Android device(s)

Problem Description

The problem occurred during testing with multiple reconnect attempts from our iPads. Specifically, we experienced a command timeout followed by a firmware dump when devices went out of range and then reconnected.

Configuration Details

/etc/modprobe.d/pcie8xxxx.conf

options pcie8xxx cal_data_cfg=nxp/cal_data.conf drv_mode=2 cfg80211_wext=12

/etc/modprobe.d/pcie8xxxx.conf

#blacklist mlan bt8xxx
#‘install’ mlan /bin/false
#‘install’ bt8xxx /bin/false

blacklist mwifiex mwifiex_sdio btmrvl btmrvl_sdio
install mwifiex /bin/false
install btmrvl /bin/false

/lib/systemd/network/80-uap.link

[Match]
Driver=wlan_pcie

[Link]
NamePolicy=keep kernel

/etc/hostapd.config

interface=uap0
hw_mode=a
channel=40
ieee80211n=1
ssid=XXXX-861c
own_ip_addr=192.168.98.1
wpa=2
wpa_passphrase=#%XXXXXXXXXXX4!bz
rsn_pairwise=CCMP
wpa_pairwise=CCMP

wifi-crash-journal.log (165.9 KB)
wifi-crash.log (38.8 KB)

2

Hi, I’m the Toradex AI Assistant. I’m in early beta, and I would appreciate your feedback.
The Toradex Support team will follow up with you shortly!

Did you like my answer?

:+1: :-1:

Handshake,

The issue you’re encountering with the Toradex Colibri iMX8 WB IT 1 GB module in AP mode, specifically the command timeout followed by a firmware dump, is likely related to the NXP W8997 WiFi chip’s handling of reconnect attempts under certain conditions. Given the detailed context you’ve provided, here are some steps and considerations to troubleshoot and potentially resolve the issue:

  1. Driver and Firmware Version: Ensure that the driver and firmware versions for the NXP W8997 WiFi chip are the latest provided by Toradex. It’s crucial as updates often contain fixes for stability issues, including those related to AP mode operations and device reconnections.

  2. Driver Configuration: The configuration details you’ve provided in /etc/modprobe.d/pcie8xxxx.conf suggest that you’ve blacklisted certain modules and prevented their installation. This is generally done to avoid conflicts between drivers. However, ensure that this configuration is indeed preventing any conflicting drivers from loading, which might interfere with the operation of the NXP W8997 chip in AP mode.

  3. Testing Environment: Given that the issue occurs during reconnect attempts by devices going out of range and then back in range, it’s important to consider environmental factors that might affect the WiFi signal and the chip’s ability to manage connections reliably. Testing in a different environment or adjusting the placement of the AP and client devices could provide insights into whether the issue is environment-related.

  4. Log Analysis: The firmware dump and command timeout are significant clues that there might be an underlying issue with the firmware’s handling of specific scenarios, such as rapid reconnect attempts. Analyzing the logs for any patterns or specific error messages preceding the firmware dump could help identify the root cause. Look for messages related to the WiFi chip’s state, errors in handling connections, or issues with the firmware.

  5. Alternative Configurations: Experiment with different driver and firmware configurations. For example, adjusting the drv_mode and cfg80211_wext options in the pcie8xxxx.conf file might influence the chip’s behavior in AP mode. Documentation or support from Toradex or NXP might offer insights into optimal configurations for stability in AP mode operations.

  6. Stress Testing: Conduct stress testing with a focus on the reconnect scenario that triggers the issue. This could involve systematically varying the number of devices, the distance of the out-of-range condition, and the frequency of reconnect attempts. Such testing might help in identifying a threshold at which the issue

Please, also check if these links can help you solve your problem:

Watchdog (Linux) | Toradex Developer Center.

3

Hello @JormenJanssen,

I believe you need to use the NXP proprietary driver for this to work. Are you aiming to use the dunfell image here or planning to upgrade to kirkstone?