Stats

  • Replies 2
  • Subscribers 160
  • Views 12282
  • Members are here 0
More Content

Looping folders fail after x numbers of entries ???

Romme

Hello dear Friends.

  We have some skill tools that change properties on footprints and other files. We can do this perfectly on 1 file, 10 files and so on up. But it fails and kills Allegro with error messages after eg 250 footprints. Is there a "undocumented counter" for forci Allegro to be "rebooted".

 

  Imagine a folder of 1500 footprints, for which You need changing a properties in each footprint. It is rather anoiying to experience that one have to do this in 6 - 8 tasks, due to Allegro chrashes after 250 runs.

 

  Anyone who have any clues on why ?

BRGD

  Klavs.

 

  •  Greetings Klavs,

    Without looking over the code, my first guess would be the crashes are memory-related, perhaps due to the code not saving and closing one footprint before opening another causing Allegro memory footprint to "grow".

     As a kludge you could:

    1- modify the looping SKILL routine to read footprint filenames from a file when passed the filename as an argument, kind of like this

     

    procedure( fixem( ffilename)
      innfile = inFile( ffilename)
      while( gets( innline innfile) != nil
        call_yer_func( innline)   ; innline contains a footprint name
      );end-while
      close( ffilename);
    );end-proc

    then divvy up your 1500 footprints amongst 7 files such that each files contains slightly less than 250 names. But that's pretty ugly. A better kludge would be a Perl script that read all the footprint names from one file, kept a count, and opened/closed an Allegro session with the -nographic option on each count % 200 == 0, feeding call_yer_func filenames as it goes.

    HTH,

    Chris Walters

    local Cadence guru-at-large

  • Hello Chris.

     

      That is not the way i do open the footprint, i use axlOpenDesign() and axlKillDesign() from this i do not know if there is a more "deep" way to "reset" the allegro. Though i haven tryed the GC() command yet due to the warnings.

     

      Anyone out there who knows what can go wrong with use of GC(), exept that windows dies and needs reinstallation :-).

     

    BRGD

      Klavs.

     

Cadence Guidelines

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.