How i can use mt7662U drivers in OpenWrt

As i know the mt7662u same to the mt7612u, and i download the offical mt7612u drivers from the MTK, so i want to ask how i can use it in openwrt, pls

But if it's the same, shouldn't it already be supported? MT7612U USB adapter not working

i use the follow openwrt version:

DISTRIB_ID="OpenWrt"
DISTRIB_RELEASE="Barrier Breaker"
DISTRIB_REVISION="unknown"
DISTRIB_CODENAME="barrier_breaker"
DISTRIB_TARGET="ramips/generic"
DISTRIB_DESCRIPTION="OpenWrt Barrier Breaker 14.07"
DISTRIB_TAINTS="no-all busybox"

This topic is mainly to ask How the mt7662u_sta.ko and the file mt7662t_firmware_e1.bin mt7662t_patch_e1_hdr.bin in /lib/firmware are Associated? I can`t understand the work process

Barrier Breaker, that was what? 8 years ago?

Time to upgrade, or get a new(er) device, don't think people will help you with your archeology endeavor here, sorry.

the usb wifi module 'mt7662' Occasional loading failures at boot, I want to track down if it's a hardware issue or a software issue?

procd: - init complete -
[   34.056000] cfg80211: Calling CRDA to update world regulatory domain
[   34.632000] 
[   34.632000] 
[   34.632000] === pAd = c10c5000, size = 2430648 ===
[   34.632000] 
[   34.652000] <-- RTMPAllocAdapterBlock, Status=0
[   34.664000] WiFi Chip ID = 0x76620100
[   34.672000] ==>rlt_wlan_chip_onoff(): OnOff:1, Reset= 1, pAd->WlanFunCtrl:0x0, Reg-WlanFunCtrl=0x20b
[   34.696000] Driver version-JEDI.MP2.mt76x2u.wifi.v3.2.1
[   34.708000] MT76x2T chip!
[   34.712000] RtmpChipOpsEepromHook::e2p_type=0, inf_Type=2
[   34.724000] RtmpEepromGetDefault::e2p_dafault=1
[   34.732000] NVM is EFUSE mode
[   34.740000] Endpoint(8) is for In-band Command
[   34.748000] Endpoint(4) is for WMM0 AC0
[   34.756000] Endpoint(5) is for WMM0 AC1
[   34.764000] Endpoint(6) is for WMM0 AC2
[   34.772000] Endpoint(7) is for WMM0 AC3
[   34.780000] Endpoint(9) is for WMM1 AC0
[   34.788000] Endpoint(84) is for Data-In
[   34.796000] Endpoint(85) is for Command Rsp
[   34.804000] get_dev_name_prefix(): dev_idx = 0, dev_name_prefix=wlan
[   34.816000] Allocate net device ops success! -> c1318000
[   34.828000] 80211> RFICType= 3, NumOfChan= 47
[   34.836000] 80211> Number of rate = 12
[   34.844000] 80211> CurTxPower = 20 dBm
[   34.852000] 80211> TxStream = 0
[   34.856000] crda> requlation requestion by core: 00
[   34.868000] 80211> CFG80211_Register
[   34.876000] usbcore: registered new interface driver rt2870
[   35.216000] Entering RTMPSwReset
[   35.224000] RTMPSwReset: Disable UDMA T/R
[   35.232000] RTMPSwReset: Drop Bulkout EP4~9
[   35.272000] RTMPSwReset: Reset UDMA TX
[   35.312000] RTMPSwReset: Reset IFDMA/FCE
[   35.348000] RTMPSwReset: Reset MAC/PBF
[   35.392000] RTMPSwReset: Reset UDMA RX
[   35.428000] RTMPSwReset: Enble UDMA T/R
[   35.452000] Exiting RTMPSwReset
[   35.460000] andes_usb_load_rom_patch --> ChipID : 0x76620100
[   35.468000] andes_usb_load_rom_patch --> mac_value : 0x1001 , cap->rom_code_protect = 1
[   35.484000] Rom patch already loaded, skip load again
[   35.496000] -->RTUSBVenderReset
[   35.504000] <--RTUSBVenderReset
[   35.516000] Load WiFi firmware from BinFile $FIRMWARE_PATH/mt7662t_firmware_e1.bin
[   35.608000] fw version:1.e1.301 build:1
[   35.616000] build time:201604211439____
[   35.624000] fw for E3 IC
[   35.628000] ilm length = 69080(bytes)
[   35.636000] dlm length = 19408(bytes)
[   35.644000] loading fwupload fw timeout(1000ms)
[   36.652000] andes_usb_loadfw: submit urb, sent_len = 14584, ilm_ilm = 69080, cur_len = 14584
[   36.668000] andes_usb_erasefw
[   36.672000] ERROR!!! NICLoadFirmware failed, Status[=0x00000001]
[   36.684000] tx_kickout_fail_count = 0
[   36.692000] tx_timeout_fail_count = 0
[   36.700000] rx_receive_fail_count = 0
[   36.708000] alloc_cmd_msg = 1
[   36.712000] free_cmd_msg = 1
[   36.720000] !!! rt28xx init fail !!!
[   36.832000] Entering RTMPSwReset
[   36.840000] RTMPSwReset: Disable UDMA T/R
[   36.848000] RTMPSwReset: Drop Bulkout EP4~9

I have no any way, i have no newer sdk by MTK

If it's Mediatek, check if your device has proper openwrt support.
With the vendor SDK, you're on your own, it's their openwrt, not "ours".

1 Like