Build your hardware, easily!
Go to file
Sebastien Bourdeauducq 1e7783a41e build.py: use implicit get_fragment 2013-03-12 16:13:20 +01:00
build Initial import 2011-12-13 17:33:12 +01:00
common Use new module, autoreg and eventmanager Migen APIs 2013-03-10 19:32:38 +01:00
milkymist Use automatic register naming 2013-03-12 15:47:54 +01:00
software Use new module, autoreg and eventmanager Migen APIs 2013-03-10 19:32:38 +01:00
tb tb: use default runner 2013-02-09 17:09:29 +01:00
tools tools: add byteswap 2013-02-19 13:22:35 +01:00
verilog lm32: update 2013-02-24 17:42:28 +01:00
.gitignore tools: add byteswap 2013-02-19 13:22:35 +01:00
.gitmodules lm32: use submodule 2013-02-24 15:57:19 +01:00
Makefile Build FPG file 2013-02-19 13:27:43 +01:00
README software: go back to GCC 2013-02-16 23:41:42 +01:00
build.py build.py: use implicit get_fragment 2013-03-12 16:13:20 +01:00
cmacros.py Get CSR base addresses from include file 2012-05-16 10:36:46 +02:00
load.jtag load.jtag: remove CFG_OUT/CFG_IN instructions 2013-02-15 19:39:54 +01:00
soc.xst Add build Makefile and JTAG load script 2012-02-17 18:09:48 +01:00
top.py Use new module, autoreg and eventmanager Migen APIs 2013-03-10 19:32:38 +01:00

README

[> Milkymist-NG system-on-chip
------------------------------

This is the next-generation Milkymist(tm) system-on-chip design,
introducing two key innovations:
 * Built on the powerful Migen VLSI logic design system.
 * Increased system memory performance thanks to a new architecture
   (ASMI) containing a transaction-reordering and superscalar controller.

The Milkymist-NG SoC supports the Milkymist One board. Obtain yours at:
  http://milkymist.org

Note that the -NG version is still experimental work in progress. For the
production version of Milkymist SoC, visit:
  https://github.com/milkymist/milkymist

[> Instructions (software)
--------------------------
1. Compile and install binutils. Take the latest version from GNU.
  mkdir build && cd build
  ../configure --target=lm32-elf
  make
  make install
  
2. Compile and install GCC 4.5. Take gcc-core and gcc-g++ from GNU.
  rm -rf libstdc++-v3
  mkdir build && cd build
  ../configure --target=lm32-elf --enable-languages="c,c++" --disable-libgcc --disable-libssp
  make
  make install

3. Obtain compiler-rt and set the CRTDIR environment variable to the root of 
   its source tree.
  svn co http://llvm.org/svn/llvm-project/compiler-rt/trunk compiler-rt
  export CRTDIR=/path_to/compiler-rt

4. Build and flash the BIOS (part of this source distribution).
  cd software/bios
  make
  make flash

The second command requires m1nor, FJMEM and UrJTAG.
These tools can be found at:
  https://github.com/milkymist/fjmem-m1
  http://urjtag.org
  
[> Instructions (gateware)
--------------------------
First, download and install Migen from:
  https://github.com/milkymist/migen

Once this is done, build the bitstream with:
  make
This will generate the build/soc.bit programming file.
Use:
  make load
to load it with UrJTAG.

The SoC expects a bootloader to be located in flash at 0x860000, just
like the legacy SoC did. However, there is no binary compatibility and a
new BIOS needs to be built and flashed for the -NG SoC.

Enjoy!

[> Misc
-------
Code repository:
  https://github.com/milkymist/milkymist-ng

Send questions, comments and patches to devel [AT] lists.milkymist.org
We are also on IRC: #milkymist on the Freenode network.

Milkymist-NG is free software: you can redistribute it and/or modify it
under the terms of the GNU General Public License as published by the
Free Software Foundation, version 3 of the License. This program is
distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY;
without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE. See the GNU General Public License for more details.

The authors grant the additional permissions that the code can be used in
conjunction with the LatticeMico32 CPU core from Lattice.

Unless otherwise noted, Milkymist-NG's source code is copyright (C)
2011-2013 Sebastien Bourdeauducq. Other authors retain ownership of their
contributions. If a submission can reasonably be considered independently
copyrightable, it's yours and I encourage you to claim it with
appropriate copyright notices. This submission then falls under the
"otherwise noted" category. All submissions must use a license compatible
with the GPL and the additional permissions above.