Stats

  • Locked Locked
  • Replies 2
  • Subscribers 64
  • Views 13281
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

regarding URM development

archive

hi..
       iam new in developing URM methodolgy....now am doing APB using URM..... in this I am considering  only one master & one slave..
 
 Doubt:
              Is arbitration necesary for this to develop URM? if it necessary how i have to resolve? if it is not necessary how i have to create master_monitor, master_seq_drv......

              please anyone help me regarding this issue..

Thanks & regards
raghavendra


Originally posted in cdnusers.org by raghavendrap

  • Hi Raghavendra,

    URM does not require your models to include arbitration and it is not appropriate for a bus like APB that can only have a single master. For the system you describe, you should create one master agent and one slave agent - these can be similar to the agents in the xbus example provided in the IPCM release.

    The master sequence driver should generate a series of read or write transactions that the master agent will drive onto the APB bus. The master monitor will independently watch the APB bus and detect the how master is driving it and extract the relevant data (read/write, address, etc).

    The slave sequence driver should control how the slave responds to read/write commands on the bus. The slave monitor should detect bus activity corresponding to that particular slave (a real APB system would have multiple slaves so your model should take account of that).

    You could also have an overall bus monitor (like the xbus example) that is accessed from the agent monitors and coordinates the sequence driver activity.

    Hope that gives you some ideas.

    Regards,
    Dave


    Originally posted in cdnusers.org by dl_doulos

  • Thanks dave..i got some idea what you said & i will get back to you if any suggestions needed


    Originally posted in cdnusers.org by raghavendrap

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.