VCAR - Routing Specified Nets

So have you tried launching the router from Layout XL? That's the supported flow, as the document suggests...

In other words, use Route->Start Chip Assembly Router. 

Regards,

Andrew.

I'm doing it exactly like that, but I want to invoke -nets switch with "myNetList.txt".

Thanks

Hi sPoK

In the VCAR startup form, please press "More options" button to display the full form. At the bottom of the form, there is a "Startup Options" field which you can use.


Best regards
Quek

Hi Quek

I know about that, thanks, actually the main issuse is exporting netlist from LayuotXL.

What I want is VCAR to route ~2700 of 3000 nets.

BR 

I just created a text file, nets.txt with the following content:

outm
outp

and then on the form that Quek mentioned, in the  Startup Options field I typed:

 -nets /project/demos/MyData/design/nets.txt

i.e. the full path to  the file I created.

Once VCAR had started, it only knew about those two nets, and doing a "route" only routed those nets.

So the idea is that the connectivity comes from the starting database - which is Layout XL compliant and so has all the connectivity - and the -nets option allows you to specify the names of the nets you want to allow to be routed.

You'll be able to see the names of the nets in the layout view by using the navigator assistant (set the filter to Nets), or from the CIW you can type:

geGetEditCellView()~>nets~>name

You could always write them into a file to edit later by doing:

op=outfile("./nets.txt")
foreach(netName geGetEditCellView()~>nets~>name
  fprintf(op "%s\n" netName)
)
close(op)

Regards,

Andrew.

Thanks Andrew, 

With this code I can extract nets from layout.

But, for some reason not all nets are loaded from my nets.txt file, I made a test with 200 nets and only 87 are recognized.

BR 

Not sure why that is. It works for me, even with bussed nets (I wondered whether that was the reason). 

You should contact customer support or if a university, follow the process for your university programme - that way we could take a look at your data.

Regards,

Andrew.

Well, I'm not at any University, I'm subcontarctor and unfortunetly don't have access to support. 

Previously, in the IC5.1 there was an option Routing->Export to router which, btw, creates *.net file.

This file contained net names with devices|pins on every net.

Perhaps VCAR expects the same syntax?  

Anyway, this option -nets should be more detailed explained within documentation.

Thanks

BR

In IC5141 it had to export the design - all the shapes and connectivity - into VCAR's internal format and then read that. In IC615, since they both support OpenAccess, there's no need to do that any more - VCAR can directly read the shapes and the connectivity information from the OA database.

The *.nets file wasn't anything to do with the -nets argument, as far as I know.

Regards,

Andrew.

I just found out that bused nets are not recognized at all, I tried with a nets.txt containing only one 16bit bus net, none loaded, tried with another 8bit bus net, but again the same error.

No idea why is that happening :( 

BR