Und wie komme ich bei der 3370 in den Konfigurationsmodus? Hier gibt es keine WPS-Taste.
TomH
3. Dezember 2024 um 21:40
2
Es dürfte hier wohl der „Power“ Button sein:
freifunk-gluon:master ← dzzinstant:lantiq-avm3370
opened 01:20AM - 13 Jun 20 UTC
(This is a resubmission of https://github.com/freifunk-gluon/gluon/pull/2050, co… uldn't reopen. Sorry for inconvenience.)
Based on Dark4MD's patch (https://github.com/freifunk-gluon/gluon/commit/2360924e4a43754b5a3c24e5797d94c6a9451a7f).
Further changes, might need discussion:
1. Long press (>3s) the power button to get to setup mode. There is the problem of incidentally powering off the device by releasing the button too soon. But this shouldn't cause real damage (except for the loss of time), because the operator was planning to shut down the device anyway.
And the opposite problem of incidentally putting the device into setup mode, when the intention was to switch it off.
2. Patch to show LAN activity on LED, but IMHO that's not an important feature.
3. Don't know the reason for the ordering of LAN ports, so didn't change anything there (https://github.com/dzzinstant/gluon/issues/4), probably not relevant for gluon?
The flashing process is a bit more involved than for other AVM devices, see hints in follow-up to this message.
### Device Integration Checklist
- [x] must be flashable from vendor firmware
- [ ] webinterface
- [ ] tftp
- [x] other: ftp [EVA bootloader, separate images for kernel and filesystem partitions] -> https://github.com/dzzinstant/gluon/issues/3
- [x] must support upgrade mechanism
- [x] must have working sysupgrade
- [x] must keep/forget configuration (if applicable)
*think `sysupgrade [-n]` or `firstboot`*
- [x] 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] -> https://github.com/dzzinstant/gluon/commit/7ba5577eac5146fc8df3b669cd3c10a96e0ad0a1
- [x] primary mac should match address on device label (or packaging) (https://gluon.readthedocs.io/en/latest/dev/hardware.html#notes)
- wired network
- [x] 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?] -> https://github.com/dzzinstant/gluon/issues/4
- wifi (if applicable)
- [x] association with AP must be possible on all radios
- [x] association with 802.11s mesh must be working on all radios
- [x] ap/mesh mode must work in parallel on all radios
- led mapping
- power/sys led (_critical, because led definitions are setup on firstboot only_)
- [x] lit while the device is on
- [x] should display config mode blink sequence
(https://gluon.readthedocs.io/en/latest/features/configmode.html)
- radio leds
- [x] should map to their respective radio
- [x] should show activity
- switchport leds
- [x] 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] -> https://github.com/dzzinstant/gluon/commit/84fe9fc1a0d9642b84f7bda9077f4b8038a1dfc4
- 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**
- [x] wan-radio/private wlan [can be enabled in parallel with client + mesh wlan]
- [ ] 'WLAN' button enables/disables radio -> https://github.com/openwrt/openwrt/pull/3042
- [ ] also works in the 5 Ghz band [3370 only has a single radio for both bands]
- [x] association with AP must be possible
- [x] association with 802.11s mesh must be working (only indoor mode)
- [x] ap/mesh mode must work in parallel (only indoor mode)
- [ ] outdoor mode with DFS [basically works, but some clients cause false radar detections]
Successfully tested on:
```
$ grep "^HW.*Revision\s\|^bootloader\|NAND device:" support\ FRITZ.Box\ WLAN\ 3370*.txt
HWRevision 175
HWSubRevision 2
bootloaderVersion 1.1186
[ 1.560000] NAND device: Manufacturer ID: 0x20, Chip ID: 0xdc (ST Micro NAND04GW3B2DN6), 512MiB, page size: 2048, OOB size: 64
```
(using the `..-hynix-nand-..` images; there was no automatic reboot after 30s)
Aufpassen mindestens drei Sekunden zu drücken. Sonst triggert das wohl den Shutdown.
Es hat nicht geklappt. Das mit dem Power-Button wurde wohl verworfen.
TomH
4. Dezember 2024 um 21:19
4
mhm, du hast recht, ist so auch im Code hinterlegt:
device('avm-fritz-box-3370-rev-2-hynix-nand', 'avm_fritz3370-rev2-hynix', {
factory = false,
extra_images = {
{'-squashfs-eva-filesystem', '-eva-filesystem', '.bin'},
{'-squashfs-eva-kernel', '-eva-kernel', '.bin'},
},
broken = true, -- no button for setup mode; hw revision not visible on device
})
device('avm-fritz-box-3370-rev-2-micron-nand', 'avm_fritz3370-rev2-micron', {
factory = false,
extra_images = {
{'-squashfs-eva-filesystem', '-eva-filesystem', '.bin'},
{'-squashfs-eva-kernel', '-eva-kernel', '.bin'},
},
broken = true, -- no button for setup mode; hw revision not visible on device
})
War wohl ein Patch (der aber abgelehnt wurde) und dementsprechend gibt es keinen Button welcher passend gemapped ist. Daher ist das Gerät auch broken und wird wohl nie von uns eine stable Firmware bekommen.
Ich sehe nun gerade drei Möglichkeiten:
falls ssh Zugriff besteht (nur mit hinterlegtem key im normalem Betriebsmodus) gluon-enter-setup-mode
Gerät aufmachen und per serieller Konsole gluon-enter-setup-mode eingeben
neu installieren per EVA und public ssh key für die Zukunft hinterlegen
1 „Gefällt mir“
