Página inicial Explorar Ajuda
Entrar
SoftwareDesign
/
csu3_am335x
8
0
Fork 0
Arquivos Issues 0 Pull Requests 0 Wiki
Branch: master
Branches Tags
csu3_am335x
/
EVSE
/
GPL
/
open-plc-utils-0.3
/
docbook
/
ch04s14.html

ch04s14.html 14 KB
Link permanente Histórico Raw

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101 
  1. <html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Boot from Host (INT6400)</title><meta name="generator" content="DocBook XSL Stylesheets V1.76.1"><meta name="keywords" content="Intellon, Atheros, Qualcomm, HomePlug, powerline, communications, INT6000, INT6300, INT6400, AR7400, AR7420"><link rel="home" href="index.html" title="Qualcomm Atheros Open Powerline Toolkit"><link rel="up" href="ch04.html" title="Chapter 4.  Firmware"><link rel="prev" href="ch04s13.html" title="Boot from Host (INT6300)"><link rel="next" href="ch04s15.html" title="Boot from Host (AR7400)"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">
    2. 

  2. 			Boot from Host (INT6400)
    3. 

  3. 			</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch04s13.html">Prev</a> </td><th width="60%" align="center">Chapter 4. 
    4. 

  4. 		Firmware 
    5. 

  5. 		</th><td width="20%" align="right"> <a accesskey="n" href="ch04s15.html">Next</a></td></tr></table><hr></div><div class="section" title="Boot from Host (INT6400)"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="firmware-6400-boot"></a>
    6. 

  6. 			Boot from Host (INT6400)
    7. 

  7. 			</h2></div></div></div><p>
    8. 

  8. 			The <span class="productname">INT6400</span>™ boot-from-host operation downloads and executes a memory configuration applet then downloads runtime parameters and firmware from a local host and starts firmware execution. This method is initiated by the <span class="productname">INT6400</span>™ bootloader after reset on a device having no flash memory, blank flash memory or corrupted flash memory. The method requires bootloader aware software running on the local host in order to complete.
    9. 

  9. 			</p><p>
    10. 

  10. 			The <span class="productname">INT6400</span>™ boot-from-host method is similar to the <span class="productname">INT6300</span>™ boot-from-host method but it downloads and executes an SDRAM configuration applet instead of downloading SDRAM parameters. The applet is downloaded and executed using the same mechanism as runtime firmware. The applet executes and returns to the bootloader when done. The bootloader then continues to drive the boot process using <code class="varname">VS_HOST_ACTION</code> messages.
    11. 

  11. 			</p><p>
    12. 

  12. 			The <span class="productname">INT6400</span>™ boot-from-host method will work for <span class="productname">AR7400</span>™ and <span class="productname">QCA7420</span>™ chipsets but will not work on successive chipsets. Customers should adopt or implement the <span class="productname">AR7400</span>™ boot-from-host method, instead of this one, to avoid building obsolete products.
    13. 

  13. 			</p><p>
    14. 

  14. 			The <span class="productname">INT6400</span>™ does not have a unique hardware address until the firmware starts and assigns one from the parameter information block. Until that time, the bootloader will only acknowledge messages addressed to <code class="constant">00:B0:52:00:00:01</code>. In addition, the bootloader does not know the hardware address of the local host and so it addresses <code class="constant">VS_HOST_ACTION</code> messages to <code class="constant">FF:FF:FF:FF:FF:FF</code>; however, these messages are not transmitted over the powerline.
    15. 

  15. 			</p><div class="figure"><a name="idp21524656"></a><p class="title"><b>Figure 4.6. 
    16. 

  16. 				Boot from Host (INT6400)
    17. 

  17. 				</b></p><div class="figure-contents"><pre class="programlisting">
    18. 

  18. 

  19.           INT6400                            LOCAL-HOST
    20. 

  20.         [01] |                                    |
    21. 

  21.         [02] |-------- VS_HOST_ACTION.IND -------&gt;| [03]
    22. 

  22.         [05] |&lt;------- VS_HOST_ACTION.RSP --------| [04]
    23. 

  23.              |                                    |
    24. 

  24.         [06] |&lt;------- VS_WR_MEM.REQ -------------| [06]
    25. 

  25.         [06] |-------- VS_WR_MEM.CNF ------------&gt;| [06]
    26. 

  26.         [06] |&lt;-----------------------------------| [06]
    27. 

  27.         [06] |-----------------------------------&gt;| [06]
    28. 

  28.              |                                    |
    29. 

  29.         [08] |&lt;------- VS_ST_MAC.REQ -------------| [07]
    30. 

  30.         [09] |-------- VS_ST_MAC.CNF ------------&gt;| [10]
    31. 

  31.         [11] |                                    |
    32. 

  32.         [12] |-------- VS_HOST_ACTION.IND -------&gt;| [13]
    33. 

  33.         [15] |&lt;------- VS_HOST_ACTION.RSP --------| [14]
    34. 

  34.              |                                    |
    35. 

  35.              |                                    | [16]
    36. 

  36.              |                                    |
    37. 

  37.         [17] |&lt;------- VS_WR_MEM.REQ -------------| [17]
    38. 

  38.         [17] |-------- VS_WR_MEM.CNF ------------&gt;| [17]
    39. 

  39.         [17] |&lt;-----------------------------------| [17]
    40. 

  40.         [17] |-----------------------------------&gt;| [17]
    41. 

  41.              |                                    |
    42. 

  42.         [18] |&lt;------- VS_WR_MEM.REQ -------------| [18]
    43. 

  43.         [18] |-------- VS_WR_MEM.CNF ------------&gt;| [18]
    44. 

  44.         [18] |&lt;-----------------------------------| [18]
    45. 

  45.         [18] |-----------------------------------&gt;| [18]
    46. 

  46.              |                                    |
    47. 

  47.         [20] |&lt;------- VS_ST_MAC.REQ -------------| [19]
    48. 

  48.         [21] |-------- VS_ST_MAC.CNF ------------&gt;| [22]
    49. 

  49. 

  50.  </pre></div></div><br class="figure-break"><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>
    51. 

  51. 					The bootloader automatically starts after device reset and attempts to read the runtime firmware image from flash memory, write it into <acronym class="acronym">SDRAM</acronym> and start execution. If it succeeds then normal operation begins and no futher action is required. If it fails, for any reason, then the bootloader initiates the boot-from-host sequence.
    52. 

  52. 					</p></li><li class="listitem"><p>
    53. 

  53. 					The bootloader broadcasts <code class="constant">VS_HOST_ACTION.IND</code> with <code class="varname">HOST_ACTION_REQ</code> set to <code class="constant">0x04</code> to request configuration. The destination address is <code class="constant">FF:FF:FF:FF:FF:FF</code> and source address is <code class="constant">00:B0:52:00:00:01</code> as explained above. This message is sent every <code class="constant">500</code> milliseconds which differs from that of other chips.
    54. 

  54. 					</p></li><li class="listitem"><p>
    55. 

  55. 					The local host receives the <code class="constant">VS_HOST_ACTION.IND</code> message and inspects the <code class="varname">HOST_ACTION_REQ</code> field to determine the appropriate action. On a single-host system, the lone host must service the request or the device will not start. On a multi-host system, one host must elect to service the request of the device will not start.
    56. 

  56. 					</p></li><li class="listitem"><p>
    57. 

  57. 					The local host sends <code class="constant">VS_HOST_ACTION.RSP</code> to silence the bootloader or indicate the ability and willingness to service the request. The destination address must be <code class="constant">00:B0:52:00:00:01</code> and the source address is that of the host interface. The <code class="varname">MSTATUS</code> field is set to <code class="constant">0x00</code> for affirmative and <code class="constant">0x01</code> for negative. 
    58. 

  58. 					</p></li><li class="listitem"><p>
    59. 

  59. 					The bootloader receives the <code class="constant">VS_HOST_ACTION.RSP</code> from the host and inspects the <code class="varname">MSTATUS</code> field. On affirmative response, the bootloader stops broadcasting <code class="constant">VS_HOST_ACTION.IND</code> messages and waits indefinitely for the local host to download a configuation applet and start execution. 
    60. 

  60. 					</p></li><li class="listitem"><p>
    61. 

  61. 					The host downloads the memory control applet to the device by sending <code class="constant">VS_WR_MEM.REQ</code> messages to the device and waiting for a <code class="constant">VS_WR_MEM.CNF</code> message from the device after each one. Each message contains an image segment and the segment memory offset, length and checksum. These values are used to monitor and manage download progress. If a transaction fails, the host can detect it and should repeat it.
    62. 

  62. 					</p></li><li class="listitem"><p>
    63. 

  63. 					The host starts execution of the memory control applet by sending a <code class="constant">VS_ST_MAC.REQ</code> message to the device. The message contains the applet load address, length, checksum and start address. These values are often obtained from an NVM file image header.
    64. 

  64. 

  65. 					</p></li><li class="listitem"><p>
    66. 

  66. 					The bootloader receives the <code class="constant">VS_ST_MAC.REQ</code> from the host and validates the contents.					
    67. 

  67. 					</p></li><li class="listitem"><p>
    68. 

  68. 					The bootloader sends a <code class="constant">VS_ST_MAC.CNF</code> message to the host indicating the ability and willingness to start applet execution. The <code class="varname">MSTATUS</code> field is set to <code class="constant">0x00</code> for affirmative and <code class="constant">0x01</code> for negative.
    69. 

  69. 					</p></li><li class="listitem"><p>
    70. 

  70. 					The host receives the <code class="constant">VS_ST_MAC.CNF</code> message from the device and evaluates the <code class="varname">MSTATUS</code> field. On affirmative,  the host waits for further requests from the device. On negative,  the host may attempt another start or another download followed by a start or attempt to alert a human.
    71. 

  71. 					</p></li><li class="listitem"><p>
    72. 

  72.  					The bootloader starts applet execution. The applet configures memory, runs to completion and returns to the Bootloader.		
    73. 

  73. 					</p></li><li class="listitem"><p>
    74. 

  74. 					The bootloader broadcasts a <code class="constant">VS_HOST_ACTION.IND</code> message every 500 milliseconds to request runtime firmware and parameter download. The message destination address is <code class="constant">FF:FF:FF:FF:FF:FF</code> and source address is <code class="constant">00:B0:52:00:00:01</code> as explained above. The <code class="varname">HOST_ACTION_REQ</code> field is set to <code class="constant">0x00</code>. 
    75. 

  75. 					</p></li><li class="listitem"><p>
    76. 

  76. 					The host receives the <code class="constant">VS_HOST_ACTION.IND</code> message and inspects the <code class="varname">HOST_ACTION_REQ</code> field to determine the requested action. On a single-host system,  the lone host must service the request or the device will not start. On a multi-host system, one host must elect to service the request of the device will not start.
    77. 

  77. 					</p></li><li class="listitem"><p>
    78. 

  78. 					The host sends a <code class="constant">VS_HOST_ACTION.RSP</code> message to the device to indicate the ability and willingness to service the request. The <code class="varname">MSTATUS</code> field is set to <code class="constant">0x00</code> for affirmative and <code class="constant">0x01</code> for negative. 
    79. 

  79. 					</p></li><li class="listitem"><p>
    80. 

  80. 					The bootloader receives the <code class="constant">VS_HOST_ACTION.RSP</code> from the host and inspects the <code class="varname">MSTATUS</code> field. On affirmative response, the bootloader stops broadcasting <code class="constant">VS_HOST_ACTION.IND</code> messages and waits indefinitely for the host to download the runtime firmware and parameters and start execution. 
    81. 

  81. 					</p></li><li class="listitem"><p>
    82. 

  82. 					The host determines which firmware and parameter image to download. In some cases there may be no choice. In other cases, there may be a choice between default and custom images or between current and upgraded images. This is a principle design issue to consider. 
    83. 

  83. 					</p></li><li class="listitem"><p>
    84. 

  84. 					The host downloads the firmware image to the device by sending <code class="constant">VS_WR_MEM.REQ</code> messages to the device and waiting for a <code class="constant">VS_WR_MEM.CNF</code> message from the device after each one. Each message contains an image segment and the segment memory offset, length and checksum. These values are used to monitor and manage download progress. If a transaction fails, the local host can detect it and should repeat it.
    85. 

  85. 					</p></li><li class="listitem"><p>
    86. 

  86. 					The host downloads the parameter block to the device by sending <code class="constant">VS_WR_MEM.REQ</code> messages to the device and waiting for a <code class="constant">VS_WR_MEM.CNF</code> message from the device after each one. Each message contains an image segment and the segment memory offset, length and checksum. These values are used to monitor and manage download progress. If a transaction fails, the local host can detect it and should repeat it. 
    87. 

  87. 					</p></li><li class="listitem"><p>
    88. 

  88. 					The host starts runtime firmware execution by sending a <code class="constant">VS_ST_MAC.REQ</code> message to the device. The message contains the firmware load address, length, checksum and start address. These values are often obtained from an NVM file image header.
    89. 

  89. 					</p></li><li class="listitem"><p>
    90. 

  90. 					The bootloader receives the <code class="constant">VS_ST_MAC.REQ</code> from the host and validates the content.
    91. 

  91. 					</p></li><li class="listitem"><p>
    92. 

  92. 					The bootloader sends a <code class="constant">VS_ST_MAC.CNF</code> message to indicate the ability or willingness to start firmware execution.   
    93. 

  93. 					</p></li><li class="listitem"><p>
    94. 

  94. 					The host receives the <code class="constant">VS_ST_MAC.CNF</code> message from the device, inspects the <code class="varname">MSTATUS</code> field and acts accordingly. 
    95. 

  95. 					</p></li><li class="listitem"><p>
    96. 

  96.  					The bootloader starts runtime firmware execution. The firmware reads and validates the parameter block then assumes full control of the device. It can take several seconds for firmware start to be evident. Once the firmware starts,  any future <code class="constant">VS_HOST_ACTION</code> messages will contain the unique hardware address for the device.
    97. 

  97. 					</p></li></ol></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch04s13.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch04.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch04s15.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">
    98. 

  98. 			Boot from Host (INT6300)
    99. 

  99. 			 </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 
    100. 

  100. 			Boot from Host (AR7400)
    101. 

  101. 			</td></tr></table></div></body></html>
    102.