Stats

  • Locked Locked
  • Replies 5
  • Subscribers 48
  • Views 14408
  • 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

Memory writes from separate execution thread

archive

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


Originally posted in cdnusers.org by slide_o_mix
Parents

  • 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


    Originally posted in cdnusers.org by volker.wegner
Reply

  • 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


    Originally posted in cdnusers.org by volker.wegner
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.