Sigh.

Running 2.13.0.0020 (and 0030) still gives the same situation when the CCO decides to not let other adapters join/rejoin/ throws them out...

These other adapters refuse to build their own network and start lurking in somehwat a non-op mode with TEI 0, even after a reset. (CCO selection is set to auto on these adapters).

Here one plc locally via ethernet in a 8360 and aonther one via wlan:

# plcstat -t
 P/L NET TEI ------ MAC ------ ------ BDA ------  TX  RX CHIPSET FIRMWARE
 LOC STA 000 98:DE:D0:31:A0:9E 18:A6:F7:A1:F5:BA n/a n/a QCA7500 MAC-QCA7500-2.13.0.20-00-20220812-CS
 P/L NET TEI ------ MAC ------ ------ BDA ------  TX  RX CHIPSET FIRMWARE
 LOC STA 000 18:A6:F7:A1:F5:BC 18:A6:F7:A1:F5:BA n/a n/a QCA7500 MAC-QCA7500-2.13.0.30-01-20221117-CS

So in terms of long-term stability it is still ... well ...

Hi!

First of all, thank you very much for providing those newer firmware files!

Unfortunately I seem to have bricked my device, a TL-WPA8630P V1 EU.

The are no firmware updates available from TP-LINK, and the stock firmware is the ancient 2.0.0.382-05_863111_151015_001.

I managed to export the original PIB file (20.888 bytes) from the device using the FRITZ! tool.

Using tpPLC, I tried to update the firmware past 2.0.0 without any luck. I tried many different firmware versions, and I also tried with the 2.3.3 PIB file from the dropbox folder: QCA75XX/pib_collection/Unknown_Origin/WPA8630P_V1_EU_2.2.3_unknown_origin.pib

Next, I switched to using the plctool linux utility. Using that, after a few attempts, I successfully flashed WPA8630P_V1_EU_2.2.3_unknown_origin.pib and full size QCA75XX-2.13.0030.nvm.

The device did not show up in tpPLC, so I added the MAC addr to the pib file with modpib, and flashed the device again. Now the device at least shows up in tpPLC, but as an Unknown device with no options for version information or firmware update.

Only downstream to my WPA8630P v1 EU now works (TL-PA8010P(EU)_V1 in the other end). Using tcpdump on a device connected to the WPA8630P I can see packages coming in, but uplink doesn't seem to work. The PA8010P is on firmware 2.13.

The device MAC seems to have changed to 00:B0:52:00:00:01. The device does not show up in "PLC Recover".

Using plctool, I'm unable to go back to the original firmware. (Invalid PIB Checksum (0x44) or Minor Version Mismatch (0x48) or Failure (0xFF): Device refused request). I suspect I managed to flash a broken pib file to the device.

I would like to try with the TP-LINK provided 2.4.0 PIB file for WPA8630P v1 EU, linked here:

https://community.tp-link.com/en/home/forum/topic/111229?replyId=250606

Unfortunately the link no longer works. Maybe someone here can provide me with TL-WPA8630Pv1_171117.EU.Beta.stability.zip?

Should I have flashed the stripped version instead?

Any other suggestions for how to recover my device?

The plcboot does not seem to work for me. It just keeps saying "Bootloader must be running". Attempting plctool -R local -P <pibfile> always fails with Individual Module Error (0x31): Device refused request.

More device info:

$ sudo plctool -Iarm
eth1 00:B0:52:00:00:01 Request Version Information
eth1 00:80:31:08:13:01 QCA7500 MAC-QCA7500-2.13.0.30-01-20221117-CS
eth1 00:B0:52:00:00:01 Fetch Device Attributes
eth1 00:80:31:08:13:01 QCA7500-MAC-QCA7500-2.13.0.30-01-20221117-CS (128mb)
    PIB 0-0 21384 bytes
    MAC 00:80:31:08:13:01
    DAK 68:9F:07:4B:8B:02:75:A2:71:0B:0B:57:79:AD:16:30 (HomePlugAV)
    NMK E8:A7:94:78:AD:C4:5B:6A:BF:1B:94:7B:54:AD:D1:A2
    NID 07:DE:67:C3:84:3F:0C
    Security level 0
    NET Qualcomm Atheros Enabled Network
    MFG Qualcomm Atheros HomePlug AV Device
    USR tpver_863111_170511_901
    CCo Auto
    MDU N/A
eth1 00:B0:52:00:00:01 Fetch Network Information
eth1 00:80:31:08:13:01 Found 0 Network(s)

source address = 00:80:31:08:13:01

* Update *:

What the heck. As a last attempt out of desperation, I tried different combinations of pushing and holding the two buttons (WiFi and Pair). Around the same time, I pushed the Pair button on the TL-PA8010P, and they managed to Pair. Now everything works. It even shows up correctly in tpPLC which confirms that it is running 2.13!

Best regards

Anders

Hi I recently got a TPLink pa8033p kit.

I managed to upgrade the 8010 with the tp utility but for some reason the 8030p(UK) would not upgrade. I tired and used the stripped NVM and tried under Mac and Windows. Is there any other way to try to upgrade the firmware either Mac or Windows..??

The version on the powerline is 2.07 and tried 2.08, 2.10, 2.11 and 2.13

  @dept27 Did you extract the .pib file from the device itself (with the AVM FritzPowerline Utility)? Extract the pib file (again) and use that file to upgrade. To extract the .pib file from the device: click report, save and yes for additional info. I would also suggest to download the .nvm files again.

You probably have a "stubborn" adapter. I had one too that failed to upgrade for multiple times (while other adapters succeeded at first attempt). The upgrade finally succeeded after I extracted a "fresh" .pib file and a freshly downloaded .nvm file. Don't ask me why. It worked but can't explain.

TP Utility:  reset the device and quickly/immediately click refresh [left pane] and try to upgrade the device with the extracted .pib and the downloaded .nvm file. Use the stripped one for V2 with WIFI module.

BTW, you should be able to upgrade straight to 2.13. Assuming your pib file is about 22 kB in size.

  @PowerlineFW 

Many thanks for the new .0053 fw. Added to the dropbox folder.