ProjectBook Title
GreenMessageGreenMessage Manual

The manual in PDF format can be found here: files/GreenMessageManual.pdf
GS EngineeringGreenSocs Changelog

<nowiki><pre>

GreenSocs 4.2.0 (2010-09-07, r3814) 

  * GreenControl
  ** minor updates to command_if signatures (GC_Logger)
  ** Added Extension mechanism to Services (gc_service_ID_extension)
  ** Added gc_port constructor getting extended Service ID
  ** Added extension example
GreenSocs 4.1.1 (2010-09-07, r3810)

GreenConfigGCnf Details

GreenConfig Details
Atom and Neo platformHardware List for Both Platform

Spreadsheet containing hardware IP list used in both Atom / Neo Platforms..
Atom and Neo platformBrief Description on Atom/ Neo Qemu Platform

This documents gives briefs description on specification/overview of Both platform. Also provides reference list for where to start with..
GS EngineeringGreenSocs 3.0.x changelog
QEMU SystemCImporting Wrapper for QEMU in Innovator

Instructions to import the QEMU Wrapper to Innovator.

You will need this file that contains:

  • libraries:
    • libqemu.a
    • libqemu_common.a
    • libqemuSC.a
  • source code:
    • qemuWPSC.[cc|h]
    • sc_slave_dummy.h

The libraries are built from QEMU source code (at svn) using gcc shiped with Innovator.

To import the wrapper into Innovator:

  1. Impo
GS EngineeringGreenSocs Development Environment

The GreenSocs Development Environment is some Makefile tricks to avoid changing the Makefiles by hand.

The Problem

Many Makefiles in the GreenSocs projects hardcode the paths for the projects. All these paths points to home directories or directories that are not available in all machines.
GreenRegGreenReg Tutorial

Tutorial Slides

These slides are based on the DRF slides and modified to include changes and drop unsupported features (like state machine modeling).
GS EngineeringRegression tests

Regression tests is the GreenSocs projects

For all projects we should have regression tests.

Regression tests shall ensure that updates and bug fixes to any feature do not break anything which was working fine before. They shall also test as much cases as possible to a) have compiled each code line and b) to have executed each code line.

  • Directory:
    • The best is having a sub di
12345678next ›last »