Stats

  • Locked Locked
  • Replies 3
  • Subscribers 63
  • Views 1538
  • 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

"Word too long" error while running write_vectors step in Encounter test

krishcit

Hi,

I am getting an error called "word too long" while executing write_vectors step in command line prompt of ET with version 8.1.200.

A particular keyword in the write_vectors step namely "releasepioffsetlist" is having 173 primary inputs listed under it and assigned with offset values.

As a workaround i reduced it to 164 primary inputs under this keyword then it is working fine (vectors are getting writtern).

Please help me on this issue.

Thanks

Krishnaraj

  •  Hi Krishna,

                 I guess this is issue with linux, there is some limit in linux when considering the hash/length of a variable (may be we can change this limit with some settings but i am not aware of that).

                        I also had the same issue when assiging a variable with some details, below are the details of the issue i had and the way we sloved.

     Issue occured when i used:

    echo "\n\t$toolLogFiles" >> logs/infralogs/$stageName.log

     

    Issue sloved with:

    foreach logFile ($toolLogFiles)
    echo "\n\t$logFile" >> logs/infralogs/$stageName.log
    end

     

                    Hope you can use similar method to get rid of the issue.

     

    regards

    deepak.

  •  Hi Deepak,

    Thanks a lot for your reply.

    If it is like there is a limit for a command length in unix then can you let me know what is the commnad line buffer size?

    How can i change the command line buffer size?

     Thanks

    Krishnaraj 

  • Krishnaraj,

       Is there a reason you are using version 8.1.200 of our software?  We are releasing 11.1 in a couple of weeks which puts you 3 major releases behind.  There have been command, variable and character length issues in the past.  Most of those have been fixed.  Please try your design with a a more recent released version and see if you have the same issue.

     

    Andy Hughes

    ET Product Engineer/Architect

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.