Alberto Palacios Pawlovsky wrote: I used the Alliance tools for about two weeks in a Windows PC and two days ago I started the installation of them in a PowerMac running MKLinux(R3). For this I downloaded the 3.2b version of the common package and the sources of version 3.2c. I follow the instructions of the README and tried the installation. After two days of a try-fail process I could compile all the tools with the exception of yagle and tas that seems not to be included in the sources. A new distrib should be ready in a few month. A lot of bugs and compile problems have been fixed...but we don't have any power mac... Could these changes and renaming made graal do not work,made scr change the units in the al files and made druc run without stopping and consume all memory until bring the xwindow environment down? Any advise or help will be really appreciatte. In the mean time I will continue using your tools in the PC(linux) environment. I don't think so... please wait till the new distrib be ready Now, regarding this, I found that when running the amd tutorial if one use asimut -b -c amd ....asimut ends with a fatal error 101 executing 'beh_abl2gex': unknown terminal operand ''d'' but if one use the command used in the makefile asimut -bdd -b -d It ends without noticing any errors. Is this correct? No... We are looking for this bug. Normally 'dont care' are replaced by zeros. Here in Japan since 1996 the universities has access to (low cost) foundry services provided through the University of Tokyo's VDEC (VLSI) center. Also commercial software licenses are provided at low cost but the reason that impede their use is the (still) high cost of the workstations needed to run them. Pad and cell libraries are provided for four technologies (ranging from 1.2um to 0.5um) in GDSII format. I am planning to use your tools with these libraries (if possible). it will be difficult! I would appreciatte any information that could help me in translating the technology "dependent" information to the format needed by your system. In the alliance documentation is mentioned the existence of the tool "logic" to map user's behavioral descriptions to a symbolic library. Is this tool available to us? Yes...But the problem is that Alliance uses a library of portable cells (symbolic layout). This means that at the very last step of design we use a tool (s2r) to convert from symbolic to real layout. This tool needs a technological file for a given process... Please look at ftp://asim.lip6.fr/pub/alliance/obsolete/prol.tar.gz this might help you building your .rds file Are the data of the projects (dlx, data-safe, FRISC,etc) mentioned in the Alliance manuals available? old version not fully working may be available... -- Sincerely, Olivier. ==================================================================== Olivier SIROL Alliance Team ASIM/LIP6/UPMC Coul. 55-65, 2e etg, Bur. 213 75252 Paris Cedex 05 mailto:Olivier.Sirol@lip6.fr Tel: (33/0) 1.44.27.74.78 http://asim.lip6.fr/~czo/ Fax: (33/0) 1.44.27.72.80