Then, fortunately for us, the sysadmins kept around an old copy of the Aspec RAM generator programs that seem to work. I've verified that the two RAM generators produce identical results except that the *.gds files produced are different. I don't know how to tell what the differences are there, because the files are in a binary format.
The only problem with the newer one (the default one you get when you just use "pkgadd aspec" and the commands indicated below) is that it does not generate VHDL or Verilog simulation models of the RAMs. If all you want is a data sheet for area and timing, or a GDS2 file, the new RAM generator works fine.
To run the old Aspec RAM generator, I would recommend opening up a new shell window where you don't do anything else with any other Aspec tools, because it involves mucking with your command path, and it wouldn't be good to accidentally use older versions of other Aspec commands.
Then, assuming you already have the package "aspec" added, do this:
set path = (/pkg/aspec/bin.sol_19980227 $path)Then, there is a Perl script that Rex wrote to run the RAM generator with the proper options that can be run this way:
~rex/designs/lib/ramgen/genapicram.pl vxt4096x32 4096x32 oneclock 0The last two options only affect the generation of some 'wrappers' containing flip-flops that go around the RAMs.
I have a similar Perl script, modified from Rex's version. The only difference is in the wrappers that it generates. It is accessible at
~jaf/ipp2/bin/genaspecram.pl vxt4096x32 4096x32 oneclock 0I am guessing that either we don't have consistent set of up to date Aspec binaries for their RAM generator, or they just screwed up in their latest release. (.... ..... ... Huh? Where am I? Oh, sorry, my faith in Aspec's tools was just momentarily shattered, again. Had to readjust my world view for a few seconds there.)