Posted: Fri Feb 19, 2021 16:55 Post subject: Serial Connection to Archer C7 v2
Hi,
After a load of trouble with a boot loop, I've bought a USB-serial adaptor as advised on here, and soldered suitable pins on to the C7 PCB.
I'm trying to connect via Putty, but I'm just getting a blank screen.
Com port is set correctly, baud rate is 115200 as a guide on here suggested, but nothing is happening (other than four of the router lights are now on solidly, rather than flashing and cycling like when it was stuck in the boot loop)
I tried swapping the TX and RX in case I got them in the wrong order, but that just leaves a load of garbled text in Putty...
normally when you get garbled text you have the RX & TX the wrong way around _________________ Netgear R7800 PPPoE Main Router
Network IPV4 - Isolated Vlan's with IoT Devices. Unifi AC-Pro x 3 AP's, Router Wi-Fi Disabled. OVPN Server With Paid Commercial Wireguard Client's. Gateway Mode, DNSMasq, Static Leases & DHCP, Pi-Hole DNS & Running Unbound.
No one can build you the bridge on which you, and only you, must cross the river of life!
I either have garbled text with the TX/RX one way round, or nothing at all with them the other way (which I think is the correct way)
I'm not a regular user of this sort of thing, so I'm pretty clueless to be honest!
I've seen a few guides which say I need to hit Control-C a few times as I power up the router, another one says I need to type tpl, but neither seem to do anything, I just get the same blank screen!
Joined: 16 Nov 2015 Posts: 6447 Location: UK, London, just across the river..
Posted: Fri Feb 19, 2021 19:19 Post subject:
on my 1043v2 witch has the same SoC and i guess MB is the same, as well the serial...i don't need the 3.3v wire connected, only GRD and Tx, Rx...but it depends..from your USB to TTL too...try with or without...i had this output too and this sorted it... _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55630 WAP
TP-Link WR1043NDv2 -DD-WRT 55723 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55779 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55819 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55779 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
I've now plugged in the 3.3v on the adaptor to the VCC on the PCB and am getting "something"...
From the way it's outputting and the lights are flashing, it looks like it's back in it's bootloop... presumably there will be a way to break it if I could read the garbled text.
Joined: 16 Nov 2015 Posts: 6447 Location: UK, London, just across the river..
Posted: Fri Feb 19, 2021 21:30 Post subject:
first resize that pic...or it will be deleted
on start quickly type tpl + enter...
if you have serial connected correctly, this is not a normal output, check your connections or god knows what...make sure all settings are correct... _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55630 WAP
TP-Link WR1043NDv2 -DD-WRT 55723 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55779 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55819 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55779 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
Joined: 08 May 2018 Posts: 14246 Location: Texas, USA
Posted: Fri Feb 19, 2021 22:20 Post subject:
I fixed your images. There is a setting in PuTTY v0.73 and up that is required so the output isn't garbled as long as the TX, RX, and GND are correct and good connections. The only other thing if your config in PuTTY is correct is a bad ground or bad connections.
