首頁 探索 說明
登入
SoftwareDesign
/
csu3_am335x
8
0
複刻 0
Files 問題管理 0 合併請求 0 Wiki
分支: master
分支列表 標籤列表
csu3_am335x
/
EVSE
/
GPL
/
open-plc-utils-0.3
/
docbook
/
ch05s14.html

ch05s14.html 8.3 KB
永久連結 文件歷史 原始文件

1234567891011121314151617181920212223242526272829303132333435363738394041 
  1. <html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Trouble-shooting Problems</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="ch05.html" title="Chapter 5.  Procedures"><link rel="prev" href="ch05s13.html" title="Pairing UART Devices post PTS"><link rel="next" href="ch05s15.html" title="SLAC Configuration"></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. 			Trouble-shooting Problems 
    3. 

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

  4. 		Procedures 
    5. 

  5. 		</th><td width="20%" align="right"> <a accesskey="n" href="ch05s15.html">Next</a></td></tr></table><hr></div><div class="section" title="Trouble-shooting Problems"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="procedure-troubleshoot-problems"></a>
    6. 

  6. 			Trouble-shooting Problems 
    7. 

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

  8. 			The following steps may help determine why two devices cannot communicate via ethernet over the powerline.  They assume that you have successfully installed the Powerline Toolkit but are having trouble forming a powerline network.
    9. 

  9. 			</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p><a name="trouble-shoot-1"></a>
    10. 

  10. 					On <span class="application">Linux</span>, run program <span class="application">ifconfig</span> to determine available interface names as described <a class="link" href="ch05s02.html" title="Select an Interface on Linux">earlier</a>. The default interface name is <code class="constant">eth1</code> on Linux. You must use interface names, not numbers, on the Linux command line.
    11. 

  11. 					</p><p>
    12. 

  12. 					On <span class="application">Windows</span>, run program <a class="ulink" href="pcapdevs.7.html" target="_top">pcapdevs</a> to determine available interface numbers as described <a class="link" href="ch05s03.html" title="Select an Interface on Windows">earlier</a>. The default interface number is <code class="constant">2</code> on Windows. You must use interface numbers,  not names,  on Windows command lines, even under Cygwin.
    13. 

  13. 					</p><p>
    14. 

  14. 					In either case, <span class="application">Linux</span> or <span class="application">Windows</span>, if a powerline device is connected to any interface other than the default interface then you must specify the name or number on the command line each time you run <a class="ulink" href="int6k.7.html" target="_top">int6k</a>. In the following examples, we will use device numbers <code class="constant">3</code> and <code class="constant">4</code> to indicate two different interfaces on the same host.
    15. 

  15. 					</p></li><li class="listitem"><p><a name="trouble-shoot-2"></a>
    16. 

  16. 					Make sure both devices respond to <strong class="userinput"><code>int6k -ri3</code></strong> and <strong class="userinput"><code>int6k -ri4</code></strong> as described <a class="link" href="ch05s04.html#script-example-device-identification" title="Example 5.6.  Device Identification">earlier</a>. They should each display the software revision information. If you get no response then check your connections and network configuration. If you see <span class="quote">“<span class="quote">Bootloader</span>”</span> then the connection is good but the firmware is not running. If the firmware versions are different then make them the same.
    17. 

  17. 					</p><p>
    18. 

  18. 					You must have running firmware to continue and the firmware revisions should be the same.
    19. 

  19. 					</p></li><li class="listitem"><p><a name="trouble-shoot-3"></a>
    20. 

  20. 					Make sure both devices respond to <strong class="userinput"><code>int6k -Ii3</code></strong> then <strong class="userinput"><code>int6k -Ii4</code></strong> as described <a class="link" href="ch05s04.html#script-example-device-configuration" title="Example 5.7.  Inspecting Device Configuration">earlier</a>. They should display about 10 lines of information showing their <acronym class="acronym">MAC</acronym>, <acronym class="acronym">DAK</acronym> and <acronym class="acronym">NMK</acronym>.
    21. 

  21. 					</p><p>
    22. 

  22. 					If the <acronym class="acronym">MAC</acronym> is <code class="constant">00:B0:52:00:00:01</code> then either the default Atheros <acronym class="acronym">PIB</acronym> was stored in <acronym class="acronym">NVRAM</acronym> or you downloaded and flashed the generic Atheros <acronym class="acronym">PIB</acronym> without changing the <acronym class="acronym">MAC</acronym> address beforehand. 
    23. 

  23. 					</p><p>
    24. 

  24. 					If the <acronym class="acronym">MAC</acronym> is <code class="constant">00:B0:52:00:00:03</code> then either no <acronym class="acronym">PIB</acronym> was stored in <acronym class="acronym">NVRAM</acronym> or you downloaded and attempted to flashed an invalid <acronym class="acronym">PIB</acronym>. The firmware will disable powerline communications in this case.
    25. 

  25. 					</p></li><li class="listitem"><p><a name="trouble-shoot-4"></a>
    26. 

  26. 					If the devices have different <acronym class="acronym">NMK</acronym>s they will not form a network. 
    27. 

  27. 					</p><p>
    28. 

  28. 					One way to form a network is to manually set the <acronym class="acronym">NMK</acronym> on each device to a known value with <strong class="userinput"><code>int6k -Mi3</code></strong> then <strong class="userinput"><code>int6k -Mi4</code></strong>. Each device will reset afterwards and may reset again when the other device is changed. Repeat <a class="link" href="ch05s14.html#trouble-shoot-3">Step 3</a> and confirm that both devices have the same <acronym class="acronym">NMK</acronym> and that <span class="quote">“<span class="quote">(HomePlugAV)</span>”</span> appears next to the <acronym class="acronym">NMK</acronym>.
    29. 

  29. 					</p><p>
    30. 

  30. 					Another way to form a network is to physically press the push-button on each device for 2 to 3 seconds or simulate a push-button press on each device with <strong class="userinput"><code>int6k -B1 -i3</code></strong> then <strong class="userinput"><code>int6k -B1 -i4</code></strong>. The devices should reset several times and then form a network.
    31. 

  31. 					</p></li><li class="listitem"><p><a name="trouble-shoot-5"></a>
    32. 

  32. 					Make sure each device knows the other one is present on the network with <strong class="userinput"><code>int6k -mi3</code></strong> then <strong class="userinput"><code>int6k -Mi4</code></strong>. Each device should show that a network exists and identify the other device as a station on that network. It may take up to 120 seconds for one device to find another and up to 5 minutes to recognise that the other device has left the network.
    33. 

  33. 					</p></li><li class="listitem"><p><a name="trouble-shoot-6"></a>
    34. 

  34. 					<a class="link" href="ch05s14.html#trouble-shoot-5">Step 5</a> should also show the <acronym class="acronym">TX</acronym> and <acronym class="acronym">RX</acronym> <acronym class="acronym">PHY</acronym> rates for each device. <span class="application">Ping</span> each host Interface from the other several times to generate traffic. The <acronym class="acronym">PHY</acronym> Rates should then be non-zero. We use <a class="ulink" href="efsu.7.html" target="_top">efsu</a> to generate <a class="link" href="ch06s10.html" title="Generating Powerline Traffic">traffic</a> inside our own scripts. You may elect to use another method.
    35. 

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

  36. 					Power down both devices then power them up. Wait about 20 seconds and confirm that you can <span class="application">ping</span> in either direction.
    37. 

  37. 					</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="ch05s13.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch05.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch05s15.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">
    38. 

  38. 			Pairing UART Devices post PTS
    39. 

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

  40. 			SLAC Configuration
    41. 

  41. 			</td></tr></table></div></body></html>
    42.