Firmware for TL-WPA8630(P) TL-PA8033(P) TL-PA8030(P) TL-PA8010(P) QCA75XX-2.11.0.0043

Re:Firmware for TL-WPA8630(P) TL-PA8033(P) TL-PA8030(P) TL-PA8010(P) QCA75XX-2.10.0.0032
2021-02-13 21:23:16

@PowerlineFW 

 

Many thanks!!!!!

 

Bey the way, what are modules 5 and 6 for?

  1  
  1  
#63
Options
Re:Firmware for TL-WPA8630(P) TL-PA8033(P) TL-PA8030(P) TL-PA8010(P) QCA75XX-2.10.0.0032
2021-02-13 21:31:07
I don`t know. It has something to do with special functionalities, maybe for connection monitoring.
  1  
  1  
#64
Options
Re:Firmware for TL-WPA8630(P) TL-PA8033(P) TL-PA8030(P) TL-PA8010(P) QCA75XX-2.10.0.0032
2021-02-14 09:15:02

@PowerlineFW 

Just updated to QCA75XX-2.10.0.0032 with no problems on my 4 adapters! Great work Guyz on continuing to bring us updates to these adapters! ;)

It's All Good!!! ;)
  1  
  1  
#65
Options
Re:Firmware for TL-WPA8630(P) TL-PA8033(P) TL-PA8030(P) TL-PA8010(P) QCA75XX-2.10.0.0032
2021-02-14 13:04:32 - last edited 2021-02-14 20:30:11

@PowerlineFW @Migz @turboleak Just updated the TL-WPA8630PKIT V2 (EU). Both adapters without error messages but I'm not sure if the WPA8630P V2 (EU) is updated to the latest PLC firmware as the version number didn't change. So I'm a bit confused as i'm not sure if the TL-WPA8630P V2 (EU) adapter is updated to 2.10.

All suggestions are welcome.

 

BTW, the Zyxel Firmware Update tool (post #43) or the TL Link PLC Recover tool doesn't find any adapters. I guess they need some configuration to use the correct network interface controller and it can't be done manually.

 

Fritz!Powerline 01.03.00 tool:

TL-PA8010P V2 (EU): PLC: 2.10.0.1, tpver_801192_170511_906 (C4:71:54:FF:B9:11)

TL-WPA8630P V2 (EU): PLC: 2.8.0.1, tpver_863112_170509_902 (0C:80:63:EE:F4:A3)

 

Command line:

plctool -a -i 4 -f  0C:80:63:EE:F4:A3 [TL-WPA8630P V2 (EU)]
nic4 0C:80:63:EE:F4:A3 Fetch Device Attributes
nic4 0C:80:63:EE:F4:A3 QCA7550-MAC-QCA7550-2.8.0.30-01-20190705-CS (16mb)
nic4 0C:80:63:EE:F4:A3 Fetch NVRAM Configuration
nic4 0C:80:63:EE:F4:A3 TYPE=0x14 (M25P16_ES) PAGE=0x0100 (256) BLOCK=0x10000 (65536) SIZE=0x200000 (2097152)


plctool -a -i 4 -f  C4:71:54:FF:B9:11 [TL-PA8010P V2 (EU)]
nic4 C4:71:54:FF:B9:11 Fetch Device Attributes
nic4 C4:71:54:FF:B9:11 QCA7550-MAC-QCA7550-2.10.0.32-01-20200626-CS (16mb)
nic4 C4:71:54:FF:B9:11 Fetch NVRAM Configuration
nic4 C4:71:54:FF:B9:11 TYPE=0x14 (M25P16_ES) PAGE=0x0100 (256) BLOCK=0x10000 (65536) SIZE=0x200000 (2097152)

 

 

@turboleak Yep, that is what i'm thinking. Still on 2.8.

 

Update: both adapters are now on version 2.10.0.32-01. Flashed the WPA8630P V2 (EU) with the stripped nvm.

 

plctool -a -i 4 -f  0C:80:63:EE:F4:A3 [TL-WPA8630P V2 (EU)]
nic4 0C:80:63:EE:F4:A3 Fetch Device Attributes
nic4 0C:80:63:EE:F4:A3 QCA7550-MAC-QCA7550-2.10.0.32-01-20200626-CS (16mb)
nic4 0C:80:63:EE:F4:A3 Fetch NVRAM Configuration
nic4 0C:80:63:EE:F4:A3 TYPE=0x14 (M25P16_ES) PAGE=0x0100 (256) BLOCK=0x10000 (65536) SIZE=0x200000 (2097152)
  1  
  1  
#66
Options
Re:Firmware for TL-WPA8630(P) TL-PA8033(P) TL-PA8030(P) TL-PA8010(P) QCA75XX-2.10.0.0032
2021-02-14 13:20:04

@Dleb 

 

so it seems that the 8630P v2 is still at 2.8.

  0  
  0  
#67
Options
Re:Firmware for TL-WPA8630(P) TL-PA8033(P) TL-PA8030(P) TL-PA8010(P) QCA75XX-2.10.0.0032
2021-02-14 19:41:17 - last edited 2021-02-14 19:58:38

 

For a quick firmware update session, I am using this scriptlet on Openwrt (or any other Linux) with open-plc-utils.

The PIB is retrieved from the running PLC, so no hazzle here. Caveat: when retrieving the PIB remotely (ie not locally attached), the DAK is deleted. Also, the script expected all locally attached PLCs to be QCA7500...

Locally attached means any ethernet or WLAN, just not a PLC connection.


export PLC=br-lan
fwfile=QCA7500-2.10.0032_modules_5-6_stripped.nvm
for localplcmac in $(plctool -q -L|awk '{print $2;}'); do
localshortmac=$(echo $localplcmac|sed -e 's/://g')
echo $localplcmac $localshortmac
plctool -a -f $localplcmac
pibfile=${localshortmac}.pib
plctool -p $pibfile $localplcmac
ls -l $pibfile
plctool -P ${pibfile} -N ${fwfile} ${localplcmac}
sleep 5
plctool -R ${localplcmac}
sleep 10
plcstat -t
done

Done on TL-WPA8630V1 running a local Openwrt, now going forward to the other boxes (TL-WPA8630V2, 8030, 8010).

 

  0  
  0  
#68
Options
Re:Firmware for TL-WPA8630(P) TL-PA8033(P) TL-PA8030(P) TL-PA8010(P) QCA75XX-2.10.0.0032
2021-02-15 10:08:29
Ok, this PIB retrieval does not work for upgrade from MAC-QCA7500-2.0.0.382-05-20150511-CS : Minor Version Mismatch (0x48): Device refused request
  0  
  0  
#69
Options
Re:Firmware for TL-WPA8630(P) TL-PA8033(P) TL-PA8030(P) TL-PA8010(P) QCA75XX-2.10.0.0032
2021-02-15 10:24:16 - last edited 2021-02-15 10:25:38

@PowerlineFW @netadair  2.0.0 is the stock firmware? If I remember correctly the TL-WPA8630p V2 (EU) adapter had to be updated incrementally. Try to update to 2.4 > 2.5/2.6 > 2.8/2.10. At some point you will pass the "minor version mismatch" and directly updating to 2.10 should be fine.

  0  
  0  
#70
Options
Re:Firmware for TL-WPA8630(P) TL-PA8033(P) TL-PA8030(P) TL-PA8010(P) QCA75XX-2.10.0.0032
2021-02-15 11:05:26
@Ariek Ok, thanks! Upgrade straight from MAC-QCA7550-2.2.3.32-00-20161104-CS (which has 22k pib file) to 2.10 worked with the script (ie 8010P V2). So I will try an upgrade from 2.0 to 2.2 first to get the pib updated to the new version, also the 20k pib file grows to 22k.
  0  
  0  
#71
Options
Re:Firmware for TL-WPA8630(P) TL-PA8033(P) TL-PA8030(P) TL-PA8010(P) QCA75XX-2.10.0.0032
2021-02-16 10:02:37

@PowerlineFW 

I own a pair of TL-PA8010P (UK) V1.0 adapters and I wish to update from 2.0.0.382-05_801111_160406_913 to the latest 2.10 firmware (even incrementally if possible).

First of all, quick question: Is that possible considering I have V1.0 adapters? I understand yes.. as I read in the first post that the hardware version is irrelevant as long as I use the correct pib file.

Secondly, I extracted the pib from my adapter and the checksum is different to the one that already exists in the QCA_Firmware folder for the same version. However, with either pib files I can successfully re-flash the original 2.0.0 version via the latest tpplc utility.

 

What I really cannot do, is to flash to any higher version (2.2.2, 2.2.3, 2.4.0 or higher).Fyi, I tried either pib files as I described above:

-Tpplc just says "update failed".

-Linksys's PL5405 utility returns "Minor version Mismatch (0x48). Device Refused request".

-The older TP Link utility (powerline.exe) located in the "Recovery/Utility/" directory comes up with "successful update", the adapter then needs re-pairing, but apparently the version stays the same as before. (I only tried 2.2.2 here). the pib file became different after this.

Any idea?

 

Finally, if let's say I am successful in updating the adapter by 1 step (to 2.2.2 or 2.4), am I supposed to use a later extracted pib file that would correspond to the newly flashed version (i.e. 2.2.2/2.4) ?

 

Thanks in advance!

  0  
  0  
#72
Options