Stats

  • Locked Locked
  • Replies 1
  • Subscribers 126
  • Views 12922
  • 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

Abstract generator ver 5.6

Satendra

Dear Sir,

I am using Abstract genertor 5.6. 

The exact version detail is

@(#)$CDS: ui version 6.1.3. 02/05/2009 20:51 (cic612lnx) $

 

But I am getting these warning/error


*WARNING* dbDeleteShape: A memory allocation for 2147483648 bytes failed.
 The process heap is 1047MB, and OpenAccess is using 1039MB.
 The available system memory is 3574MB, and physical system memory is 7988MB.

*WARNING* dbCreatePinOnTerm: A memory resize for 2147483648 bytes failed.
 The process heap is 1047MB, and OpenAccess is using 1039MB.
 The available system memory is 3573MB, and physical system memory is 7988MB. 

 

Because of this I am not able to generate the LEF file.

 It seems that the issue is with the new abstract generator tool that comes with IC6.1. 

It accumulates all the dumps from the previous pins extraction information and hence reaches the upper limit.

 It clearly looks like a big bug in the design as no one can ever be able to generate any macro block with this tool.

Satendra

 

Parents

  •  Hi,

    starting with ISR9 of 6.1.3 we support a 64-bit executable of abstract. To be launched with:

    abstract -64 &

    From ISR6 onwards there is also an environment setting to enhance the memory usage:

    absSetOption( "OptimizeBigDesignMemory" "true")

    Regards,

    Marc

Reply

  •  Hi,

    starting with ISR9 of 6.1.3 we support a 64-bit executable of abstract. To be launched with:

    abstract -64 &

    From ISR6 onwards there is also an environment setting to enhance the memory usage:

    absSetOption( "OptimizeBigDesignMemory" "true")

    Regards,

    Marc

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.