ĭescription: ARM64 OpenWrt MTK-AX3200-MT7531 device tree blob # Loading fdt from FIT Image at 4007ff28. # Loading kernel from FIT Image at 4007ff28. NAND read: device 0 offset 0x500000, size 0x27c000 NAND read: device 0 offset 0x500000, size 0x2000 U-Boot console Hit any key to stop autoboot: 3 2 1 0 System Load Preloader then write to Flash via TFTP. System Load ATF then write to Flash via TFTP. System Load U-Boot then write to Flash via Serial. System Load U-Boot then write to Flash via TFTP. System Load Linux Kernel then write to Flash via TFTP. *** U-Boot SPI NAND *** Press UP/DOWN to move or Press 1~8 to choose, ENTER to select 1. NAND: Recognize SNAND: ID, Device Name, Page Size B Spare Size B Total Size MBįirst booting, write default data (s_env) to flash. Static declaration g_total_rank_size = 0x1F000000 bldr load tee part ret=0x0, addr=0x43001000 Mt_pll_init: Set pll frequency for 25M crystal Optionally enable Hardware Flow Offloading In general, on MT7622 WED is only supported in TX direction (from router point of view), so CPU load reduction (from around 15% load to around 3% load when running speedtest) can only be observed if traffic is sent from the router to the client. If you ware willing to try development snapshots, you can use WED by installing the bridger package which facilitates flow-offloading also in bridged configuration. If you only use it as bridged access point, WED cannot work on OpenWrt 22.03. Again, this is expected if you do not use the device as NAT/router. If /sys/kernel/debug/mtk_ppe/bind is empty, that merely means that there are no offloaded flows. Note that the above shows all traffic that is accelerated by the chipset's Packet Processing Engine (PPE), including the wired clients, so if a mix of wired and wireless clients are expected, the output will need to be inspected for specific MACs or IPs of the wireless clients to confirm WED is working. To see which flows are actually getting off-loaded. If you do want to use OpenWrt permanently, it is recommended to convert the device to UBI layout by following this guide: In this case, download the non-UBI variant of the device firmware openwrt-mediatek-mt7622-linksys_e8450-squashfs-sysupgrade.bin and upload it in the vendor firmware Web UI upgrade page. “non-UBI”), as it contains ECC errors out of the factory, and these errors are not compatible with the new SPI-NAND driver, that means you cannot install the non-UBI firmware ( *.bin).ĭue to the not exactly advantageous layout and management of the SPI Flash, the best way to use the device is to replace the bootloader and convert the flash layout of the device to UBI rather than trying to stay compatible with the vendor firmware, but if you just want to try OpenWrt and still plan to go back to the vendor firmware, use the non-UBI version of the firmware which can be flashed using the vendor's web interface. It is no longer possible to keep the default vendor flash layout (a.k.a.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |