Serial unbricking no eth port CF-we72v1

Installing and Using OpenWrt
1

I wrongly apply firmware V2 to CF-we72v1. So my eth01 is broken. Try to put openwrt through serial. See only text about FTP, but no eth0 working. Any help?
eth0 link down
FAIL
dup 1 speed 1000
Using eth1 device
ping failed;
Hit any key to stop autoboot: 0

Booting image at 9f020000 ...

Image Name: MIPS LEDE Linux-4.4.198
Created: 2021-03-02 0:47:59 UTC
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 1753284 Bytes = 1.7 MB
Load Address: 81001000
Entry Point: 81001000
Verifying Checksum at 0x9f020040 ...OK
Uncompressing Kernel Image ... OK
No initrd

Transferring control to Linux (at address 81001000) ...

Giving linux memsize in bytes, 134217728

Starting kernel ...
ath> help
? - alias for 'help'
boot - boot default, i.e., run 'bootcmd'
bootd - boot default, i.e., run 'bootcmd'
bootm - boot application image from memory
cp - memory copy
erase - erase FLASH memory
help - print online help
start www server for firmware recovery
md - memory display
mm - memory modify (auto-incrementing)
mtest - simple RAM test
mw - memory write (fill)
nm - memory modify (constant address)
ping - send ICMP ECHO_REQUEST to network host
printenv- print environment variables
reset - Perform RESET of the CPU
run - run commands in an environment variable
setenv - set environment variables
save new MAC address in FLASH
restore devicen
tftpboot- boot image via network using TFTP protocol
version - print monitor version

2

in u-boot, openwrt, or physically ?

does it boot openwrt at all (it shouldn't) ?

what's this, the stock fw ?

you've seen https://openwrt.org/toh/comfast/cf-ew72#debricking ?

3

in u-boot, openwrt, or physically ? got the wrong stockfirmware, so not physically but bij de wrong firmwate (gigabit versus 100mbit)

no it does noot boot; it is the wrong firmware Image Name: MIPS LEDE Linux-4.4.198

you've seen https://openwrt.org/toh/comfast/cf-ew72#debricking ? yes this is all

Serial

→ port.serial general information about the serial port, serial port cable, etc.

How to connect to the Serial Port of this specific device:
Insert photo of PCB with markings for serial port

FIXME Replace EXAMPLE by real values.

Serial connection parameters
for COMFAST CF-EW72 EXAMPLE 115200, 8N1

4

not even close, try again.

5

Well I all read the serial https://openwrt.org/docs/techref/hardware/port.serial, as you can see I got a working serial connection, my question is no eth0 of eth1, how to get working firmware on my device? And of course how to start it.

6

that's not the link you've been given.

since uboot is till working, the firmware you flashed probably didn't include uboot.
I see no reason why both ports wouldn't work in uboot.
what makes you think eth0 is broken ?

7

Yesterday I all read the openwrt docs about the ew72v1, including https://openwrt.org/toh/comfast/cf-ew72#debricking
In the past I tryed to reset the stockfirmware ew72v1 with the help of Comfast. But there was no way to get a connection through the one of the two ethernet ports. Comfast gave up and concluded that the ew72 was bricked for ever.
So I went to the serial consol with the help of your documentation. The first thing I read is: eth0 link down FAIL dup 1 speed 1000 Using eth1 device ping failed; Hit any key to stop autoboot: 0

The speed of the eth is only 100 mbit.

When I read Debricking

In the event of a failed install, hold the “reset” button during power on for several seconds. This enables a firmware upload page to be presented at 192.168.1.1 which will allow install of a downloaded image. eg: https://downloads.openwrt.org/snapshots/targets/ath79/generic/openwrt-ath79-generic-comfast_cf-ew72-squashfs-sysupgrade.bin

So getting firmware through TFTP is no way I think., or am I wrong?

8

this usually means there's no connection on the port, doesn't mean it's dead.

what was this ping for ?

did you do anything else, but reading ?

depends on which port uboot is using for the recovery, and if the port's truly dead.

9

this usually means there's no connection on the port, doesn't mean it's dead. -> but not functioning

what was this ping for ? -> not mine, a boot ping

did you do anything else but reading it ? Yes applying it without it I could not have a serial connection

depends on which port uboot is using for the recovery, and if the port's truly dead. -> well can you help me, because reading all the documentation got me at the serial in log and monitor but now I am stuck I think

10

If it pings some random IP, why would you think it would succeed ?

it's hard, because you provide zero useful info.

do ^^^ in uboot 1st, post the complete serial log of it.

11

eth0 link down
FAIL
dup 1 speed 1000
Using eth1 device
ping failed;
Hit any key to stop autoboot: 0
ath> boot

Booting image at 9f020000 ...

Image Name: MIPS LEDE Linux-4.4.198
Created: 2021-03-02 0:47:59 UTC
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 1753284 Bytes = 1.7 MB
Load Address: 81001000
Entry Point: 81001000
Verifying Checksum at 0x9f020040 ...OK
Uncompressing Kernel Image ... OK
No initrd

Transferring control to Linux (at address 81001000) ...

Giving linux memsize in bytes, 134217728

Starting kernel ...

12

that's not the output of the uboot start command ...

13

This is what I get as help, where is uboot|?
help
? - alias for 'help'
boot - boot default, i.e., run 'bootcmd'
bootd - boot default, i.e., run 'bootcmd'
bootm - boot application image from memory
cp - memory copy
erase - erase FLASH memory
help - print online help
start www server for firmware recovery
md - memory display
mm - memory modify (auto-incrementing)
mtest - simple RAM test
mw - memory write (fill)
nm - memory modify (constant address)
ping - send ICMP ECHO_REQUEST to network host
printenv- print environment variables
reset - Perform RESET of the CPU
run - run commands in an environment variable
setenv - set environment variables
save new MAC address in FLASH
restore devicen
tftpboot- boot image via network using TFTP protocol
version - print monitor version

14

this is uboot.

15


frollic

tonbor

3m

this is uboot. -> ?

by the way tftpboot
eth0 link down
FAIL
Using eth1 device
TFTP from server 192.168.1.10; our IP address is 192.168.1.1

Load address: 0x80800000
Loading: T T ath> ath> tftpboot

16

by the way, this is not what you were told to do ...

I give up, enjoy your brick.

17

I am not an engineer just an user that manage to get in an serial monitor of an bricked router and got stuck, Have patience with the not knowing please

ath> uboot
Unknown command 'uboot' - try 'help' so??????

18

This is not openwrt this is stock firmware, so uboot maybe is different, and you are expecting an openwrt uboot could that be the case?

I am not an engineer just an user that manage to get in an serial monitor of an bricked router and got stuck, Have patience with the not knowing please

Depends on how u-boot was configured by OEM. Also, keep in mind that there is no such thing as single coherent u-boot - it has at least 40 semi-official forks and god knows how many unofficial ones. It is possible to configure u-boot such that you cannot really interrupt boot process, but it is not very common.

19

U-Boot 1.1.4-ga1cd7d4b-dirty (May 31 2018 - 16:44:04)

ap143 - Honey Bee 2.0

DRAM: 128 MB
Flash: 16 MB

eth0 link down
FAIL
dup 1 speed 1000
Using eth1 device
ping failed;
Hit any key to stop autoboot: 0

Booting image at 9f020000 ...

Image Name: MIPS LEDE Linux-4.4.198
Created: 2021-03-02 0:47:59 UTC
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 1753284 Bytes = 1.7 MB
Load Address: 81001000
Entry Point: 81001000
Verifying Checksum at 0x9f020040 ...OK
Uncompressing Kernel Image ... OK
No initrd

Transferring control to Linux (at address 81001000) ...

Giving linux memsize in bytes, 134217728

Starting kernel ...
here you are

20

This is not the first time for you see Joowin CF-EW72, a Comfast clone

But there is no solution I can find.

Pitty Rob