Home Esplora Aiuto
Accedi
SoftwareDesign
/
csu3_am335x
8
0
Forka 0
File Problemi 0 Pull Requests 0 Wiki
Ramo (Branch): master
Rami (Branch) Tag
csu3_am335x
/
EVSE
/
GPL
/
open-plc-utils-0.3
/
docbook
/
ch04s11.html

ch04s11.html 6.6 KB
Permalink Cronologia Originale

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

  3. 			</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch04s10.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="ch04s12.html">Next</a></td></tr></table><hr></div><div class="section" title="Update Local Host (INT6000/INT6300/INT6400)"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="firmware-6000-upload"></a>
    6. 

  6. 			Update Local Host (INT6000/INT6300/INT6400)
    7. 

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

  8. 			The Update Local Host operation transfers a firmware image and/or <acronym class="acronym">PIB</acronym> image from the device to the local host for permanent storage. After the firmware and <acronym class="acronym">PIB</acronym> are stored, the local host will reset the device and the device will retrieve parameters and firmware using the <a class="link" href="ch04s12.html" title="Boot from Host (INT6000)">Boot from Host</a> operation described in the next section.
    9. 

  9. 			</p><p>
    10. 

  10. 			The firmware may initiate this operation after a remote host has downloaded new firmware or <acronym class="acronym">PIB</acronym> and issued a <code class="constant">VS_MOD_NVM.REQ</code> to the device,  the device has been asked to restore factory default settings or the firmware has dynamically altered the runtime <acronym class="acronym">PIB</acronym> in some way. Consequently, the device will be reset by the host in each case.
    11. 

  11. 			</p><p>
    12. 

  12. 			The device initiates this operation to complete an Upgrade Device operation when the device has no dedicated flash memory onboard. This operation requires running Atheros firmware on the device and custom software on the local host.
    13. 

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

  14. 				Update Local Host (INT6000/INT6300/INT6400)
    15. 

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

  16. 

  17.       INT6300/INT6400                           LOCAL-HOST
    18. 

  18.         [01] |-------- VS_HOST_ACTION.IND -------&gt;| [01]
    19. 

  19.         [03] |&lt;------- VS_HOST_ACTION.RSP --------| [02]
    20. 

  20.              |                                    |
    21. 

  21.         [04] |&lt;------- VS_RD_MOD.REQ -------------| [04]
    22. 

  22.         [04] |-------- VS_RD_MOD.CNF ------------&gt;| [04]
    23. 

  23.         [04] |&lt;-----------------------------------| [04]
    24. 

  24.         [04] |-----------------------------------&gt;| [04]
    25. 

  25.              |                                    |
    26. 

  26.         [05] |&lt;------- VS_RD_MOD.REQ -------------| [05]
    27. 

  27.         [05] |-------- VS_RD_MOD.CNF ------------&gt;| [05]
    28. 

  28.         [05] |&lt;-----------------------------------| [05]
    29. 

  29.         [05] |-----------------------------------&gt;| [05]
    30. 

  30.              |                                    |
    31. 

  31.         [06] |&lt;------- VS_RS_DEV.REQ -------------| [06]
    32. 

  32.         [07] |-------- VS_RS_DEV.CNF ------------&gt;| [07]
    33. 

  33. 

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

  35. 					The runtime firmware initiates this operation by broadcasting <code class="constant">VS_HOST_ACTION.IND</code> messages every 500 milliseconds. The <code class="constant">HOST_ACTION_REQ</code> field of the message can be either <code class="constant">0x01</code>, <code class="constant">0x02</code> or <code class="constant">0x03</code> to indicate that a firmware image, a parameter block image or both are ready for upload by the local host. 
    36. 

  36. 					</p></li><li class="listitem"><p>
    37. 

  37. 					The local host sends a <code class="constant">VS_HOST_ACTION.RSP</code> message to the device to indicate the ability and willingness to upload the information. 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. 
    38. 

  38. 					</p></li><li class="listitem"><p>
    39. 

  39. 					Assuming an affirmative response, the device stops broadcasting and will wait indefinitely for local host action. 
    40. 

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

  41. 					Optionally, the local host reads the firmware image from the device by sending a series of VS_RD_MOD.REQ messages to the device and waiting for a <code class="constant">VS_RD_MOD.CNF</code> message after each one. The message <code class="varname">MODULEID</code> field is set to <code class="constant">0x01</code> for this operation. 
    42. 

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

  43. 					Optionally, the local host reads the <acronym class="acronym">PIB</acronym> from the device by sending a series of <code class="constant">VS_RD_MOD.REQ</code> messages to the device and waiting for a <code class="constant">VS_RD_MOD.CNF</code> message after each one. The message <code class="varname">MODULEID</code> field is set to <code class="constant">0x02</code> for this operation. 
    44. 

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

  45. 					The local host sends a <code class="constant">VS_RS_DEV.REQ</code> message to the device to initiate a firmware reboot. 
    46. 

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

  47. 					The device sends a <code class="constant">VS_RS_DEV.CNF</code> to the host and performs a software reset. This forces a <a class="link" href="ch04s12.html" title="Boot from Host (INT6000)">Boot from Host</a>.
    48. 

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

  49.             Upgrade Device (INT6000/INT6300/INT6400)
    50. 

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

  51. 			Boot from Host (INT6000)
    52. 

  52. 			</td></tr></table></div></body></html>
    53.