• 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. Custom IC SKILL
  3. update progress bar in real time

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 143
  • Views 14831
  • 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

update progress bar in real time

mlea
mlea over 9 years ago

Hi,

im using ipcBeginProcess commands to launch two external process, and trying to update a progress bar :

the first process run generate  verilog netlist .

the second one phrase the log file of the generation process and update a progress bar accordingly.

I have two problem 

1. the progress bar got freeze out while the first process is running.

2. the first process exit code become alive only if i use ipcwait(first_process)

this is what i do :

procedure(simTerm(cid1 exit)
printf("Simulator expired with exit status = %L\n" exit)
exitCode=exit
)
procedure(handler(cid1 data)
printf("\n Date:%s\n" data)
)
procedure( simErr(cid1 err)
printf("Error %L Msg: %s\n" cid1 err)
)
procedure(handler2(cid2 data)
myvar=data;
printf("\n%s\n" data)
)

exitCode=nil

myvar=nil

cid1=ipcBeginProcess(strcat( pwd "/libFlow/" libname "/" cellname "/verilog/" "si.csh") "" "handler" "simErr" "simTerm" )
ipcSleep(1)
cid2=ipcBeginProcess(strcat( pwd "/readSiLogFile.pl") "" "handler2")

ipcSleep(1)

;; now launching the progress  bar

hiDisplayProgressBox(
?name 'myBar
?banner "verilog progress"
?text "Run completed.. "
?callback "printf(\"Done\n\")"
?totalSteps 10
?autoClose t
)

;; now running a while loop to check when exit status  cid1 

while(!exitCode

  while( myvar

do something - update progress bar -hihiSetProgressAndText....

        )

)

this make the progress bar freeze, and the while loop is endless( the exitCode variable never get "alive").

i guess this is because SKILL dont see the any exitCode/myvar variable  while its inside the loop, even though the cid1 process was launched

with communication channels. 

but if I do :

while(!exitCode

  ipcWait(cid1)

        )

.

.

.

;;and  only now  update the progress bar with hihiSetProgressAndText(myBar 4 "running") 

this loop run and terminate but :

1. virtuoso is freeze as long the while loop running

2. the progress bar is freeze and blank out

3. it is impossible to update the progress bar in real time , only after the verilog netlist process was terminated.

i couldn't find any real example/explanation on the progress bar. should it be execute with ipcbeginProcess?

thx

meny

  • Cancel
  • mlea
    mlea over 9 years ago
    i solved this issue by modify the code to :

    while(ipcIsAliveProcess(cid1) && !exitCode
    ipcSleep(2)
    if(!rexMatchp("Running netlisting" myvar ) then

    hiSetProgressAndText(myBar 2 "Running netlisting")
    printf("stage1\n")

    )

    ipcSleep(1)
    if(!rexMatchp("Initializing from libInit.il for library tsmcN28" myvar ) then

    hiSetProgressAndText(myBar 5 "Initialize libInit.il")
    printf("stage2\n")
    )


    ipcSleep(1)
    if(!rexMatchp("CELL NAME VIEW NAME NOTE" myvar ) then

    hiSetProgressAndText(myBar 7 "Grouping..")
    printf("stage3\n")
    )


    ipcSleep(1)

    if(!rexMatchp("End netlisting" myvar ) then

    hiSetProgressAndText(myBar 9 "Finish")
    printf("stage3\n")
    ipcKillProcess(cid1)
    )

    ipcSleep(1)


    )
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 9 years ago

    Hi Meny,

    Glad you've got it working, but I don't think this is the right way to do this. You are using a polling model which is still holding up the Virtuoso UI except is checking between ipcSleep calls.

    Better would be to use a fully-asynchronous approach and get your data handler / exit handler to update the progress bar. That way there's no need for anything to wait or sleep at all, and Virtuoso would remain responsive.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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