Gowee
February 20, 2022, 1:39pm
1
Hi.
My Letv LBA-047-CH router hasn't been used for a few years. Previously, the router is flashed with openwrt-ar71xx-generic-ap147-010-rootfs-squashfs.bin . Almost everything works well except the reset button.
I am going to re-use it again. So I would like to upgrade to a more recent OpenWrt version. The model name turns out not to be listed in the Table of Hardware and https://downloads.openwrt.org/ . But it is actually listed in https://github.com/openwrt/openwrt/blob/6f88526fa4e0aa5f60834d181d04f8a9911887be/target/linux/ath79/image/generic.mk#L1440 .
Why isn't it listed in the ToH and no release is provided?
It has to be added, as it's not automatic. Also, is this actualy the firmware for this device?
One of the admins can add it if so.
tmomas
February 20, 2022, 3:54pm
3
Done, dataentry added.
If your problem is solved, please consider marking this topic as [Solved]. See How to mark a topic as [Solved] for a short how-to.
slh
February 21, 2022, 3:53am
4
Is neither the correct device, nor has it any chance of actually working (missing kernel, just the rootfs, flashing that would brick the device). AP147 is the codename for one of QCA's reference designs/ devboards, while your Letv LBA-047-CH might be similar (based on this reference design), there will be differences (at least the flash partitioning, ar71xx could auto-detect that to some extent, ath79 cannot) which will break the idea.
That aside, there now is:
committed 11:15PM - 31 Oct 21 UTC
Specifications:
SOC: QCA9531 650 MHz
ROM: 16 MiB Flash (Winbond W25Q128FV)
RAM: … 128 MiB DDR2 (Winbond W971GG6SB)
LAN: 10/100M *2
WAN: 10/100M *1
LED: BGR color *1
Mac address:
label C8:0E:77:xx:xx:68 art@0x0
lan C8:0E:77:xx:xx:62 art@0x6
wan C8:0E:77:xx:xx:68 art@0x0 (same as the label)
wlan C8:0E:77:xx:xx:B2 art@0x1002 (load automatically)
TFTP installation:
* Set local IP to 192.168.67.100 and open tftpd64, link lan
port to computer.
Rename "xxxx-factory.bin" to
"openwrt-ar71xx-generic-ap147-16M-rootfs-squashfs.bin".
* Make sure firmware file is in the tftpd's directory, push
reset button and plug in, hold it for 5 seconds, and then
it will download firmware from tftp server automatically.
More information:
* This device boot from flash@0xe80000 so we need a okli
loader to deal with small kernel partition issue. In order
to make full use of the storage space, connect a part of the
previous kernel partition to the firmware.
Stock Modify
0x000000-0x040000(u-boot) 0x000000-0x040000(u-boot)
0x040000-0x050000(u-boot-env) 0x000000-0x050000(u-boot-env)
0x050000-0xe80000(rootfs) 0x050000-0xe80000(firmware part1)
0xe80000-0xff0000(kernel) 0xe80000-0xe90000(okli-loader)
0xe90000-0xff0000(firmware part2)
0xff0000-0x1000000(art) 0xff0000-0x1000000(art)
Signed-off-by: Shiji Yang <yangshiji66@qq.com>
1 Like
Gowee
February 21, 2022, 4:44am
5
Also, is this actualy the firmware for this device?
Seems not, but it worked at that time.
Is neither the correct device, nor has it any chance of actually working (missing kernel, just the rootfs, flashing that would brick the device)
Haven't used it for years, so I might remember incorrectly. Should be openwrt-18.06.1-ar71xx-generic-ap147-010-squashfs-sysupgrade.bin , I think. It is actually still working now:
Model Atheros AP147-010 reference board
Architecture Qualcomm Atheros QCA9533 ver 2 rev 0
Firmware Version OpenWrt 18.06.1 r7258-5eb055306f / LuCI openwrt-18.06 branch (git-18.228.31946-f64b152)
Kernel Version 4.9.120
Gowee
February 21, 2022, 4:47am
6
Thank you all for the help.
Gowee
February 21, 2022, 6:10am
7
I am trying to sysupgrade with the snapshot image. But sysupgrade rejects since the device name does not match. Is it fine to proceed with -F
(force) in such case?
root@OpenWrt:~# sysupgrade -i -n openwrt-ath79-generic-letv_lba-047-ch-squashfs-sysupgrade.bin
Image not in /tmp, copying...
Device ap147-010 not supported by this image
Supported devices: letv,lba-047-ch
Image check 'fwtool_check_image' failed.
Gowee
February 23, 2022, 11:03am
8
But sysupgrade rejects since the device name does not match. Is it fine to proceed with -F
(force) in such case?
Bricked (fortunately, u-boot is still working). Seems not the right way.
tmomas
Closed
February 24, 2022, 11:04am
9
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.