diff options
author | oharboe <oharboe> | 2008-09-04 12:17:30 +0000 |
---|---|---|
committer | oharboe <oharboe> | 2008-09-04 12:17:30 +0000 |
commit | f4abb6c6014eb8a46236bf44eecea82f44124d75 (patch) | |
tree | c8acbf5d6ab1d225f864c60682be5d756a3af719 | |
parent | 0cc528bc3fc6f11e7997a2f68bf4badb59b3117f (diff) | |
download | zpu-f4abb6c6014eb8a46236bf44eecea82f44124d75.zip zpu-f4abb6c6014eb8a46236bf44eecea82f44124d75.tar.gz |
a bit of info on implementing a UART
-rw-r--r-- | zpu/docs/zpu_arch.html | 10 |
1 files changed, 9 insertions, 1 deletions
diff --git a/zpu/docs/zpu_arch.html b/zpu/docs/zpu_arch.html index 5404057..67a572e 100644 --- a/zpu/docs/zpu_arch.html +++ b/zpu/docs/zpu_arch.html @@ -1582,7 +1582,15 @@ of the simpler ones: <a href="http://www.opencores.org/projects.cgi/web/uart/overview"> http://www.opencores.org/projects.cgi/web/uart/overview</a> - +<h2>Implementing your own UART / debug channel</h2> +The first thing you need to do is to choose a debug channel for your +hardware. This could be a UART, but it doesn't have to be. +<p> +Secondly you should write a small HDL module that interface between +the ZPU memory map of debug channel to the UART. This should + be relatively simple as all you need to do is to let the ZPU + query the FIFO in/out for busy flag and allow the ZPU to read/write + data to the UART via the memory map. <a name="zpu_core.vhd"/> <h1>About zpu_core.vhd</h1> The zpu_core.vhd has a single port memory interface. All data, code and IO is |