Re: Help unbricking AC750

Hi! W dniu 2022-06-18 o 17:14, Luca Bertoncello pisze: Hi! I have an TP-Link AC750 Archer C2. It worked with TP-Link Firmware and I wanted to install OpenWRT. Unfortunately, something went really wrong and now the devices seems to be bricked... Only Power-LED is on, no other activity. Has som

Re: Help unbricking AC750

Am 18.06.2022 um 18:03 schrieb Michael Fuckner: > I'd solder pins and connect to serial console and try if this still works Thank you very much. Unfortunately I don't have the possibility to do that myself... I'll check in my circle of friends if someone can help me... Regards Luca Bertoncello (

Re: Help unbricking AC750

The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- You can connect a serial interface

Re: Help unbricking AC750

I'd solder pins and connect to serial console and try if this still works HT, Michael! Am 18/06/2022 um 17:59 schrieb Luca Bertoncello: Am 18.06.2022 um 17:55 schrieb Brice GIBOUDEAU: Try the recovery procedure detailed on the device page. (Tftp, recovery). I tried it, but no TFTP-Session w

Re: Help unbricking AC750

Am 18.06.2022 um 17:55 schrieb Brice GIBOUDEAU: > Try the recovery procedure detailed on the device page. (Tftp, recovery). I tried it, but no TFTP-Session will be started... I prepared the server, power off the router, hold the Reset and power on the device, but only the power LED will turn on...

Re: Help unbricking AC750

The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- Try the recovery procedure detaile

Help unbricking AC750

Hi! I have an TP-Link AC750 Archer C2. It worked with TP-Link Firmware and I wanted to install OpenWRT. Unfortunately, something went really wrong and now the devices seems to be bricked... Only Power-LED is on, no other activity. Has someone an idea how can I try to recover it? Thanks a lot Lu

Re: [PATCH v3 3/6] ath79: D-Link DAP-2680 A1: convert ath10k caldata to nvmem

Hi Sebastian, On Sat, 2022-06-18 at 11:45 +0200, Sebastian Schaper wrote: > Tested successfully on DAP-2680, both radios are available and > the MAC address assignment is correct for LAN and both radios. > > Feel free to add my Tested-By to the commit message. > > I also tested DAP-2660 as an ex

Re: [PATCH v3 3/6] ath79: D-Link DAP-2680 A1: convert ath10k caldata to nvmem

Tested successfully on DAP-2680, both radios are available and the MAC address assignment is correct for LAN and both radios. Feel free to add my Tested-By to the commit message. I also tested DAP-2660 as an example Wave-1 device from the series, both radios and MAC assignment are working fine h

[PATCH v3 6/6] ath79: D-Link DAP-3662 A1: convert ath10k caldata to nvmem

Add the PCIe node for the ath10k radio to the devicetree, and refer to the art partition for the calibration data using nvmem-cells. MAC address assignment is moved to '10_fix_wifi_mac', so the device can then be removed from the caldata extraction script '11-ath10k-caldata'. Cc: Sebastian Schape

[PATCH v3 5/6] ath79: D-Link DAP-2695 A1: convert ath10k caldata to nvmem

Add the PCIe node for the ath10k radio to the devicetree, and refer to the art partition for the calibration data using nvmem-cells. MAC address assignment is moved to '10_fix_wifi_mac', so the device can then be removed from the caldata extraction script '11-ath10k-caldata'. Cc: Sebastian Schape

[PATCH v3 4/6] ath79: D-Link DAP-2660 A1: convert ath10k caldata to nvmem

Add the PCIe node for the ath10k radio to the devicetree, and refer to the art partition for the calibration data using nvmem-cells. MAC address assignment is moved to '10_fix_wifi_mac', so the device can then be removed from the caldata extraction script '11-ath10k-caldata'. Cc: Sebastian Schape

[PATCH v3 1/6] ath79: D-Link DAP-2xxx (QCA955x): move art partition to DTSI

The art partition containing the radio calibration data is in the same location for all supported devices. Move the definition to the base file so the reference from the wmac node can refer to the same file. Cc: Sebastian Schaper Signed-off-by: Sander Vanheule --- target/linux/ath79/dts/qca9557

[PATCH v3 2/6] ath79: D-Link DAP-2xxx (QCA955x): convert ath9k caldata to nvmem

Convert the calibration data reference for the ath9k radio to an nvmem-cell, replacing the downstream mtd-cal-data property. Cc: Sebastian Schaper Signed-off-by: Sander Vanheule --- Changes in v2: - Put nvmem cell definition directly in partition node --- target/linux/ath79/dts/qca955x_dlink_da

[PATCH v3 3/6] ath79: D-Link DAP-2680 A1: convert ath10k caldata to nvmem

Add the PCIe node for the ath10k radio to the devicetree, and refer to the art partition for the pre-calibration data using nvmem-cells. MAC address assignment is moved to '10_fix_wifi_mac', so the device can then be removed from the caldata extraction script '11-ath10k-caldata'. Cc: Sebastian Sc

[PATCH v3 0/6] ath79: convert QCA955x-based D-Link DAP-2xxx to nvmem

Convert the QCA955x based devices to nvmem-cell based calibration data extraction, so this can be removed from the init scripts. Changes in v3: - Use "pre-calibration" for 11ac Wave-2 hardware instead of "calibration" (kept for Wave-1) Changes in v2: - Put nvmem cell definition directly into pa

Re: [PATCH v2 3/6] ath79: D-Link DAP-2680 A1: convert ath10k caldata to nvmem

Hi Christian, On Sat, 2022-06-18 at 02:24 +0200, Christian Lamparter wrote: > Hi, > > On 18/06/2022 01:26, Sebastian Schaper wrote: > > unfortunately, testing these changes on DAP-2680 resulted in board-2.bin > > not being loaded, the driver is only looking for board.bin instead. > > > > [   12.