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

Subversion Repositories tv80

[/] [tv80/] [trunk/] [doc/] [tv80_docs.xml] - Diff between revs 55 and 84

Go to most recent revision | Only display areas with differences | Details | Blame | View Log

Rev 55 Rev 84
tv80 Core Documentation
tv80 Core Documentation
OpenCores.org
OpenCores.org
ghutchis@opencores.org
ghutchis@opencores.org
General
General
private
private
XML
XML
Extensible Markup Language
Extensible Markup Language
A synthesizable 8-bit microprocessor which is instruction-set compatable
A synthesizable 8-bit microprocessor which is instruction-set compatable
with the Z80, targetted at embedded and system-on-a-chip designs.
with the Z80, targetted at embedded and system-on-a-chip designs.
    
    
        The tv80 core was created as a Verilog port of the VHDL T80 core, for use as a maintenence processor inside an ASIC.
        The tv80 core was created as a Verilog port of the VHDL T80 core, for use as a maintenence processor inside an ASIC.
            The tv80 has been modified since then for better synthesis
            The tv80 has been modified since then for better synthesis
            timing/area results, and to incorporate several bug-fixes.
            timing/area results, and to incorporate several bug-fixes.
        The T80, and the tv80 derived from it, attempt to maintain the
        The T80, and the tv80 derived from it, attempt to maintain the
            original cycle timings of the Z80, but have radically different
            original cycle timings of the Z80, but have radically different
            internal designs and timings.  With its target being ASIC and
            internal designs and timings.  With its target being ASIC and
            embedded applications, the tv80 does not attempt to maintain
            embedded applications, the tv80 does not attempt to maintain
            the original pinout of the Z80.
            the original pinout of the Z80.
    
    
    This section tracks synthesis results in various technologies.  LSI 10K technology is
    This section tracks synthesis results in various technologies.  LSI 10K technology is
       used as a baseline because the library ships with Design Compiler.  
       used as a baseline because the library ships with Design Compiler.  
  
  
  
  
    Component         Clock Speed    Area     Technology (units)
    Component         Clock Speed    Area     Technology (units)
    ================  ===========  ========  =====================
    ================  ===========  ========  =====================
      tv80              33 Mhz     10733      lsi_10k (gates)
      tv80              33 Mhz     10733      lsi_10k (gates)
      simple_gmii       33 Mhz      1247      lsi_10k (gates)
      simple_gmii       33 Mhz      1247      lsi_10k (gates)
  
  
  
  
    
    
  The TV80 design includes a number (one, at this point) of peripherals.  These peripherals
  The TV80 design includes a number (one, at this point) of peripherals.  These peripherals
      are hardware-synthesizable, but may not be fully tested or functional.
      are hardware-synthesizable, but may not be fully tested or functional.
  
  
    This block presents a GMII interface on one side and a TV80 processor interface on
    This block presents a GMII interface on one side and a TV80 processor interface on
        the other.  The processor-side controls are all mapped into I/O-space.  The block
        the other.  The processor-side controls are all mapped into I/O-space.  The block
        can only process a single packet in each direction at one time.  This is only really
        can only process a single packet in each direction at one time.  This is only really
        a limitation on the RX side, where any incoming packets will be dropped until the
        a limitation on the RX side, where any incoming packets will be dropped until the
        processor removes the first packet from the RX buffer.
        processor removes the first packet from the RX buffer.
    The GMII interface is signalling only, and does not support 10/100 operation, half duplex
    The GMII interface is signalling only, and does not support 10/100 operation, half duplex
        mode, flow control, or any other aspects of 802.3.
        mode, flow control, or any other aspects of 802.3.
    
    
        This block consumes 3 bits of I/O address space.  The register addresses below are
        This block consumes 3 bits of I/O address space.  The register addresses below are
            relative to the configurable base address of the block, which must be aligned to an
            relative to the configurable base address of the block, which must be aligned to an
            8-byte boundary.  Registers 0x6 and 0x7 are reserved.
            8-byte boundary.  Registers 0x6 and 0x7 are reserved.
        
        
            Bit 0 of the status register indicates that a packet is available in the RX buffer.
            Bit 0 of the status register indicates that a packet is available in the RX buffer.
                This bit will be cleared when the last byte of data is read out of the RX buffer.
                This bit will be cleared when the last byte of data is read out of the RX buffer.
            Bit 1 is set when the packet in the TX buffer has finished transmitting.  This bit
            Bit 1 is set when the packet in the TX buffer has finished transmitting.  This bit
                will be cleared when the first byte of data of the next packet is written into the
                will be cleared when the first byte of data of the next packet is written into the
                TX buffer.
                TX buffer.
            This register is read-only.
            This register is read-only.
        
        
        
        
            Bit 0 controls sending packets.  When a 1 is written to this bit, the data in
            Bit 0 controls sending packets.  When a 1 is written to this bit, the data in
                the TX buffer will be sent as a single packet.
                the TX buffer will be sent as a single packet.
           This register is write-only.
           This register is write-only.
        
        
        
        
            This register contains the low 8 bits of the length of the packet currently
            This register contains the low 8 bits of the length of the packet currently
                residing in the RX buffer.
                residing in the RX buffer.
            This register is read-only.
            This register is read-only.
        
        
        
        
            This register contains the high 8 bits of the length of the packet currently
            This register contains the high 8 bits of the length of the packet currently
                residing in the RX buffer.
                residing in the RX buffer.
            This register is read-only.
            This register is read-only.
        
        
        
        
            This register contains the next byte of data in the RX packet buffer.
            This register contains the next byte of data in the RX packet buffer.
            This register is read-only.
            This register is read-only.
        
        
        
        
            Writing to this register puts data in the TX packet buffer.  This register does
            Writing to this register puts data in the TX packet buffer.  This register does
               not perform bounds checking; it is the program's responsibility not to write more
               not perform bounds checking; it is the program's responsibility not to write more
               data than the size of the TX buffer.
               data than the size of the TX buffer.
           This register is write-only.
           This register is write-only.
        
        
    
    
  
  
 
 
Environment memory space is divided into a 32k ROM region and a 32k RAM
Environment memory space is divided into a 32k ROM region and a 32k RAM
region, as follows:
region, as follows:
  0000-7FFF:  ROM
  0000-7FFF:  ROM
  8000-FFFF:  RAM
  8000-FFFF:  RAM
Environment I/O space is allocated as follows:
Environment I/O space is allocated as follows:
  00-0F:  Unused
  00-0F:  Unused
  10-1F:  Test devices
  10-1F:  Test devices
  20-7F:  Unused
  20-7F:  Unused
  80-9F:  Environment control
  80-9F:  Environment control
  A0-FF:  Unused
  A0-FF:  Unused
 
 
 
 
The tv80 environment is controlled by the program under simulation.  The
The tv80 environment is controlled by the program under simulation.  The
program can affect the environment through a set of control registers,
program can affect the environment through a set of control registers,
which are mapped into I/O space.
which are mapped into I/O space.
  
  
    
    
        Write '01' to end simulation with test passed
        Write '01' to end simulation with test passed
        Write '02' to end with test failed
        Write '02' to end with test failed
        Write '03' to turn on dumping
        Write '03' to turn on dumping
        Write '04' to turn off dumping
        Write '04' to turn off dumping
    
    
  
  
  
  
        Write characters to this port one at a time.  When the
        Write characters to this port one at a time.  When the
        newline ('\n', ASCII 0x0A) character is written, the
        newline ('\n', ASCII 0x0A) character is written, the
        environment will print out the collected string.
        environment will print out the collected string.
  
  
  
  
    
    
        Bit[0] enables the timeout counter,
        Bit[0] enables the timeout counter,
        Bit[1] resets the counter to 0.
        Bit[1] resets the counter to 0.
        Timeout counter defaults to enabled at simulation start.
        Timeout counter defaults to enabled at simulation start.
    
    
  
  
  
  
   
   
        Holds 16-bit timeout value (amount of time in clocks before
        Holds 16-bit timeout value (amount of time in clocks before
        timeout error occurs).
        timeout error occurs).
   
   
  
  
  
  
    
    
        When set, starts a countdown (in clocks) until assertion of
        When set, starts a countdown (in clocks) until assertion of
        the INT_N signal.
        the INT_N signal.
   
   
  
  
  
  
    This register holds the checksum value of all data
    This register holds the checksum value of all data
       written to the accumulate register.  The checksum is a simple
       written to the accumulate register.  The checksum is a simple
       twos-complement checksum, so it can be compared with a CPU-generated
       twos-complement checksum, so it can be compared with a CPU-generated
       checksum.
       checksum.
    This register is readable and writeable.  Writing the register sets
    This register is readable and writeable.  Writing the register sets
       the current checksum value.
       the current checksum value.
  
  
  
  
    This write-only register adds the written value to the value
    This write-only register adds the written value to the value
       contained in the Checksum Value register.
       contained in the Checksum Value register.
  
  
  
  
    This register increments every time it is read, so reading it
    This register increments every time it is read, so reading it
       repeatedly generates an incrementing sequence.  It can be reset
       repeatedly generates an incrementing sequence.  It can be reset
       by writing it to a new starting value.
       by writing it to a new starting value.
  
  
 
 
 
 
     The minimum toolchain required to simulate the tv80 is the
     The minimum toolchain required to simulate the tv80 is the
         CVer Verilog simulator, and the
         CVer Verilog simulator, and the
         SDCC compiler/assembler/linker.  In
         SDCC compiler/assembler/linker.  In
         addition, to run the tvs80 instruction
         addition, to run the tvs80 instruction
         test suite, the DOSBox DOS emulator
         test suite, the DOSBox DOS emulator
         is required.
         is required.
     
     
 
 
 
 
   Most of the tests in the tv80 environment are written in C, and should
   Most of the tests in the tv80 environment are written in C, and should
       be compiled with the sdcc compiler.
       be compiled with the sdcc compiler.
   
   
     
     
      The tvs80 test is different than the rest of the tests, and is
      The tvs80 test is different than the rest of the tests, and is
         written in its own flavor of assembly language.  This test provides
         written in its own flavor of assembly language.  This test provides
         a fairly comprehensive Z80 instruction test.
         a fairly comprehensive Z80 instruction test.
      The assembler for this test only runs under DOS.  To assemble
      The assembler for this test only runs under DOS.  To assemble
          under Unix/Linux, the "dosbox" DOS emulator is required.  A script
          under Unix/Linux, the "dosbox" DOS emulator is required.  A script
         to run the assembler under dosbox, as well as the tvs80.asm source,
         to run the assembler under dosbox, as well as the tvs80.asm source,
         is checked in under the "tests/tvs80" directory.
         is checked in under the "tests/tvs80" directory.
     
     
 
 
    
    
        
        
            
            
                VHDL T80 Core
                VHDL T80 Core
                
                
                    OpenCores.org
                    OpenCores.org
                
                
            
            
        
        
        
        
            
            
                Small Device C Compiler
                Small Device C Compiler
            
            
        
        
        
        
            
            
                GPL Cver Simulator
                GPL Cver Simulator
                
                
                    Pragmatic C Software
                    Pragmatic C Software
                
                
            
            
        
        
        
        
            
            
                DOSBox
                DOSBox
            
            
        
        
    
    
 
 

powered by: WebSVN 2.1.0

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