Hi everyone, I received a few days ago a COMFAST CF-E391AX AP. I've been using OpenWrt for a few years, but I have never ported it to a new device, and I’m not sure whether I am on the right track. I am worried about missing something that could lead me to brick my device. I would be grateful if s…

I successfully flashed OpenWrt on the AP! Thank you to @db260179 , @ElektromAn and @who_what8 for helping me solve this challenge. Check this repo to compile your firmware. I will stress‑test the AP a bit before requesting the merge [LuCI] As I promised earlier, here is a picture of the UART pi…

[image] clsergent: is the .config file ok? if in doubt, you can delete your .config file and make menuconfig and selecting your device from the menu to ensure it's "clean" [image] clsergent: is it alright to use the DTS without any modification? You should not use the factory DTS file…

First of all, thank you very much taking time to read and answer my post! About the .config file, I'm really unsure about which values should be selected to make a fully working firmware. Very few values are ticked by default, while the filogik config file used to compile distributed firmwares (suc…

[image] clsergent: About the .config file, I'm really unsure about which values should be selected to make a fully working firmware. Very few values are ticked by default, while the filogik config file used to compile distributed firmwares (such as this one ) seems to tick almost everything... T…

Alright, I'm creating a brand new DTS following OpenWrt conventions as much as possible, copying as much as possible from cf-e393AX. I'm already facing differences between the mt7981b.dtsi and my stock DTS. Indeed, the cf-e391AX has a crypto: compatible = "inside-secure,safexcel-eip97"; reg =…

[image] clsergent: while mt7981b.dtsi doesn't seem to have any crypto, which I don't understand because e393AX has a crypto entry: &crypto { status = "okay"; }; Where is it described? The upstream mt7981b.dtsi file doesn't include crypto, but a patch exists within Openwrt repo to add it…

[image] clsergent: &crypto { status = "okay"; }; Where is it described? now it's get messy :wink: the decribed patch form @who_what8 is a modification from "uptream". The driver is upstream

I followed @who_what8 advice and compiled OpenWrt for cf-e393ax, then retrieved the patched ˋmt7981b.dtsi` file from the build directory. I created a new DTS including this DTSI, with very little difference with cf-e393ax (mainly Ethernet wiring) and successfully compiled. I expect to flash my dev…

Hi, Comfast are very lazy when adding new devices, so usually its a case of copy and paste an existing comfast, as per the 393ax. then just changing the number. Tweaking the ethernet and gpio numbers - I did e593ax recently, had a new phy Airoha AN8801SB and no switch. Make sure to have serial ac…

Crystal clear. Just a question about how to access uart pins as I have yet to open my device: I read that on the cf-e393ax one can solder wires on the rear face of the soc to avoid removing the heatsink, is there a picture of this anywhere?

Comfast cf-e391ax

For Developers

who_what8 April 16, 2026, 4:54pm 13

Did you create a branch for the CF-E593AX? I have a PR open and we can do a comparison.

Let's move the CF-E593AX talk to:

This is for you to find out since you are the only one in this thread with the device. Thankfully, Comfast devices are not difficult to open.