fpga/trashernet
1
0
Fork 0
Code Issues 7 Pull Requests 2 Releases 2 Wiki Activity
Trashernet is a very trashy Ethernet stack for FPGAs written in VHDL aiming to cover all OSI layers, including physical!
90 Commits 8 Branches 2 Tags 449 KiB
VHDL 96.6%
Python 3%
Makefile 0.3%
87bc9ce3d7
Go to file
Markus Koch 87bc9ce3d7 ipv4: Add rx_length field
2022-11-01 16:22:59 +01:00
.externalToolBuilders env: Add Sigasi project files 2022-04-18 10:17:42 +02:00
.settings env: Add Sigasi project files 2022-04-18 10:17:42 +02:00
bench bench: Add cocotb-based test bench for MAC test 2022-04-18 17:06:53 +02:00
cocotb bench: Test ARP requests in HWITL 2022-10-28 18:55:04 +02:00
demo/lattice_brevia2 demo: Move top level to library work 2022-02-12 13:19:14 +01:00
design ipv4: Implement IPv4 TX 2022-10-31 23:46:46 +01:00
doc doc: Add KiCad schematic 2022-04-18 10:04:24 +02:00
trashernet ipv4: Add rx_length field 2022-11-01 16:22:59 +01:00
.gitignore bench: Move HWITL tests to own top level / test bench file 2022-04-30 12:53:35 +02:00
.gitmodules bench: Add cocotb-based test bench for MAC test 2022-04-18 17:06:53 +02:00
.library_mapping.xml env: Add Sigasi project files 2022-04-18 10:17:42 +02:00
.project env: Add Sigasi project files 2022-04-18 10:17:42 +02:00
README.MD doc: Add ARP layer to README 2022-10-30 17:38:29 +01:00
run.py bench: Use VUnit 2022-01-16 17:46:01 +01:00

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

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!