@lmore377 thank you for all your time and work on this device. Now I'm in process of flashing my first SAC2V1K and found a small mistake in the "readme.md" 
All the best from Ukraine!
The fi means that it's the end of the script. Tell me if it fails and if it does I'll take a look at it
1 Like
Thank you for quick reply! Yes, it was saying "bad syntax". When I've changed "fi" to "if" it'd worked. ( Update 2 hours later: just checked the "fi" and it worked also...) But I have stuck with some error at the end of flashing sysupgrade.bin --
Fri Dec 25 07:37:00 UTC 2020 upgrade: Performing system upgrade...
removing ubiblock0_1
[ 332.663188] block ubiblock0_1: released
Volume ID 0, size 23 LEBs (2920448 bytes, 2.7 MiB), LEB size 126976 bytes (124.0 KiB), dynamic, name "kernel", alignment 1
Volume ID 1, size 31 LEBs (3936256 bytes, 3.7 MiB), LEB size 126976 bytes (124.0 KiB), dynamic, name "rootfs", alignment 1
Set volume size to 211034112
Volume ID 2, size 1662 LEBs (211034112 bytes, 201.2 MiB), LEB size 126976 bytes
(124.0 KiB), dynamic, name "rootfs_data", alignment 1
sysupgrade successful
umount: can't unmount /dev: Resource busy
umount: can't unmount /tmp: Resource busy
[ 335.934188] reboot: Restarting system
I have such machine but the board says: RT4230W-D187 Rev.9.3
sac2v1k / AE32 xxxx xxxx / 177e (rev 10) / taiwan (id 3) /winbond / 256mb
I will recheck mine this weekend. thnaks
The text on the board doesn't seem to have a correlation to the actual revision. If there is one I haven't seen it.
First of all, thank you for your work.
I have bought RAC2V1K. Board's label says RT4230W-D187(RoHS)A Rev:9.3. But ubus call system board | grep model (on the stock firmware) says: Askey RT4230W-D187/REV10. So I think I have rev. 10 instead of the rev. 6.
I have followed Method 1 (for RAC2V1K) and got soft brick (blink led; no access).
Then I followed Method 2 (section for SAC2V1K) and unbricked it.
Also, I think that needs to be replaced:
setenv bootcmd "setenv mtdids nand0=nand0 && set mtdparts mtdparts=nand0:0xDC00000@0x2400000(firmware) && ubi part firmware && ubi read 0x44000000 kernel 0x6e0000 && bootm; fi"
to this
setenv bootcmd "setenv mtdids nand0=nand0 && set mtdparts mtdparts=nand0:0xDC00000@0x2400000(firmware) && ubi part firmware && ubi read 0x44000000 kernel 0x6e0000 && bootm"
(I had an error on it: looks like the condition is was broken).
Maybe the methods descriptions also need corrections due to different revisions of the board.
fi isn't needed actually. I just remembered that a while ago, the pci bus initialization was broken in openwrt so I had to run bootipq (which happens to initialize the bus correctly), wait for it to fail, then run my command for booting openwrt. They fixed that at some point so the bootipq workaround wasn't needed anymore.
1 Like
I uploaded an updated image to the repo and the opkg repo Don't forget to replace /etc/opkg/distfeeds.conf with the one in github.
Some quick tips to increase speed if you have 500+ Mbits/s speed.
All you need is to install irqbalance and set the CPU governor to performance mode.
- Set lmore377's repo in /etc/opkg/distfeeds.conf:
src/gz openwrt_core http://rt4230w-openwrt.ddns.net:8081/snapshots/targets/ipq806x/generic/packages
src/gz openwrt_base http://rt4230w-openwrt.ddns.net:8081/snapshots/packages/arm_cortex-a15_neon-vfpv4/base
src/gz openwrt_luci http://rt4230w-openwrt.ddns.net:8081/snapshots/packages/arm_cortex-a15_neon-vfpv4/luci
src/gz openwrt_packages http://rt4230w-openwrt.ddns.net:8081/snapshots/packages/arm_cortex-a15_neon-vfpv4/packages
src/gz openwrt_routing http://rt4230w-openwrt.ddns.net:8081/snapshots/packages/arm_cortex-a15_neon-vfpv4/routing
src/gz openwrt_telephony http://rt4230w-openwrt.ddns.net:8081/snapshots/packages/arm_cortex-a15_neon-vfpv4/telephony
- Update opkg DB, install irqbalance, run irqbalance:
opkg update && opkg install irqbalance && irqbalance - Set the governor:
echo performance > /sys/devices/system/cpu/cpufreq/policy0/scaling_governor
echo performance > /sys/devices/system/cpu/cpufreq/policy1/scaling_governor
That's all. If the result is acceptable, you can add irqbalance and governor settings to autostart in any preferred method (uci/luci/config/rc.local etc).
Before (my speed is ~1gbps):
After:
1 Like
Wow that's crazy! I only have a 480mbps connection and I don't have good hardware to do iperf tests with. Can you do some tests over wifi? @nolseek has been working on getting the wifi board files from the OEM firmware working so that'll hopefully improve things even more. We'll upload them to the improved_wifi branch in the github repo.
Unfortunately, I don't have good wifi equipment (except a smartphone and old wifi card) for testing right now.
Howdy. I finally got back to this and was able to install over firmware 1.1.31. Thanks lmore377.
Question for any other users of this device. During normal operation, does the indicator light slowly pulse blue or is it a steady blue led?
That's just how it is. The LED has a separate microcontroller that does the effects and colors and it changes based on how the 3 led gpio pins in /sys/class/leds are changed and a solid blue takes 2 gpio pins. Here's an example if you want to mess with it
on,off,off = red glow
on,off,on = red/blue glow
off,on,on = solid blue
understood. I just wanted to make sure that the blue glow indicated proper function.
Hi,
I have extended the work of @lmore377 by adding WiFi board calibration data specific to the Askey, for improved WiFi performance. The updated builds for improved WiFi are here
There are two sub-folders - 1.0 and 2.0 - with two different versions of board calibration files. One is not necessarily better than the other. Try both and see which works better for you.
Please test the builds and share your results on this thread along with your build version number, router model, and router revision number, so that I can track and further fine tune the board calibration files for improved WiFi in future builds.
i will give it a shot. do I need to do anything with the /etc/apt/dist.conf?
No, I don't think so. I have uploaded only the sysupgrade file (which you can use in Luci) to permanently upgrade, and the initramfs file (which you can use in U-boot) for temporary upgrade.