Thursday, February 09, 2012     Register | Login | Search | Contact Us
     
   
     
     

Many of you already received communications about the move of the Cadence user community into cadence.com. And many of you have already joined, with over 4000 registrations in the first two weeks.

The new Cadence Community enhances the ability of Cadence users to connect and collaborate. In addition to moving the community into cadence.com -- enabling single sign-on for community, Sourcelink and Cadence events -- the new site is organized around nine technology segments, giving you easy access to product information, training, forums and blogs. Some of the new features include:
  • Ability to respond to posts via e-mail
  • Technology-specific blogs
  • Latest Web 2.0 social networking capabilities
  • Public profile options
  • Private messaging
  • Friends lists
Visit the new Cadence Community today at www.cadence.com/community and join the discussions!

Registration note: Due to the scope of the enhancements and the new SSO registration system, we were not able to migrate existing cdnusers.org member accounts. So new registrations are required, but this enables a broader set of functionality we think you'll enjoy.

Forum note: Under the guidance of forum moderators, we have taken the 20+ cdnusers.org forums and consolidated them into 11 forums on the new site. Posts have been brought over so you can leverage that posting history. CDNusers forums will be set to read only starting 7/30, and cdnusers.org will be redirected to the new community on 8/4.

Best regards,
Mike and Tom

Michael A. Catrambone - Steering Committee Chairman
Distinguished Engineer
PCB/Mechanical
UTStarcom, Inc.

Tom Diederich
Cadence Community Manager
Home
Forums
Forums > Functional Verification > Simulation, Acceleration, Emulation

Subject: Memory writes from separate execution thread
Posting to forums is available to community members only.
Login or Register
Rate this topic:
   
Author Messages
slide_o_mix
Posts: 3
Online: User is Offline
10/22/2007 3:30 PM  
We have developed a set of scripts such that we source one on the Palladium and it waits for command files to be present, then from a remote machine we can copy a command file over to the server and have our commands executed. In the sourced script, I have something like the following:

after 1000 check_command_files
vwait stop

and inside the check_command_files proc, I look for certain files and then source that file.

The sourced file might contain other "source" lines.

The problem I am running into is that writing to memory areas from those secondary sourced files. When I try and source them, the memory writes are not completing correctly, I get an error that it could not complete.

Is there an issue with multiple sourcing like that? Is there anything I need to do in my TCL scripts to make the variables from higher level sourced scripts available? Is there something I need to do special to write to memory regions from those sourced scripts?

Thanks

Alex
volker.wegner
Posts: 4
Online: User is Offline
10/22/2007 11:51 PM  
Hi Alex,

there is nothing wrong with nesting various source commands like you described it. However, since you point to global/local variables: You can declare variables to be known locally, e.g.:

proc my_mem_write {} {
    # memory instance and memory content come from elsewhere
    global memInst memCont
...
}

With that $memInst and $memCont are now also known within my_mem_write.

Hope this helps. If not, please provide more informations, like the error message, and the procedures you're using.

Best regards, Volker@Cadence.com
slide_o_mix
Posts: 3
Online: User is Offline
10/23/2007 7:06 AM  
Thanks for the reply, I have one follow up question. If I am sourcing the secondary scripts which do memory writes inside a proc, does that mean they are executed within the scope of that proc and thus the "global" would be required in those scripts? I think that is what you are referring to, but I wanted to make sure. Thanks again!
volker.wegner
Posts: 4
Online: User is Offline
10/23/2007 7:12 AM  
Hi Alex,

based on your comments I believe that, yes, it is necessary to make the global variable visible within your proc.

Let me know if this solves the issue. If not, please provide error msg and (skeleton) scripts.

Best regards, Volker
slide_o_mix
Posts: 3
Online: User is Offline
10/23/2007 7:29 AM  
That looks like it worked, I appreciate the help!
volker.wegner
Posts: 4
Online: User is Offline
10/23/2007 7:30 AM  
You're welcome!
Posting to forums is available to community members only.
Login or Register
Forums > Functional Verification > Simulation, Acceleration, Emulation > Memory writes from separate execution thread


ActiveForums 3.6
     
Copyright 2006 Cadence Design Systems, Inc.