Installation of Mico32/FPG-EYE development environment

From ErikaWiki

Revision as of 09:53, 29 September 2011 by Eguidieri (Talk | contribs)
Jump to: navigation, search


This tutorial describes a set of steps needed to compile and deploy a platform on FPG-EYE board.

To achive this goal you need follow softwares from Lattice installed in your environment (follow links for download pages):

To download and use these softwares you need a Lattice registration and a fre license (follow instruction on Lattice web site)

Be careful each version of ispLEVER need a correspondent version of LatticeMico System Development Tools. In regard to ispVM System you need version 18.0 or superior.

All FPG-EYE development has been made with ispLEVER 8.0 and correspondant LatticeMico System Development Tools.

Hereunder it's supposed that all the tools are installed in the same base directory and we refer at this directory as: %ispTOOLS%

Standard Mico32 components Patches

During FPG-EYE software development we found and correct a few bugs in standard Mico32 components. Especially we found small bugs in following components:

  • SPI Flash Controller (Component directory: spi_flash. Verilog files: spi_flash_intf.v wb_intf.v)
  • Async SRAM Controller (Componet directory: asram_top. Verilog files: asram_core.v)

We found these bugs in ispLEVER version 8.0 components. We don't know if they have been fixed in later versions.

You can found the patched verilog files [here]. To apply the patches you need to copy these new files in the right componets folders. The base directory for components is: %ispTOOLS%\micosystem\components. You have to put patched verilog files for each component in %ispTOOLS%\micosystem\components\<Component directory>\rtl\verilog to fix found bugs

Personal tools