Chciałbym podzielić się z Wami moim skompilowanym od podstaw obrazem OpenWrt 25.12.5 dedykowanym dla routera MikroTik hAP ac² (architektura ipq40xx).
Projekt powstał w celu optymalizacji systemu, pełnego wykorzystania zasobów sprzętowych oraz pod kątem lepszego monitorowania i diagnostyki.
Oto zestaw modyfikacji i pakietów, które zostały zintegrowane w tej kompilacji:
Optymalizacja i zegary SoC: Prawidłowe zarządzanie częstotliwością pracy procesora dla architektury arm_cortex-a7_neon-vfpv4.
Pełne wsparcie dla USB i systemów plików: Wkompilowane sterowniki USB 3.0 (DWC3) oraz obsługa systemów plików (ext4, exFAT, NTFS3, VFAT), co umożliwia bezproblemowe montowanie pamięci masowej (np. pod ścieżką /mnt/***).
Narzędzia diagnostyczne: Domyślnie wbudowany pakiet htop ze wsparciem dla czujników lm-sensors, co pozwala na szybki podgląd obciążenia rdzeni i zasobów w czasie rzeczywistym bezpośrednio z terminala.
Monitoring i statystyki: Skonfigurowany collectd oraz lm-sensors do śledzenia temperatur układów i parametrów środowiskowych.
Usługi sieciowe: Wbudowana obsługa serwera plików (ksmbd) do udostępniania zasobów z podłączonego dysku USB w sieci lokalnej.
Link do projektu: https://github.com/KFede/openwrt-mikrotik-hap-ac2
Chętnie odpowiem na pytania, jeśli ktoś z Was pracuje nad tym modelem lub planuje własną kompilację z podobnym zestawem pakietów.
]]>6.6.141 eko.one działa 24.10
6.12.71 openwrt działa 25.12.0
6.12.94 openwrt działa 25.12.5
6.12.103 eko.one nie działa 25.12-snapshot
6.12.112 openwrt nie działa 25.12.6
6.18.55 openwrt działa 25.12-snapshot
najnowszy snapshot oficjalny openwrt działa 6.18.55
nie wiem czy to wynika z regresji w kernelach 6.12 powyżej 94 ??
trzeba podbić albo zniżyć wersje kernela bo obecna jest zepsuta dla buildu eko.one
ponizej logi
cat dmesg-6.12.94-good.txt
[ 0.000037] Switching to timer-based delay loop, resolution 5ns
[ 0.064627] clocksource: Switched to clocksource orion_clocksource
[ 3.670836] mv88e6085 f1072004.mdio-bus-mii:10: switch 0x1710 detected: Marvell 88E6171, revision 2
[ 3.770468] mv88e6085 f1072004.mdio-bus-mii:11: switch 0x1710 detected: Marvell 88E6171, revision 2
[ 6.411530] mv88e6085 f1072004.mdio-bus-mii:10: configuring for fixed/rgmii-txid link mode
[ 6.422271] mv88e6085 f1072004.mdio-bus-mii:10: configuring for fixed/rgmii-id link mode
[ 6.431710] mv88e6085 f1072004.mdio-bus-mii:10: Link is Up - 1Gbps/Full - flow control off
[ 6.443449] mv88e6085 f1072004.mdio-bus-mii:10: Link is Up - 1Gbps/Full - flow control off
[ 6.452106] mv88e6085 f1072004.mdio-bus-mii:11: configuring for fixed/rgmii-txid link mode
[ 6.464065] mv88e6085 f1072004.mdio-bus-mii:11: Link is Up - 1Gbps/Full - flow control off
[ 6.483584] mv88e6085 f1072004.mdio-bus-mii:10 lan5 (uninitialized): PHY [mv88e6xxx-0:00] driver [Generic PHY] (irq=POLL)
[ 6.508917] mv88e6085 f1072004.mdio-bus-mii:10 lan1 (uninitialized): PHY [mv88e6xxx-0:01] driver [Generic PHY] (irq=POLL)
[ 6.532864] mv88e6085 f1072004.mdio-bus-mii:10 lan6 (uninitialized): PHY [mv88e6xxx-0:02] driver [Generic PHY] (irq=POLL)
[ 6.557852] mv88e6085 f1072004.mdio-bus-mii:10 lan2 (uninitialized): PHY [mv88e6xxx-0:03] driver [Generic PHY] (irq=POLL)
[ 6.583015] mv88e6085 f1072004.mdio-bus-mii:10 lan7 (uninitialized): PHY [mv88e6xxx-0:04] driver [Generic PHY] (irq=POLL)
[ 6.606960] mv88e6085 f1072004.mdio-bus-mii:11 lan3 (uninitialized): PHY [mv88e6xxx-1:00] driver [Generic PHY] (irq=POLL)
[ 6.632209] mv88e6085 f1072004.mdio-bus-mii:11 lan8 (uninitialized): PHY [mv88e6xxx-1:01] driver [Generic PHY] (irq=POLL)
[ 6.656589] mv88e6085 f1072004.mdio-bus-mii:11 lan4 (uninitialized): PHY [mv88e6xxx-1:02] driver [Generic PHY] (irq=POLL)
[ 6.681014] mv88e6085 f1072004.mdio-bus-mii:11 dmz (uninitialized): PHY [mv88e6xxx-1:03] driver [Generic PHY] (irq=POLL)
[ 6.695367] DSA: tree 0 setup
[ 8.518141] mv88e6085 f1072004.mdio-bus-mii:10 lan1: configuring for phy/gmii link mode
[ 12.975838] mount_root: switching to ubifs overlay
[ 34.369951] mv88e6085 f1072004.mdio-bus-mii:10 lan1: configuring for phy/gmii link mode
[ 34.517404] mv88e6085 f1072004.mdio-bus-mii:10 lan1: entered allmulticast mode
[ 34.880713] mv88e6085 f1072004.mdio-bus-mii:10 lan1: entered promiscuous mode
[ 35.173270] mv88e6085 f1072004.mdio-bus-mii:10 lan2: configuring for phy/gmii link mode
[ 35.237292] mv88e6085 f1072004.mdio-bus-mii:10 lan2: entered allmulticast mode
[ 35.363818] mv88e6085 f1072004.mdio-bus-mii:10 lan2: entered promiscuous mode
[ 35.491106] mv88e6085 f1072004.mdio-bus-mii:11 lan3: configuring for phy/gmii link mode
[ 35.557191] mv88e6085 f1072004.mdio-bus-mii:11 lan3: entered allmulticast mode
[ 35.753528] mv88e6085 f1072004.mdio-bus-mii:11 lan3: entered promiscuous mode
[ 35.904082] mv88e6085 f1072004.mdio-bus-mii:11 lan4: configuring for phy/gmii link mode
[ 35.947226] mv88e6085 f1072004.mdio-bus-mii:11 lan4: entered allmulticast mode
[ 36.110010] mv88e6085 f1072004.mdio-bus-mii:11 lan4: entered promiscuous mode
[ 36.355031] mv88e6085 f1072004.mdio-bus-mii:10 lan5: configuring for phy/gmii link mode
[ 36.402843] mv88e6085 f1072004.mdio-bus-mii:10 lan5: entered allmulticast mode
[ 36.612297] mv88e6085 f1072004.mdio-bus-mii:10 lan5: entered promiscuous mode
[ 36.782178] mv88e6085 f1072004.mdio-bus-mii:10 lan6: configuring for phy/gmii link mode
[ 36.818193] mv88e6085 f1072004.mdio-bus-mii:10 lan6: entered allmulticast mode
[ 37.018059] mv88e6085 f1072004.mdio-bus-mii:10 lan6: entered promiscuous mode
[ 37.161598] mv88e6085 f1072004.mdio-bus-mii:10 lan7: configuring for phy/gmii link mode
[ 37.228454] mv88e6085 f1072004.mdio-bus-mii:10 lan7: entered allmulticast mode
[ 37.402608] mv88e6085 f1072004.mdio-bus-mii:10 lan7: entered promiscuous mode
[ 37.548411] mv88e6085 f1072004.mdio-bus-mii:11 lan8: configuring for phy/gmii link mode
[ 37.712077] mv88e6085 f1072004.mdio-bus-mii:11 lan8: entered allmulticast mode
[ 37.963666] mv88e6085 f1072004.mdio-bus-mii:11 lan8: entered promiscuous mode
[ 38.102367] mv88e6085 f1072004.mdio-bus-mii:11 dmz: configuring for phy/gmii link mode
[ 38.134819] mv88e6085 f1072004.mdio-bus-mii:11 dmz: entered allmulticast mode
[ 38.198154] mv88e6085 f1072004.mdio-bus-mii:11 dmz: entered promiscuous mode
[ 41.303286] mv88e6085 f1072004.mdio-bus-mii:11 dmz: Link is Up - 1Gbps/Full - flow control rx/txcat dmesg-6.12.103-bad.txt
[ 1.195840] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[ 4.140889] mv88e6085 f1072004.mdio-bus-mii:10: switch 0x1710 detected: Marvell 88E6171, revision 2
[ 4.250183] mv88e6085 f1072004.mdio-bus-mii:11: switch 0x1710 detected: Marvell 88E6171, revision 2
[ 6.915685] mv88e6085 f1072004.mdio-bus-mii:10: configuring for fixed/rgmii-txid link mode
[ 6.926383] mv88e6085 f1072004.mdio-bus-mii:10: configuring for fixed/rgmii-id link mode
[ 6.935822] mv88e6085 f1072004.mdio-bus-mii:10: Link is Up - 1Gbps/Full - flow control off
[ 6.948299] mv88e6085 f1072004.mdio-bus-mii:11: configuring for fixed/rgmii-txid link mode
[ 6.957391] mv88e6085 f1072004.mdio-bus-mii:10: Link is Up - 1Gbps/Full - flow control off
[ 6.968697] mv88e6085 f1072004.mdio-bus-mii:11: Link is Up - 1Gbps/Full - flow control off
[ 6.986910] mv88e6085 f1072004.mdio-bus-mii:10 lan5 (uninitialized): validation of gmii with support 00,00000000,00000000,000062ff and advertisement 00,00000000,00000000,000062ff failed: -EOPNOTSUPP
[ 7.006847] mv88e6085 f1072004.mdio-bus-mii:10 lan5 (uninitialized): failed to connect to PHY: -EOPNOTSUPP
[ 7.016590] mv88e6085 f1072004.mdio-bus-mii:10 lan5 (uninitialized): error -95 setting up PHY for tree 0, switch 0, port 0
[ 7.041091] mv88e6085 f1072004.mdio-bus-mii:10 lan1 (uninitialized): validation of gmii with support 00,00000000,00000000,000062ff and advertisement 00,00000000,00000000,000062ff failed: -EOPNOTSUPP
[ 7.061287] mv88e6085 f1072004.mdio-bus-mii:10 lan1 (uninitialized): failed to connect to PHY: -EOPNOTSUPP
[ 7.071028] mv88e6085 f1072004.mdio-bus-mii:10 lan1 (uninitialized): error -95 setting up PHY for tree 0, switch 0, port 1
[ 7.094927] mv88e6085 f1072004.mdio-bus-mii:10 lan6 (uninitialized): validation of gmii with support 00,00000000,00000000,000062ff and advertisement 00,00000000,00000000,000062ff failed: -EOPNOTSUPP
[ 7.115076] mv88e6085 f1072004.mdio-bus-mii:10 lan6 (uninitialized): failed to connect to PHY: -EOPNOTSUPP
[ 7.124819] mv88e6085 f1072004.mdio-bus-mii:10 lan6 (uninitialized): error -95 setting up PHY for tree 0, switch 0, port 2
[ 7.148978] mv88e6085 f1072004.mdio-bus-mii:10 lan2 (uninitialized): validation of gmii with support 00,00000000,00000000,000062ff and advertisement 00,00000000,00000000,000062ff failed: -EOPNOTSUPP
[ 7.168910] mv88e6085 f1072004.mdio-bus-mii:10 lan2 (uninitialized): failed to connect to PHY: -EOPNOTSUPP
[ 7.178649] mv88e6085 f1072004.mdio-bus-mii:10 lan2 (uninitialized): error -95 setting up PHY for tree 0, switch 0, port 3
[ 7.202552] mv88e6085 f1072004.mdio-bus-mii:10 lan7 (uninitialized): validation of gmii with support 00,00000000,00000000,000062ff and advertisement 00,00000000,00000000,000062ff failed: -EOPNOTSUPP
[ 7.222484] mv88e6085 f1072004.mdio-bus-mii:10 lan7 (uninitialized): failed to connect to PHY: -EOPNOTSUPP
[ 7.232223] mv88e6085 f1072004.mdio-bus-mii:10 lan7 (uninitialized): error -95 setting up PHY for tree 0, switch 0, port 4
[ 7.256083] mv88e6085 f1072004.mdio-bus-mii:11 lan3 (uninitialized): validation of gmii with support 00,00000000,00000000,000062ff and advertisement 00,00000000,00000000,000062ff failed: -EOPNOTSUPP
[ 7.275973] mv88e6085 f1072004.mdio-bus-mii:11 lan3 (uninitialized): failed to connect to PHY: -EOPNOTSUPP
[ 7.285703] mv88e6085 f1072004.mdio-bus-mii:11 lan3 (uninitialized): error -95 setting up PHY for tree 0, switch 1, port 0
[ 7.309615] mv88e6085 f1072004.mdio-bus-mii:11 lan8 (uninitialized): validation of gmii with support 00,00000000,00000000,000062ff and advertisement 00,00000000,00000000,000062ff failed: -EOPNOTSUPP
[ 7.329807] mv88e6085 f1072004.mdio-bus-mii:11 lan8 (uninitialized): failed to connect to PHY: -EOPNOTSUPP
[ 7.339549] mv88e6085 f1072004.mdio-bus-mii:11 lan8 (uninitialized): error -95 setting up PHY for tree 0, switch 1, port 1
[ 7.363405] mv88e6085 f1072004.mdio-bus-mii:11 lan4 (uninitialized): validation of gmii with support 00,00000000,00000000,000062ff and advertisement 00,00000000,00000000,000062ff failed: -EOPNOTSUPP
[ 7.383813] mv88e6085 f1072004.mdio-bus-mii:11 lan4 (uninitialized): failed to connect to PHY: -EOPNOTSUPP
[ 7.393546] mv88e6085 f1072004.mdio-bus-mii:11 lan4 (uninitialized): error -95 setting up PHY for tree 0, switch 1, port 2
[ 7.417762] mv88e6085 f1072004.mdio-bus-mii:11 dmz (uninitialized): validation of gmii with support 00,00000000,00000000,000062ff and advertisement 00,00000000,00000000,000062ff failed: -EOPNOTSUPP
[ 7.437867] mv88e6085 f1072004.mdio-bus-mii:11 dmz (uninitialized): failed to connect to PHY: -EOPNOTSUPP
[ 7.447520] mv88e6085 f1072004.mdio-bus-mii:11 dmz (uninitialized): error -95 setting up PHY for tree 0, switch 1, port 3
[ 7.459833] mv88e6085 f1072004.mdio-bus-mii:11 dsl (uninitialized): fixed link full duplex 100Mbps not recognised
[ 7.473960] DSA: tree 0 setupcat dmesg-6.12.112-bad.txt
[ 0.000038] Switching to timer-based delay loop, resolution 5ns
[ 0.064456] clocksource: Switched to clocksource orion_clocksource
[ 3.680617] mv88e6085 f1072004.mdio-bus-mii:10: switch 0x1710 detected: Marvell 88E6171, revision 2
[ 3.779945] mv88e6085 f1072004.mdio-bus-mii:11: switch 0x1710 detected: Marvell 88E6171, revision 2
[ 6.421081] mv88e6085 f1072004.mdio-bus-mii:10: configuring for fixed/rgmii-txid link mode
[ 6.431821] mv88e6085 f1072004.mdio-bus-mii:10: configuring for fixed/rgmii-id link mode
[ 6.441261] mv88e6085 f1072004.mdio-bus-mii:10: Link is Up - 1Gbps/Full - flow control off
[ 6.453000] mv88e6085 f1072004.mdio-bus-mii:10: Link is Up - 1Gbps/Full - flow control off
[ 6.461656] mv88e6085 f1072004.mdio-bus-mii:11: configuring for fixed/rgmii-txid link mode
[ 6.473659] mv88e6085 f1072004.mdio-bus-mii:11: Link is Up - 1Gbps/Full - flow control off
[ 6.492394] mv88e6085 f1072004.mdio-bus-mii:10 lan5 (uninitialized): validation of gmii with support 00,00000000,00000000,000062ff and advertisement 00,00000000,00000000,000062ff failed: -EOPNOTSUPP
[ 6.512330] mv88e6085 f1072004.mdio-bus-mii:10 lan5 (uninitialized): failed to connect to PHY: -EOPNOTSUPP
[ 6.522066] mv88e6085 f1072004.mdio-bus-mii:10 lan5 (uninitialized): error -95 setting up PHY for tree 0, switch 0, port 0
[ 6.546314] mv88e6085 f1072004.mdio-bus-mii:10 lan1 (uninitialized): validation of gmii with support 00,00000000,00000000,000062ff and advertisement 00,00000000,00000000,000062ff failed: -EOPNOTSUPP
[ 6.566723] mv88e6085 f1072004.mdio-bus-mii:10 lan1 (uninitialized): failed to connect to PHY: -EOPNOTSUPP
[ 6.576465] mv88e6085 f1072004.mdio-bus-mii:10 lan1 (uninitialized): error -95 setting up PHY for tree 0, switch 0, port 1
[ 6.600409] mv88e6085 f1072004.mdio-bus-mii:10 lan6 (uninitialized): validation of gmii with support 00,00000000,00000000,000062ff and advertisement 00,00000000,00000000,000062ff failed: -EOPNOTSUPP
[ 6.620338] mv88e6085 f1072004.mdio-bus-mii:10 lan6 (uninitialized): failed to connect to PHY: -EOPNOTSUPP
[ 6.630070] mv88e6085 f1072004.mdio-bus-mii:10 lan6 (uninitialized): error -95 setting up PHY for tree 0, switch 0, port 2
[ 6.653940] mv88e6085 f1072004.mdio-bus-mii:10 lan2 (uninitialized): validation of gmii with support 00,00000000,00000000,000062ff and advertisement 00,00000000,00000000,000062ff failed: -EOPNOTSUPP
[ 6.674346] mv88e6085 f1072004.mdio-bus-mii:10 lan2 (uninitialized): failed to connect to PHY: -EOPNOTSUPP
[ 6.684087] mv88e6085 f1072004.mdio-bus-mii:10 lan2 (uninitialized): error -95 setting up PHY for tree 0, switch 0, port 3
[ 6.708035] mv88e6085 f1072004.mdio-bus-mii:10 lan7 (uninitialized): validation of gmii with support 00,00000000,00000000,000062ff and advertisement 00,00000000,00000000,000062ff failed: -EOPNOTSUPP
[ 6.727923] mv88e6085 f1072004.mdio-bus-mii:10 lan7 (uninitialized): failed to connect to PHY: -EOPNOTSUPP
[ 6.737664] mv88e6085 f1072004.mdio-bus-mii:10 lan7 (uninitialized): error -95 setting up PHY for tree 0, switch 0, port 4
[ 6.761566] mv88e6085 f1072004.mdio-bus-mii:11 lan3 (uninitialized): validation of gmii with support 00,00000000,00000000,000062ff and advertisement 00,00000000,00000000,000062ff failed: -EOPNOTSUPP
[ 6.781454] mv88e6085 f1072004.mdio-bus-mii:11 lan3 (uninitialized): failed to connect to PHY: -EOPNOTSUPP
[ 6.791193] mv88e6085 f1072004.mdio-bus-mii:11 lan3 (uninitialized): error -95 setting up PHY for tree 0, switch 1, port 0
[ 6.815097] mv88e6085 f1072004.mdio-bus-mii:11 lan8 (uninitialized): validation of gmii with support 00,00000000,00000000,000062ff and advertisement 00,00000000,00000000,000062ff failed: -EOPNOTSUPP
[ 6.835244] mv88e6085 f1072004.mdio-bus-mii:11 lan8 (uninitialized): failed to connect to PHY: -EOPNOTSUPP
[ 6.844974] mv88e6085 f1072004.mdio-bus-mii:11 lan8 (uninitialized): error -95 setting up PHY for tree 0, switch 1, port 1
[ 6.867806] mv88e6085 f1072004.mdio-bus-mii:11 lan4 (uninitialized): validation of gmii with support 00,00000000,00000000,000062ff and advertisement 00,00000000,00000000,000062ff failed: -EOPNOTSUPP
[ 6.889035] mv88e6085 f1072004.mdio-bus-mii:11 lan4 (uninitialized): failed to connect to PHY: -EOPNOTSUPP
[ 6.898772] mv88e6085 f1072004.mdio-bus-mii:11 lan4 (uninitialized): error -95 setting up PHY for tree 0, switch 1, port 2
[ 6.922680] mv88e6085 f1072004.mdio-bus-mii:11 dmz (uninitialized): validation of gmii with support 00,00000000,00000000,000062ff and advertisement 00,00000000,00000000,000062ff failed: -EOPNOTSUPP
[ 6.942740] mv88e6085 f1072004.mdio-bus-mii:11 dmz (uninitialized): failed to connect to PHY: -EOPNOTSUPP
[ 6.952388] mv88e6085 f1072004.mdio-bus-mii:11 dmz (uninitialized): error -95 setting up PHY for tree 0, switch 1, port 3
[ 6.964711] mv88e6085 f1072004.mdio-bus-mii:11 dsl (uninitialized): fixed link full duplex 100Mbps not recognised
[ 6.978044] DSA: tree 0 setup
[ 13.984730] mount_root: switching to ubifs overlayposiadam router GL-AX1800, OpenWrt 23.05-SNAPSHOT / LuCI openwrt-23.05 i chciałbym na nim zainstalować oscam.
Próbowałem zainstalować: oscam-mega45_11702-1_aarch64_cortex-a53, oscam_11760-1_aarch64_cortex-a53, oscam_2024-05-10-6d9801f2-1_aarch64_cortex-a53 te pakiety w ogóle nie instalują się zgłaszany jest error.
Prosiłbym o ewentualne wskazanie po kolei mam zainstalować.
pozdrawiam
]]>zwykły u-boot.kbw łapie zwieche ponieważ szuka drugiego banku pamięci
nowsze L-50 mają 2x 256MB ram co daje 512MB ram
działający U-Boot 2020.04 dla wariantu z 256 MiB RAM
pobrałem z oficjalnego repo https://downloads.openwrt.org/snapshots … boot-l-50/
procedura jak się dostać do L50
1 kabel szeregowy do portu console
dla tradycyjnego potru com poniżej a dla usb zamień na /dev/ttyUSB0
2
# picocom -b 115200 /dev/ttyS03 nacisnąć klawisz 3 wejść do menu serwisowego
podpiąć usb do portu usb ja używałem tylnego
4
# mkdir -p /tmp/usb5
# mount /dev/sda1 /tmp/usbteraz kolejne polecenia poniżej
tu kopiujemy u-boot fabryczny należny zrobić dwie kopie np mtd0_u-boot.bin oraz mtd0_u-boot2.bin
6
# dd if=/dev/mtd0 of=/tmp/usb/mtd0_u-boot.bin bs=1310727
# umount /dev/sda1 przechodzimy do komputera gdzie wykonamy pozostałe polecenia
polecam sprawdzić integralność plików .bin za pomocą polecenia sha256sum
###################################################################
### należny oczywiście skopiować również pozostałe partycje tak jak przy wgrywaniu w zwykłym L-50 ###
###################################################################
na komputerze wykonujemy pozostałe polecenia w folderze np ~/L50
zostawiam angielskie napisy bo to jest tłumaczenie maszynowe nie moje
Wyodrębnij plik kwbimage.cfg (wraz z tabelą RAM) z kopii zapasowej fabrycznego U-Boota 1.1.4
Extract the kwbimage.cfg (including the RAM table) from your stock U-Boot 1.1.4 backup
# dumpimage -T kwbimage -p -1 mtd0_u-boot.bin -o stock_kwb.cfg Wyodrębnij plik kwbimage.cfg z obrazu U-Boota OpenWrt 2020.04
Extract the kwbimage.cfg from the OpenWrt U-Boot 2020.04 image
# dumpimage -T kwbimage -p -1 u-boot.kwb -o openwrt_kwb.cfg Wyświetl wyodrębnioną fabryczną tabelę RAM i porównaj różnice między plikami
Print the extracted stock RAM table and compare the differences
# cat stock_kwb.cfg
# diff -u stock_kwb.cfg openwrt_kwb.cfg Wyodrębnij surowy kod U-Boota z obrazu OpenWrt u-boot.kwb
Extract the raw U-Boot payload from OpenWrt u-boot.kwb
# dumpimage -T kwbimage -p 0 u-boot.kwb -o u-boot-raw.bin Zbuduj plik u-boot-256m.kwb, używając fabrycznego pliku stock_kwb.cfg
oraz adresu wejściowego 0x00600000
Build u-boot-256m.kwb using your stock_kwb.cfg and 0x00600000 entry point
# mkimage -n stock_kwb.cfg -T kwbimage -a 0x00600000 -e 0x00600000 -d u-boot-raw.bin u-boot-256m.kwbw tym momencie mamy działający u-boot-256m.kwb który ładujemy do ram
# sudo kwboot -B 115200 /dev/ttyS0 -b u-boot-256m.kwb -t
[sudo] password for user:
kwboot version 2025.10
Detected kwbimage v0 with NAND boot signature
Patching image boot signature to UART
Sending boot message. Please reboot the target...\
Sending boot image header (512 bytes)...
25 % [.... ]
Done
Sending boot image data (631328 bytes)...
0 % [......................................................................]
1 % [......................................................................]
2 % [......................................................................]
4 % [......................................................................]
5 % [......................................................................]
95 % [......................................................................]
96 % [......................................................................]
97 % [......................................................................]
99 % [................................. ]
Done
Finishing transfer
[Type Ctrl-\ + c to quit]
U-Boot 2020.04 (Oct 15 2026 - 15:08:58 +0000)
Check Point L-50
SoC: Kirkwood 88F6281_A1
Model: Check Point L-50
DRAM: 256 MiB
NAND: 512 MiB
MMC:
Loading Environment from NAND... *** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Net:
Error: ethernet-controller@72000 address not set.
Error: ethernet-controller@76000 address not set.
No ethernet found.
Hit any key to stop autoboot: 0
ubi0: attaching mtd3
ubi0: scanning is finished
ubi0 error: ubi_read_volume_table: the layout volume was not found
ubi0 error: ubi_attach_mtd_dev: failed to attach mtd3, error -22
UBI error: cannot attach mtd3
UBI error: cannot initialize UBI, error -22
UBI init error 22
Please check, if the correct MTD partition is used (size big enough?)
Error, no UBI device selected!
Wrong Image Format for bootm command
ERROR: can't get kernel image!
=>
=>
=>
=> printenv
baudrate=115200
bootargs=console=ttyS0,115200
bootcmd=ubi part ubi; ubi read 0x800000 kernel; bootm 0x800000
bootdelay=1
fdtcontroladdr=fb1f948
ipaddr=192.168.1.1
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:0xc0000@0x0(u-boot)ro,0x40000@0xc0000(bootldr-env),0x7900000@0x100000(ubi),0x800000@0x7a00000(kernel-2),0x7100000@0x8200000(rootfs-2),0x7900000@0xf300000(default_sw),0x1800000@0x16c00000(logs),0x100000@0x18400000(preset_cfg),0x100000@0x18500000(adsl),-@0x18600000(storage)
serverip=192.168.1.2
Environment size: 511/131068 byteswyświetla prawidłowo DRAM: 256 MiB oraz NAND: 512 MiB
pozostaje pytanie czy nie można dodać flagi dla u-boot w celu nie lądowania domyślnie obu banków pamięci tylko sprawdzić czy urządzenie ma jeden czy dwa banki.
kolejna część to będą obrazy Initramfs i Sysupgrade
]]>Sprzęt ma fizycznie 256 MiB RAM i 512 MiB NAND
jest to okrojona wersja w stosunku do nowszego L-50
różnice wizualne
nie ma wejścia na kartę od frontu , niebieskie pole niema wycięcia jest jednolite po tym można najłatwiej rozróżnić
go od nowszego
nie ma wejścia an kartę sd
tylna naklejka obkleja dokładnie metalowe ramki portów od tyłu - nowsze mają charakterystyczne srebrne ramki
dolna nalepka Model: L50
Made in Taiwan
to jest po to żeby nie kupić czegoś czego nie chcemy
l50 można dostać na ebay dlatego ten post
jaka jest największa różnica ma tylko 256MB ram
co jest problematyczne dlatego że u-boot łapie zwieche
jest to dobrze opisane w tym wątku więc nie będę dublował
https://forum.openwrt.org/t/unable-to-i … 0/144572/6
powyższy wątek pozostaje nierozwiązany
spoiler
l50 działa razem z najnowszym 25.12-snapshot kernel 6.18.55
niestety trzeba przy tym rzeźbić
** MARVELL BOARD: RD-88F6281A LE
U-Boot 1.1.4 (Aug 11 2010 - 13:38:30) Check Point version: 3.4.27
U-Boot code: 00600000 -> 0067FFF0 BSS: -> 006CFB00
Soc: 88F6281 A1 (DDR2)
DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000 size 256MB
DRAM Total size 256MB 16bit width
Then it boots the stock Check Point Linux:
Booting Check Point RD-6281-A User Space...
Linux (none) 2.6.22.18 #20 Tue Aug 10 17:56:48 IDT 2010 armv5tejl arm
Number of LAN ports is 8.to jest log z u-boot tego checkpointa
reszta w dziale software
]]>
pozdro
]]>Mam postawiony Proxmox i chciałbym uniezależnić te dwie usługi od serwera Proxmox. Da radę coś w tym temacie powalczyć czy raczej "marne szanse"? Tylko Tailscale zżera pamięć czy też Cloudflare?
Mam domenę i wystawiam sobie jedną usługę na świat a dostęp do routera, proxmox czy innych usług dla bezpieczeństwa idzie przez tailscale.
i chciałbym dać im drugie życie, poprzez flashmod 16 MB. Czy jest tutaj ktoś kto by się podjął? Albo możecie mi kogoś wskazać? Jaki byłby to koszt?
]]>I'm following stich86's MF289F recovery guide (Windows) on a bare MF289F module (mini-PCIe to USB adapter, no UART access). I'm stuck at the same place every time and would appreciate any idea.
Setup
- Original firmware before the brick: CR_VDFDEMF289FV1.0.0B08 (note: no "1" after F)
- Package flashed: Vodafone DE - AT2, which is VDF_DE_MF289F1MODV1.0.0B05 (the config inside the sysfs ztedata is the same string)
- Tool: qfenix (flash, efsbackup, efsls/efspush/efspull, efsrestore, readall)
Symptom
1. Flash from EDL works. Module comes up as 19d2:0016 with the 3 TTY. At this point qfenix efsbackup completes and AT commands work.
2. After ANY reboot (QCN restore, AT+CFUN=1,1, qfenix reset, or even just the auto reset after readall) the module comes back as 19d2:0076, a single "ZTE Diagnostics Interface" COM port, no NMEA/AT. QPST and EFS Explorer trigger a reboot when they connect. I have to short the board to get back into EDL.
What I tried (always the same result)
- Dummy QCN, my own QCN, and no QCN at all
- Pushing the "config" file to the EFS root with qfenix efspush before rebooting; verified with efspull + fc /b, identical to ztedata/config from the flashed sysfs. It survives the reboot (found in efs2.bin)
- QPST QCN restore after pushing config (config still present afterwards)
- AT sequence from the guide (ZCDRUN=8, ZCDRUN=F, ZSNT=6,0,0, CFUN=1,1) before the reboot
- Writing back my full original efs2 partition (11,534,336 bytes, dumped with QFIL before the brick)
- Other firmware versions from the MEGA folder: only this one gives me 3 TTY
- Different USB ports, Windows and Linux
Partition comparison (qfenix readall, 28 partitions, fresh-flash state vs bricked state)
- Identical: sbl, tz, abl, uefi, boot, mibib, recovery, recoveryfs, devinfo, misc, fota
- Different: ddr (about 750 bytes differ between EVERY dump, bricked or not, so it looks like normal training data), efs2, and the UBI partitions
- ZTERW contents (extracted with ubi_reader) are identical except logfs/syslog
Syslog (ZTERW logfs, bricked state)
- zte_adapter_cfg requests the file "config" from the modem (q6_file:config) and gets "cfg send to modem failed, qmi_error:0, resp_msg.resp.error:3", retries about 20 times over ~18 s, then "cfg get config file from Q6 failed"
- "read nv usb_speed_mode empty" and "Don't find the USB cmd[0]"
- The Linux side keeps running for at least 2-3 minutes after that. The clock restarts from a fixed value (hw_diff_systime 1700950138) every boot, so the dates in the log are meaningless
- I have not compared with a healthy-boot syslog, so I don't know if error 3 also appears there
The 0076 state
- qfenix lists it as a DIAG/EDL COM port but it refuses Firehose. The first packets from the module look like Sahara HELLO with mode 2 followed by command 9 (memory debug) with address 0x14878B20 and size 0x5B0. My reading, which may be wrong, is that the SoC crashes and offers a RAM dump
- qfenix ramdump stops right after that packet, same on Linux, so I can't get the dump
Questions
1. Are F and F1 firmware interchangeable? My original firmware was named MF289F, the package is MF289F1.
2. Has anyone seen this "works once, crashes on every following boot" behaviour, or seen a module end up in Sahara memory-debug mode?
3. Does the error 3 on config mean anything specific (missing NV item, file location, version check)?
4. Is there a tool that can extract the ramdump in this mode when qfenix stops?
5. Anything else worth checking before I consider the hardware (NAND/RAM) damaged?
I can post full logs, partition dumps hashes or the syslog if useful. Thanks!
]]>