OpenCores
URL https://opencores.org/ocsvn/dbg_interface/dbg_interface/trunk

Subversion Repositories dbg_interface

[/] [dbg_interface/] [tags/] [sdram_test_working/] [rtl/] [README.txt] - Diff between revs 2 and 9

Go to most recent revision | Show entire file | Details | Blame | View Log

Rev 2 Rev 9
Line 43... Line 43...
//////////////////////////////////////////////////////////////////////
//////////////////////////////////////////////////////////////////////
//
//
// CVS Revision History
// CVS Revision History
//
//
// $Log: not supported by cvs2svn $
// $Log: not supported by cvs2svn $
 
// Revision 1.1.1.1  2001/09/13 13:49:19  mohor
 
// Initial official release.
 
//
// Revision 1.2  2001/06/01 22:22:35  mohor
// Revision 1.2  2001/06/01 22:22:35  mohor
// This is a backup. It is not a fully working version. Not for use, yet.
// This is a backup. It is not a fully working version. Not for use, yet.
//
//
// Revision 1.1  2001/05/18 13:12:09  mohor
// Revision 1.1  2001/05/18 13:12:09  mohor
// Header changed. All additional information is now avaliable in this README.txt file.
// Header changed. All additional information is now avaliable in this README.txt file.
Line 67... Line 70...
http://www.opencores.org/cores/DebugInterface/
http://www.opencores.org/cores/DebugInterface/
 
 
Documentation can also be found there. For direct download of the
Documentation can also be found there. For direct download of the
documentation go to:
documentation go to:
 
 
http://www.opencores.org/cgi-bin/cvsget.cgi/DebugInterface/Doc/DbgSupp.pdf
http://www.opencores.org/cgi-bin/cvsget.cgi/dbg_interface/doc/DbgSupp.pdf
 
 
 
 
 
 
 
 
OVERVIEW (main Features):
OVERVIEW (main Features):
Line 83... Line 86...
debugger or BS tester connects to the core via JTAG port.
debugger or BS tester connects to the core via JTAG port.
The Development Port also contains a trace and support for
The Development Port also contains a trace and support for
tracing the program flow, execution coverage and profiling
tracing the program flow, execution coverage and profiling
the code.
the code.
 
 
 
dbg_tb.v is a testbench file.
 
file_communication.v is used for simulating the whole design together with the
 
  debugger through two files that make a JTAG interface
 
dbg_top.v is top level module of the development interface design
 
 
 
 
 
 
COMPATIBILITY:
COMPATIBILITY:
 
 
- WISHBONE rev B.1
- WISHBONE rev B.1
Line 99... Line 107...
Mclk clock signal. Simulation should do the same.
Mclk clock signal. Simulation should do the same.
 
 
 
 
 
 
TO DO:
TO DO:
- Add reset and cpu stall signals that are related to the RISCOP register
- Add a WISHBONE master support if needed
- Add a WISHBONE master support
 
- Add support for boundary scan (This is already done, but not yet incorporated in the design)
- Add support for boundary scan (This is already done, but not yet incorporated in the design)
- Signal RecSelDepend is not connected anywhere, yet. Read the pdf for details on that.
 
 No newline at end of file
 No newline at end of file
 
 

powered by: WebSVN 2.1.0

© copyright 1999-2024 OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.