dzzinstant / gluon Goto Github PK

From https://github.com/openwrt/openwrt/blob/openwrt-19.07/target/linux/lantiq/base-files/etc/board.d/02_network:

avm,fritz3370-rev2-hynix|\
avm,fritz3370-rev2-micron)
[..]
	ucidef_add_switch "switch0" \
		"0:lan:3" "1:lan:4" "2:lan:2" "4:lan:1" "6t@eth0"
;;

This mixes up the port numbering...

• Is there a reason for this?
• Is it relevant for gluon Device Integration?

Device Integration Checklist

• must be flashable from vendor firmware
  ( ) webinterface
  ( ) tftp
  • other: ftp [EVA bootloader, separate images for kernel and filesystem partitions] -> #3
• must support upgrade mechanism
  • must have working sysupgrade
    • must keep/forget configuration (if applicable)
      think sysupgrade [-n] or firstboot
  • must have working autoupdate
    usually means: gluon profile name must match image name

  :~# lua -e 'print(require("platform_info").get_image_name())'
  avm-fritz-box-3370-rev-2-hynix-nand
  

• reset/wps/phone button must return device into config mode [no such button => use 'power' button instead] -> 7ba5577
• primary mac should match address on device label (or packaging) (https://gluon.readthedocs.io/en/latest/dev/hardware.html#notes)
• wired network
  • should support all network ports on the device
  • must have correct port assignment (WAN/LAN) [numbering of LAN ports is mixed up, does that matter?] -> #4
• wifi (if applicable)
  • association with AP must be possible on all radios
  • association with 802.11s mesh must be working on all radios
  • ap/mesh mode must work in parallel on all radios
• led mapping
  • power/sys led (critical, because led definitions are setup on firstboot only)
    • lit while the device is on
    • should display config mode blink sequence
      (https://gluon.readthedocs.io/en/latest/features/configmode.html)
  • radio leds
    • should map to their respective radio
    • should show activity
  • switchport leds
    • should map to their respective port (or switch, if only one led present)
    • should show link state and activity [shows only state, maybe apply patch to also show activity] -> 84fe9fc
• outdoor devices only
  ( ) added board name to is_outdoor_device function in package/gluon-core/luasrc/usr/lib/lua/gluon/platform.lua

Additional / device-specific

• wan-radio/private wlan [can be enabled in parallel with client + mesh wlan]
• 'WLAN' button enables/disables radio -> openwrt/openwrt#3042
• also works in the 5 Ghz band [3370 only has a single radio for both bands]
  • association with AP must be possible
  • association with 802.11s mesh must be working (only indoor mode)
  • ap/mesh mode must work in parallel (only indoor mode)
  • outdoor mode with DFS [basically works, but some clients cause false radar detections]

Installing gluon on the Fritzbox 3370

Gluon can be installed using the EVA FTP method as described in OpenWRT: AVM FRITZ!Box WLAN 3370. Just use your community's gluon images instead of the stock OpenWRT ones.
However, a few things should be kept in mind:

Differences to other AVM boxes, possible difficulties

1. Device should be at least HWSubRevision 2 (see first lines of file obtained through http://fritz.box/support.lua)
2. The kernel and filesystem reside on different flash partitions, so you have to flash two images:
   gluon-avm-fritz-box-3370-rev-2-..-eva-kernel.bin -> mtd1
gluon-avm-fritz-box-3370-rev-2-..-eva-filesystem.bin -> mtd0
3. The device is available with different types of flash memory, you have to use the corresponding set of images:
   Micron flash chip -> use ..-micron-nand-.. set of images
   ST Micro or Hynix flash chip -> use ..-hynix-nand-.. set of images
   Unfortunately, it's not easy to determine which flash chip is installed, so:
   • While Fritz!OS is still installed, call http://fritz.box/support.lua in your web browser, save the support file to disk (it may take ~one minute to gather the data, be patient).
     The resulting file should contain a debug line starting with NAND device:, which identifies the flash chip.
   • Installing the wrong set of images seems to be non-fatal (the device will either bootloop or remain at the bootloader stage). If you picked the wrong ones, just use the EVA/ftp procedure again to install the other set of images.
4. Some versions of the bootloader automatically reboot after ~30 seconds. In this case be really fast or copy-paste the complete sequence of commands from the clipboard to the terminal.

References

OpenWRT: AVM FRITZ!Box WLAN 3370
Commit message: lantiq: complete AVM FRITZ!Box 3370 support
Michael Kuron: OpenWRT on AVM Fritz!Box 3370