Microchip Technology DM163024 用户手册
PICDEM.net™ 2 Development Board User’s Guide
DS51623D-page 26
2011 Microchip Technology Inc.
4.
The PICDEM.net 2 Development Board will not communicate with the host
system.
system.
Verify that the correct Ethernet cable is being used (see Item 2, above).
Verify that the Ethernet cable is connected and undamaged.
Verify that the IP address as displayed on the LCD is used to communicate.
If the board fails when connected through a network device, verify that the device
is working properly. If it is, try connecting the host system directly to the Ethernet
board, as described in Chapter 2. “Getting Started with the PICDEM.net 2
Development Board”. Also, check that the proper cable is being used (see
above).
is working properly. If it is, try connecting the host system directly to the Ethernet
board, as described in Chapter 2. “Getting Started with the PICDEM.net 2
Development Board”. Also, check that the proper cable is being used (see
above).
Check TCP/IP connectivity with the ping command:
1.
Launch a DOS (or Command Prompt) window.
2.
Type ping x.x.x.x, where “x.x.x.x” is that of the Development Board.
If ping returns the message “Request timed out”, check the Activity LED on the
active Ethernet ICM:
active Ethernet ICM:
•
If the LED blinks during attempted communications, the IP addressing may be
wrong (i.e., the board and the host are not in the same subnet).
wrong (i.e., the board and the host are not in the same subnet).
•
If the LED does NOT blink, the Ethernet cable is defective, or the wrong type,
or the host system has not been properly configured for TCP/IP.
or the host system has not been properly configured for TCP/IP.
Verify the operation of the Ethernet card. In Microsoft
®
Windows
®
operating
systems, this is done through the System or Network applet in the Control Panel
(the exact applet and method of getting there varies from version to version).
Other operating systems may use different methods. Consult the documentation
for your operating system to get detailed information:
(the exact applet and method of getting there varies from version to version).
Other operating systems may use different methods. Consult the documentation
for your operating system to get detailed information:
Check the Development Board for power (see Issue 1, above).
If all else fails, reconfigure the Development Board’s network settings using the
default Ethernet ID and IP address. See Section 3.3 “Reprogramming and
Restoring the Application Firmware” for more information.
default Ethernet ID and IP address. See Section 3.3 “Reprogramming and
Restoring the Application Firmware” for more information.
5.
The host system communicates with the board, but the demo web site is
not present or does not function correctly.
not present or does not function correctly.
If the external serial data EEPROM is blank or absent, any attempt to access the
demo web site will result in the message, “File Not Found”. If this message
appears, reload the web pages to the EEPROM as described in the Microchip
TCP/IP Stack Help.
demo web site will result in the message, “File Not Found”. If this message
appears, reload the web pages to the EEPROM as described in the Microchip
TCP/IP Stack Help.
If the web page display is “broken” (disjointed display, error messages
displayed), use your browser’s “Reload” command to refresh the page. If the
page is still broken, reload the EEPROM as described in the Microchip TCP/IP
Stack Help.
displayed), use your browser’s “Reload” command to refresh the page. If the
page is still broken, reload the EEPROM as described in the Microchip TCP/IP
Stack Help.
6.
The board will not communicate with the host system after changing the IP
address and/or Ethernet ID.
address and/or Ethernet ID.
Check the Development Board and host system as in Issue 4, above.
Verify that the host system is set up correctly.
Clear the host system’s ARP cache. For Windows operating systems, open a
Command window, type arp -d * and hit <ENTER>.
Command window, type arp -d * and hit <ENTER>.
If these steps don’t work, restore the Development Board’s default network
configuration to see if communications can be re-established. See
Section 3.3 “Reprogramming and Restoring the Application Firmware” for
more information.
configuration to see if communications can be re-established. See
Section 3.3 “Reprogramming and Restoring the Application Firmware” for
more information.