Stats

  • Locked Locked
  • Replies 3
  • Subscribers 92
  • Views 13304
  • 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

[SOC Encounter] ERROR (cannot malloc)

Yusuf

I have a problem in running SOC Encounter. During the 'optDesign -preCTS' (after placement), Encounter is terminated with this message 

>Nr of prerouted/Fixed nets = 1164
>routingBox: (200 400) (26039800 26039600)
>coreBox:    (620000 620000) (25420000 25420000)
>**ERROR: (SOCSYUTIL-15):    Cannot malloc type "trsSNode" size=744623712 bytes.
>Probably ran out of virtual memory.

>*** Memory Usage v0.144 (Current mem = 2407.844M, initial mem = 62.289M) ***

I running this in the Linux machine with 32Gbyte memory. This problem occors on both SOCE 8.1 and 7.1 version.

Instance number of design is 400K and chip size is 13mm x 13mm

Can I know the reason of tool termination or any solutions? I would really appreciate...

Thanks,

  • I am affraid that your job is too big for your machine.

    Try it on a 64bit machine...

    I see in the doc the following nanoroute attribut (setNanoRouteMode):

    -envAdvancedIntegration {true | false}

    Reduces the router's memory footprint in most designs, allowing it to route larger designs. This parameter is most effective when you are routing an unrouted design. Using this parameter when you route a design with a 32-bit machine allows the machine to handle large designs that could not be routed otherwise.
    Default: false

    It may help you.

    Pat.

  •  Are you running encounter in 64-bit mode?

    encounter -64

  • Thanks, PatBoug and Kari --

    Let me try it with 64-bit mode. Actually, there is library problem at 64bit mode now (libXm.so.3: cannot open shared ...) I will install the librarary and try it.

     

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.