What's this?

This is my personal variant of the Ethersex firmware for the Atmel megaAVR processors.

Branches:

• master
  the common master branch of this repository. New features will be added here when they are ready for prime time.
• e6_upstream
  this branch should always closely track upstream/master by pull'ing from ethersex/ethersex and push'ing here.
• experimental
  this branch is used for experimental stuff. It will be reset --hard as needed from time to time and might not even compile...
• project_neptun
  Ethersex based firmware for the main controller of a project codenamed "Project Neptun", an aquarium / aquarium computer using "as many µcontrollers as possible" ™.
• ...
  several other transient experimental- and bugfix-branches.

---

(Text of original Ethersex README.markdown follows)

---

About Ethersex

Ethersex, originally developed to provide an alternative firmware for the etherrape hardware, evolved into a full-featured still light-weight firmware for the Atmel megaAVR processors.
For more information and a comprehensive documentation consult http://www.ethersex.de!

How to configure the firmware

Make sure that you meet the requirements.
Use make menuconfig to configure and make to compile the firmware. The final hex file is named ethersex.hex.

See the Quick Start Guide in the wiki for more information

How to add a new hardware pinning

Use the script at scripts/add-hardware to add a new pinning.

Used 3rd party software

This program contains software by other authors:

• the uIP tcp/ip stack in the directory /protocols/uip/, written by Adam Dunkels
• usb-software stack from obdev in /protocols/usb/usbdrv/, written by Objective Development
• sd card reader in /hardware/storage/sd_reader, written by Roland Riegel
• IRMP - Infrared Multi Protocol Decoder in /hardware/ir/irmp/lib, written by Frank Meyer
• ucglib in /lib/ucglib, written by Oliver Kraus
• u8g2 in /lib/ucglib, written by Oliver Kraus

License

All ethersex related code is licensed under GPLv3, unless otherwise noted. See COPYING in the main directory, but in doubt check the file header. Usually every file contains a header, stating all contributing authors and the specific license used.

Various make targets

• make show-config -- Shows the activated modules