FPGA et ETHERNET

Patrick Nayman

Introduction
Raliser une connexion rapide entre un FPGA et un systme hte avec ETHERNET 10-100-1000 Mbits (vitesse relle). Avantages
Rapide Possibilit dun cble relativement long Full duplex Debugger gratuit TCPDUMP (linux) , WireShark (Windows) Mise en uvre relativement facile

Peu de ressources FPGA ncessaires :

2200 LE (Logic Element) <= 8 M9K (Memory block)

Interface FPGA/ETHERNET

Les Composants
FPGA ALTERA srie Cyclone (Stratix galement) Bas sur un core GEDEK UDP (socit ALSE)
Restriction : ncessite une liaison point point (pas de collision)

Ncessite 2 composants externes :

Ethernet PHY (srialiseur) par exemple MARVELL 88E1119R
Connexion au FPGA par interface MII (Media Independent Interface) et GMII (Gigabit Media Independent Interface)

Non compatible avec les anciens PHY/MAC Transformateur (peut tre inclus dans la prise RJ45)

Interface FPGA/ETHERNET

Connexion Rseau
Encapsulation of Application Data Application Transport (TCP or UDP) Internet Link

UDP (User Datagram Protocol) : simpler messaging transmissions TCP (Transmission Control Protocol): more complex protocol reliable transmission when collisions
Interface FPGA/ETHERNET 4

Implmentation
Utilisation dUDP (standard de transmission) la place de TCP
Faibles ressources utilises: low cost FPGA (~30) Plus rapide

Possibilit de re-programmer le FPGA par ETHERNET 100Mbits or 1Gbits/s (cuivre)

Interface FPGA/ETHERNET

LInterface globale
GMII FPGA MDIO
MARVELL 88E1119R

LEDs

Gigabit PHY

RJ45+ Magntique

25MHz Contrle du PHY

Interface FPGA/ETHERNET

Le circuit Marvell 88E1119R

Circuit relativement petit : 72 pins

Interface FPGA/ETHERNET

LInterface FPGA-Marvell
Ce qui entre et sort du FPGA

Attention interface en 2.5V

En provenance du MARVELL
Clock reconstruite (125MHz) Dtection de collision Dtection de porteuse Data reue (8 ou 4 bits) Data Valid Erreur dtecte sur le cble Clock reue (25MHz)

Vers le MARVELL

Clock pour gigabit (125MHz) Management Interface Clock (1MHz) Management Interface I/O Bidir Data envoyer (8 ou 4 bits) Data Enable : etx_d valide

erx_d/etx_d :

8 bits en 1000Mbps 4 bits en 10-100Mbps

Interface FPGA/ETHERNET

Exemple de Projet

MII MAC UDP ICMP ARP

: Media Independant Interface : Media Access Control : User Datagram Protocol : Internet Control Message Protocol Interface FPGA/ETHERNET : Address Resolution Protocol

Les Modules disponibles dans lIP

Banc de registres internes (16x32 bits) (pas ETHERNET) Banc de registres (256x32 bits) (ETHERNET) UART Virtuelle (Permet denvoyer des chaines de caractres et remplacer RS232, CAN, I2C Une interface donnes 32 bits Une interface de programmation de la PROM EPCS

Interface FPGA/ETHERNET

10

Banc de registres internes (16x32 bits)

Permet de programmer (ou lire) :

FPGA Board MAC Address Destination MAC Address Destination IP Address Etc.
-- interface register Cpu_Sel Cpu_R Cpu_W Cpu_Ad Cpu_Wdata Cpu_RData Cpu_WaitRequest

Accessible uniquement par les signaux (fournis par le GEDEK):

: in STD_LOGIC; : in STD_LOGIC; : in STD_LOGIC; : in STD_LOGIC_VECTOR(3 downto 0); : in STD_LOGIC_VECTOR(31 downto 0); : out STD_LOGIC_VECTOR(31 downto 0); : out STD_LOGIC;

Interface FPGA/ETHERNET

11

Linterface de donnes
REF_UserRxUDP_Sop : Out REF_UserRxUDP_Eop : Out REF_UserRxUDP_Dav : Out REF_UserRxUDP_Data: Out REF_UserTxUDP_Busy : Out REF_UserTxUDP_Sop : in REF_UserTxUDP_Eop : in REF_UserTxUDP_Dav : in REF_UserTxUDP_Data : in REF_UserDest_Port : in Std_logic; -- Flag indicating a new frame, Rx side Std_logic; -- Flag indicating a end of frame, Rx side Std_logic; -- Flag indicating that data is valid, Rx side Std_logic_vector(31 downto 0); -- Data, Rx side Std_logic; -- Signal indicating that the Gedek IP is ready Std_logic; -- Flag indicating a new frame, Tx side Std_logic; -- Flag indicating a end of frame, Tx side Std_logic; -- Flag indicating that data is valid, Tx side Std_logic_vector(31 downto 0); -- Data, Tx side Std_logic_vector(15 downto 0); -- PN

Interface FPGA/ETHERNET

12

Interface EPCS (PROM de programmation)

Pour la partie Hardware :
1- Dans le FPGA dfinir les pins suivantes et les connecter top_dbm.vhd

2- Dans QUARTUS : Settings/Assignments/Device and Pin Options/Dual-Purpose Pins Data[0] Use as regular I/O Data[1] Use as regular I/O DCLK Use as regular I/O Flash_nCE/nCS Use as regular I/O

Interface FPGA/ETHERNET

13

Les diffrents VHDL pour lIP GEDEK

Un ensemble de petits programmes est ncessaire :
top_dbm.vhd fait appel aux programmes suivants :
fdiv.vhd epcsprog.vhd phyregwrite.vhd phyadd.vhd cnt_max.vhd epcs.vhd eth_miim_beh.vhd (pour la simulation) Gedek_2010.01_beh_hotfix.vhd (pour la simulation) gedek_2010.01.vhd (pour la synthse)

Interface FPGA/ETHERNET

14

Les Signaux
Flot : Start of Protocol, Data/Data Valid, End of Protocol En lecture ETH vers FPGA

En criture FPGA vers ETH

Interface FPGA/ETHERNET

15

Exemple : Hardware (1)

- La gnration dhorloges : utiliser une PLL pour les horloges utilisateurs et pour lIP

Horloge pour cadencer les programmes

Horloge pour un circuit extrieur Horloge pour lIP Horloge pour des circuits extrieurs

- On peut utiliser PLLLocked pour faire un Reset : Resetb <= not PLLLocked;

Interface FPGA/ETHERNET

16

Hardware : top_dbm.vhd (2)

Interface FPGA/ETHERNET

17

Comment se connecter ETH vers FPGA (1)

Top_dbm

1 2

Interface FPGA/ETHERNET

18

Comment se connecter FPGA vers ETH (2)

FifoTx_Empty RstFifoTx Clk66 WrReq FifoTxData RdReq

Fifo_Tx
Ref_UserTxUDP_Busy Ref_UserTxUDP_Data (31:0)

1 2 3 4

Ref_UserTxUDP_Sop Ref_UserTxUDP_Eop Ref_UserTxUDP_Dav

Interface FPGA/ETHERNET

19

Comment se connecter FPGA vers ETH (3)

Exemple de machine dtats (VHDL) utiliser :
when sSending => if RefUserTx_Busy='0' then -- Not Busy UserTx_Davi <= '1'; RefUserTx_Data <= DAQF_q; if Phase=0 then RefUserTx_Sop <= '1'; -- Start of Protocol Phase <= Phase+1; else RefUserTx_Sop <= '0'; if FifoTx_Empty='1' then RefUserTx_Eop <= '1'; UserSdState <= sEnd; end if; end if; else UserTx_Davi <= '0'; end if; -When sEnd => UserTx_Davi <= '0'; RefUserTx_Eop <= '0'; UserSdState <= sIDLE;

| | | | | |

Etat sSending

Etat sEnd

Et en global :
RdReq <= '1' when (UserSdState=sSending) and FifoTx_Empty ='0' and RefUserTx_Busy='0' else'0';
Interface FPGA/ETHERNET 20

Modification des adresses ETH (1)

Changement dun GENERIC dans top_dbm
iGedek : Entity work.gedek Generic Map ( gFeatures => "'HkZ+B<-Bm[$2&8TnF).3~iuGDB:?<)?v>%/nAy^e2[D(iOc67VJOr,;tKe9g&,{g" , gMACAddress => x"0007EDA1B2C4", -- Default GEDEK MAC Address is 00:07:ED:A1:B2:C4 gIPAddress => x"C0A80112", -- Default GEDEK IP Address is 192.168.1.18 Debug => Debug )

Interface FPGA/ETHERNET

21

Modification des adresses ETH (2)

Ecriture dans le banc de registres internes par le port CPU Functionality FPGA Board MAC Address (32 LSB) FPGA Board IP Address Destination MAC Address (32 LSB) Destination MAC Address (16 MSB) Destination IP Address Reserved Reserved Reserved Status Register Version Register Virtual Uart Link UDP Port Number Reserved Reserved Reserved Reserved Reserved Access R/W R/W R/W R/W R/W N/A N/A N/A R/W R R/W N/A N/A N/A N/A N/A Reset Value Generic Dependent Generic Dependent 0x66322E2A 0x00000019 0xC0A801CF N/A N/A N/A 0x00000000 0x<VER> 0x00000017 N/A N/A N/A N/A N/A
22

Address 0x00 0x01 0x02 0x03 0x04 0x05 0x06 0x07 0x08 0x09 0x0A 0x0B 0x0C 0x0D 0x0E 0x0F

Interface FPGA/ETHERNET

Les contraintes de timing

Le core Ethernet ne fonctionnera pas sans contraintes de timing ! 2 cas selon la version de QUARTUS
Avant la version 10 : spcification des contraintes dans le fichier .qsf et selon les cas lutilisation de TimeQuest est possible. A partir de la version 10 : spcification des contraintes dans le fichier .sdc ( Synopsys Design Constraint , utilisation de TimeQuest).

Interface FPGA/ETHERNET

23

Pour simuler !
2 fichiers txt : input et output
Input dfinit les commandes ETHERNET Output donnera le rsultat de la simulation

Interface FPGA/ETHERNET

24

Exemple de input.txt
# Wait Delay: The provided integer is the waiting time in us # S2 # Ping Frame -> Command is 'P' # First Parameter is the IP of the ping sender (here source ip is c0.a8.01.00 = 192.168.1.0) # Second Parameter is the target IP (here destination ip is c0.a8.01.17 = 192.168.1.23) # P c0a80100 c0a80117 # Data Frame -> Command is 'D' # The 'D' command is followed by the destination port then the origin port in decimal !! # The Frame content is provided on the same line with always 8 hexa. digits (ie 0 => 00000000) # # CNTRLNectarReg # D 04D2 4096 AAAAAAAA 00007E3E 00000001 00000002 00000003 00000004 00000005 AAAAAAAA

Interface FPGA/ETHERNET

25

Exemple de output.txt
0D 0A 47 45 44 45 4B 20 2D 20 44 65 66 61 75 6C 74 20 20 28 63 29 20 32 30 30 39 20 41 4C 53 45 2E 46 52 @11977.502 ns => Data Frame to 192.168.1.207:1200 BBBBBBBB 0000EE10 EDA1B2C4 C0A80112 66322E2A 66320019 C0A801CF C0A801CF BBBBBBBB

@15292.502 ns => Data Frame to 192.168.1.207:1200 AAAAAAAA 0000CCC3 C0A80112 00000001 AAAAAAAA

Interface FPGA/ETHERNET

26

Cas du script qsf

# -- Global Clock, Fmax & Timing constraints set_instance_assignment -name GLOBAL_SIGNAL "GLOBAL CLOCK" -to Clock set_global_assignment -name fmax_requirement 66MHz set_global_assignment -name FMAX_REQUIREMENT "125 MHz" -section_id rx_clk set_instance_assignment -name TCO_REQUIREMENT "10 ns" -from * -to gtx_clk set_instance_assignment -name MIN_TCO_REQUIREMENT "9 ns" -from * -to gtx_clk set_instance_assignment -name FAST_OUTPUT_REGISTER ON -to gtx_clk set_instance_assignment -name TCO_REQUIREMENT "10 ns" -from * -to tx_* set_instance_assignment -name FAST_OUTPUT_REGISTER ON -to tx_d* set_instance_assignment -name FAST_OUTPUT_REGISTER ON -to tx_err set_instance_assignment -name FAST_OUTPUT_REGISTER ON -to tx_dv set_instance_assignment -name CLOCK_SETTINGS rx_clk -to rx_clk set_instance_assignment -name TH_REQUIREMENT "0 ns" -from * -to rx_* set_instance_assignment -name TSU_REQUIREMENT "3 ns" -from * -to rx_* set_instance_assignment -name FAST_INPUT_REGISTER ON -to rx_d* set_instance_assignment -name FAST_INPUT_REGISTER ON -to rx_err set_instance_assignment -name FAST_INPUT_REGISTER ON -to rx_dv

Interface FPGA/ETHERNET

27

A propos du script sdc (TimeQuest)

TimeQuest est un outil puissant qui demande un peu dinvestissement Ncessit de contraindre toutes les E/S du design. Assure un routage fonctionnel.

Interface FPGA/ETHERNET

28

Cas du script sdc

# Constrain MAC network-side interface clocks create_clock -period "125 MHz" -name gedek_tx_clk [ get_ports etx_clk ] create_clock -period "125 MHz" -name gedek_rx_clk [ get_ports erx_clk ] create_clock -period "125 MHz" -name gedek_rx_clk_virtual create_generated_clock -name {gedek_gtx_clk} -source [get_ports {erx_clk}] [get_ports {egtx_clk}] set_false_path -from [get_clocks $Clock125MHz] -to [get_ports {egtx_clk}] # Cut the timing path betweeen unrelated clock domains set_clock_groups -exclusive -group {gedek_gtx_clk} -group {gedek_tx_clk} -group {gedek_rx_clk} set_clock_groups -exclusive -group {gedek_rx_clk} -group {gedek_gtx_clk} -group {gedek_tx_clk} set_clock_groups -exclusive -group {gedek_tx_clk} -group {gedek_rx_clk} -group {gedek_gtx_clk} set_clock_groups -exclusive -group {gedek_rx_clk} -group [get_clocks $Clk66] #*********** # GMII - RX #*********** set_max_delay -from [get_clocks {gedek_rx_clk_virtual}] -to * 0 set_min_delay -from [get_clocks {gedek_rx_clk_virtual}] -to * 0 set_input_delay -clock gedek_rx_clk_virtual -max [ expr 0.0 - $ETH_GMII_RX_Tsetup] [get_ports {erx_d[*] erx_dv}] set_input_delay -clock gedek_rx_clk_virtual -min [ expr $ETH_GMII_RX_Thold] [get_ports {erx_d[*] erx_dv}] set_input_delay -clock_fall -clock gedek_rx_clk_virtual -max [ expr 0.0 - $ETH_GMII_RX_Tsetup] [get_ports {erx_d[*] erx_dv}] add_delay set_input_delay -clock_fall -clock gedek_rx_clk_virtual -min [ expr $ETH_GMII_RX_Thold] [get_ports {erx_d[*] erx_dv}] -add_delay

Etc.
Interface FPGA/ETHERNET 29

CONCLUSIONS

Interface FPGA/ETHERNET

30