int6kboot.1.html 11 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189
  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. int6kboot.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='int6kbaud.1.html' title=' int6kbaud.1 '>PREV</a>]
  17. [<a href='toolkit.html' title=' Index '>HOME</a>]
  18. [<a href='int6kdetect.1.html' title=' int6kdetect.1 '>NEXT</a>]
  19. </div>
  20. <pre>
  21. int6kboot(1) Qualcomm Atheros Open Powerline Toolkit int6kboot(1)
  22. NAME
  23. int6kboot - Qualcomm Atheros Powerline Device Boot Utility I
  24. SYNOPSIS
  25. int6kboot [options] -N file -P file [device] [device] [...]
  26. DESCRIPTION
  27. Download and start runtime firmware on any local Atheros powerline device that is in bootloader mode. A device remains
  28. in bootloader mode when it cannot load firmware from flash memory for some reason. This can happen because there is no
  29. flash memory or because the flash memory is blank or corrupted. This program can start a device or start then flash a
  30. device.
  31. The bootloader only recognizes a subset of Atheros message types. This program uses that subset to write runtime
  32. firmware and parameters into SDRAM then start firmware execution at a known address. Optionally, this program can then
  33. proceed to download the same firmware and parameters, again, and instruct the runtime firmware to write them to flash
  34. memory.
  35. Starting a device is a three phase operation that can only be performed when the bootloader is running. The first phase
  36. writes an SDRAM configuration program into TCM and executes it. The second phase writes runtime firmware and parameters
  37. as images into SDRAM. The third phase starts firmware execution. Once the runtime firmware starts, the device will be
  38. operational.
  39. Flashing a device is a two phase operation that can only be performed when the firmware is running. The first phase
  40. downloads runtime firmare and parameters into scratch buffers under firmware control. The second phase instructs the
  41. firmware to write the scratch buffers to flash memory and restart the device. After flashing, the device will be self-
  42. sustaining.
  43. Since the device address is 00:B0:52:00:00:01 on boot, the host must send all messages to that address. This can cause
  44. problems if multiple devices are connected to the host and in Bootloader mode. The devices will have the same firmware
  45. and MAC address because their PIBs will be identical. One should avoid this situation.
  46. Is probably alright to have other device connected to the host that are running firmware because they will still see but
  47. not recognize the messages used in this operation. If only one device is connected to the host, then is save to flash
  48. the device using address 00:B0:52:00:00:01. Otherwise, the host should address messages to the actual device address so
  49. that other devices do not attempt to write to their own flash memory at the same time.
  50. This program is part of the Qualcomm Atheros Powerline Toolkit. See the plc man page for an overview and installation
  51. instructions.
  52. OPTIONS
  53. -e Redirects stderr messages to stdout. By convention status and error messages are printed on stderr while primary
  54. program output is printed on stdout. This option prints all output on stdout in cases where this is desired.
  55. -F[F] Write previously downloaded MAC and PIB to NVRAM using VS_MOD_NVM. Adding a second F here or another -F anywhere
  56. on the command line will force-flash a blank or corrupted NVRAM. Firmware loaded from NVRAM will treat force-
  57. flash as an error. This option can be used to create factory settings but cannot be used to change them once cre‐
  58. ated. Subsequent use creates and updates operational settings that can be erased using a factory reset.
  59. -i interface
  60. Select the host Ethernet interface. All requests are sent via this host interface and only reponses received via
  61. this host interface are recognized. The default interface is eth1 because most people use eth0 as their principle
  62. network connection; however, if environment string &quot;PLC&quot; is defined then it takes precedence over the default
  63. interface. This option then takes precedence over either default.
  64. -N filename
  65. Read the named NVM file and write it to the device. This option and argument are required. Any file having an
  66. invalid NVM file format will be rejected. No assumptions are made based on filename and no filename conventions
  67. are enforced.
  68. -P filename
  69. Read the named PIB file and write it to the device. This option and argument are required. Any file having an
  70. invalid PIB file format will be rejected. No assumptions are made based on filename and no filename conventions
  71. are enforced.
  72. -q Suppresses status messages on stderr.
  73. -t milliseconds
  74. Read timeout in milliseconds. Values range from 0 through UINT_MAX. This is the maximum time allowed for a
  75. response. The default is shown in brackets on the program menu.
  76. -v Prints additional information on stdout. In particular, this option dumps outgoing Ethernet packets on stdout.
  77. -?,--help
  78. Print program help summary on stdout. This option takes precedence over other options on the command line.
  79. -!,--version
  80. Print program version information on stdout. This option takes precedence over other options on the command line.
  81. Use this option when sending screen dumps to Atheros Technical Support so that they know exactly which version of
  82. the Linux Toolkit you are using.
  83. ARGUMENTS
  84. device The Ethernet hardware address of some powerline device. More than one address may be specified on the command
  85. line. If more than one address is specified then operations are performed on each device in turn. The default
  86. address is local. as explained in the DEVICES section.
  87. DEVICES
  88. Powerline device addresses are 12 hexadecimal digits in upper, lower or mixed case. Individual octets may be separated
  89. by colons, for clarity, but colons are not required. For example, &quot;00b052000001&quot;, &quot;00:b0:52:00:00:01&quot; and
  90. &quot;00b052:000001&quot; are valid and equivalent.
  91. A local device is any Atheros Powerline Device connected directly to a host Ethernet interface. A remote device is any
  92. Atheros Powerline Device at the far end of a powerline connection. A foreign device is any powerline device not manufac‐
  93. tured by Atheros.
  94. Common device addresses have symbolic names that can be used in place of the actual address value. The following sym‐
  95. bolic addresses are recognized by this program and most other toolkit programs.
  96. all Equivalent to &quot;broadcast&quot;, described next.
  97. broadcast
  98. A synonym for the Ethernet broadcast address, FF:FF:FF:FF:FF:FF. All devices, whether local, remote or foreign
  99. will respond to this address.
  100. local A synonym for the Qualcomm Atheros Local Management Address (LMA), 00:B0:52:00:00:01. All local Atheros devices
  101. will respond to this address but remote and foreign devices will not.
  102. REFERENCES
  103. See the Qualcomm Atheros HomePlug AV Firmware Technical Reference Manual for technical information. See the Qualcomm
  104. Atheros Powerline Toolkit Online Documetation for practical information and examples.
  105. EXAMPLES
  106. The -N and -P options are always required. Their order is not important. Tne MAC address is not needed because devices
  107. default to address 00:B0:52:00:00:01 (the program default address) in bootloader mode. Once this operation completes,
  108. firmware is running in SDRAM but the NVRAM, if present, has not been programmed. This operation is common for flash-less
  109. devices. If we reset the device at this point then the device will return to bootloader mode.
  110. int6kboot -N test.nvm -P test.pib
  111. # eth0 00:B0:52:00:00:01 Write SDRAM Configuration
  112. # eth0 00:B0:52:00:00:01 Written.
  113. # eth0 00:B0:52:00:00:01 Write to device memory
  114. # eth0 00:B0:52:00:00:01 Written.
  115. # eth0 00:B0:52:00:00:01 Write to device memory
  116. # eth0 00:B0:52:00:00:01 Written.
  117. # eth0 00:B0:52:00:00:01 Start Firmware
  118. # eth0 00:B0:52:00:00:01 Started.
  119. The next example does the same thing but performs the extra steps needed to program NVRAM. It first downloads the
  120. firmware image from file test.nvm and the parameter block image from file test.pib using VS_WR_MEM then starts firmware
  121. execution using VS_ST_MAC. Once runtime firmware has started, it downloads the same firmware image and parameter block
  122. image (again) using VS_WR_MOD and commits them to NVRAM using VS_MOD_NVM.
  123. int6kboot -N test.nvm -P test.pib -F
  124. # eth0 00:B0:52:00:00:01 Write SDRAM Configuration
  125. # eth0 00:B0:52:00:00:01 Written.
  126. # eth0 00:B0:52:00:00:01 Write to device memory
  127. # eth0 00:B0:52:00:00:01 Written.
  128. # eth0 00:B0:52:00:00:01 Write to device memory
  129. # eth0 00:B0:52:00:00:01 Written.
  130. # eth0 00:B0:52:00:00:01 Start Firmware
  131. # eth0 00:B0:52:00:00:01 Started.
  132. # eth0 00:B0:52:00:00:01 Write MAC as module
  133. # eth0 00:B0:52:00:00:01 Written.
  134. # eth0 00:B0:52:00:00:01 Write PIB as module
  135. # eth0 00:B0:52:00:00:01 Written.
  136. # eth0 00:B0:52:00:00:01 Flash Device
  137. # eth0 00:B0:52:00:00:01 Flashed.
  138. DISCLAIMER
  139. Atheros HomePlug AV Vendor Specific Management Message structure and content is proprietary to Qualcomm Atheros, Ocala FL
  140. USA. Consequently, public information may not be available. Qualcomm Atheros reserves the right to modify message
  141. structure and content in future firmware releases without any obligation to notify or compensate users of this program.
  142. SEE ALSO
  143. plc(1), ampboot(1), chknvm(1), chkpib(1), int6k(1), modpib(1)
  144. CREDITS
  145. Charles Maier &lt;cmaier@qca.qualcomm.com&gt;
  146. open-plc-utils-0.0.3 Mar 2014 int6kboot(1)
  147. </pre>
  148. <div class='footerlink'>
  149. [<a href='int6kbaud.1.html' title=' int6kbaud.1 '>PREV</a>]
  150. [<a href='toolkit.html' title=' Index '>HOME</a>]
  151. [<a href='int6kdetect.1.html' title=' int6kdetect.1 '>NEXT</a>]
  152. </div>
  153. </body>
  154. </html>