Welcome to TP-LINK Tech Support Forum
+ Reply to Thread
Page 4 of 4 FirstFirst ... 2 3 4
Results 46 to 56 of 56
  1. #46
    I do not find the newest tpPLC utility on the tp-limk.de side. Where can I get the newest version? thank you

  2. #47

  3. #48
    For those interested, firmware v2.4.0-01 for QCA7500 :

    PIB v2.2.x are OK with it.
    I take no responsibility if you brick your PLC. Don't try to flash blindly.
    Do understand beforehand that it's a full QCA firmware, ie there are 7 modules in it vs TP-Link ones which use 5, and there's might/must be a reason for this choice.

    So if you want to have a 5 modules firmware, you have to :
    0 download and build binaries from Qualcomm Atheros Open Powerline Toolkit : https://github.com/qca/open-plc-utils
    1 split modules (nvmsplit)
    2 merge needed modules - i.e omit "OAS Client IP Stack" and "OAS Client TR069" module - (nvmmerge)
    3 verify the integrity of the new merged NVM (chknvm2 -v + nvmsplit -v )
    Last edited by shroeder; 09-05-2017 at 09:34.

  4. #49
    Could you please provide a more detailed instructions how to do that? What software is needed? If you could post FW for PL8010P, I would be grateful :-)

  5. #50
    OK, I've added some instructions in italic in my post, about what software is needed, and what commands are to be passed. HTH.
    As for "already-made customisation for TP-Link", I'm a little bit reluctant to provide one this since it defeats the purpose of giving explanations in order for people to understand stuff they are doing but well, here it is:
    Last edited by shroeder; 09-05-2017 at 09:39.

  6. #51
    Thank you very much! So NVM is the actal firmware whereas PIB is just the frequeny table? So I can mix newer NVM and older PIB for the same product?

  7. #52
    Well to be precise, only module 4 (counting from 0) of the NVM is the actual "Runtime Firmware", but this is nitpicking.
    As for the PIB, it's more like a configuration file which, apart from the frequency table with exclusions according to local regulations (hence the EU, UK, US flavors), contains amongst other things CCo("P2P") or MDU("Master/Slave") configuration, QoS settings, DAK (Device Access Key), MAC @, NMK (Network Membership Key) which are not reflashed except in bootloader mode.
    The format of PIB file is not immutable but a v2.2.x PIB should work with a v2.4.0 NVM. AFAIK latest PIB for a EUropean 8010P is in http://static.tp-link.com/Beta_TL-PA...01.0_2.2.3.rar
    For flashing, it's better to use the old TP-Link Utility rather than tpPLC, but in a newer version than the one packaged by NOLAN (v2.0 build 20150327 vs v2.0 build 20140923), which can be found in http://www.tplink.com/resources/soft...V1_Utility.zip

  8. #53
    Thanks for clarifying! Can I use PIB from 2.0.0 with 2.2, 2.3 or 2.4 NVM?

  9. #54
    I don't have a clear response to your question because I haven't tested that sort of weird mix (and don't want to answer theoretically).
    But why would you want to do such a thing ? PIBs, just like NVMs, are refined/adjusted with time.

  10. #55
    I use the adapters on a really bad wiring across two phases and with fw 2.0.0 I get a stable connection at around 30 Mbps. If I try a newer fw, the connection drops to 4 Mbps and is unstable, or cannot be established at all. So older fw is good, newer doesn't work. That's why I would like to try newer fw with older PIB.

  11. #56
    Quote Originally Posted by shroeder View Post
    it still shows unkown. no device name


Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

Copyright 1996-2017 TP-LINK Technologies Co., Ltd. All rights reserved.