Question about emigrating to Linux + IC 5.0

Dear All:



I'm going to change my design enviroment from Sun + IC 4.4.3 to Linux
+ IC 5.0. However, I'm not sure if the data we had could be translated
to new enviroment or not.

How to translate those design data, like schematics, layouts? Does
anyone have such experience?

Appreciate your help.


Regards

Vincent

 

hi,
Just copy over your design to the linux machine.
For example:

scp -r your_design [email protected]:/ee/Vincent/ADC/

Then set up the environment variables in the linux machine.

sincerely

 

Vincent:
You shouldn't have to do any translation on your design data to move
from 443 to 50. 434 to 50 or CDBA to OA would require translation.

 

Vincent,

You don t need to leave your homeland either. Most of those who packed for Finland now regret it: Penguins smell a lot, and that s bad BBQ material.

 

You don't even have to copy the DFII data from Sun to Linux.

We, in flow engineering, use both Sun & Linux machines interchangably
on the _same_ IC5033 & IC5041 DFII CDB & OpenAccess data without
problems.

We store the DFII data on a common terabyte-sized array
(using Veritas for large partitions)
in the simple structure for each chip we build:
design/{custom_oa,custom_cdb,digital} (for design data)
doc/{install,flow,hints} (for documents)
share/{gpdk090,gsclib090,giolib090} (for foundry-supplied data)

If you must copy the design & foundry data, be (very) careful about
following symbolic links & permissions! Make sure your command does
what you need it to to. (Test on a trivial test case first).

Based on years of experience, we use the "cpdir" alias extensively
in our company-wide cshrc file (instead of the flawed UNIX '-rp' which
doesn't handle links the way we like them to be handled):

alias cpdir 'pushd \!:1 && tar cf - . | ( popd && mkdir -p \!:2 &&
pushd \!:2 && tar xfBp - ) && popd'

USAGE:
% cpdir /path/to/source/directory /path/to/target/directory

John Gianni