Did you try switching RX & TX? That's an easy mistake (since RX on one end means TX on the other...).
sorry, now it's ok.
I had connected Tx with Tx and Rx witn Rx.
I forgot to reverse
thank you for everything
Sorry ,
The router and the SSH client are talking to each other correctly, but I can't run the command (tftpboot) where it asks me for my username and password.
Also typing the password configured from the router login page (192.168.1.1) I cannot log in with the SHH client. I reset device to factory setting
Are you sure you interrupted the boot sequence? That login prompt suggests you did not. The login prompt shouldn't be displayed for the boot environment.
You should watch the output closely, at one point during the boot process you should see a message about interrupting the bootloader, sometimes it's with a specific key but often any key will do.
1 Like
thanks, as always you are right.
I made a good step forward; I renamed the firmware openwrt snapshit and it seems to have uploaded it to me.
Now I don't know what to do though, in the sense that I didn't understand if I have to delete something and if so, what
continue reading the github instruction ?
You boot from the memory address you copied the image to, using bootm. @frollic is right though - the commands are clearly listed in the commit/installation procedure we linked you to. They're there for a reason.
P.S. Paste the text instead of taking screenshots please, screenshots aren't searchable and they contribute little compared to plain text.
1 Like
Ok, I ran these commands and everything seems to be fine
TFTP from server 192.168.1.100; our IP address is 192.168.1.1
Filename '0101A8C0.img'.
Load address: 0x81000000
done
Bytes transferred = 6029628 (5c013c hex)
ath> erase 0x9f020000 +5c013c
Erasing flash...
First 0x2 last 0x5e sector size 0x10000 94
Erased 93 sectors
ath> cp.b 0x81000000 0x9f020000 5c013c
Copy to Flash... write addr: 9f020000
done
ath> reset
U-Boot 1.1.4 (Feb 23 2017 - 10:01:09)
ap147 - Honey Bee 2.0DRAM:
sri
Honey Bee 2.0
ath_ddr_initial_config(195): (16bit) ddr2 init
tap = 0x00000003
Tap (low, high) = (0x8, 0x25)
Tap values = (0x16, 0x16, 0x16, 0x16)
64 MB
Top of RAM usable for U-Boot at: 8400
....
...
etc
however, it stopped there
[ 24.797703] ieee80211 phy1: Atheros AR9531 Rev:2 mem=0xb8100000, irq=13
[ 24.840668] kmodloader: done loading kernel modules from /etc/modules.d/*
[ 42.469165] eth0: link up (1000Mbps/Full duplex)
[ 42.489227] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 42.498713] br-lan: port 1(eth0.1) entered blocking state
[ 42.504394] br-lan: port 1(eth0.1) entered disabled state
[ 42.510334] device eth0.1 entered promiscuous mode
[ 42.515342] device eth0 entered promiscuous mode
[ 42.551551] br-lan: port 1(eth0.1) entered blocking state
[ 42.557204] br-lan: port 1(eth0.1) entered forwarding state
[ 43.542650] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
I re-performed the reset
and then it appears
BusyBox v1.35.0 (2022-03-15 07:33:45 UTC) built-in shell (ash)
_______ ________ __
| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -__| || | | || _|| _|
|_______|| __|_____|__|__||________||__| |____|
|__| W I R E L E S S F R E E D O M
-----------------------------------------------------
OpenWrt SNAPSHOT, r19118-23f94aa330
-----------------------------------------------------
=== WARNING! =====================================
There is no root password defined on this device!
Use the "passwd" command to set up a new password
in order to prevent unauthorized SSH logins.
--------------------------------------------------
root@OpenWrt:/# passwd
Changing password for root
New password:
Bad password: too weak
Retype password:
I set the password, performed the reset again and then ran the reboot command to restart and now I'm in this situation
BusyBox v1.35.0 (2022-03-15 07:33:45 UTC) built-in shell (ash)
_______ ________ __
| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -__| || | | || _|| _|
|_______|| __|_____|__|__||________||__| |____|
|__| W I R E L E S S F R E E D O M
-----------------------------------------------------
OpenWrt SNAPSHOT, r19118-23f94aa330
-----------------------------------------------------
root@OpenWrt:/# ls
bin etc mnt proc root sys usr www
dev lib overlay rom sbin tmp var
root@OpenWrt:/#
these lights turned on
Well that's according to plan, no? Now copy over the sysupgrade image for your device to /tmp on the router (the only folder with enough space!), then run sysupgrade on it. Like this, from your computer:
$ scp /path/to/openwrt_sysupgrade_image root@$router_ip:/tmp/
On OpenWrt, through the serial connection:
# sysupgrade /tmp/openwrt_sysupgrade_image
might be a good idea to use stable 21.02, instead of snapshots.
the latter doesn't come with a with a webui, it can however be installed afterwards.
link's is in your 3rd post
only wired ethernet works out of the box, you manually have to enable wifi.
IPs 192.168.1.1
@Borromini seems the image is already flashed, no need for double flashing ?
Yes, you're right, I assumed he was still booting from RAM, but that isn't the case, he clobbered his code tags and that made his response close to illegible.
I downloaded to this link (https://openwrt.org/toh/hwdata/tp-link/tp-link_archer_d50_v1) the Firmware OpenWrt Upgrade URL and rename openwrt-sysupgrade.bin.
I uploaded , with winscp , in the folder temp of router and I have run the command:
root@OpenWrt:/# sysupgrade /tmp/openwrt-sysupgrade.bin
Tue Mar 15 08:05:54 UTC 2022 upgrade: Image metadata not present
Tue Mar 15 08:05:54 UTC 2022 upgrade: Use sysupgrade -F to override this check when downgrading or flashing to vendor firmware
Image check failed.
root@OpenWrt:/#
With option - F , it's started , but is stopped always here
[ 43.542650] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes read
and always the same 2 lights are on.
I'm stuck.
Do I have to start over?
what makes you think you're stuck ?
tried hitting enter ?
tried the IP using ssh in putty, with a client connected directly to the D50 ?
I think to be stuck , because i press ENTER , the result it's the same
BusyBox v1.35.0 (2022-03-15 07:33:45 UTC) built-in shell (ash)
_______ ________ __
| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -__| || | | || _|| _|
|_______|| __|_____|__|__||________||__| |____|
|__|
I tried to connect with putty (SSH) and ...
login as: root
root@192.168.1.1's password:
BusyBox v1.35.0 (2022-03-15 07:33:45 UTC) built-in shell (ash)
_______ ________ __
| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -__| || | | || _|| _|
|_______|| __|_____|__|__||________||__| |____|
|__| W I R E L E S S F R E E D O M
-----------------------------------------------------
OpenWrt SNAPSHOT, r19118-23f94aa330
-----------------------------------------------------
root@OpenWrt:~# ^C
root@OpenWrt:~#
I tried to connect with lan cable at 192.168.1.1 and this is the page that obtain
Like @frollic explained you should use a stable release image, the master (development- images do not have a web interface (LuCI).
So do I have to do it all over again?
nah, just DL the 21.02.2 sysupgrade image to /tmp, and run sysupgrade /tmp/filename.bin
but, I've already done that.
When I performed the procedure indicated by @Borromini, I loaded the sysupgrade 21.02.2, after the rename
guess you didn't complete it, since you still appear to run a snapshot.