verilog-apple-one/boards
Alan Garfield 5a969c5f6f
Update README.md
2024-04-22 08:56:44 +10:00
..
blackice2 removed wrong images 2018-03-31 10:19:49 +01:00
ice40hx8k-b-evn fixed param paths for yosys, may need more work 2018-02-14 15:27:36 +11:00
ice40updevboard Update README.md 2024-04-22 08:56:44 +10:00
icoboard boards: icoboard support 2019-11-05 17:27:25 +01:00
olimex_ice40hx8k_evb_ice40-io Fixed olimex makefile path error 2018-04-12 22:47:20 +10:00
spartan3e_starterkit Updated DE0 project to have 0xC00X colour support. 2018-05-09 02:59:11 +02:00
terasic_de0 Add preliminary FuseSoC support 2018-02-12 15:19:40 +01:00
terasic_de0cv/Quartus Terasic DE0-CV board support 2020-07-11 16:04:20 +01:00
tinyfpga_b2 fixed tinyfpga_b2 image path. oops 2018-02-12 08:57:24 +11:00
upduino Fixed paths on upduino build 2018-02-12 09:35:44 +11:00
README.md Update board readme 2018-02-12 08:29:43 +11:00

README.md

Board directory requirements

The directory structure for board should follow the following convention:

/boards/[target_board_name]/[build_env]

target_board_name

Choose a target/board name that uniquely identifies the board, including required extension boards. For example: UPDuino_v1 or Terasic_DE0

When an extension board is required, for instance, a VGAXYZ board, the target_board_name should be something like: UPDuino_v1_VGAXYZ

build_env

Choose a build_env name that uniquely identifies the development environment, such as yosys or quartus or webpackISE etc.

README.md

For each project, a README.md file should be present describing the hardware setup, the build environment and, if needed, the pinout used. Also include contact information of the maintainer.

Photos are a plus.