Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revisionBoth sides next revision
user:jiringgot [2021/05/04 21:23] jiringgotuser:jiringgot [2021/05/05 17:11] jiringgot
Line 1: Line 1:
 +==== Jiringgot ====
 +  * Casual computer nerd
 +  * Teaching sand to think was a good mistake.
 +
 +
 ====== WIP ZyXEL NBG6515 AC750====== ====== WIP ZyXEL NBG6515 AC750======
 ~~NOTOC~~ ~~NOTOC~~
  
 {{page>meta:infobox:construction&noheader&nofooter&noeditbtn}} {{page>meta:infobox:construction&noheader&nofooter&noeditbtn}}
- 
-== TODO == 
-  * Instruct users how to modify the device tree for cluing in the mt76x0 driver on where to find factory data. 
-  * Update informatory sections to reflect current findings and activites 
-  * Sprinkle some more information around instructions that are obvious to experienced users, but completely oblivious to people scrolling by. 
  
  
Line 13: Line 13:
   * MEDIATEK MT7620A: CPU, WLAN   * MEDIATEK MT7620A: CPU, WLAN
   * MEDIATEK MT7530WU: Switch   * MEDIATEK MT7530WU: Switch
-  * MEDIATEK MT7610EN: WLAN+  * MEDIATEK MT7610EN: WLAN (not working in the provided release build)
  
 /*****/ /*****/
Line 35: Line 35:
 ===== Supporting activities ===== ===== Supporting activities =====
 //Describe if there are any ongoing activities that might lead to OpenWrt support.// //Describe if there are any ongoing activities that might lead to OpenWrt support.//
- +  A dedicated device profile is being worked on. A preliminary patch which fixes previous [[https://forum.openwrt.org/t/nbg6515-zyxel-wlan-fails/73773 | MT76x0E errors]] can be found here: https://pastebin.com/HxyK4zsu  (details on how to build below) 
-  MT76x0e driver fails: [[https://forum.openwrt.org/t/bricked-asus-rt-ac51u-and-need-an-eeprom-for-wifi/55787]] +  * 2.4Ghz WLAN works with the RaLink driver: rt2x00 in conjunction with data from the <color #ed1c24>mtd2 partition of the original firmware</color> (detailed instructions below).
-  * WLAN works with the RaLink driver: rt2x00 in conjunction with data from the <color #ed1c24>mtd2 partition of the original firmware</color> +
-  * Fix availabe in the OpenWrt Forum: [[https://forum.archive.openwrt.org/viewtopic.php?id=59349]], to be applied in modified form after preservation of original firmware and installing OpenWrt (detailed instructions below).+
   * The overlayFS only works after flashing the sysupgrade image from inside a running OpenWrt system, e.g. one that has been started via TFTP boot   * The overlayFS only works after flashing the sysupgrade image from inside a running OpenWrt system, e.g. one that has been started via TFTP boot
  
Line 51: Line 49:
  
 ===== Hardware highlights ===== ===== Hardware highlights =====
-^ CPU                        ^ Ram      ^ Flash   ^ Network     ^ WLAN   ^ USB      ^ Serial   ^ JTag   ^ +^ CPU                        ^ Ram      ^ Flash   ^ Network     ^ WLAN Hardware                     ^ WLAN2.4 ^ WLAN5.0 ^ USB      ^ Serial   ^ JTag   ^ 
-| MT7620A @ 580 MHz    64 MiB  |  8 MiB  |  5x 10/100/1000  |  2.4/5 GHz bgn <color #ed1c24>(supported in OpenWrt with EEPROM data from original firmware)</color>   1x 2.0  |   Yes    |   ?    |+| MT7620A @ 580 MHz    64 MiB  |  8 MiB  |  5x 10/100/1000  |  Mediatek MT7620A, Mediatek MT7610E | b/g/n    | a/n/ac | 1x 2.0  |   Yes    |   ?    |
  
 ===== Installation ===== ===== Installation =====
Line 81: Line 79:
   - If you plan to permanently install OpenWrt, do so by flashing the previously downloaded "sysupgrade" image.     - If you plan to permanently install OpenWrt, do so by flashing the previously downloaded "sysupgrade" image.  
   - The bootloader offers an alternative option "2" to directly flash an image to the internal flash memory; follow the instructions from the bootloader.   - The bootloader offers an alternative option "2" to directly flash an image to the internal flash memory; follow the instructions from the bootloader.
-==== Enabling wireless through information taken from the mt2 (factory) partition of the original firmware ====+ 
 + 
 +==== Enabling 2.4GHz wireless through information taken from the mtd2 (factory) partition of the original firmware ====
   - After booting into OpenWrt, open an ssh session and verify that you have a working overlayfs: ''ssh root@192.168.1.1'' then ''mount'' (should reveal a line about overlayfs) and ''df -h'' should reveal /dev/mtdblock6 with approx. 4 MB space.   - After booting into OpenWrt, open an ssh session and verify that you have a working overlayfs: ''ssh root@192.168.1.1'' then ''mount'' (should reveal a line about overlayfs) and ''df -h'' should reveal /dev/mtdblock6 with approx. 4 MB space.
   - To make sure that overlayfs is functional, create a new directory by ''mkdir /root/testdir'', then ''reboot'' and verify that the directory you created is still there by ''ls -l /root''.   - To make sure that overlayfs is functional, create a new directory by ''mkdir /root/testdir'', then ''reboot'' and verify that the directory you created is still there by ''ls -l /root''.
Line 92: Line 92:
   - After logging into LuCi, you can now use the WLAN as usual.   - After logging into LuCi, you can now use the WLAN as usual.
  
 +Note: OpenWRT source contains patches that add device-tree tags in the rt2x00 driver. "ralink,eeprom=soc_wmac.eeprom" it shouldn't be to much work to modify those to read data from the mtd-partitions similarly to what the mt76x0 driver does. it would provide a more smooth install experience for tinkerers.
 +
 +==== Enabling device 5GHz wireless with a custom build ====
 +This section assumes you have read and understood in detail what is explained above and why. Enabling the 5GHz radio requires that you know how to patch the source tree of OpenWRT.
 +It is also asumed that the "Factory" partition is still intact, as the MT7610E-eeprom data is further in compared to the 2.4GHz one.
 +
 +The preliminary patch adds a <color #ed1c24>(very much w.i.p)</color> device profile to the configuration menu and a new device tree that is based on the two evaluation boards that already exist upstream. "mt7620a_mt7530" "mt7620a_mt7610e"
 +
 +Patch Link: https://pastebin.com/HxyK4zsu
 +
 +  - Clone the OpenWRT source tree to a directory of your choosing.
 +  - Download the patch and apply using ''patch -Np1 -i <path-to-patch>'' [[https://01.org/linuxgraphics/gfx-docs/drm/process/applying-patches.html | Link if you need a guide]]
 +  - Now configure the source tree as described here: [[:docs:guide-developer:build-system:use-buildsystem || Build System]] (Note that if you need to install luci as a feed-package if you want a webgui)
 +  - If you have already completed the previous section enabling 2.4 wireless, you can run ''mkdir -p files/lib/firmware'' in the source tree and then copy soc_wmac.eeprom to that folder and it will get baked into the finished sysupgrade automatically.
 +  - Depending on your hardware the build could take a while, but when it finishes you should have a [[:docs:guide-user:installation:generic.sysupgrade | sysupgrade file]] that looks similar to this: <color #008080>bin/targets/ramips/mt7620/openwrt-ramips-mt7620-zyxel_nbg6515-ac750-squashfs-sysupgrade.bin</color>
 +  - If done correctly, the produced build can be flashed onto the device as described in the previous installation section. Note however that the compatability-identifier is changed in the patch so you have to do a force-flash.
  
 /*** if info available: uncomment and fill in /*** if info available: uncomment and fill in
Line 172: Line 188:
 </WRAP> </WRAP>
 ***/ ***/
 +==== Flash Layout ====
 +
 +=== Stock ===
 +^ Start ^ Stop ^ Name ^
 +^ 0x000000 | 0x800000 | ALL         |
 +^ 0x000000 | 0x030000 | Bootloader  |
 +^ 0x030000 | 0x040000 | Config      |
 +^ 0x040000 | 0x048000 | Factory     |
 +^ 0x048000 | 0x050000 | iNIC_rf     |
 +^ 0x050000 | 0x724000 | Kernel      |
 +^ 0x210000 | 0x724000 | user        |
 +^ 0x724000 | 0x7ba000 | manufacture |
 +^ 0x7ba000 | 0x7ca000 | backup      |
 +^ 0x7ca000 | 0x800000 | storage     |
  
 +=== Wrt ===
 +^ Device ^ Size ^ Name ^
 +^ mtd0   | 00030000 | "u-boot"      |
 +^ mtd1   | 00010000 | "u-boot-env" 
 +^ mtd2   | 00010000 | "factory"     |
 +^ mtd3   | 007b0000 | "firmware"    | 
 +^ mtd4   | 00138694 | "kernel"      |
 +^ mtd5   | 0067796c | "rootfs"      |
 +^ mtd6   | 00442000 | "rootfs_data" |
  
 /*==== Photos ====*/ /*==== Photos ====*/
  • Last modified: 2021/10/15 08:26
  • by bobafetthotmail