Stats

  • Locked Locked
  • Replies 9
  • Subscribers 50
  • Views 20190
  • 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

using command ncverilog cause hang issue

Jack Lee
Hi, I am Jack.I have something to verify about the ncverilog command.

I write the ncverilog command to compile and simulate my design:ncverilog   abc_tb.v -f abc_tb.f -l abc_tb.log  +ncelabargs+"-timescale 1ps/1ps" +access+rw(abc_tb.f is the filelist which contains all files required for this design) I face hanging issue while running simulation, when I remove the option +access+rw, the hang issue can be avoided.Why this can be happened?I have tried out with other tools like VCS, I have not experienced this type of issue, thanks for giving me some advices.
Parents

  • Hi Mickey,

     First thanks for your explanations and help.

     I would like to clarify one point: In my situation the time is frozen and delta cycles are not also counting up. Simulator doesnt respond to my pause command(I used both the pause button and ctrl+C).It only come out of its infinite run with multiple ctrl+Cs and that multiple ctrl+Cs are causing the simulator to terminate.

     When I try to do line-by-line debugging very close to the hanging time, I lost the yellow arror(it gets grayed out) somewhere close to that hanging time and I can't know where is the last statement executed before entering that infinite loop.It could be somewhere in one of those c library.

    If it was a delta cycle issue, it would be much and much more easy to debug as I can trace the code and see the feedback path, but now I can do simply nothing other then givin multiple ctrl+C commands end then let the simulator terminate.Therefore even if I enable a breakpoint of 1 delta cycles, simulator hangs before even a single delta cycle!!!!

    By the way, +nbasync option couldn't solve the issue, but it chaned the hanging time point. When I recompile the same design at different times, it also changes the hanging time point as well.

     How can I also check the compatibility of STIL DPV libraries, simulator and the compiler that I use for my .c files' compilation.

     Regards,

     Inan.

Reply

  • Hi Mickey,

     First thanks for your explanations and help.

     I would like to clarify one point: In my situation the time is frozen and delta cycles are not also counting up. Simulator doesnt respond to my pause command(I used both the pause button and ctrl+C).It only come out of its infinite run with multiple ctrl+Cs and that multiple ctrl+Cs are causing the simulator to terminate.

     When I try to do line-by-line debugging very close to the hanging time, I lost the yellow arror(it gets grayed out) somewhere close to that hanging time and I can't know where is the last statement executed before entering that infinite loop.It could be somewhere in one of those c library.

    If it was a delta cycle issue, it would be much and much more easy to debug as I can trace the code and see the feedback path, but now I can do simply nothing other then givin multiple ctrl+C commands end then let the simulator terminate.Therefore even if I enable a breakpoint of 1 delta cycles, simulator hangs before even a single delta cycle!!!!

    By the way, +nbasync option couldn't solve the issue, but it chaned the hanging time point. When I recompile the same design at different times, it also changes the hanging time point as well.

     How can I also check the compatibility of STIL DPV libraries, simulator and the compiler that I use for my .c files' compilation.

     Regards,

     Inan.

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.