Trashernet is a very trashy Ethernet stack for FPGAs written in VHDL aiming to cover all OSI layers, including physical!
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
Markus Koch 2190f146a0 doc: Add IPv4 modules to doc 3 months ago
.externalToolBuilders env: Add Sigasi project files 10 months ago
.settings env: Add Sigasi project files 10 months ago
bench bench: Add cocotb-based test bench for MAC test 10 months ago
cocotb bench: Test ARP requests in HWITL 3 months ago
demo/lattice_brevia2 demo: Add ICMP ping reply demo design 3 months ago
design demo: Add ICMP ping reply demo design 3 months ago
doc doc: Add KiCad schematic 10 months ago
trashernet ipv4: Change syntax to make Synplify happy 3 months ago
.gitignore bench: Move HWITL tests to own top level / test bench file 9 months ago
.gitmodules bench: Add cocotb-based test bench for MAC test 10 months ago
.library_mapping.xml env: Add Sigasi project files 10 months ago
.project env: Add Sigasi project files 10 months ago
README.MD doc: Add IPv4 modules to doc 3 months ago
run.py bench: Use VUnit 1 year ago

README.MD

Trashernet

Trashernet Logo

Trashernet is a very trashy Ethernet stack for FPGAs written in VHDL aiming to cover all OSI layers:

  • Layer 1, Physical: trashernet_phy
  • Layer 2, Data link: trashernet_mac, trashernet_eth, trashernet_arp
  • Layer 3, Network: trashernet_ipv4, trashernet_ipv4prot, trashernet_icmp

When writing it, the following were the main design philosophies:

  1. Standards are nice and all, but this, it just needs to work.
  2. Hardware is expensive, LOC are not. So let's do everything we can inside the FPGA.
  3. If there's a feature that feels optional even though it isn't, it is. See 1. if in doubt.

IMPORTANT: This code (and HW suggestions) violate the Ethernet standard in many ways. Do not use in proper (especially commercial) products.

Hardware

Circuit Diagram

  • RX: Use resistors behind Ethernet magnetics to reduce Ethernet RX voltage levels (0 +-2.5V) to LVPECL voltage levels (1.65V +-400mV). Or LVDS if your FPGA can't handle LVPECL. Also, pull up/down resistors help to avoid glitchy behavior with no cable connected or little data activity.
  • TX: Meh, a series current limiting resistor is good enough. Drive two outputs differentially to increase the voltage swing. (Technically not true antivalent signals as there's also the "off" state with both disabled.)

Notes:

  • The RX pull up/downs are probably not the best idea, and fixable in a better way. But for now, this shall work -- and suffice!
  • On the TX side, I'm grossly overloading the drivers. A line driver would probably be a good idea. Or you can just parallel multiple outputs ;D

License

This Source Code Form is subject to the terms of the Mozilla Public License, v. 2.0.

The Trashernet logo uses graphics from svgrepo.com, which are released under the Creative Commons CC0 license, granting the right to freely adapt and use them in any context. Thank you for making these available:

The font used in the logo, "White Rabbit" by Matthew Welch, is also released on a free-to-use basis. Thank you!