It really works!
I logged in as root under SSH on firmware 1.1.16.
2.0MM cable DuPont connect TTL
F+Enter to safefail
Edit shadow, group, passwd replace root user 4230W (replace user. adduser cannot connect to reboot)
Login web backup configuration
I got root-console without disassembling the router and without connecting via TTL. I restored Config.cfg from the folder 1.1.16. Then I connected to the router via SSH on the LAN- port using the PuTTY utility.
SSH login: 4230w, password: linuxbox
File transfer also works with the SCP-protocol (WinSCP utility). Only first you need to exit the SSH console.
Login and password for WEB-interface: admin / linuxbox
efsg, thanks again for your work!
If you can see output on the serial console but can't type anything, you need to remove the two resistors I circled in red in this image: https://ibb.co/G7cY1fb
They are labelled R415 and R1126. You should be able to knock them off with a pointy object like the tip of a multimeter or a knife, you just have to be careful not to knock anything else off. Also you can interrupt uboot after doing that
Edit: forgot to mention that this is the opposite side of the board under the serial port
All of the stable initramfs images here boot fine but are useless because they don't have compatible ethernet or wifi modules. I'm trying to build my own image but it keeps crashing when it tries to set up power management (I assume). Can anyone help out with this? Here's the boot log. The same also happens with snapshot images.
Apparently booting via initramfs will not work any longer due to this patch:
My Netgear R7800, which is very similar to the Askey RAC2V1K, also could not boot properly. WiFi interfaces will not come up. Even after I reverted the 'offending' patch, the warnings (which you also saw in your posted bootlog) were gone, but the WiFi interfaces are still missing.
I was told the only way to test now is to flash it into the router.
Well I rebuilt openwrt with the 4.19 kernel instead if 5.4 and the pci error is gone now but I still get the regulator errors at the end. Here's the new boot log.
Edit: To use 4.19, edit target/linux/ipq806x/Makefile and change KERNEL_PATCHVER. Also, do you know how to get a dts file from a dtb file?
You need some tools to do that. This link may help:
Alright so I got some device tree files out of it. I uploaded all the dtb files here and converted them to dts files. I think the main thing that's different is the nand. On the wikidev page it says it has Spansion flash but on one of the routers I have it's MXIC flash
Yet another edit: if you run
cat /proc/device-tree/model you can see what revision your board is
mtd no offset！
check here Spectrum RAC2V1K TTL SSH Firmware(about Askey 4230W)
Alright I got openwrt mostly working on this router. It's on 4.19 kernel because of the issue 4 posts above. Here's a list of things that are working, working but needs more testing / more work, and broken:
Booting (only over tftp)
Networking (I'm not sure if the offsets for the ART partition are consistent across all of these routers and I'm only getting 200mbps wired instead of the 500mbps it's usually capable of on my internet)
WiFi (Same issue as above)
Front LED (Askey uses 3 gpios to do like 7 or 8 different things)
WPS Button (Can't figure out the correct GPIO pin)
Not all the ram is being allocated
Flashing to nand flash (the mtd partition layout is confusing, it looks like it boots from a ubi partition by default, it looks like some routers use different flash chips, and none of the uboot commands have a help)
I'll make another post in a bit with info on how you can help with networking and wifi.
Turning on software flow-offload should help.
Do you need to reboot for that to take affect? I tried enabling it but it didn't help much.
There's no need to reboot. It's odd tho that an ipq8065 board could only do 200mbps. Try setting the CPU governor to performance and try again.
I'll try that in a bit. I'm making the tutorial for trying out the firmware.
some routers use different flash chips
mtd none offsets
mtd none offsets
I really don't get what you mean by that.
Sorry i don't speak english
mtd has no partition offsets
It actually does but they get defined by uboot. Before linux loads, there's a line like this
This is what tells linux the partition sizes and offsets
Edit: if you interrupt uboot and run
smeminfo, it will tell you where each partition starts and what the size of it is in a more readable format
Here's a tutorial on how you can try it: https://pastelink.net/1p69j
I'll upload the build files a bit later when I figure out how to use git.