Difference between revisions of "Ethernet Module"

From OpenCircuits
Jump to navigation Jump to search
(update internal links)
 
(10 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
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.
 +
 
==Objectives==
 
==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.
 
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.
Line 4: 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===
*provide a means to perform remote control and monitoring via Internet
+
*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)
+
*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
+
*Socket API implementation allows more extensible framework for future development and upgrades
*enable remote control and monitoring via
+
*Enable remote control and monitoring via
**web browser on desktop computer (better web page design and implementation)
+
**Web browser on desktop computer (better web page design and implementation)
 
**SNMP agents, controlling and monitoring several instruments simultaneously
 
**SNMP agents, controlling and monitoring several instruments simultaneously
 
**TELNET applications for command prompt control and monitoring
 
**TELNET applications for command prompt control and monitoring
Line 17: Line 19:
  
 
===Limitations===
 
===Limitations===
*higher cost chips compare to software stack
+
*Higher cost chips compare to software stack
*need to change hardware if features in stack are updated
+
*Need to change hardware if features in stack are updated
 
 
 
 
==Architecture==
 
*See [http://www.opencircuits.com/Multi-purpose_Embedded_System#TCP.2FIP_Stack here] for block diagram
 
 
 
 
 
==[[Development Roadmap]]==
 
*Contains directions for development
 
 
 
 
 
==Connection Schemes==
 
[[Image:Connection_schemes.png ]]
 
[[Image:connection_schemes_withdhcp.png]]
 
 
 
 
 
==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]]===
+
==Development==
*Light-weight TCP/IP stack designed for 8-bit/16-bit embedded systems
+
*[[Ethernet Module Development]]
*consume more resource than uIP
 
  
  
==Hardware TCP/IP Stack Solution==
+
==User Guide==
 +
*[[Ethernet Module User's Guide]]
  
===Circuit and PCB===
+
[[category:projects]]
*[http://www.wiznet.co.kr/en/pro02.php?&page=1&num=26 WIZNET W5300]
 

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.

Objectives[edit]

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.

Benefits[edit]

  • 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

Limitations[edit]

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


Development[edit]


User Guide[edit]