plctool.1.html 16 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260
  1. <?xml version='1.0' encoding='iso-8859-1'?>
  2. <!doctype html public '-//W3C//DTD XHTML 1.0 Strict//EN' 'http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd'>
  3. <html xmlns='http://www.w3c.org/1999/xhtml' lang='en-us'>
  4. <head>
  5. <title>
  6. plctool.1
  7. </title>
  8. <meta http-equiv='content-type' content='text/html;iso-8859-1'/>
  9. <meta name='generator' content='motley-tools 1.9.4 13:40:33 Feb 18 2015'/>
  10. <meta name='author' content='cmaier@cmassoc.net'/>
  11. <meta name='robots' content='noindex,nofollow'/>
  12. <link href='toolkit.css' rel='stylesheet' type='text/css'/>
  13. </head>
  14. <body>
  15. <div class='headerlink'>
  16. [<a href='plctone.1.html' title=' plctone.1 '>PREV</a>]
  17. [<a href='toolkit.html' title=' Index '>HOME</a>]
  18. [<a href='plcwait.1.html' title=' plcwait.1 '>NEXT</a>]
  19. </div>
  20. <pre>
  21. plctool(1) Qualcomm Atheros Open Powerline Toolkit plctool(1)
  22. NAME
  23. plctool - Qualcomm Atheros Panther/Lynx Powerline Device Manager
  24. SYNOPSIS
  25. plctool [options] [device] [device] [...]
  26. DESCRIPTION
  27. This version of the Qualcomm Atheros Powerline Device Manager performs basic operations on powerline devices using ven‐
  28. dor-specific management messages. It can be used to interrogate and control devices or upgrade firmware if on-board
  29. NVRAM is present. See amptool for a similar utility that supports AR7400 devices. It supports chipsets QCA6410, QCA7000
  30. and QCA7420.
  31. This program is the proper tool for upgrading panther/lynx devices. It is important to reset panther/lynx devices after
  32. update since reset after update is not automatic anymore. Also, everything takes longer because part memory is erased
  33. before being written. Some operations may take 20 to 40 seconds so be patient.
  34. This program is part of the Qualcomm Atheros Powerline Toolkit. See the plc man page for an overview and installation
  35. instructions.
  36. COMMENTS
  37. This program version is identical to legacy program int6k except for option -m which uses version 1 of the Qualcomm
  38. Atheros VS_NW_INFO vendor-specific message. Older firmware versions may not recognize this message version.
  39. OPTIONS
  40. -a Read device attributes using VS_OP_ATTRIBUTES. Attributes are short strings and integers that describe device
  41. hardware and firmware. They are concatenated to form the output that is similar to option -r but derived differ‐
  42. ently.
  43. -B action
  44. press the simple connect pushbutton using VS_PB_ENC. The action can be specified by number 1, 2, 3 or 4 or by
  45. symbol &quot;join&quot;, &quot;leave&quot;, &quot;status&quot; or &quot;reset&quot;, respectively. Use 1 on both devices that are expected to join. Use
  46. 2 only on the device that is expected to leave the network.
  47. -d filename
  48. Read Watchdog Report from the device and write it to the named file in binary format using VS_WD_RPT. The report
  49. file can be sent to Qualcomm Atheros for technical analysis. No assumptions are made based on filename and no
  50. filename convetions are enforced; however, you should use a .log file extension to indicate binary format.
  51. -D xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx
  52. Define the 16 octet Device Access Key (DAK) in hex format. The DAK is used by option -J. It may also be set to
  53. &quot;key1&quot; or &quot;key2&quot; as explained in the KEYS section.
  54. -e Redirects stderr messages to stdout. Normally, status and error messages are printed on stderr while primary pro‐
  55. gram output is printed on stdout. This option prints all output on stdout in cases where this is desired.
  56. -f Read flash memory parameters using VS_GET_NVM. An error will be reported if no flash memory is present.
  57. -F[F] Write previously downloaded MAC and PIB to NVRAM using VS_MOD_NVM. Adding a second F here or another -F anywhere
  58. on the command line WILL NOT force-flash a blank or corrupted NVRAM as with programs int6k and amptool. Firmware
  59. loaded from NVRAM will treat force-flash as an error. This option can be used to create factory settings but can‐
  60. not be used to change them once created. Subsequent use creates and updates operational settings that can be
  61. erased using a factory reset. This option is executed after all others on the command line, except for the -R
  62. option.
  63. -g Read multicast group information discovered while IGMP snooping using VS_MULTICAST_INFO.
  64. -i interface
  65. Select the host Ethernet interface. All requests are sent via this host interface and only reponses received via
  66. this host interface are recognized. The default interface is eth1 because most people use eth0 as their principle
  67. network connection; however, if environment string &quot;PLC&quot; is defined then it takes precedence over the default
  68. interface. This option then takes precedence over either default.
  69. -I Read the device PIB header using VS_MODULE_OPERATION and print the PIB major and minor revision number, Device
  70. Access Key (DAK), Network Membership Key (NMK), MAC address and other identity information on stdout. The values
  71. displayed can be changed using program modpib.
  72. -J xx:xx:xx:xx:xx:xx
  73. Set the Network Membership Key (NMK) on a remote device using VS_SET_KEY. This option is similar to option -K but
  74. requires the remote device MAC and DAK in addition to the NMK and local device MAC address. The NMK value is
  75. defined using option -K unless you want to use the default value. The remote DAK is defined using option -D
  76. unless you want to use the default value. Programming remote device keys is complicated. It is often easier to
  77. connect the device directly to the host and use the -K option.
  78. -K xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx
  79. Define the Network Membership Key (NMK) value used by options -M or -J. The symbolic names &quot;key1&quot; and &quot;key2&quot; are
  80. recognized as described in the KEY section.
  81. -l count
  82. Define the number of times that the command will be repeated for each device specified. Normally, you will repeat
  83. operations on one device only.
  84. -L Read and display powerline link status.
  85. -m Read network membership information using VS_NW_INFO. This can be used to determine network configuration.
  86. -M Set the Network Membership Key (NMK) on the local device using VS_SET_KEY. The NMK value is specified using the
  87. -K option unless you want to use the default value.
  88. -n filename
  89. Read firmware from the device SDRAM and write it to the named .nvm file using multiple VS_RD_MOD messages. No
  90. assumptions are made based on filename and no filename conventions are enforced. This option is performed before
  91. option -N when both are specified.
  92. -N filename
  93. Read the named .nvm file and write it to the device using multiple VS_WR_MOD messages. No assumptions are made
  94. based on filename and no filename conventions are enforced; however, files having invalid .nvm format will be
  95. rejected. This option is executed after -n when both are specified.
  96. -p filename
  97. Read parameters from the device NVRAM and write them to the named .pib file using multiple VS_RD_MOD messages. No
  98. assumptions are made based on filename and no filename convetions are enforced. This option is executed before
  99. option BP when both are specified.
  100. -P filename
  101. Read the named .pib file and write it to the device using multiple VS_WR_MOD messages. No assumptions are made
  102. based on filename and no filename conventions are enforced; however, files having invalid .pib format will be
  103. rejected. This option is executed after -p when both are specified.
  104. -q Suppresses status messages on stderr.
  105. -Q Quick flash. The program will not wait for a device to reset or the firmware to restart after writing flash mem‐
  106. ory. This option is desirable with newer firmware that writes flash memory in the background. It has no effect
  107. unless used with option -F or -C.
  108. -r Read device firmware and hardware revision using VS_SW_VER. Output is similar to option -a but is derived differ‐
  109. ently.
  110. -R Reset the device using VS_RS_DEV. This option is executed after all others on the same command line.
  111. -t milliseconds
  112. Read timeout in milliseconds. Values range from 0 through UINT_MAX. This is the maximum time allowed for a
  113. response. The default is shown in brackets on the program menu.
  114. -T Restore factory defaults. This permanently erases all PIB changes made since the device was last programmed with
  115. factory default settings. The device will automatically reset and reboot.
  116. -v Print additional information on stdout. In particular, this option dumps incoming and outgoing packets which can
  117. be saved as text files for reference.
  118. -w seconds
  119. Defines the number of seconds to wait before repeating command line options. This option has no effect unless
  120. option -l is also specified with a non-zero value.
  121. -x Cause the program to exit on the first error instead of continuing with remaining iterations, operations or
  122. devices. Normally, the program reports errors and moves on to the next operation, iteration or device depending
  123. on the command line.
  124. -?,--help
  125. Print program help summary on stdout. This option takes precedence over other options on the command line.
  126. -?,--version
  127. Print program version information on stdout. This option takes precedence over other options on the command line.
  128. Use this option when sending screen dumps to Atheros Technical Support so that they know exactly which version of
  129. the Linux Toolkit you are using.
  130. ARGUMENTS
  131. device The Ethernet hardware address of some powerline device. More than one address may be specified on the command
  132. line. If more than one address is specified then operations are performed on each device in turn. The default
  133. address is local. as explained in the DEVICES section.
  134. KEYS
  135. Passwords are variable length character strings that end-users can remember. Keys are fixed length binary values created
  136. by encrypting passwords. There are two encryption algorithms for HomePlugAV. One for DAKs and the other for NMKs. This
  137. means that a given password will produce different keys depending on use. This program only deals with keys because that
  138. is what powerline devices recognize. The passwords that generated the keys are irrelevant here.
  139. Encryption keys are tedious to type and prone to error. For convenience, symbolic names have been assigned to common
  140. encryption keys and are recognized by options -D and -K.
  141. key1 Key for encrypted password &quot;HomePlugAV&quot;. This is &quot;689F074B8B0275A2710B0B5779AD1630&quot; for option -D and
  142. &quot;50D3E4933F855B7040784DF815AA8DB7&quot; for option -K.
  143. key2 Key for encrypted password &quot;HomePlugAV0123&quot;. This is &quot;F084B4E8F6069FF1300C9BDB812367FF&quot; for option -D and
  144. &quot;B59319D7E8157BA001B018669CCEE30D&quot; for option -K.
  145. none Always &quot;00000000000000000000000000000000&quot;.
  146. DEVICES
  147. Powerline devices use Ethernet hardware, or Media Access Control (MAC), addresses. Device addresses are 12 hexadecimal
  148. digits (0123456789ABCDEFabcdef) in upper, lower or mixed case. Individual octets may be separated by colons, for clar‐
  149. ity, but not all octets need to be seperated. For example, &quot;00b052000001&quot;, &quot;00:b0:52:00:00:01&quot; and &quot;00b052:000001&quot; are
  150. valid and equivalent.
  151. These symbolic addresses are recognized by this program and may be used instead of the actual address value.
  152. all Equivalent to &quot;broadcast&quot;, described next.
  153. broadcast
  154. A synonym for the standard Ethernet broadcast address, FF:FF:FF:FF:FF:FF. All devices, whether local, remote or
  155. foreign will respond to this address.
  156. local A synonym for the Qualcomm Atheros vendor specific Local Management Address (LMA), 00:B0:52:00:00:01. All local
  157. Atheros devices will recognize this address but remote and foreign devices will not. A remote device is any
  158. device at the far end of a powerline connection. A foreign device is any device not manufactured by Atheros.
  159. REFERENCES
  160. See the Qualcomm Atheros HomePlug AV Firmware Technical Reference Manual for more information.
  161. DISCLAIMER
  162. Atheros HomePlug AV Vendor Specific Management Message structure and content is proprietary to Qualcomm Atheros, Ocala FL
  163. USA. Consequently, public information may not be available. Qualcomm Atheros reserves the right to modify message
  164. structure or content in future firmware releases without any obligation to notify or compensate users of this program.
  165. EXAMPLES
  166. The following command writew file QCA7000.pib and QCA7000.nvm to a remote powerline device then resets it. The reset is
  167. required because reset after flash is no longer automatic.
  168. # plctool -P QCA7000.pib -N QCA7000.nvm -R 00B05201053E
  169. The previous command does not replace existing PIB values. Instead, it appends the new PIB values to the end of the old
  170. PIB. To replace existing PIB values, you must write the same PIB again, as follows.
  171. # plctool -P QCA7000.pib -R 00B05201053E
  172. The following commands do the same thing but avoid one unecessary reset.
  173. # plctool -P QCA7000.pib -N QCA7000.nvm 00B05201053E
  174. # plctool -P QCA7000.pib -R 00B05201053E
  175. The reset can also be postponed as follows.
  176. # plctool -P QCA7000.pib -N QCA7000.nvm 00B05201053E
  177. # plctool -P QCA7000.pib 00B05201053E
  178. # plctool -R 00B05201053E
  179. The next two commands are equivalent. They set the NMK on the local device to key1 as descripted in the KEYS section.
  180. The first command resets the NMK on the local device with -M then specifies the NMK as key1. The second command omits
  181. the key specification since key1 is the program default NMK. One could, of course, type the encryption key.
  182. # plctool -MK key1
  183. # plctool -M
  184. SEE ALSO
  185. plc(1), ampboot(1), ampboot(1), amphost(1), int6kid(1), amprate(1), amprule(1), ampstat(1), ampwait(1)
  186. CREDITS
  187. Charles Maier &lt;cmaier@qca.qualcomm.com&gt;
  188. Nathaniel Houghton &lt;nhoughto@qca.qualcomm.com&gt;
  189. open-plc-utils-0.0.3 Mar 2014 plctool(1)
  190. </pre>
  191. <div class='footerlink'>
  192. [<a href='plctone.1.html' title=' plctone.1 '>PREV</a>]
  193. [<a href='toolkit.html' title=' Index '>HOME</a>]
  194. [<a href='plcwait.1.html' title=' plcwait.1 '>NEXT</a>]
  195. </div>
  196. </body>
  197. </html>