I've been told that comfast no longer makes CF-E110N with 16MB. This might be untrue, as that's the sales guy who tried everything so far with me. Either way, I'm stuck with a 8MB version of this device, and I'm wondering if there's anyway to load a basic OpenWRT onto it. All I want to do is to clone my MAC address, and the factory firmware doesn't allow you to do that.
Hello,
I had the same issue, CF-E110 with 8MB flash.
I retreived the flash memory map from the EOM firmware log (see previous screenshot) and modified accordingly the dts file of the OpenWRT 19.0.rc2 distribution code, Then I compiled the new firmware and it works fine now.
In case you have tried the 16M firmware maybe you are stuck in the boot process. Using the TFTP recovery method works well and allows you to either reload the EOM firmware (I did it several time) or the new image.
Hi 66enligne. Thanks for that. I was able to recover the original firmware via web interface, and a reset key combination. Now, I just setup a VM for OpenWRT compiling, and it seems to be working. I was able to create .config file using "make menuconfig" successfully for:
Target System: Atheros AR7xxx/AR9xxx
Subtarget: Generic
Target Profile: COMFAST CF-E320N v2
but I do not know where to find the DTS file you're referring to. My syslog is as below:
m25p80 spi0.0: en25qh64a (8192 Kbytes)
7 cmdlinepart partitions found on MTD device spi0.0
Creating 7 MTD partitions on "spi0.0":
0x000000000000-0x000000010000 : "u-boot"
0x000000010000-0x000000020000 : "art"
0x000000020000-0x0000001a0000 : "kernel"
0x0000001a0000-0x0000007e0000 : "rootfs"
mtd: device 3 (rootfs) set to be root filesystem
1 squashfs-split partitions found on MTD device rootfs
0x000000530000-0x0000007e0000 : "rootfs_data"
0x0000007e0000-0x0000007f0000 : "configs"
0x0000007f0000-0x000000800000 : "nvram"
0x000000020000-0x0000007e0000 : "firmware"
where do I find the DTS file to edit?
DTS is for ath79, not the deprecated ar71xx.
Many thanks for that. I got it working on the 8MB Comfast CF-E110N-V2. With the original firmware (CF-E110NV2_V2.6.0.6.bin) syslog:
m25p80 spi0.0: en25qh64a (8192 Kbytes)
7 cmdlinepart partitions found on MTD device spi0.0
Creating 7 MTD partitions on "spi0.0":
0x000000000000-0x000000010000 : "u-boot"
0x000000010000-0x000000020000 : "art"
0x000000020000-0x0000001a0000 : "kernel"
0x0000001a0000-0x0000007e0000 : "rootfs"
mtd: device 3 (rootfs) set to be root filesystem
1 squashfs-split partitions found on MTD device rootfs
0x000000530000-0x0000007e0000 : "rootfs_data"
0x0000007e0000-0x0000007f0000 : "configs"
0x0000007f0000-0x000000800000 : "nvram"
0x000000020000-0x0000007e0000 : "firmware"
The file I changed was: openwrt/target/linux/ath79/dts/qca9533_comfast_cf-e110n-v2.dts - only this section was required to be changed
&spi {
status = "okay";
num-cs = <1>;
flash@0 {
compatible = "winbond,en25qh64a", "jedec,spi-nor";
reg = <0>;
spi-max-frequency = <25000000>;
partitions {
compatible = "fixed-partitions";
#address-cells = <1>;
#size-cells = <1>;
partition@0 {
label = "u-boot";
reg = <0x000000 0x010000>;
read-only;
};
art: partition@10000 {
label = "art";
reg = <0x010000 0x020000>;
read-only;
};
partition@20000 {
compatible = "denx,uimage";
label = "firmware";
reg = <0x020000 0x7e0000>;
};
partition@ff0000 {
label = "nvram";
reg = <0x7f0000 0x800000>;
read-only;
};
};
};
};
Then, in make menuconfig:
Target System: Atheros ATH79 (DTS)
Subtarget: Generic
Target Profile: COMFAST CF-E110N v2
LuCI > Collections > luci * built-in
Save, then "make".
Then, the web recovery was slightly fiddly, but it worked with this:
Comfast CF-E110V2 recovery steps:
1. Connect Ethernet cable between CPE LAN port and POE injector's CPE port
2. Connect Ethernet cable between POE injector's PC port and your PC
3. Set your PC LAN with a static IP address: 192.168.1.10 (sometimes this could be is 192.168.10.10), subnet mask 255.255.255.0
4. Press and hold the reset button. KEEP HOLDING until instructed to release.
5. Power on POE injector.
6. Watch the lights on the back of the CPE.
7. At first, you will see SEQUENCE A: Power (green), Signal1 (red), Signal2 (red), Signal3 (green), Signal4 (green) lights.
7. After, about 7 seconds, the lights will go to SEQUENCE B: Power (green), WAN (green), LAN (green), WIFI (green) lights on.
8. After about 2 seconds, you will see it change it briefly (less than 0.5 second) to SEQUENCE A.
9. The light sequence will return to SEQUENCE B for about 2 seconds.
10. The light sequence will go again to SEQUENCE A briefly (less than 0.5 second).
11. As soon as the light sequence returns to SEQUENCE B, release the reset button.
12. The light sequence will remain on SEQUENCE B for approx. 7 seconds.
13. Then, the light sequences will alternate very rapidly and return to SEQUENCE B.
14. At this stage, the device is in LAN recovery mode.
15. In your browser go to http://192.168.1.1 (or 192.168.10.1, if you set differently it above)
16. Click Browse to select the target software
17. Then click Upgrade
18. This process can take up to 5 minutes.
19. After the upgrade is complete, the device will automatically restart.
20. Set your IP address back to dynamic (DHCP).
Now, I have a working OpenWRT device. THANKS ALL FOR YOUR HELP!
1 Like
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.