CF-E110N: 8MB or 16MB flash?

https://openwrt.org/toh/hwdata/comfast/comfast_cf-e110n

@66enligne What makes you think that the CF-E110N has only 8MB flash?
The bootlog clearly shows 16MB flash. Can you please explain?

The chip on board is a cfeon en25q64hip which is a 64Mb therefore 8MB
In my bootlog it is stated found en25qh64, expected w25q128

I also checked the board and the chip reference soldered onto the board, see attached picture.

I also noticed that you refer to a qca9533 which i didnt found in qualcomm data base as also the chip on my board is a qca9531

Br

Thanks for this information!
Seems like we have a v1 vs. v2 issue here.

Do you have a v1 or a v2?
Is there anything printed on the board that allows identification of your device?
Something like this:
grafik
Can you please post your complete bootlog?

Yes I agree, most probably a V1 vs V2 issue.
My model is a V2 (sold as is)

see the PCB top side reference (R169QH_VER1.1)

Bottom side reference is (SR-02A / E258603)

see the bootlog sequence of the snapshot version. (which is operating well as it is but I didnt do any customization nor saving because of the nvram status)

[    0.314137] bootconsole [early0] disabled
[    0.314137] bootconsole [early0] disabled
[    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
[    0.443304] libphy: Fixed MDIO Bus: probed
[    0.789647] libphy: ag71xx_mdio: probed
[    0.795094] libphy: ar8xxx-mdio: probed
[    0.808270] switch0: Atheros AR8229 rev. 1 switch registered on mdio-bus.0
[    1.201543] ag71xx 19000000.eth: connected to PHY at mdio-bus.0:1f:04 [uid=00    4dd042, driver=Generic PHY]
[    1.212136] eth0: Atheros AG71xx at 0xb9000000, irq 4, mode: mii
[    1.551096] ag71xx 1a000000.eth: connected to PHY at fixed-0:00 [uid=00000000    , driver=Generic PHY]
[    1.561167] eth1: Atheros AG71xx at 0xba000000, irq 5, mode: gmii
[    1.571030] NET: Registered protocol family 10
[    1.582823] Segment Routing with IPv6
[    1.586719] NET: Registered protocol family 17
[    1.591460] bridge: filtering via arp/ip/ip6tables is no longer available by     default. Update your scripts to load br_netfilter if you need this.
[    1.604859] 8021q: 802.1Q VLAN Support v1.8
[    1.611162] hctosys: unable to open rtc device (rtc0)
[    1.621272] VFS: Mounted root (squashfs filesystem) readonly on device 31:4.
[    1.638479] Freeing unused kernel memory: 1204K
[    1.643190] This architecture does not have kernel memory protection.
[    2.219451] init: Console is alive
[    2.223252] init: - watchdog -
[    2.479272] random: fast init done
[    3.070429] kmodloader: loading kernel modules from /etc/modules-boot.d/*
[    3.186954] kmodloader: done loading kernel modules from /etc/modules-boot.d/    *
[    3.205073] init: - preinit -
[    4.158598] random: jshn: uninitialized urandom read (4 bytes read)
[    4.318717] random: jshn: uninitialized urandom read (4 bytes read)
[    4.445392] random: jshn: uninitialized urandom read (4 bytes read)
[    4.946729] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Press the [f] key and hit [enter] to enter failsafe mode
Press the [1], [2], [3] or [4] key and hit [enter] to select the debug level
[    7.063180] eth0: link up (100Mbps/Full duplex)
[    7.067918] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[    8.187843] mount_root: jffs2 not ready yet, using temporary tmpfs overlay
[    8.224641] urandom-seed: Seed file not found (/etc/urandom.seed)
[    8.399005] eth0: link down
[    8.416474] procd: - early -
[    8.419708] procd: - watchdog -
[    9.070383] procd: - watchdog -
[    9.074003] procd: - ubus -
[    9.105001] urandom_read: 5 callbacks suppressed
[    9.105011] random: ubusd: uninitialized urandom read (4 bytes read)
[    9.127154] random: ubusd: uninitialized urandom read (4 bytes read)
[    9.135534] procd: - init -
Please press Enter to activate this console.
[    9.533912] kmodloader: loading kernel modules from /etc/modules.d/*
[    9.548967] ip6_tables: (C) 2000-2006 Netfilter Core Team
[    9.565715] Loading modules backported from Linux version v4.19.32-0-g3a2156c    839c7
[    9.573628] Backport generated by backports.git v4.19.32-1-0-g1c4f7569
[    9.584277] ip_tables: (C) 2000-2006 Netfilter Core Team
[    9.601153] nf_conntrack version 0.5.0 (1024 buckets, 4096 max)
[    9.686762] xt_time: kernel timezone is -0000
[    9.767877] PPP generic driver version 2.4.2
[    9.775452] NET: Registered protocol family 24
[    9.852622] ieee80211 phy0: Atheros AR9531 Rev:2 mem=0xb8100000, irq=12
[    9.899788] kmodloader: done loading kernel modules from /etc/modules.d/*
[   69.670959] jffs2_scan_eraseblock(): End of filesystem marker found at 0x0
[   69.678094] jffs2_build_filesystem(): unlocking the mtd device...
[   69.678099] done.
[   69.686551] jffs2_build_filesystem(): erasing all blocks after the end marker    ...
[   73.180796] br-lan: port 1(eth0) entered blocking state
[   73.194000] br-lan: port 1(eth0) entered disabled state
[   73.199802] device eth0 entered promiscuous mode
[   73.274313] IPv6: ADDRCONF(NETDEV_UP): br-lan: link is not ready
[   73.367036] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[   74.420517] eth1: link up (1000Mbps/Full duplex)
[   74.425346] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[   75.222528] eth0: link up (100Mbps/Full duplex)
[   75.227281] br-lan: port 1(eth0) entered blocking state
[   75.232742] br-lan: port 1(eth0) entered forwarding state
[   75.309772] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
[   86.545669] done.
[   86.547721] jffs2: notice: (1062) jffs2_build_xattr_subsystem: complete build    ing xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead,     0 orphan) found.
[   86.724509] overlayfs: upper fs does not support tmpfile.
[  129.449267] random: crng init done

Since we now have one bootlog showing 16MB (see devicepage) and one showing 8MB (see above), I updated the dataentry accordingly.

The question remains how to discern between both versions.

I understand that during the boot process the FW reads the flash type (from boot console messaging) would it be possible that depending on the flash type 8 or 16 the partition memory mapping is adapted accordingly?

As additionnal info here is the memory mapping of the OEM firmware V2.6

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"

For comparison, the OEM bootlog from the devicepage:

[    0.700000] m25p80 spi0.0: found w25q128, expected m25p80
[    0.710000] m25p80 spi0.0: w25q128 (16384 Kbytes)
[    0.710000] 7 cmdlinepart partitions found on MTD device spi0.0
[    0.720000] Creating 7 MTD partitions on "spi0.0":
[    0.720000] 0x000000000000-0x000000010000 : "u-boot"
[    0.730000] 0x000000010000-0x000000020000 : "art"
[    0.740000] 0x000000020000-0x0000001a0000 : "kernel"
[    0.740000] 0x0000001a0000-0x000000fe0000 : "rootfs"
[    0.750000] mtd: device 3 (rootfs) set to be root filesystem
[    0.760000] 1 squashfs-split partitions found on MTD device rootfs
[    0.760000] 0x0000006e0000-0x000000fe0000 : "rootfs_data"
[    0.770000] 0x000000fe0000-0x000000ff0000 : "configs"
[    0.780000] 0x000000ff0000-0x000001000000 : "nvram"
[    0.780000] 0x000000020000-0x000000fe0000 : "firmware"

In theory, yes (ar71xx) - in practice, in a DTS based target (ath79), no. The concept of device tree is not to rely on heuristics or device specific detection methods, but to hardcode the information via DTS, you'll need to DTS variants here.

In case a new DTS MUST be generated. The existing one is already named V2 and not V1 as it should. Can you rename current V1 in V2, with many references to CF-E110 V2 to modify?? In the new V2 as well the memory type (8MB) and the SoC type QCA9531 (vs QCA9533 for V1) shall be modified

You can include the the common parts (*.dts --> *.dtsi), for the rest you'll have to provide a patch/ pull request.

This can't be a v1 vs. v2 problem, hence renaming would be a bad idea:

  • the bootlog on the devicepage indicates it is from a v2 (which has 16MB flash)
    [ 0.000000] Kernel command line: board=COMFAST-CF-E110NV2 console=ttyS0,115200 ...
    [ 0.700000] m25p80 spi0.0: found w25q128, expected m25p80
    [ 0.710000] m25p80 spi0.0: w25q128 (16384 Kbytes)
    
  • you are saying further above that you have a v2 too, but with 8MB flash and different flash layout
    [    0.333588] m25p80 spi0.0: found en25qh64, expected w25q128
    [    0.339454] m25p80 spi0.0: en25qh64 (8192 Kbytes)
    

What does the Kernel command line: board=... say in your bootlog?

Important as well is if there is a way to determine 8/16 from the OEM firmware.

Here i have a problem because i install the serial console since i've experienced an issue after switching from original eom v2.7 (which i didnt backup) to cf-e320-sysupgrade which was given to operate and failed on my device.
Now any message sent to the console before the line "bootconsole [early0] disable" is corrupted, meaning not possible to read anything.
I donnot understand why because a sysupgrade version should not modify the boot?
At the end either using the cf-e110 snapshot or the v2.6eom the device complete the boot and v2.6 works well in any conf as well as snapshot ethernet lan and wan operate properly (didnt went forward due to the reported nvram partition problem)
No more ideas
Both box and product stickers are CF-E110N V2

Hi Gentlemen
Did you stop to investigate? I hope not.

I realize that I only rely on the RS232 console output without considering the internal log (sorry, I'm not an expert in FW debug). Then i have retrieved the internal log which is not corrupted (donnot understand).
Find hereafter the snapshot log start which gives the machine name CF-E110NV2 and also differentiate the SoC QCA9533 from the wlanphy 9531 (marking on my board chip is QCA9531)

root@OpenWrt:/# dmesg
[    0.000000] Linux version 4.14.121 (buildbot@602ce18687ab) (gcc version 7.4.0 (OpenWrt GCC 7.4.0 r10085-8128a7e4fc)) #0 Tue May 28 11:18:58 2019
[    0.000000] bootconsole [early0] enabled
[    0.000000] CPU0 revision is: 00019374 (MIPS 24Kc)
[    0.000000] MIPS: machine is COMFAST CF-E110N v2
[    0.000000] SoC: Qualcomm Atheros QCA9533 ver 2 rev 0
[    0.000000] Determined physical RAM map:
[    0.000000]  memory: 04000000 @ 00000000 (usable)
[    0.000000] Initrd not found or empty - disabling initrd
[    0.000000] Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes.
[    0.000000] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
[    0.000000] Zone ranges:
[    0.000000]   Normal   [mem 0x0000000000000000-0x0000000003ffffff]
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000000000000-0x0000000003ffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x0000000003ffffff]
[    0.000000] On node 0 totalpages: 16384
[    0.000000] free_area_init_node: node 0, pgdat 8055fec0, node_mem_map 81007e60
[    0.000000]   Normal zone: 128 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 16384 pages, LIFO batch:3
[    0.000000] random: get_random_bytes called from start_kernel+0x90/0x480 with crng_init=0
[    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[    0.000000] pcpu-alloc: [0] 0 
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 16256
[    0.000000] Kernel command line: console=ttyS0,115200n8 rootfstype=squashfs,jffs2
[    0.000000] PID hash table entries: 256 (order: -2, 1024 bytes)
[    0.000000] Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
[    0.000000] Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Writing ErrCtl register=00000000
[    0.000000] Readback ErrCtl register=00000000
[    0.000000] Memory: 57952K/65536K available (4007K kernel code, 161K rwdata, 956K rodata, 1204K init, 211K bss, 7584K reserved, 0K cma-reserved)
[    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] NR_IRQS: 51
[    0.000000] CPU clock: 650.000 MHz
[    0.000000] clocksource: MIPS: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 5880801374 ns
[    0.000010] sched_clock: 32 bits at 325MHz, resolution 3ns, wraps every 6607641598ns
[    0.008276] Calibrating delay loop... 432.53 BogoMIPS (lpj=2162688)
[    0.074874] pid_max: default: 32768 minimum: 301
[    0.079961] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.086938] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.099054] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.109502] futex hash table entries: 256 (order: -1, 3072 bytes)
[    0.116039] pinctrl core: initialized pinctrl subsystem
[    0.124510] NET: Registered protocol family 16
[    0.159255] clocksource: Switched to clocksource MIPS
[    0.165879] NET: Registered protocol family 2
[    0.171569] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[    0.178937] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[    0.185718] TCP: Hash tables configured (established 1024 bind 1024)
[    0.192628] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.198811] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.205785] NET: Registered protocol family 1
[    0.210458] PCI: CLS 0 bytes, default 32
[    0.215166] Crashlog allocated RAM at address 0x3f00000
[    0.222366] workingset: timestamp_bits=30 max_order=14 bucket_order=0
[    0.235072] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.241281] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[    0.263206] io scheduler noop registered
[    0.267350] io scheduler deadline registered (default)
[    0.275339] pinctrl-single 1804002c.pinmux: 576 pins at pa b804002c size 72
[    0.283916] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled
[    0.293605] console [ttyS0] disabled
[    0.297430] 18020000.uart: ttyS0 at MMIO 0x18020000 (irq = 9, base_baud = 1562500) is a 16550A
[    0.306595] console [ttyS0] enabled
[    0.314154] bootconsole [early0] disabled
[    0.333550] m25p80 spi0.0: found en25qh64, expected w25q128
[    0.339418] m25p80 spi0.0: en25qh64 (8192 Kbytes)
[    0.344327] 4 fixed-partitions partitions found on MTD device spi0.0
[    0.350898] Creating 4 MTD partitions on "spi0.0":
[    0.355858] 0x000000000000-0x000000010000 : "u-boot"
[    0.361996] 0x000000010000-0x000000020000 : "art"
[    0.367734] 0x000000020000-0x000000ff0000 : "firmware"
[    0.373114] mtd: partition "firmware" extends beyond the end of device "spi0.0" -- size truncated to 0x7e0000
[    0.387518] 2 uimage-fw partitions found on MTD device firmware
[    0.393712] Creating 2 MTD partitions on "firmware":
[    0.398852] 0x000000000000-0x0000001a0000 : "kernel"
[    0.404906] 0x0000001a0000-0x0000007e0000 : "rootfs"
[    0.410940] mtd: device 4 (rootfs) set to be root filesystem
[    0.416835] 1 squashfs-split partitions found on MTD device rootfs
[    0.423306] 0x000000390000-0x0000007e0000 : "rootfs_data"
[    0.429860] 0x000000ff0000-0x000001000000 : "nvram"
[    0.434912] mtd: partition "nvram" is out of reach -- disabled
[    0.443284] libphy: Fixed MDIO Bus: probed
[    0.789699] libphy: ag71xx_mdio: probed
[    0.795137] libphy: ar8xxx-mdio: probed
[    0.808344] switch0: Atheros AR8229 rev. 1 switch registered on mdio-bus.0
[    1.201593] ag71xx 19000000.eth: connected to PHY at mdio-bus.0:1f:04 [uid=004dd042, driver=Generic PHY]
[    1.212190] eth0: Atheros AG71xx at 0xb9000000, irq 4, mode: mii
[    1.551148] ag71xx 1a000000.eth: connected to PHY at fixed-0:00 [uid=00000000, driver=Generic PHY]
[    1.561219] eth1: Atheros AG71xx at 0xba000000, irq 5, mode: gmii
[    1.571109] NET: Registered protocol family 10
[    1.582887] Segment Routing with IPv6
[    1.586783] NET: Registered protocol family 17
[    1.591523] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[    1.604920] 8021q: 802.1Q VLAN Support v1.8
[    1.611277] hctosys: unable to open rtc device (rtc0)
[    1.621390] VFS: Mounted root (squashfs filesystem) readonly on device 31:4.
[    1.638579] Freeing unused kernel memory: 1204K
[    1.643295] This architecture does not have kernel memory protection.
[    2.219516] init: Console is alive
[    2.223327] init: - watchdog -
[    2.479321] random: fast init done
[    3.070234] kmodloader: loading kernel modules from /etc/modules-boot.d/*
[    3.186764] kmodloader: done loading kernel modules from /etc/modules-boot.d/*
[    3.204890] init: - preinit -
[    4.157880] random: jshn: uninitialized urandom read (4 bytes read)
[    4.318400] random: jshn: uninitialized urandom read (4 bytes read)
[    4.443370] random: jshn: uninitialized urandom read (4 bytes read)
[    4.945143] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[    7.062616] eth0: link up (100Mbps/Full duplex)
[    7.067369] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[    8.233386] jffs2: notice: (452) jffs2_build_xattr_subsystem: complete building xattr subsystem, 17 of xdatum (0 unchecked, 17 orphan) and 49 of xref (9 dead, 40 orphan) found.
[    8.251376] mount_root: overlay filesystem has not been fully initialized yet
[    8.260035] mount_root: switching to jffs2 overlay
[    8.292378] overlayfs: upper fs does not support tmpfile.
[    8.301801] urandom-seed: Seed file not found (/etc/urandom.seed)
[    8.476368] eth0: link down
[    8.493885] procd: - early -
[    8.496989] procd: - watchdog -
[    9.150519] procd: - watchdog -
[    9.154130] procd: - ubus -
[    9.185135] urandom_read: 5 callbacks suppressed
[    9.185145] random: ubusd: uninitialized urandom read (4 bytes read)
[    9.207270] random: ubusd: uninitialized urandom read (4 bytes read)
[    9.215581] procd: - init -
[    9.612515] kmodloader: loading kernel modules from /etc/modules.d/*
[    9.627596] ip6_tables: (C) 2000-2006 Netfilter Core Team
[    9.646607] Loading modules backported from Linux version v4.19.32-0-g3a2156c839c7
[    9.654517] Backport generated by backports.git v4.19.32-1-0-g1c4f7569
[    9.665217] ip_tables: (C) 2000-2006 Netfilter Core Team
[    9.681986] nf_conntrack version 0.5.0 (1024 buckets, 4096 max)
[    9.765288] xt_time: kernel timezone is -0000
[    9.846153] PPP generic driver version 2.4.2
[    9.853700] NET: Registered protocol family 24
[    9.912941] ath: EEPROM regdomain: 0x0
[    9.912954] ath: EEPROM indicates default country code should be used
[    9.912957] ath: doing EEPROM country->regdmn map search
[    9.912975] ath: country maps to regdmn code: 0x3a
[    9.912982] ath: Country alpha2 being used: US
[    9.912985] ath: Regpair used: 0x3a
[    9.927934] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[    9.930252] ieee80211 phy0: Atheros AR9531 Rev:2 mem=0xb8100000, irq=12
[    9.982919] kmodloader: done loading kernel modules from /etc/modules.d/*
[   45.113460] br-lan: port 1(eth0) entered blocking state
[   45.118874] br-lan: port 1(eth0) entered disabled state
[   45.124739] device eth0 entered promiscuous mode
[   45.151157] IPv6: ADDRCONF(NETDEV_UP): br-lan: link is not ready
[   45.203693] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[   46.260626] eth1: link up (1000Mbps/Full duplex)
[   46.265456] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[   47.222599] eth0: link up (100Mbps/Full duplex)
[   47.227365] br-lan: port 1(eth0) entered blocking state
[   47.232825] br-lan: port 1(eth0) entered forwarding state
[   47.349390] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready

I suspect the topic will close with no answer because of no change since more than a week.
Meaning that I will not be in position to be using openwrt on this machine like on other ones I have in my network.
As a consequence we shall warn users having 8MB CF-E110N V2 devices that Openwrt is not appropriate for them
Very desapointed

If there's a way that an end-user, preferably without cracking the case, can determine if they have a unit populated with 8 MB or 16 MB, then it is straightforward to prepare two variants. Without that, it is "unsafe" to instruct a user to flash OpenWrt on the device.

Since you've got the device in hand, you're uniquely positioned to be able to provide that critical piece of information.

OK, makes sense.
While the EOM FW kernel log is not accesible can I use the initramfs FW version as a probe?
From what I understand this FW donnot load in flash therefore donnot compromise the EOM FW in place.
But this FW as the snapshot does should verify the HW config when the kernel starts and reports info in the kernel log.
Therefore I would get the flash size info without craking the case nor removing the EOM FW.
Is this approach right?? THX to confirm

Oups! Sorry gentlemen i did a mistake. I have reload the OEM and checked the system log from the EOM web interface. And very clearly the flash size is reported. see the sceenshot => therefore easy to manage
image

1 Like