• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Functional Verification
  3. *E,OBJACC: Object must have write access: <object name>

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 66
  • Views 5887
  • 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

*E,OBJACC: Object must have write access: <object name>

prkroon
prkroon over 15 years ago

I am new to the forum so I do not know if the subject I post in this forum is the correct place.

Anyway, During simulation in ncsim I want to force an internal digital signal in the mixed signal design to a certain binairy value.

The signal in question is generated in vhdl and in my opinion a normal digital signal output.

However when I force it during simulation I get the following message:

*E,OBJACC: Object must have write access: <object name>

The <object name> is the signal/pin I force.

I searched in the online ncsim/simvision manuals and cadence site but sofar I could not find the cause of the error message.

So the question is why I can't force this digital signal, other signals in the design I can but some I can not giving me the discussed error message.

  • Cancel
Parents
  • TAM1
    TAM1 over 15 years ago

    As far as I know, there's nothing that tells you what the optimizer did or didn't do. It will always try to make the simulation run as fast as possible given the kinds of access you tell it you need. The only other kind of access I didn't mention that I commonly use is to add the option "-linedebug." This tells the simulator to keep track of what line of source code it is executing at any particular time and can be useful for single stepping thru the simulation. All of these options can slow the simulator down, so are turned off by default.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • TAM1
    TAM1 over 15 years ago

    As far as I know, there's nothing that tells you what the optimizer did or didn't do. It will always try to make the simulation run as fast as possible given the kinds of access you tell it you need. The only other kind of access I didn't mention that I commonly use is to add the option "-linedebug." This tells the simulator to keep track of what line of source code it is executing at any particular time and can be useful for single stepping thru the simulation. All of these options can slow the simulator down, so are turned off by default.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information