Hello. I'm getting stuck with a LAN comms problem trying to flash the firmware.
I can successfully control the U-boot interface using the serial line to setenv the suitable IP in order to talk to my PC but then from it I can't ping the Archer unit. The PC LAN interface is connected to the Archer switch, in fact I tried from LAN1 through LAN4/WAN but weirdly none of them responds - I double checked my connections and network address/mask details. Is there any protection measure from TpLink that prevents U-Boot to work as expected? Thank you for any help.
Marco
Why would you expect icmp to work? Try arping, at least that bears some functionality in context.
Hello, thank you for the hint. Arping probes do not return any reply. The network set-up is ok because I can arping another node on the same LAN.
I even tried keeping the U-boot default env as follows:
AP135> printenv
bootargs=console=ttyS0,115200 root=31:02 rootfstype=squashfs init=/sbin/init mtdparts=ath-nor0:128k(u-boot),1280k(kernel),14656k(rootfs),64k(radioDECT),64k(config),64k(romfs),64k(rom),64k(radio)
bootcmd=bootm 0x80800000
bootdelay=1
baudrate=115200
ethaddr=0x00:0xaa:0xbb:0xcc:0xdd:0xee
ipaddr=192.168.1.1
serverip=192.168.1.100
dir=
lu=tftp 0x80060000 ${dir}u-boot.bin&&erase 0x9f000000 +$filesize&&cp.b $fileaddr 0x9f000000 $filesize
lf=tftp 0x80060000 ${dir}ap135${bc}-jffs2&&erase 0x9f050000 +0x630000&&cp.b $fileaddr 0x9f050000 $filesize
lk=tftp 0x80060000 ${dir}vmlinux${bc}.lzma.uImage&&erase 0x9f680000 +$filesize&&cp.b $fileaddr 0x9f680000 $filesize
stdin=serial
stdout=serial
stderr=serial
ethact=eth0
Environment size: 711/65532 bytes
-Marco
Neithrr of pings serves any purpose. What problem you are facing with the router?
everything you need to know is in https://openwrt.org/toh/tp-link/archer_d7, except for the TFTP server software you need to install/fire up.
there's a sh-t load of TFTP flashing openwrt videos on YT.
it's not the router's fault you don't know how it's done.
The router does not show any problem with the original Tplink firmware. I'm aware that the environment functionalities may be very limited and the only thing I'd like to d is pulling an image from the TFTP server that is sitting aside on the LAN. The ping/arping attempts are just to diagnose my problem.
unfortunately, you picked the wrong diag tool.
most transfer issues are caused by firewalls on the TFTP host.
1 Like
Yes, indeed, this set-up is way simple. Thank you for your tips
Disable firewall on tftp host and check tftp log.
If nothing appears in tftp log make sure you are connected to only connection to the router and run wireshark to see what travels in protocol.
Thank you for the help from everyone, I just was assuming too much.