From 873e0043c4c132ff16d90fa6bf4196674e8482ad Mon Sep 17 00:00:00 2001 From: oharboe Date: Fri, 22 Aug 2008 19:50:10 +0000 Subject: more doc work in progress --- zpu/docs/images/compile.PNG | Bin 0 -> 17735 bytes zpu/docs/images/simulator.PNG | Bin 0 -> 42848 bytes zpu/docs/images/simulator2.PNG | Bin 0 -> 42623 bytes zpu/docs/images/simulator3.PNG | Bin 0 -> 69583 bytes zpu/docs/zpu_arch.html | 120 +++++++++++++++++++++++++++++++++++++++++ 5 files changed, 120 insertions(+) create mode 100644 zpu/docs/images/compile.PNG create mode 100644 zpu/docs/images/simulator.PNG create mode 100644 zpu/docs/images/simulator2.PNG create mode 100644 zpu/docs/images/simulator3.PNG diff --git a/zpu/docs/images/compile.PNG b/zpu/docs/images/compile.PNG new file mode 100644 index 0000000..8a00c07 Binary files /dev/null and b/zpu/docs/images/compile.PNG differ diff --git a/zpu/docs/images/simulator.PNG b/zpu/docs/images/simulator.PNG new file mode 100644 index 0000000..9765366 Binary files /dev/null and b/zpu/docs/images/simulator.PNG differ diff --git a/zpu/docs/images/simulator2.PNG b/zpu/docs/images/simulator2.PNG new file mode 100644 index 0000000..070084e Binary files /dev/null and b/zpu/docs/images/simulator2.PNG differ diff --git a/zpu/docs/images/simulator3.PNG b/zpu/docs/images/simulator3.PNG new file mode 100644 index 0000000..34e0540 Binary files /dev/null and b/zpu/docs/images/simulator3.PNG differ diff --git a/zpu/docs/zpu_arch.html b/zpu/docs/zpu_arch.html index 5d7fc5e..968ae34 100644 --- a/zpu/docs/zpu_arch.html +++ b/zpu/docs/zpu_arch.html @@ -2,6 +2,10 @@

Index

+ +

The worlds smallest 32 bit CPU with GCC toolchain +

+

This CPU is finding a new home at www.opencores.org, please +contact me if you are willing and able to help in shaping up the +www.opencores.org pages. +

+

The HDL, GCC toolchain and eCos HAL are actually done. Mainly I +could need a hand with writing up docs/web pages/examples/bug +reports.

+

The ZPU has a BSD license for the HDL and GPL for the rest(source +files are sadly out of date here, patches gladly accepted!). This +allows deployments to implement any version of the ZPU they want +without running into commercial problems, but if improvements are +done to the architecture as such, then they need to be contributed +back. +

+

One strength of the ZPU is that it is tiny and therefore easy to +implement from scratch to suit specialized needs and optimizations.

+

Currently there exists some pages at http://www.zylin.com/zpu.htm +that explains about the ZPU. According to OpenCores policy this +information should be moved to www.opencores.org. Patches gratefully +accepted to do so!

+

Per Jan 1. 2008, Zylin has the Copyright for the ZPU, i.e. Zylin +is free to decide that the ZPU shall have a BSD license for HDL + GPL +for the rest.

+

Sincerley,

+

Øyvind Harboe
Zylin AS +

+

Features +

+ +

Survey +

+

Please take the time to fill in this short survey so we can gather +information about where the ZPU can be the most useful:

+

http://www.zylin.com/zpusurvey.html

+

Status +

+ +

Simulator +

+

The ZPU simulator is integrated into the Zylin Embedded CDT plugin +to ease debugging of ZPU applications:

+

http://www.zylin.com/embeddedcdt.html

+

The ZPU simulator has many features besides debugging an +application:

+ +

The plugin is still pretty rough around the edges, and needs to +get GUI support for enabling the ModelSim trace input feature.

+


Compiling +ZPU application

+


Setting +up the simulator

+


Choosing +ZPU executable

+


Debug +session

+


+

+

Getting started - FPGA

The simplest version of the ZPU uses BRAM. When getting accustomed to the ZPU, a BRAM ZPU with a UART @@ -1740,6 +1843,23 @@ This ZPU could run a TCP/IP stack with relevant performance to compete with stripped down ARM7 type systems. +
+

Download source code

+

+

The simplest way to get the ZPU HDL source and tools is to check +it out from CVS:

+

cvs -d :pserver:anonymous@cvs.opencores.org:/cvsroot/anonymous co +zpu/zpu

+

Start by reading zpu/zpu/hdl/index.html

+
+

Creating a patch

+


If you have an changes, modify the files locally, create a +patch and email it to
zylin-zpu mailing list. Attach it +as an uncompressed .txt file:

+

cd zpu
cvs diff -upN . > mypatch.txt

+ +

Getting help - mailing list

+The place to get help is the
zylin-zpu mailing list \ No newline at end of file -- cgit v1.1