Ethernet Module

From OpenCircuits
(Difference between revisions)
Jump to: navigation, search
(add an internet link)
(update internal links)
 
(2 intermediate revisions by 2 users not shown)
Line 6: Line 6:
 
Since a full-scale TCP/IP stack consumes a large amount of memory and processing power, a number of small footprint TCP/IP stacks have been devised for embedded systems, such as uIP and lwIP. Nevertheless, these TCP/IP stacks are usually not compatible to socket programming, and being implemented by software, still consumes a considerable amount of system resources. Therefore, hardware chips that implemented the TCP/IP stack (e.g. [http://www.wiznet.co.kr/en/pro02.php?&page=1&num=26 WIZNET W5300]) emerged in recent years so as to offload the computation power from the host microcontroller unit (MCU).
 
Since a full-scale TCP/IP stack consumes a large amount of memory and processing power, a number of small footprint TCP/IP stacks have been devised for embedded systems, such as uIP and lwIP. Nevertheless, these TCP/IP stacks are usually not compatible to socket programming, and being implemented by software, still consumes a considerable amount of system resources. Therefore, hardware chips that implemented the TCP/IP stack (e.g. [http://www.wiznet.co.kr/en/pro02.php?&page=1&num=26 WIZNET W5300]) emerged in recent years so as to offload the computation power from the host microcontroller unit (MCU).
  
This project aims to devise a driver and Linux socket wrapper inside freertos_posix for a hardware implemented TCP/IP stack. It is to be used in conjunction with a 8/16 bits embedded system such as (but not restricted to) the [http://opencircuits.com/DsPIC30F_5011_Development_Board dsPic33F development board]. Based on the Linux socket API, common application protocols (DHCP/HTTP/DNS/SMTP/SNMP/TELNET) are devised to enable remote control and monitoring.
+
This project aims to devise a driver and Linux socket wrapper inside freertos_posix for a hardware implemented TCP/IP stack. It is to be used in conjunction with a 8/16 bits embedded system such as (but not restricted to) the [[DsPIC30F_5011_Development_Board | dsPic33F development board]]. Based on the Linux socket API, common application protocols (DHCP/HTTP/DNS/SMTP/SNMP/TELNET) are devised to enable remote control and monitoring.
  
 
===Benefits===
 
===Benefits===
Line 23: Line 23:
  
  
==Architecture==
+
==Development==
*See [http://www.opencircuits.com/Multi-purpose_Embedded_System#TCP.2FIP_Stack here] for block diagram
+
*[[Ethernet Module Development]]
  
  
==Development Roadmap==
+
==User Guide==
===Phase 1===
+
*[[Ethernet Module User's Guide]]
*Select chips and draw schematic and pcb
+
*Obtain samples for chip
+
 
+
===Phase 2===
+
*Device driver
+
*Create a Linux socket API wrapper in freertos_posix
+
 
+
===Phase 3===
+
*Reference to Linux socket/lwip, create libraries for
+
**DHCP client
+
**HTTP server
+
***Decide how to get files (html, css, cgi, etc) from nvm (with/without file system)
+
***Decide an efficient means to create and download web page to nvm
+
**DNS resolver
+
**SMTP mail client
+
**SNMP agent
+
**TELNET application
+
 
+
===Phase 4===
+
*Explore wireless-bridge solutions
+
**[http://www.wiznet.co.kr/en/pro02.php?&page=1&num=180 WIZ610wi]
+
**[http://ftp1.digi.com/support/documentation/productmanual_xstream_oem_rfmodule_v5.x00.pdf XStream OEM RF Module]
+
 
+
 
+
==Network Configuration==
+
Our Ethernet products (units) can be controlled by a PC using the TCP-IP protocol. The PC and the units can be setup using one of three topologies:
+
#Direct Connection;
+
#Intranet Connection;
+
#Internet Connection.
+
===Direct Connection===
+
An example showing how to connect a PC and a unit directly is shown in Fig. 1. In this topology, the unit can be connected with the PC simply using a direct Ethernet cable. Please ensure that the PC and the unit share the same subnet mask and gateway, but different IP addresses. An incorrect example is shown in Fig. 2. Under direct connection, the user has to set these network configurations manually.
+
:[[Image:correct_network_setting.png]]
+
:[[Image:incorrect_network_setting.png]]
+
To set the network configuration on the unit, the user has to select the Static mode. The default IP addresses, subnet mask, and gateway are 192.168.1.128, 255.255.255.0 and 192.168.1.1 respectively. These settings can only be changed when the Ethernet status is Down. Once they have been changed, the values will be automatically saved.
+
 
+
'''To configure the network settings on the PC, '''
+
*Goto '''<Start>''' and '''<Control Panel>''', open '''<Network Connections>'''
+
:[[Image:Nict_networksetting11.png]]
+
*Select the Local Area Connection corresponding to the network card on your PC. Right click and select '''<Properties>'''
+
:[[Image:Nict_networksetting12.png]]
+
*Under '''<General>''' tab, scroll down to '''<Internet Protocol (TCP/IP)>'''and click '''<Properties>'''
+
:[[Image:Nict_networksetting13.png]]
+
*Select '''<Use the following IP address:>''' and enter the appropriate network settings. Please ensure that the IP address is different from the one used by the unit.
+
:[[Image:Nict_networksetting14.png]]
+
 
+
===Intranet Connection===
+
An example showing how to connect a PC and 3 units in an intranet is shown in Fig. 3. In this topology, the PC and the units can be plugged into the network sockets directly or through a hub. The units can obtain IP addresses either dynamically by DHCP or statically by assignment.
+
:[[Image:Nict_networksetting_intranet.png]]
+
In a network supporting DHCP, the IP address, subnet mask and gateway can be configured automatically if DHCP mode is selected. If the unit cannot acquired a valid connection via DHCP, the IP address, subnet mask and gateway will be displayed as 0.0.0.0. Please consult your network administrator whether your network supports DHCP.
+
 
+
In Static mode, the user has to configure the IP address, subnet mask and gateway manually. These settings can only be changed when the Ethernet status is Down. The default settings are 192.168.1.128, 255.255.255.0 and 192.168.1.1 respectively. Please note that a logical network cannot accommodate two units with the same IP address, so you should consult your network administrator before using the Static mode. The network administrator will give you the appropriate settings.
+
===Internet Connection===
+
An example showing how to connect a PC and a unit (Unit 4) in the Internet is shown in Fig. 4. Similar to the intranet topology, the PC and the units can also be plugged into the network sockets directly or through a hub. The units can also obtain IP addresses either dynamically by DHCP or statically by assignment.
+
:[[Image:Nict_networksetting_internet.png]]
+
Network configuration on the unit is identical to that described in [{{SERVER}}/Ethernet_Module#Intranet_Connection intranet connection]. Note that the IP address displayed on the unit is the local IP address. To remote access a unit under Internet connection, the PC needs to know the global IP address of the unit. Please consult your network administrator of the corresponding gl
+
 
+
 
+
==Software TCP/IP Stack Solution==
+
===Circuit and PCB===
+
*In [http://chungyan5.no-ip.org/vc/?root=ethernet gEDA format] and its gEDA [http://www.opencircuits.com/PCB_Footprints#gEDA_Symbols_and_footprints sym and footprints]
+
{|border="1" cellspacing="0" cellpadding="5"
+
! Special Item !! Description !! Quantity
+
|-valign="top"
+
| [http://www.davicom.com.tw/userfile/24247/DM9000A-DS-F01-101906.pdf DM9000AEP] || Ethernet Controller from [http://www.davicom.com.tw/ Davicom] || 1
+
|-
+
| [http://www.hanrun.com/hr/upfile/2_1_113.pdf HR911102A] || RJ45 Connector with Integrated Magnetics for 10/100 Base-TX  || 1
+
|-
+
| [http://ww1.microchip.com/downloads/en/DeviceDoc/21749F.pdf 93LC46B-I/SN] || 1K Serial EEPROM  || 1 (Optional)
+
|-
+
| 25MHz Crystal || Crystal || 1
+
|-
+
| 22pF || For Crystal Use || 2
+
|-
+
| 220uF || For RXVDD25/TXVDD25  || 1
+
|-
+
| 49.9ohm || For RX+/RX-/TX+/TX- || 4
+
|-
+
| 6.8kohm || For BGRES/BGGND || 1
+
|-
+
| 510ohm || For LEDs|| 2
+
|-
+
|}
+
*[http://www.davicom.com.tw/eng/products/dm9000a.htm DM9000A Description]
+
*[http://www.davicom.com.tw/big5/download/Data%20Sheet/DM9000A-DS-F01-101906.pdf DM9000A Datasheet]
+
*[http://www.davicom.com.tw/big5/download/AC/dm9000a/DM9000A%20circuit_EMI_052306.pdf Application Circuit]
+
*[http://www.davicom.com.tw/big5/download/LayoutGuide/DM9000A_9010-LG-V11_031706.pdf Layout Guidelines]
+
*[http://www.davicom.com.tw/big5/download/ApplicationNote/DM9000A%20Application%20Notes%20Ver%201_20_101906.pdf Application Note]
+
*[http://www.davicom.com.tw/eng/download/Driver/driver_9000.htm DM9000A Official Drivers]
+
 
+
 
+
===Software Implementation===
+
====Driver====
+
*Download [http://chungyan5.no-ip.org/vc/trunk/demo_posix/dspic/drivers/?root=freertos_posix dm9000a.c]
+
*Download [http://chungyan5.no-ip.org/vc/trunk/demo_posix/dspic/drivers/include/?root=freertos_posix dm9000a.h]
+
*Base on [http://www.freertos.org/ FreeRTOS] and [http://opencircuits.com/DsPIC30F_5011_Development_Board dsPIC33 platform]
+
*Using POSIX-like API:
+
**'''int dmfe_open(int flags)''': initialize the Ethernet controller for 10MHz Half-Duplex
+
**'''int dmfe_close()''': turn off the PHY layer
+
**'''int dmfe_read(void)''': copy a packet to the default buffer
+
**'''int dmfe_write(unsigned char device, unsigned char *buf, int count)''': copy count bytes of the data from buf and transmit
+
**'''void dmfe_interrupt(void)''': process the transmit interrupt from DM9000A
+
 
+
====[[uIP]]====
+
*Light-weight TCP/IP stack designed for 8-bit/16-bit embedded systems
+
 
+
====[[lwIP]]====
+
*Light-weight TCP/IP stack designed for 8-bit/16-bit embedded systems
+
*Consume more resource than uIP
+
 
+
 
+
==Hardware TCP/IP Stack Solution==
+
 
+
===Circuit and PCB===
+
*[http://www.wiznet.co.kr/en/pro02.php?&page=1&num=26 WIZNET W5300]
+
 
+
  
 
[[category:projects]]
 
[[category:projects]]

Latest revision as of 02:59, 4 August 2009

This project aims to develop an Ethernet Module, to be used in conjunction with a 8/16 bits embedded system such as the dsPic33F development board.

Contents

[edit] Objectives

The Internet provides an indispensable means to exchange information over long distances. Connection to the Internet is enabled by following the implementation of the Open Systems Interconnection Reference Model (OSI model). In simple words, internet applications require a TCP/IP stack to pack and unpack information into data packets for proper transmission and reception over the Internet. The TCP/IP stack is usually implemented by software and included in the Operating System. Applications can use the stack transparently through socket programming.

Since a full-scale TCP/IP stack consumes a large amount of memory and processing power, a number of small footprint TCP/IP stacks have been devised for embedded systems, such as uIP and lwIP. Nevertheless, these TCP/IP stacks are usually not compatible to socket programming, and being implemented by software, still consumes a considerable amount of system resources. Therefore, hardware chips that implemented the TCP/IP stack (e.g. WIZNET W5300) emerged in recent years so as to offload the computation power from the host microcontroller unit (MCU).

This project aims to devise a driver and Linux socket wrapper inside freertos_posix for a hardware implemented TCP/IP stack. It is to be used in conjunction with a 8/16 bits embedded system such as (but not restricted to) the dsPic33F development board. Based on the Linux socket API, common application protocols (DHCP/HTTP/DNS/SMTP/SNMP/TELNET) are devised to enable remote control and monitoring.

[edit] Benefits

  • Provide a means to perform remote control and monitoring via Internet
  • Offload TCP/IP stack to chip, freeing memory and processing power of MCU to perform other tasks (e.g. HTTPS)
  • Socket API implementation allows more extensible framework for future development and upgrades
  • Enable remote control and monitoring via
    • Web browser on desktop computer (better web page design and implementation)
    • SNMP agents, controlling and monitoring several instruments simultaneously
    • TELNET applications for command prompt control and monitoring
    • SMTP by sending out email when critical events occur

[edit] Limitations

  • Higher cost chips compare to software stack
  • Need to change hardware if features in stack are updated


[edit] Development


[edit] User Guide

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox