Hi
Had a fresh unit loaded with 2.7 factory FW
I flashed the unit using the recommended image cf-e320n-v2-squashfs-sysupgrade.bin but the device locked in a infinite boot loop.
Then I equiped the board with a serial console connection (used as a process spy). When robooting the console reports a Kernel panic and loops to reboot infinitely.
Then I reload the V2.6 factory image retrieved from your site using the TFTP server (because I didnt save the original 2.7 before flashing openwrt)
I recovered a working unit (AP and bridge mode working)
I have tried to flash the snapshot build. The boot sequence execute properly but I didnt get a working unit (no bad message at the console, but the only lightening led was power)
I then reflash the factory FW V2.6 but did't get a full working unit (only AP mode working not the bridge one apparently)
Can you help or give recommendations (I have pictures of the board if you are interrested for the site documentation)
THX
Did you see if the device booted successfully?
Lights must still be programmed on most OpenWrt devices.
Hello
I had to re-flash the snapshop version as I had to collect boot info which i didn't previously. I reflash using TFTP instead of the SW update option of the in place factory V2.6 version.
This time the process complete and the device can be access on LAN port at the usual 192.168.1.1 address.
However the boot is not fully successful due to a flash mismatch. The boot sequence expect a w25Q128 (16MB) while the one installed on board is a EN25QH64 (8MB). As a consequence the memory mapping of the partitions is not adequate and exceeds the boundaries of the physical memory (see capture and the consequence on nvram partition) would make sense to manage 8/16MB option in the boot and partition size config.
[ 0.333588] m25p80 spi0.0: found en25qh64, expected w25q128
[ 0.339454] m25p80 spi0.0: en25qh64 (8192 Kbytes)
[ 0.344365] 4 fixed-partitions partitions found on MTD device spi0.0
[ 0.350936] Creating 4 MTD partitions on "spi0.0":
[ 0.355896] 0x000000000000-0x000000010000 : "u-boot"
[ 0.362037] 0x000000010000-0x000000020000 : "art"
[ 0.367782] 0x000000020000-0x000000ff0000 : "firmware"
[ 0.373170] mtd: partition "firmware" extends beyond the end of device "spi0. 0" -- size truncated to 0x7e0000
[ 0.387554] 2 uimage-fw partitions found on MTD device firmware
[ 0.393750] Creating 2 MTD partitions on "firmware":
[ 0.398889] 0x000000000000-0x0000001a0000 : "kernel"
[ 0.404945] 0x0000001a0000-0x0000007e0000 : "rootfs"
[ 0.410976] mtd: device 4 (rootfs) set to be root filesystem
[ 0.416872] 1 squashfs-split partitions found on MTD device rootfs
[ 0.423343] 0x000000390000-0x0000007e0000 : "rootfs_data"
[ 0.429885] 0x000000ff0000-0x000001000000 : "nvram"
[ 0.434932] mtd: partition "nvram" is out of reach -- disabled
https://openwrt.org/toh/comfast/cf-e110n
- says 8mb for devices and shows 16 in the bootlogs.... could be positive.... need more info... / input from users of device.... ( edit found your post here: CF-E110N: 8MB or 16MB flash? ) are there any other identifiers on the board etc? might help future users if you we can nail down what's going on? ( would need a partition layout/bootlog from OEM )....
- also says LAN and WAN are inverted.... did you see/test this behaviour?
- Maybe I was ot clear enough. The bootlog reports 8MB while expecting 16MB (I also check the on board chip references and verify with the supplier datasheet). See below
[ 0.333588] m25p80 spi0.0: found en25qh64, expected w25q128
[ 0.339454] m25p80 spi0.0: en25qh64 (8192 Kbytes)
[ 0.344365] 4 fixed-partitions partitions found on MTD device spi0.0
[ 0.350936] Creating 4 MTD partitions on "spi0.0":
[ 0.355896] 0x000000000000-0x000000010000 : "u-boot"
[ 0.362037] 0x000000010000-0x000000020000 : "art"
[ 0.367782] 0x000000020000-0x000000ff0000 : "firmware"
[ 0.373170] mtd: partition "firmware" extends beyond the end of device "spi0. 0" -- size truncated to 0x7e0000
[ 0.387554] 2 uimage-fw partitions found on MTD device firmware
[ 0.393750] Creating 2 MTD partitions on "firmware":
[ 0.398889] 0x000000000000-0x0000001a0000 : "kernel"
[ 0.404945] 0x0000001a0000-0x0000007e0000 : "rootfs"
[ 0.410976] mtd: device 4 (rootfs) set to be root filesystem
[ 0.416872] 1 squashfs-split partitions found on MTD device rootfs
[ 0.423343] 0x000000390000-0x0000007e0000 : "rootfs_data"
[ 0.429885] 0x000000ff0000-0x000001000000 : "nvram"
[ 0.434932] mtd: partition "nvram" is out of reach -- disabled
You ask about the OEM partition layout: see below
Mapping from CF-E110NV2_V2.6.0.6
[ 0.710000] Creating 7 MTD partitions on "spi0.0":
[ 0.720000] 0x000000000000-0x000000010000 : "u-boot"
[ 0.730000] 0x000000010000-0x000000020000 : "art"
[ 0.730000] 0x000000020000-0x0000001a0000 : "kernel"
[ 0.740000] 0x0000001a0000-0x0000007e0000 : "rootfs"
[ 0.750000] mtd: device 3 (rootfs) set to be root filesystem
[ 0.750000] 1 squashfs-split partitions found on MTD device rootfs
[ 0.760000] 0x000000530000-0x0000007e0000 : "rootfs_data"
[ 0.770000] 0x0000007e0000-0x0000007f0000 : "configs"
[ 0.770000] 0x0000007f0000-0x000000800000 : "nvram"
[ 0.780000] 0x000000020000-0x0000007e0000 : "firmware"
- using snapshot FW build for E110, LAN and WAN are NOT inverted (maybe my previous mail wasn't clear enough)
BR
Are you comfortable with the buildroot?
cat target/linux/ath79/dts/qca9533_comfast_cf-e110n-v2.dts | grep -A27 partitions
Matching the OEM layout in the section below ( optionally fix the flash type ) may help.
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 0x010000>;
read-only;
};
partition@20000 {
compatible = "denx,uimage";
label = "firmware";
reg = <0x020000 0xfd0000>; < ***fix size
};
partition@ff0000 {
label = "nvram";
reg = <0xff0000 0x010000>; < ***fix size
read-only;
};
NOTE: End value is size not address ( see art entry for reference ).
While I well understand what you propose to do I have to admit that I am not in position to generate the new code using buildroot.
I will have to wait until someone else generate a new snapshot or stable release which incorporates this new feature.
I finally decided to m
Continuing the discussion from CF-E110NV2 flashing issue:
I finally decided to make my own FW version using the snapshot Baseline. I have Added to the base line make configuration Luci (because I am not so comfortable with command line) and relayd for my network configuration.
From the EOM boot sequence I retreived the partition info so that to modify the CF-E110V2.dts file in this way:
partition@0 {
label = "u-boot";
reg = <0x000000 0x010000>;
read-only;
};
art: partition@10000 {
label = "art";
reg = <0x010000 0x010000>;
read-only;
};
partition@20000 {
compatible = "denx,uimage";
label = "firmware";
reg = <0x020000 0x7d0000>;
};
partition@7f0000 {
label = "nvram";
reg = <0x7f0000 0x010000>;
read-only;
};
The compilation went quite well and the FW works.
However the switch (AR8229) from the QR9533 which is well detected during the boot is not visible in the /etc/config/network file neither in the LuCI interface (no switch item)
I have tried to modify the etc/config/network file by adding the Following section
config switch
option name 'switch0'
option reset '1'
but while the LuCI interface is now including a switch item, errors are reported:
TypeError portstate is null
Switch switch0 has unknown topology - VLAN setings might not be accurate
Does anyone know how to declare the switch?
Does anyone know how the switch port are declared and which one is corresponding to LAN and WAN (AR8229 is given to be a 7 ports device)
THX to help
02_network and/or dts
Can you please detail your answer. I donnot catch very well what you suggest
Can you please detail which changes to introduce in dts/02_network or using uci command lines
so that the device behaves as a two ethernet lan switch (I use the device in wireless client config wwan and dont need of a ethernet wan port which I want to convert into an additional lan access)
At the end I would have 2 ethernet lan port and one wan wireless (client ) access
THX
go in interface, lan, physical setting and bridge all ethernet ports (eth1,eth0) something like that, make sure you do not bridge the wwan interface. now you can delete or leave the wan interface.
THX works fine
Thanks. Exactly what i did and it works fine. Both eth ports are tied together on the same lan with dhcp. Acces to wan in wireless as expected.
Thx a lot
Br