LOGIN   :::   RECOVER PASS   :::   GET ACCOUNT    
Browse
  • Projects
  • Code (CVS)
  • Forums
  • News
  • Articles
  • Polls
  •  
    OpenCores
  • FAQ
  • CVS HowTo
  • Mission
  • Media
  • Tools
  • Sponsors
  • Mirrors
  • Logos
  • Contact us
  •  
    Tools
  • Search
      
  • Download Cores (CVSGet)
  •  
    More
  • Wishbone
  • Perlilog
  • EDA tools
  • OpenTech CD
  •  
    Navigation: All forums > Cores > Message List > Message Post

    Message

    Reply | Reply all
    Date Prev | Date Next | Thread Prev | Thread Next Date Index | Thread Index

    From: unmesh<unmesh@s...>
    Date: Tue Oct 19 12:28:20 CEST 2004
    Subject: [oc] AHB monitor
    Top
    Typically a verification environment would consist of
    1. The RTL you are wanting to test...let's assume an AHB slave and the bus arbiter.
    2. The BFM ( Bus Function Model ) which generates all the stimulus nessecary to test the RTL .... in our case the BFM would be an AHB master.
    3. There would be a scoreboard which will check the data on the bus against the expected data ( expected data generation will depend on the functionality of the peripheral connected to your AHB slave ).
    4. A protocol checker ... the monitor which will check whether all transactions have been conducted in accordance to the AHB protocol. This is typically done using assertions.
    5. A functional/code coverage block.

    I would typically develop the monitor last when I have atleast a basic transfer going between my BFM and the RTL and the scoreboard is atleast partially functional.
    In anycase u need to explain a little more about your environment before anyone can help u or give u any suggestions.
    regards
    Unmesh



    -------------- next part --------------
    An HTML attachment was scrubbed...
    URL: attachment.htm

     
    Copyright (c) 1999 OPENCORES.ORG. All rights reserved.