Nothing.

This is MAC module routine. It initializes Ethernet controller. This function is internaly splited into 2 parts to help linker when coming short of memory.

Ethernet controller settings (parameters not mentioned here are set to default):

• receive buffer start address : 0x0000.
• receive buffer end address : 0x19AD.
• transmit buffer start address: 0x19AE.
• transmit buffer end address : 0x1FFF.
• RAM buffer read/write pointers in auto-increment mode.
• receive filters set to default: CRC + MAC Unicast + MAC Broadcast in OR mode.
• flow control with TX and RX pause frames in full duplex mode.
• frames are padded to 60 bytes + CRC.
• maximum packet size is set to 1518.
• Back-to-Back Inter-Packet Gap: 0x15 in full duplex mode; 0x12 in half duplex mode.
• Non-Back-to-Back Inter-Packet Gap: 0x0012 in full duplex mode; 0x0C12 in half duplex mode.
• half duplex loopback disabled.
• LED configuration: default (LEDA-link status, LEDB-link activity).

Parameters:

• mac: RAM buffer containing valid MAC address.
• ip: RAM buffer containing valid IP address.
• fullDuplex: ethernet duplex mode switch. Valid values: 0 (half duplex mode, predefined library const Ethernet_HALFDUPLEX) and 1 (full duplex mode, predefined library const Ethernet_FULLDUPLEX).

  Note : If a DHCP server is to be used, IP address should be set to 0.0.0.0.

var 
  myMacAddr : array[6] of byte; // my MAC address	
  myIpAddr  : array[4] of byte; // my IP addr
  ...
  myMacAddr[0] := 0x00;
  myMacAddr[1] := 0x14;
  myMacAddr[2] := 0xA5;
  myMacAddr[3] := 0x76;
  myMacAddr[4] := 0x19;
  myMacAddr[5] := 0x3F;

  myIpAddr[0]  := 192;
  myIpAddr[1]  := 168;
  myIpAddr[2]  := 20;
  myIpAddr[3]  := 60;
  
  Ethernet_Init(myMacAddr, myIpAddr, Ethernet_FULLDUPLEX);
          

Nothing.

This is MAC module routine. This routine enables appropriate network traffic on the MCU's internal Ethernet module by the means of it's receive filters (unicast, multicast, broadcast, crc). Specific type of network traffic will be enabled if a corresponding bit of this routine's input parameter is set. Therefore, more than one type of network traffic can be enabled at the same time. For this purpose, predefined library constants (see the table below) can be ORed to form appropriate input value.

Parameters:

• enFlt: network traffic/receive filter flags. Each bit corresponds to the appropriate network traffic/receive filter:

Bit	Mask	Description	Predefined library const
0	0x01	MAC Broadcast traffic/receive filter flag. When set, MAC broadcast traffic will be enabled.	_Ethernet_BROADCAST
1	0x02	MAC Multicast traffic/receive filter flag. When set, MAC multicast traffic will be enabled.	_Ethernet_MULTICAST
2	0x04	not used	none
3	0x08	not used	none
4	0x10	not used	none
5	0x20	CRC check flag. When set, packets with invalid CRC field will be discarded.	_Ethernet_CRC
6	0x40	not used	none
7	0x80	MAC Unicast traffic/receive filter flag. When set, MAC unicast traffic will be enabled.	_Ethernet_UNICAST

  Note :
• Advanced filtering available in the MCU's internal Ethernet module such as Pattern Match, Magic Packet and Hash Table can not be enabled by this routine.
  Additionaly, all filters, except CRC, enabled with this routine will work in OR mode, which means that packet will be received if any of the enabled filters accepts it.
• This routine will change receive filter configuration on-the-fly. It will not, in any way, mess with enabling/disabling receive/transmit logic or any other part of the MCU's internal Ethernet module.
  The MCU's internal Ethernet module should be properly cofigured by the means of Ethernet_Init routine.

Ethernet module has to be initialized. See Ethernet_Init.

Ethernet_Enable(_Ethernet_CRC or _Ethernet_UNICAST); // enable CRC checking and Unicast traffic

Nothing.

This is MAC module routine. This routine disables appropriate network traffic on the MCU's internal Ethernet module by the means of it's receive filters (unicast, multicast, broadcast, crc). Specific type of network traffic will be disabled if a corresponding bit of this routine's input parameter is set. Therefore, more than one type of network traffic can be disabled at the same time. For this purpose, predefined library constants (see the table below) can be ORed to form appropriate input value.

Parameters:

• disFlt: network traffic/receive filter flags. Each bit corresponds to the appropriate network traffic/receive filter:

Bit	Mask	Description	Predefined library const
0	0x01	MAC Broadcast traffic/receive filter flag. When set, MAC broadcast traffic will be disabled.	_Ethernet_BROADCAST
1	0x02	MAC Multicast traffic/receive filter flag. When set, MAC multicast traffic will be disabled.	_Ethernet_MULTICAST
2	0x04	not used	none
3	0x08	not used	none
4	0x10	not used	none
5	0x20	CRC check flag. When set, CRC check will be disabled and packets with invalid CRC field will be accepted.	_Ethernet_CRC
6	0x40	not used	none
7	0x80	MAC Unicast traffic/receive filter flag. When set, MAC unicast traffic will be disabled.	_Ethernet_UNICAST

  Note :
• Advance filtering available in the MCU's internal Ethernet module such as Pattern Match, Magic Packet and Hash Table can not be disabled by this routine.
• This routine will change receive filter configuration on-the-fly. It will not, in any way, mess with enabling/disabling receive/transmit logic or any other part of the MCU's internal Ethernet module.
• The MCU's internal Ethernet module should be properly cofigured by the means of Ethernet_Init routine.

Ethernet module has to be initialized. See Ethernet_Init.

Ethernet_Disable(_Ethernet_CRC or _Ethernet_UNICAST); // disable CRC checking and Unicast traffic

• 0 - upon successful packet processing (zero packets received or received packet processed successfully).
• 1 - upon reception error or receive buffer corruption. Ethernet controller needs to be restarted.
• 2 - received packet was not sent to us (not our IP, nor IP broadcast address).
• 3 - received IP packet was not IPv4.
• 4 - received packet was of type unknown to the library.

This is MAC module routine. It processes next received packet if such exists. Packets are processed in the following manner:

• ARP & ICMP requests are replied automatically.
• upon TCP request the Ethernet_UserTCP function is called for further processing.
• upon UDP request the Ethernet_UserUDP function is called for further processing.

  Note : Ethernet_doPacket must be called as often as possible in user's code.

Ethernet module has to be initialized. See Ethernet_Init.

while true do
  begin
    ...
    Ethernet_doPacket(); // process received packets
    ...
  end;

Nothing.

This is MAC module routine. It stores one byte to address pointed by the current Ethernet controller's write pointer (EWRPT).

Parameters:

• v: value to store

Ethernet module has to be initialized. See Ethernet_Init.

var 
  data : byte;
  ...
  Ethernet_putByte(data);  // put an byte into ethernet buffer

Nothing.

This is MAC module routine. It stores requested number of bytes into Ethernet controller's RAM starting from current Ethernet controller's write pointer (EWRPT) location.

Parameters:

• ptr: RAM buffer containing bytes to be written into Ethernet controller's RAM.
• n: number of bytes to be written.

Ethernet module has to be initialized. See Ethernet_Init.

var 
  buffer : array[17] of byte;	 
  ...
  buffer := 'mikroElektronika';	 
  ...
  Ethernet_putBytes(buffer, 16); // put an RAM array into ethernet buffer

Nothing.

This is MAC module routine. It stores requested number of const bytes into Ethernet controller's RAM starting from current Ethernet controller's write pointer (EWRPT) location.

Parameters:

• ptr: const buffer containing bytes to be written into Ethernet controller's RAM.
• n: number of bytes to be written.

Ethernet module has to be initialized. See Ethernet_Init.

const 
  buffer : array[17] of byte;	 
  ...
  buffer := 'mikroElektronika';	 
  ...
  Ethernet_putConstBytes(buffer, 16); // put a const array into ethernet buffer

Number of bytes written into Ethernet controller's RAM.

This is MAC module routine. It stores whole string (excluding null termination) into Ethernet controller's RAM starting from current Ethernet controller's write pointer (EWRPT) location.

Parameters:

• ptr: string to be written into Ethernet controller's RAM.

Ethernet module has to be initialized. See Ethernet_Init.

var 
  buffer : string[16];	 
  ...
  buffer := 'mikroElektronika';	 
  ...
  Ethernet_putString(buffer); // put a RAM string into ethernet buffer

Number of bytes written into Ethernet controller's RAM.

This is MAC module routine. It stores whole const string (excluding null termination) into Ethernet controller's RAM starting from current Ethernet controller's write pointer (EWRPT) location.

Parameters:

• ptr: const string to be written into Ethernet controller's RAM.

Ethernet module has to be initialized. See Ethernet_Init.

const 
  buffer : string[16];	 
  ...
  buffer := 'mikroElektronika';	 
  ...
  Ethernet_putConstString(buffer); // put a const string into ethernet buffer

Byte read from Ethernet controller's RAM.

This is MAC module routine. It fetches a byte from address pointed to by current Ethernet controller's read pointer (ERDPT).

Ethernet module has to be initialized. See Ethernet_Init.

var 
  buffer : byte; 
  ...
  buffer := Ethernet_getByte(); // read a byte from ethernet buffer

Nothing.

This is MAC module routine. It fetches equested number of bytes from Ethernet controller's RAM starting from given address. If value of 0xFFFF is passed as the address parameter, the reading will start from current Ethernet controller's read pointer (ERDPT) location.

Parameters:

• ptr: buffer for storing bytes read from Ethernet controller's RAM.
• addr: Ethernet controller's RAM start address. Valid values: 0..8192.
• n: number of bytes to be read.

Ethernet module has to be initialized. See Ethernet_Init.

var 
  buffer: array[16] of byte;	 
  ...
  Ethernet_getBytes(buffer, 0x100, 16); // read 16 bytes, starting from address 0x100

• 0 - there should not be a reply to the request.
• Length of TCP reply data field - otherwise.

This is TCP module routine. It is internally called by the library. The user accesses to the TCP request by using some of the Ethernet_get routines. The user puts data in the transmit buffer by using some of the Ethernet_put routines. The function must return the length in bytes of the TCP reply, or 0 if there is nothing to transmit. If there is no need to reply to the TCP requests, just define this function with return(0) as a single statement.

Parameters:

• remoteHost: client's IP address.
• remotePort: client's TCP port.
• localPort: port to which the request is sent.
• reqLength: TCP request data field length.
• flags: record consisted of two fields :
  Copy Code To Clipboard

  type TEthPktFlags = record
    canCloseTCP: boolean;  // flag which closes socket
    isBroadcast: boolean;  // flag which denotes that the IP package has been received via subnet broadcast address (not used for PIC16 family)
  end;
  

  Note : The function source code is provided with appropriate example projects. The code should be adjusted by the user to achieve desired reply.

Ethernet module has to be initialized. See Ethernet_Init.

This function is internally called by the library and should not be called by the user's code.

• 0 - there should not be a reply to the request.
• Length of UDP reply data field - otherwise.

This is UDP module routine. It is internally called by the library. The user accesses to the UDP request by using some of the Ethernet_get routines. The user puts data in the transmit buffer by using some of the Ethernet_put routines. The function must return the length in bytes of the UDP reply, or 0 if nothing to transmit. If you don't need to reply to the UDP requests, just define this function with a return(0) as single statement.

Parameters:

• remoteHost: client's IP address.
• remotePort: client's port.
• destPort: port to which the request is sent.
• flags: record consisted of two fields :
  Copy Code To Clipboard

  type TEthPktFlags = record
    canCloseTCP: boolean;  // flag which closes socket (not relevant to UDP)
    isBroadcast: boolean;  // flag which denotes that the IP package has been received via subnet broadcast address (not used for PIC16 family)
  end;
  

  Note : The function source code is provided with appropriate example projects. The code should be adjusted by the user to achieve desired reply.

Ethernet module has to be initialized. See Ethernet_Init.

This function is internally called by the library and should not be called by the user's code.

This routine should be used when DHCP server is present on the network to fetch assigned IP address.

  Note : User should always copy the IP address from the RAM location returned by this routine into it's own IP address buffer. These locations should not be altered by the user in any case!

Ethernet module has to be initialized. See Ethernet_Init.

var 
  ipAddr : array[4] of byte;  // user IP address buffer
  ...	
  memcpy(ipAddr, Ethernet_getIpAddress(), 4); // fetch IP address

This routine should be used when DHCP server is present on the network to fetch assigned gateway IP address.

  Note : User should always copy the IP address from the RAM location returned by this routine into it's own gateway IP address buffer. These locations should not be altered by the user in any case!

Ethernet module has to be initialized. See Ethernet_Init.

var 
  gwIpAddr : array[4] of byte;  // user gateway IP address buffer
  ...	
  memcpy(gwIpAddr, Ethernet_getGwIpAddress(), 4); // fetch gateway IP address 

This routine should be used when DHCP server is present on the network to fetch assigned DNS IP address.

  Note : User should always copy the IP address from the RAM location returned by this routine into it's own DNS IP address buffer. These locations should not be altered by the user in any case!

Ethernet module has to be initialized. See Ethernet_Init.

var 
  dnsIpAddr : array[4] of byte;  // user DNS IP address buffer
  ...	
  memcpy(dnsIpAddr, Ethernet_getDnsIpAddress(), 4); // fetch DNS server address 

This routine should be used when DHCP server is present on the network to fetch assigned IP subnet mask.

  Note : User should always copy the IP address from the RAM location returned by this routine into it's own IP subnet mask buffer. These locations should not be altered by the user in any case!

Ethernet module has to be initialized. See Ethernet_Init.

var 
  IpMask : array[4] of byte;  // user IP subnet mask buffer
  ...	
  memcpy(IpMask, Ethernet_getIpMask(), 4); // fetch IP subnet mask

Configures network parameters (IP subnet mask, gateway IP address, DNS IP address) when DHCP is not used.

Parameters:

• ipMask: IP subnet mask.
• gwIpAddr gateway IP address.
• dnsIpAddr: DNS IP address.

  Note : The above mentioned network parameters should be set by this routine only if DHCP module is not used. Otherwise DHCP will override these settings.

Ethernet module has to be initialized. See Ethernet_Init.

var 
  ipMask    : array[4] of byte;  // network mask (for example : 255.255.255.0)
  gwIpAddr  : array[4] of byte;  // gateway (router) IP address
  dnsIpAddr : array[4] of byte;  // DNS server IP address
  ...	
  gwIpAddr[0]  := 192;
  gwIpAddr[1]  := 168;
  gwIpAddr[2]  := 20;
  gwIpAddr[3]  := 6;

  dnsIpAddr[0] := 192;
  dnsIpAddr[1] := 168;
  dnsIpAddr[2] := 20;
  dnsIpAddr[3] := 100;

  ipMask[0]    := 255;
  ipMask[1]    := 255;
  ipMask[2]    := 255;
  ipMask[3]    := 0;
  ...
  Ethernet_confNetwork(ipMask, gwIpAddr, dnsIpAddr); // set network configuration parameters

• MAC address behind the IP address - the requested IP address was resolved.
• 0 - otherwise.

This is ARP module routine. It sends an ARP request for given IP address and waits for ARP reply. If the requested IP address was resolved, an ARP cash entry is used for storing the configuration. ARP cash can store up to 3 entries. For ARP cash structure refer to "eth_j60LibDef.h" header file in the compiler's Uses/P18 folder.

Parameters:

• ip: IP address to be resolved.
• tmax: time in seconds to wait for an reply.

  Note : The Ethernet services are not stopped while this routine waits for ARP reply. The incoming packets will be processed normaly during this time.

Ethernet module has to be initialized. See Ethernet_Init.

var 
  IpAddr : array[4] of byte;  // IP address
  ...	
  IpAddr[0] := 192;
  IpAddr[0] := 168;
  IpAddr[0] := 1;
  IpAddr[0] := 1;
  ...
  Ethernet_arpResolve(IpAddr, 5); // get MAC address behind the above IP address, wait 5 secs for the response

• 1 - UDP packet was sent successfully.
• 0 - otherwise.

This is UDP module routine. It sends an UDP packet on the network.

Parameters:

• destIP: remote host IP address.
• sourcePort: local UDP source port number.
• destPort: destination UDP port number.
• pkt: packet to transmit.
• pktLen: length in bytes of packet to transmit.

Ethernet module has to be initialized. See Ethernet_Init.

var 
  IpAddr : array[4] of byte;  // remote IP address
  ...	
  IpAddr[0] := 192;
  IpAddr[0] := 168;
  IpAddr[0] := 1;
  IpAddr[0] := 1;
  ...
  Ethernet_sendUDP(IpAddr, 10001, 10001, 'Hello', 5); // send Hello message to the above IP address, from UDP port 10001 to UDP port 10001 

• pointer to the location holding the IP address - the requested host name was resolved.
• 0 - otherwise.

This is DNS module routine. It sends an DNS request for given host name and waits for DNS reply. If the requested host name was resolved, it's IP address is stored in library global variable and a pointer containing this address is returned by the routine. UDP port 53 is used as DNS port.

Parameters:

• host: host name to be resolved.
• tmax: time in seconds to wait for an reply.

  Note :

• The Ethernet services are not stopped while this routine waits for DNS reply. The incoming packets will be processed normaly during this time.
• User should always copy the IP address from the RAM location returned by this routine into it's own resolved host IP address buffer. These locations should not be altered by the user in any case!

Ethernet module has to be initialized. See Ethernet_Init.

var 
  remoteHostIpAddr : array[4] of byte;	// user host IP address buffer
  ...
  // SNTP server:
  // Zurich, Switzerland: Integrated Systems Lab, Swiss Fed. Inst. of Technology
  // 129.132.2.21: swisstime.ethz.ch
  // Service Area: Switzerland and Europe	
  memcpy(remoteHostIpAddr, Ethernet_dnsResolve('swisstime.ethz.ch', 5), 4);

• 1 - network parameters were obtained successfully.
• 0 - otherwise.

This is DHCP module routine. It sends an DHCP request for network parameters (IP, gateway, DNS addresses and IP subnet mask) and waits for DHCP reply. If the requested parameters were obtained successfully, their values are stored into the library global variables.

These parameters can be fetched by using appropriate library IP get routines:

• Ethernet_getIpAddress - fetch IP address.
• Ethernet_getGwIpAddress - fetch gateway IP address.
• Ethernet_getDnsIpAddress - fetch DNS IP address.
• Ethernet_getIpMask - fetch IP subnet mask.

UDP port 68 is used as DHCP client port and UDP port 67 is used as DHCP server port.

Parameters:

• tmax: time in seconds to wait for an reply.

  Note :

• The Ethernet services are not stopped while this routine waits for DNS reply. The incoming packets will be processed normaly during this time.
• When DHCP module is used, global library variable Ethernet_userTimerSec is used to keep track of time. It is user responsibility to increment this variable each second in it's code.

Ethernet module has to be initialized. See Ethernet_Init.

  ...	
  Ethernet_initDHCP(5); // get network configuration from DHCP server, wait 5 sec for the response 
  ...

• 0 - lease time has not expired yet.
• 1 - lease time has expired, it's time to renew it.

This is DHCP module routine. It takes care of IP address lease time by decrementing the global lease time library counter. When this time expires, it's time to contact DHCP server and renew the lease.

Ethernet module has to be initialized. See Ethernet_Init.

while true do
  begin
    ...
    if(Ethernet_doDHCPLeaseTime() <> 0) then
      begin
        ... // it's time to renew the IP address lease                  
      end;  
  end;

• 1 - upon success (lease time was renewed).
• 0 - otherwise (renewal request timed out).

This is DHCP module routine. It sends IP address lease time renewal request to DHCP server.

Parameters:

• tmax: time in seconds to wait for an reply.

Ethernet module has to be initialized. See Ethernet_Init.

while true do
  begin 
    ...
    if(Ethernet_doDHCPLeaseTime() <> 0) then
      begin
        Ethernet_renewDHCP(5); // it's time to renew the IP address lease, with 5 secs for a reply                  
      end;  
    ...  
  end;