Issue with 5GHz WiFi Configuration on MT7628AN Evaluation Board - Firmware Fails to Start

Hello OpenWrt Community,

I am experiencing an issue with setting up the 5GHz WiFi on my device. Here are the details:

config wifi-device 'radio0'
        option type 'mac80211'
        option channel 'auto'
        option band '5g'
        option path 'pci0000:00/0000:00:00.0/0000:01:00.0'
        option htmode 'VHT80'
        option country 'CA'

    config wifi-iface 'default_radio0'
        option device 'radio0'
        option network 'lan'
        option mode 'ap'
        option ssid 'Openwrt Setup 5G'
        option encryption 'none'
        option disabled '0'
When I restart the network service using /etc/init.d/network restart, the following error messages appear in the system log repeatedly:
 [ 3578.882493] mt76x2e 0000:01:00.0: Firmware failed to start
[ 3578.894103] ieee80211 phy1: Hardware restart was requested
[ 3579.922514] mt76x2e 0000:01:00.0: MCU message 02 (seq 10) timed out
[ 3585.053286] mt76x2e 0000:01:00.0: Firmware Version: 0.0.00
[ 3585.064255] mt76x2e 0000:01:00.0: Build: 1
[ 3585.072364] mt76x2e 0000:01:00.0: Build Time: 201607111443____
[ 3585.502510] mt76x2e 0000:01:00.0: Firmware failed to start
[ 3585.514162] ieee80211 phy1: Hardware restart was requested
    

and the output from ubus command:

root@Mango_1B83:~# ubus call system board
{
	"kernel": "5.15.137",
	"hostname": "Mango_1B83",
	"system": "MediaTek MT7628AN ver:1 eco:2",
	"model": "Mediatek MT7628AN evaluation board",
	"board_name": "mediatek,mt7628an-eval-board",
	"rootfs_type": "squashfs",
	"release": {
		"distribution": "OpenWrt",
		"version": "23.05.2",
		"revision": "r23630-842932a63d",
		"target": "ramips/mt76x8",
		"description": "OpenWrt 23.05.2 r23630-842932a63d"
	}
}

Thank you in advance for your support!

You are using OpenWRT fork distribution, you need to ask folks distributing it. On real OpenWRT you can restart wifi without any failures.

Thanks @brada4. The error message "Firmware failed to start" suggests the issue relates to the EEPROM content. I need to further debug the mt76 module in the kernel to pinpoint the exact reason for the failure. However, I am unfamiliar with the kernel's debugging practice, which seems different from how I troubleshot my own packages, for which I generated the .ipk for my device with additional debug info. How can I troubleshoot issues related to kernel modules?

With Regards,

Hello OpenWRT Community,

I'm currently working with a device that uses the MediaTek MT7612e wireless chipset. As part of my project, I need a sample EEPROM binary file specific to the MT7612e to help with configuration and calibration.

Request: Could anyone provide a sample EEPROM binary file for the MT7612e chipset or point me to a resource where I might find one? This file will be used to understand the EEPROM layout and test some functionalities.

Details:

  • Chipset: MediaTek MT7612e
  • Purpose: To use as a reference for configuring and troubleshooting my device’s wireless capabilities.

I've searched through the available resources but haven't had much luck finding a suitable file. Any guidance, whether a direct link to a file or advice on where to obtain one, would be greatly appreciated.

Context: If there's any specific tool or method to extract the EEPROM data from a similar device or generate one, that information would also be very helpful.

Thank you in advance for your assistance!

Best regards,

Please post output of

ubus call system board

the output from ubus command:

root@Mango_1B83:~# ubus call system board
{
	"kernel": "5.15.137",
	"hostname": "Mango_1B83",
	"system": "MediaTek MT7628AN ver:1 eco:2",
	"model": "Mediatek MT7628AN evaluation board",
	"board_name": "mediatek,mt7628an-eval-board",
	"rootfs_type": "squashfs",
	"release": {
		"distribution": "OpenWrt",
		"version": "23.05.2",
		"revision": "r23630-842932a63d",
		"target": "ramips/mt76x8",
		"description": "OpenWrt 23.05.2 r23630-842932a63d"
	}
}

You are not using OpenWRT and you have to ask your evb supplier for such data.

I am afraid I don't get your point. I built the OpenWRT image file by following the instructions from the link - https://openwrt.org/docs/guide-developer/toolchain/use-buildsystem. I even made sure the same between the packages installed and kernel modules loaded in my build with the original sysupgrade file provided by OpenWRT using the following two commands:

opkg list-installed  > /tmp/package_installed.lst
lsmod > /tmp/lsmod.lst

Would you explain further your points on

You are not using OpenWRT

and

You are using OpenWRT fork distribution, you need to ask folks distributing it.

The OpenWRT I got is from the GitHub repo at https://git.openwrt.org/openwrt/openwrt.git. Is that a fork distribution?

With Regards,

Well, your device is not among supported , see https:///firmware-selector.openwrt.org/

How is the hardware device related to OpenWRT fork distribution? I don't understand. Would you clarify? Thanks.

Your device does appear to be officially supported by OpenWrt. I think the previous suggestions otherwise were mistaken.

I don't know why your radio is not starting up properly, but you might try upgrading to the latest version of OpenWrt and allowing it to reset to defaults during the upgrade (uncheck the keep settings box). That will at least ensure that it your configuration and the slightly older version of OpenWrt are not the culprits. (feel free to make a backup of your configuration before flashing/resetting, of course).

https://firmware-selector.openwrt.org/?version=23.05.3&target=ramips%2Fmt76x8&id=mediatek_mt7628an-eval-board

Hi @psherman,

Thank you for your insightful comments.

I encountered an error while working with the MT7612e chipset, specifically:

[ 3585.502510] mt76x2e 0000:01:00.0: Firmware failed to start

This error message suggests an issue related to the EEPROM content. To troubleshoot, I tried to isolate which EEPROM flags were causing the problem by adding debug information to the mt76 source code. I then used the make utility to compile a localized version of the kernel with these modifications for my device.

However, I suspect that my approach to diagnosing and resolving these kernel-level issues with OpenWRT may not be entirely correct. Could you provide guidance on the best practices for debugging issues at the kernel level in OpenWRT? Specifically, any advice on how to effectively use debug logs, kernel modules, or other tools in this context would be very helpful.

Additionally, to deepen my understanding of the EEPROM layout and to test functionalities, I am looking for a sample EEPROM binary file for the MT7612e chipset. Do you know where I might find such a resource, or could you provide a sample file?

Thank you again for your assistance!

Best regards,

This is actually not my area of expertise, sorry. Hopefully others can chime in.That said, making sure you're up to date and running a near-default configuration will surely be helpful as part of the debug process.

In Padavan project there are many eeprom samples but only for supported devices (usually without eLNA/ePA).
Also you can read this topic.

Thanks @123serge123. The file MT7612E_EEPROM.bin from the Padavan project does fix the issue of "Firmware failed to start":

[ 3585.502510] mt76x2e 0000:01:00.0: Firmware failed to start

However, when I run the following command, nothing returns:

root@Mango_4506:/tmp# iw phy1-ap0 scan
root@Mango_4506:/tmp#

With Regards,

Could anyone provide guidance on the best practices for debugging issues at the kernel level in OpenWRT? Specifically, any advice on how to effectively use debug logs, kernel modules, or other tools in this context would be very helpful.

The 5G AP mode is working. However, when I run the following command, it abends with the following message:

root@Mango_9EF9:~# iw phy1-ap0 scan
scan aborted!

# and the following message showing on log:
[  373.603345] mt76x2e 0000:01:00.0: MCU message 1f (seq 9) timed out
[  373.664731] mt76x2e 0000:01:00.0: Firmware Version: 0.0.00
[  373.675701] mt76x2e 0000:01:00.0: Build: 1
[  373.683834] mt76x2e 0000:01:00.0: Build Time: 201607111443____
[  373.713391] mt76x2e 0000:01:00.0: Firmware running!
[  373.724270] ieee80211 phy1: Hardware restart was requested

The following is the system info:

root@Mango_9EF9:/# ubus call system board
{
        "kernel": "5.15.150",
        "hostname": "Mango_9EF9",
        "system": "MediaTek MT7628AN ver:1 eco:2",
        "model": "Mediatek MT7628AN evaluation board",
        "board_name": "mediatek,mt7628an-eval-board",
        "rootfs_type": "squashfs",
        "release": {
                "distribution": "OpenWrt",
                "version": "23.05.3",
                "revision": "r23809-234f1a2efa",
                "target": "ramips/mt76x8",
                "description": "OpenWrt 23.05.3 r23809-234f1a2efa"
        }
}

Thanks for your advice in advance.

With Regards

Also, the latest version of MT76 (513c131c) compiles failure on the OpenWRT version 23.05.3 (latest stable version) due to the below error:

/openwrt/build_dir/target-mipsel_24kc_musl/linux-ramips_mt76x8/mt76/mac80211.c:1092:23: error: 'struct ieee80211_rx_status' has no member named 'eht'
 1092 |                 status->eht.gi = mstat.eht.gi;
      |                       ^~

Which version of OpenWRT should I use to make the compilation successful?

With Regards,

The manufacturer that provided you the WiFi chips didn't provide needed calibration tools?

You may wish to create a seperate thred for this topic.

Thanks, @lleachii. I have created a thread "Subject: MT76 Compilation Failure on OpenWRT 23.05.3" for the MT76 compilation issue.
Also, the calibration part of the issue has already been fixed. Thanks

1 Like