+ Post New Thread
Results 1 to 4 of 4
  1. #1
    Member level 1
    Points: 1,074, Level: 7

    Join Date
    Oct 2008
    Posts
    38
    Helped
    4 / 4
    Points
    1,074
    Level
    7

    tetramax violations

    Hi All TetraMax Users,

    Please Help Me !
    The error I am getting while during the DRC checking is following :
    " Wire gate (12) failed contention ability check for drivers 469 and 465. (Z3-1)"
    I am not able to troubleshoot this error. I am wondering about these 469 and 465,
    what are these two ?

    Thanks in advance.
    JaY...

    •   AltAdvertisment

        
       

  2. #2
    Junior Member level 3
    Points: 816, Level: 6

    Join Date
    Jun 2009
    Posts
    25
    Helped
    7 / 7
    Points
    816
    Level
    6

    tetramax forum

    Hi Jay,

    Here is my take :)

    The two numbers denote the gates driver IDs.

    To trouble shoot:
    1) Did you try right clicking on the message , select "Help Topic" for more details on Z3 violation? This will bring up the simulation data. Might be that would help you.
    2) or analyze violation Z3-1?
    3) This will open the schematic viewer and will show you the simulated data which leads to the contention.
    4) How about bringing up these gatesID in GSV?
    5) Input output direction of these gates?

    Thanks,
    Daman


    1 members found this post helpful.

    •   AltAdvertisment

        
       

  3. #3
    Member level 1
    Points: 1,074, Level: 7

    Join Date
    Oct 2008
    Posts
    38
    Helped
    4 / 4
    Points
    1,074
    Level
    7

    tetramax, z3

    Hi Daman ,

    I tried doing trouble shooting and got some hints about how
    to remove this error. There can be three different ways of
    handling this:
    1) By Ignoring this error using the cmd "set Rules <errorID> Ignore. I tried doing this also, but end up with Scan Blocking Rule violation.
    2) By initializing the Primary Input constraint in such that
    the contention can be overcome. This process seems
    tough one. I gues the changes has to be made in Protocol
    file( may be in test_setup macro)
    3) By modifying the circuit itself.

    It seems for me these are as tedious process, I want
    some suggestion in overcoming this in quicker way.

    Thanks for your response.
    With Regards,
    JaY

    Added after 2 hours 52 minutes:


    Some how I got success in resolving the Z3 violation. I did some
    modification in source netlist file. It was some what intuitive trial.
    I will post the details.

    " Intuition always leads over the Logic "



    •   AltAdvertisment

        
       

  4. #4
    Full Member level 2
    Points: 2,558, Level: 11
    Achievements:
    7 years registered

    Join Date
    Oct 2008
    Location
    Hyderabad
    Posts
    123
    Helped
    41 / 41
    Points
    2,558
    Level
    11

    what drc violation

    try this one in ur source netlist (if it suits)

    http://www.asic-dft.com/Bus%20Contention.html


    2 members found this post helpful.

--[[ ]]--