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

Subversion Repositories tv80

[/] [tv80/] [tags/] [rel_1_0/] [doc/] [tv80_docs.xml] - Diff between revs 35 and 55

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

Rev 35 Rev 55
Line 1... Line 1...
 
 
 
 
 
 
 
 
 
 
 
 
 
 
tv80 Core Documentation
tv80 Core Documentation
 
 
Line 31... Line 31...
            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
 
       used as a baseline because the library ships with Design Compiler.  
 
  
 
  
 
    Component         Clock Speed    Area     Technology (units)
 
    ================  ===========  ========  =====================
 
      tv80              33 Mhz     10733      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
 
      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
 
        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
 
        a limitation on the RX side, where any incoming packets will be dropped until the
 
        processor removes the first packet from the RX buffer.
 
    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.
 
    
 
        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
 
            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.
 
                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
 
                will be cleared when the first byte of data of the next packet is written into the
 
                TX buffer.
 
            This register is read-only.
 
        
 
        
 
            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.
 
           This register is write-only.
 
        
 
        
 
            This register contains the low 8 bits of the length of the packet currently
 
                residing in the RX buffer.
 
            This register is read-only.
 
        
 
        
 
            This register contains the high 8 bits of the length of the packet currently
 
                residing in the RX buffer.
 
            This register is read-only.
 
        
 
        
 
            This register contains the next byte of data in the RX packet buffer.
 
            This register is read-only.
 
        
 
        
 
            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
 
               data than the size of the TX buffer.
 
           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:

powered by: WebSVN 2.1.0

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