Эхлэл Бүгдийг харах Тусламж
Нэвтрэх
SoftwareDesign
/
csu3_am335x
8
0
Салаа 0
Файлууд Асуудлууд 0 Хуулах хүсэлтүүд 0 Мэдлэгийн сан
Салаа: master
Салаанууд Тагууд
csu3_am335x
/
EVSE
/
GPL
/
open-plc-utils-0.3
/
docbook
/
ch04s13.html

ch04s13.html 10 KB
Байнгын холболт Түүх Анхны өгөгдөл

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071 
  1. <html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Boot from Host (INT6300)</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="ch04s12.html" title="Boot from Host (INT6000)"><link rel="next" href="ch04s14.html" title="Boot from Host (INT6400)"></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 (INT6300)
    3. 

  3. 			</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch04s12.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="ch04s14.html">Next</a></td></tr></table><hr></div><div class="section" title="Boot from Host (INT6300)"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="firmware-6300-boot"></a>
    6. 

  6. 			Boot from Host (INT6300)
    7. 

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

  8. 			The boot-from-host operation downloads <acronym class="acronym">SDRAM</acronym> configuration information, runtime parameters and runtime firmware from a local host and starts firmware execution. This method is initiated by the device bootloader after reset reset if the device has no flash memory, blank flash memory or corrupted flash memory. The method requires the bootloader aware software running on the local host to detect and service <code class="constant">VS_HOST_ACTION</code> messages from the device.
    9. 

  9. 			</p><p>
    10. 

  10. 			The <span class="productname">INT6300</span>™ boot-from-host method is similar to the <span class="productname">INT6000</span>™ method but it has an extra stage to download <acronym class="acronym">SDRAM</acronym> configuration parameters and it uses <code class="constant">VS_WR_MEM</code> messages to download runtime parameters and firmware instead of <code class="constant">VS_WR_MOD</code> messages. The <code class="constant">VS_WR_MEM</code> messages write directly to <acronym class="acronym">SDRAM</acronym> and an <code class="constant">VS_ST_MAC</code> message is needed to start firmware execution. Once the firmware is running, another method is used to write runtime parameters and firmware to flash memory.
    11. 

  11. 			</p><p>
    12. 

  12. 			The <span class="productname">INT6300</span>™ does not have a unique hardware address until runtime firmware starts and assigns one from the runtime parameter block. Until that time, the bootloader will accept 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.
    13. 

  13. 			</p><div class="figure"><a name="idp21427120"></a><p class="title"><b>Figure 4.5. 
    14. 

  14. 				boot-from-host (INT6300)
    15. 

  15. 				</b></p><div class="figure-contents"><pre class="programlisting">
    16. 

  16. 

  17.          INT6300                             LOCAL-HOST
    18. 

  18.         [01] |                                    |
    19. 

  19.         [02] |-------- VS_HOST_ACTION.IND -------&gt;| [03]
    20. 

  20.         [05] |&lt;------- VS_HOST_ACTION.RSP --------| [04]
    21. 

  21.              |                                    |
    22. 

  22.         [07] |&lt;------- VS_SET_SDRAM.REQ ----------| [06]
    23. 

  23.         [07] |-------- VS_SET_SDRAM.CNF ---------&gt;| [08]
    24. 

  24.              |                                    | [09]
    25. 

  25.         [10] |&lt;------- VS_WR_MEM.REQ -------------| [10]
    26. 

  26.         [10] |-------- VS_WR_MEM.CNF ------------&gt;| [10]
    27. 

  27.         [10] |&lt;-----------------------------------| [10]
    28. 

  28.         [10] |-----------------------------------&gt;| [10]
    29. 

  29.              |                                    |
    30. 

  30.         [11] |&lt;------- VS_WR_MEM.REQ -------------| [11]
    31. 

  31.         [11] |-------- VS_WR_MEM.CNF ------------&gt;| [11]
    32. 

  32.         [11] |&lt;-----------------------------------| [11]
    33. 

  33.         [11] |-----------------------------------&gt;| [11]
    34. 

  34.              |                                    |
    35. 

  35.         [13] |&lt;------- VS_ST_MAC.REQ -------------| [12]
    36. 

  36.         [14] |-------- VS_ST_MAC.CNF ------------&gt;| [15]
    37. 

  37. 

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

  39. 					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 further action is required. If it fails, for any reason, then the bootloader starts the boot-from-host process.
    40. 

  40. 					</p></li><li class="listitem"><p>
    41. 

  41. 					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 indicate that configuration is required. The destination address is <code class="constant">FF:FF:FF:FF:FF:FF</code> and the source address is <code class="constant">00:B0:52:00:00:01</code> as explained above. This message is sent every <code class="constant">10</code> seconds which differs from that of other chips. 
    42. 

  42. 					</p></li><li class="listitem"><p>
    43. 

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

  44. 					</p></li><li class="listitem"><p>
    45. 

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

  46. 					</p></li><li class="listitem"><p>
    47. 

  47. 					The bootloader receives the <code class="constant">VS_HOST_ACTION.RSP</code> from the host and inspects the MSTATUS field. On affirmative response, the bootloader stops broadcasting <code class="constant">VS_HOST_ACTION.IND</code> and waits indefinitely for <acronym class="acronym">SDRAM</acronym> configuration information from the host. 
    48. 

  48. 					</p></li><li class="listitem"><p>
    49. 

  49. 					The host sends a <code class="constant">VS_SET_SDRAM.REQ</code> message to the device containing an SDRAM configuration block and the block checksum. 
    50. 

  50. 					</p></li><li class="listitem"><p>
    51. 

  51. 					The bootloader receives the <code class="constant">VS_SET_SDRAM.REQ</code>, validates the content, initializes <acronym class="acronym">SDRAM</acronym> parameters and sends a <code class="constant">VS_SET_SDRAM.CNF</code> message to the servicing host to indicate either success or failure. 
    52. 

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

  53. 					The local host receives the <code class="constant">VS_SET_SDRAM.CNF</code> and inspects the <code class="varname">MSTATUS</code> field for success or failure. Assuming success, the local host waits indefinitely for further requests from the device. 
    54. 

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

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

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

  57. 					The local 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> messages from the device after each request. Each message contains an image segment, the memory offset, the segment length and the checksum used to monitor and manage download progress. It a single transaction fails, the local host should detect it and repeat it.
    58. 

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

  59. 					The local host downloads a 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 request. Each message contains an image segment,  the memory offset, the segment length and the checksum used to monitor and manage download progress. If a single transaction fails, the local host should detect it and repeat it. 
    60. 

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

  61. 					The local host starts firmware execution by sending a <code class="constant">VS_ST_MAC.REQ</code> message to the device. The message contains the firmware start address.  
    62. 

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

  63. 					The bootloader receives the <code class="constant">VS_ST_MAC.REQ</code> from the local host, validates the content.
    64. 

  64. 					</p></li><li class="listitem"><p>The device sends a <code class="constant">VS_ST_MAC.CNF</code> message to indicate an ability or willingness to start firmware execution. The device immediately starts firmware execution which relinquishes device control to the firmware. It can take <code class="constant">5</code> to <code class="constant">10</code> seconds for the firmware to start.  
    65. 

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

  66. 					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. An afffirmative indication means that the firmware will start executing on the device in <code class="constant">5</code> to <code class="constant">10</code> seconds. Once the firmware starts, future messages will contain the unique hardware address for the device.
    67. 

  67. 					</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="ch04s12.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="ch04s14.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">
    68. 

  68. 			Boot from Host (INT6000)
    69. 

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

  70. 			Boot from Host (INT6400)
    71. 

  71. 			</td></tr></table></div></body></html>
    72.