The image from luci is this one:
Hi,
I am following your progress closely as I also have a v4 and would like to install OpenWRT. Have you had any success with the v3 image?
1 Like
Hi,
@restylk seems to have the v3 image running on v4.
I’m taking the more cautious approach, still trying to get fw_printenv etc working on the image from Cudy. I’m doing so to try get a uboot shell, to be able to load v3 from tftp into ram without flashing v3 onto storage. This is to slowly find differences between v3 and cudy’s image, to see what if anything needs to change in v3 for a final v4 support.
I’m doing it slowly and intermittently so I can’t say when. I’m also very new to owrt dev so having to learn as I go (I am getting good assistance from the irc channel too)
Thanks
I have been trying to get fw_printenv and fw_setenv working on the vendor owrt with no luck. I wanted to change uboot env to set it to boot images off tftp, where I planned to put v3 image and boot it into ram without flashing it to storage.
cat /prod/mtd shows hints of where the uboot env is:
mtd1: 00010000 00010000 "u-boot-env"
But trying to change it fails due to read-only mtd:
Can't open /dev/mtd1: Permission denied
Error: can't write fw_env to flash
Digging around, seemed I needed kmod-mtd-rw package to make /dev/mtd1 read-write, but opkg refused to install it:
pkg_hash_fetch_best_installation_candidate: Packages for kmod-mtd-rw found, but incompatible with the architectures configured
I then tried manually downloading the ipk file and extracting the .ko module, but modprobe of the file immediately panics the kernel.
I then tried building the module using the sdk openwrt-sdk-23.05.5-ramips-mt7621_gcc-12.3.0_musl.Linux-x86_64 which built the ipk, but copying the ipk to the router, opkg complained with the same error and refused to install it.
The guys on irc then told me the module from a build won’t load into a vendor built kernel.
Any advice then? How does the team work on a new device in a case like this, where uboot by default won’t give a shell to test images from tftp, and editing the uboot env is almost impossible?
Only guessing now, checked fw_printenv from within the Cudy image?
Console timeout might be set to zero, it'd make it read only.
Hello,
I'm not a developer, but I have three Cudy WR1300 v4 routers at home, of which I only really need two. So I took the plunge and installed the intermediate installation posted here in the forum. Then I installed the OpenWRT version for the v3, since the hardware specifications are very similar between the v3 and v4. I checked the "Force Installation" box. It seems to be working pretty well. However, I'm only using the router as an access point in a mesh network.