Sorry about my question, but reading the post I could see some RE200 EU repeaters with US firmware.
This is possible?
Can someone provide a guide how to do this?
Thanks
On other TP-Link devices with this "0.0.0 version" issue, you would just flash the vendor fimware again to fix that version number. The TP-Link FW upgrader usually only allows you to flash a different version (sometimes even only a higher version). I.e. you can't flash OpenWrt (with version 0.0.0), because you already have version 0.0.0 installed.
Is tftp to ram working for you? Are you changing defaults? I recommand to check how mtd1 starts ..
I have RE200_v3 (with serial con) and soon I will also have a RE220_v2 (with serial console)
. One strange thing that I've found is, if I try to tftp into ram and I write anything at u-boot prompt (to overwrite defaults) on those 3 questions ,is going to write to SPI (basically overwrite first 64k of mtd1 where firmware starts ), which in turn messes up loading from flash at next reboot and is stuck exactly like reported on Loading kernel ..
(Also in my case the SPI zone is corrupted if openwrt is flashed..),however after uBOOT writes SPI is no longer saying the CRC error..
Software System Reset Occurred
******************************
flash manufacture id: ef, device id 40 17
find flash: W25Q64BV
***** Warning - bad CRC, using default environment**
In my uBoot I do not need to type anything,just press enter (even if file name says empty.. it will use test.bin)
Notice Erase/Write SPI below from u-BOOT
1: System Load Linux to SDRAM via TFTP.
Please Input new ones /or Ctrl-C to discard
Input device IP (192.168.0.254) ==:192.168.0.254
Input server IP (192.168.0.184) ==:192.168.0.184
Input Linux Kernel filename () ==:test.bin
NetTxPacket = 0x83FE7840
KSEG1ADDR(NetTxPacket) = 0xA3FE7840
NetLoop,call eth_halt !
NetLoop,call eth_init !
Trying Eth0 (10/100-M)
Waitting for RX_DMA_BUSY status Start... done
ETH_STATE_ACTIVE!!
TFTP from server 192.168.0.184; our IP address is 192.168.0.254
Filename 'test.bin'.
TIMEOUT_COUNT=10,Load address: 0x82000000
Loading: Got ARP REPLY, set server/gtwy eth addr (00:01:2e:bc:3a:3d)
Got it
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#####################################
done
Bytes transferred = 6509106 (635232 hex)
LoadAddr=82000000 NetBootFileXferSize= 00635232
**Erasing SPI Flash...**
**.**
**Writing to SPI Flash...**
done
Automatic boot of image at addr 0x82000000 ...
## Booting image at 82000000 ...
text base: 80000000
entry point: 80000000
Uncompressing Kernel Image ... OK
No initrd
## Transferring control to Linux (at address 80000000) ...
## Giving linux memsize in MB, 64
Starting kernel ...
[ 0.000000] Linux version 5.4.101 (builder@buildhost) (gcc version 8.4.0 (OpenWrt GCC 8.4.0 unknown)) #0 Mon Mar 1 11:53:05 2021
[ 0.000000] Board has DDR2
[ 0.000000] Analog PMU set to hw control
....
root@OpenWrt:/#
Here we should had how the squashfs-sysupgrade starts..
root@OpenWrt:/# dd if=/dev/mtd1 bs=$((64*1024+32)) count=1 2>/dev/null|hexdump -
C
00000000 a8 9e 51 e8 62 6f 6f 74 63 6d 64 3d 74 66 74 70 |..Q.bootcmd=tftp|
00000010 00 62 6f 6f 74 64 65 6c 61 79 3d 31 00 62 61 75 |.bootdelay=1.bau|
00000020 64 72 61 74 65 3d 35 37 36 30 30 00 65 74 68 61 |drate=57600.etha|
00000030 64 64 72 3d 22 30 30 3a 41 41 3a 42 42 3a 43 43 |ddr="00:AA:BB:CC|
00000040 3a 44 44 3a 31 30 22 00 73 74 64 69 6e 3d 73 65 |:DD:10".stdin=se|
00000050 72 69 61 6c 00 73 74 64 6f 75 74 3d 73 65 72 69 |rial.stdout=seri|
00000060 61 6c 00 73 74 64 65 72 72 3d 73 65 72 69 61 6c |al.stderr=serial|
00000070 00 42 6f 6f 74 54 79 70 65 3d 33 00 66 69 6c 65 |.BootType=3.file|
00000080 73 69 7a 65 3d 36 33 35 32 33 32 00 66 69 6c 65 |size=635232.file|
00000090 61 64 64 72 3d 38 32 30 30 30 30 30 30 00 69 70 |addr=82000000.ip|
000000a0 61 64 64 72 3d 31 39 32 2e 31 36 38 2e 30 2e 32 |addr=192.168.0.2|
000000b0 35 34 00 73 65 72 76 65 72 69 70 3d 31 39 32 2e |54.serverip=192.|
000000c0 31 36 38 2e 30 2e 31 38 34 00 61 75 74 6f 73 74 |168.0.184.autost|
000000d0 61 72 74 3d 6e 6f 00 62 6f 6f 74 66 69 6c 65 3d |art=no.bootfile=|
000000e0 74 65 73 74 2e 62 69 6e 00 00 00 00 00 00 00 00 |test.bin........|
000000f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
00001000 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................|
*
00010000 59 b5 84 02 f9 f5 b4 18 73 4f b6 cb 32 65 f2 3d |Y.......sO..2e.=|
00010010 ee f7 37 2e f9 d4 45 68 6f d2 d0 b2 59 de 41 3d |..7...Eho...Y.A=|
00010020
root@OpenWrt:/#
Now rebooting and is going to get stuck at Starting kernel..
root@OpenWrt:/# reboot
root@OpenWrt:/# [ 264.609597] br-lan: port 1(eth0) entered disabled state
[ 264.636782] device eth0 left promiscuous mode
[ 264.645579] br-lan: port 1(eth0) entered disabled state
[ 268.936778] reboot: Restarting system
cid reg:00010102, cid:1[04020C0D][04020C0D]
DDR Calibration DQS reg = 00008787
DDR Calibration MEMCTRL reg = 0E120003
U-Boot 1.1.3 (Mar 5 2019 - 12:24:20)
Board: Ralink APSoC DRAM: 64 MB
relocate_code Pointer at: 83fb8000
Use New Uboot
Use New Uboot patch lock_dcache addiu $12, 0x1000
******************************
Software System Reset Occurred
******************************
flash manufacture id: ef, device id 40 17
find flash: W25Q64BV
============================================
Ralink UBoot Version: 5.0.0.0
--------------------------------------------
ASIC 7628_MP (Port5<->None)
DRAM component: 512 Mbits DDR, width 16
DRAM bus: 16 bit
Total memory: 64 MBytes
Flash component: SPI Flash
Date:Mar 5 2019 Time:12:24:20
============================================
icache: sets:512, ways:4, linesz:32 ,total:65536
dcache: sets:256, ways:4, linesz:32 ,total:32768
##### The CPU freq = 580 MHZ ####
estimate memory size =64 Mbytes
RESET MT7628 PHY!!!!!!
Please choose the operation:
1: Load system code to SDRAM via TFTP.
2: Load system code then write to Flash via TFTP.
3: Boot system code via Flash (default).
4: Entr boot command line interface.
7: Load Boot Loader code then write to Flash via Serial.
9: Load Boot Loader code then write to Flash via TFTP.
default: 3
0
3: System Boot system code via Flash.
gpioMode1 Reg: 0x571504c4
gpioMode2 Reg: 0x5550555
tplink_turn_off_led
## Booting image at bc020000 ...
text base: 70795474
entry point: 00333d65
Uncompressing Kernel Image ... OK
No initrd
## Transferring control to Linux (at address 00333d65) ...
## Giving linux memsize in MB, 64
Starting kernel ...
So for those that have serial console ,and booting latest snapshot is stuck at "Starting kernel.." ,try to do that hexdump command from my previous reply to see if uBOOT corrupted the first 64k of mtd1
I have try the latest snapshot from yesterday (r16293-310b7f76e8) on my RE200 v1 using option 2 (without changing default option for the 3 questions) and everything seem to work now.
I have also try building my custom image and flashing it through luci (sysupgrade) and that works too.
Don't know if the latest snapshot correct something or just pressing enter for the 3 question change the behaviour ?
If i have time, i will try to flash it again with the same snapshot by modifying the answer to the 3 question.
I just saw that the 5GHZ interface was missing on my RE200 v1.
I have this error in log:
mt7620-pci 10140000.pcie: PCIE0 no card, disable it(RST&CLK)
mt7620-pci: probe of 10140000.pcie failed with error -1
Currently Installed:
Does someone already encounter this ?
In my re200-v3 I can still see wlan1 (kernel 5.4.105 )
root@OpenWrt:/# ip ad|grep UP
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1000
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN qlen 1000
5: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP qlen 1000
6: wlan1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN qlen 1000
I do not have any 5Ghz AP up to test it , however I did not seen any errors in dmesg.
(my device is RE200v3)
I've tested 5Ghz and at least in today snapshot ( 5.4.113 ) some basic wlan packages are missing so had to install them manually ( opkg install kmod-mt76x0-common). Even if radio0 (2.4Ghz) was detected I was not able to use it (as 'sta' = wifi client) without installing the other one that detects 5Ghz radio1.
Anyway the issue remains with 5Ghz low tx power (10 or 11 depending on channel) which could be related to mtd6 (radio partition) data .. or driver .
Also ,what is the general impression on stock TPLINK firmware for this device.. is 5Ghz having more txpower then openwrt ?
I have a RE200 v2 and with the stock firmware the 5Ghz radio is working just fine, normal power.
Yes,it seems with stock firmware 5Ghz is working better. However I am not very sure is tx power.. once the connection happens it seems to be stable
Anyone here with a RE200 V5 or RE220 V3 that can provide the hexdump for radio partition?
Hi All,
has anyone tested already 21.02.0-rc1 ? Is it stable?
I have a spare RE200 V2.1
- flashed it with openwrt-ramips-mt76x8-tplink_re200-v2-squashfs-factory.bin
- Installed luci. Seemed to work well
- Tried to upgrade using luci and openwrt-21.02.0-rc1-ramips-mt76x8-tplink_re200-v2-squashfs-factory.bin
Result: bricked RE200 (all leds flashing). Hope I can unbrick it using the ftdi adapter that I use to flash tasmota on IoT devices.
1 Like
@moodyblue Thank you for sharing. I hope you recover your device. Taking into consideration above I see I need to postpone my upgrade of V3....
So far I've not been able to recover the bricked RE200 V2.1
- When connecting serial, WIndows says unrecognized device and does not assign a COM port, so I can't use putty to access
- When connecting rj45 (to try the TFTP method), looks like the interface is disabled
Does anyone knows how to unbrick the device ?
TFTP recovery without serial on this device is not possible ( the bootloader is not checking for reset or some other button ,at least not in the versions I have tried) . So you need a working serial console, once you have that just tftp the initramfs-kernel image.
1 Like
My V3 is running 19.7 snapshot. Is there something i can help you with this one? I'm an amateur so you would need to guide me for this one.
I was trying to tell Moodyblue about RE200/RE220 recovery .
For serial console I am not sure what to recommand, as I use linux and "it just works",kernel finds the new USB0 then I connect to that via minicom.
1 Like
I suppose you're using a USB-TTL converter cable? Which one? What and how did you connect the cable? Is it detected without the RE200 attached?
1 Like