File names corresponding to the Cell names get added by % pe

P

Pratap

Guest
Dear all,
I am facing a strange kind of problem in cadence while using the
library manager.
I had recently renamed a cell to "TEST_NMOS_COMPARATOR" using design---
"save as" but after restarting cadence I saw there were two cells
present in my Library manager,
Click to expand...
1. "test_nmos_comparator" and another "TEST_NMOS_COMPARATOR". When I
tried to open the cell showing "test_nmos_comparator" it just started
to blink several times and there were warnings in ICFB Window that the
cell physically doesn't exist. The one showing "TEST_NMOS_COMPARATOR"
was OK.
To understand the situation I went to the file browser and found the
following.
There were actually two directories created inside my design library
path.
1. test_nmos_comparator...which had schematic and symbol directories,
but both were empty.
2.%T%E%S%T_%N%M%O%S_%C%O%M%P%A%R%A%T%O%R...which had also got
schematic and symbol directories, but they actually contained the
files..."master.tag", "pc.db", "prop.xx", "sch.cd%" and "sch.cdb".

Now I wander why this has happened? What can I do to make the
corresponding physical directory names free from the strange %
letters. I had also tried renaming the folders with % to the ones
without % but in that case they don't show up in my library manager as
cells.

Hoping for some positive responses,
Warm regards,
-Pratap
 
Pratap <pratap.iisc@gmail.com> writes:

Now I wander why this has happened?
Click to expand...
I don't know as I don't reproduce this. What may help you is that the name
%T%E%S... looks like the result of name mapping upper case letters by OA
when mapping upper to a name space which is case insensitive such as
Windows file system.

Yours,

--
Jean-Marc
 
Hi,

Rather odd, never seen this before ...
What is your Cadence version ?
icfb -W
This may give some clues for Cadence guys. Have no idea as far as I'm
concerned :-(

Cheers,
Riad.
 
Jean-Marc Bourguet wrote, on 10/07/09 07:47:
Pratap <pratap.iisc@gmail.com> writes:

Now I wander why this has happened?

I don't know as I don't reproduce this. What may help you is that the name
%T%E%S... looks like the result of name mapping upper case letters by OA
when mapping upper to a name space which is case insensitive such as
Windows file system.

Yours,
Click to expand...
That was my guess too - you're using a Windows File System to store the library,
which is not a recommended use model, by any stretch of the imagination!

Regards,

Andrew.
 
On Oct 7, 1:28 pm, Andrew Beckett <andr...@DcEaLdEeTnEcTe.HcIoSm>
wrote:
Jean-Marc Bourguet wrote, on 10/07/09 07:47:

Pratap <pratap.i...@gmail.com> writes:

Now I wander why this has happened?

I don't know as I don't reproduce this.  What may help you is that the name
%T%E%S... looks like the result of name mapping upper case letters by OA
when mapping upper to a name space which is case insensitive such as
Windows file system.

Yours,

That was my guess too - you're using a Windows File System to store the library,
which is not a recommended use model, by any stretch of the imagination!

Regards,

Andrew.
Click to expand...


I am using the latest version of cadence only.

[pratap@hollerith designs]$ icfb -W
sub-version 5.10.41.500.6.132

Also I want to clarify that the libraries are stored in linux
partition only. But one more strange thing is happening. The same
files if I rename to normal names and copy to another new blank
library it works fine. Where as in the same library it gives problem
i.e. It's not detected properly by the library manager.
So I guess the library is some how got corrupted. Any clue how can I
recover a corrupted library?
Thanks,
Pratap
 
Pratap wrote, on 10/08/09 02:12:
On Oct 7, 1:28 pm, Andrew Beckett <andr...@DcEaLdEeTnEcTe.HcIoSm
wrote:
Jean-Marc Bourguet wrote, on 10/07/09 07:47:

Pratap <pratap.i...@gmail.com> writes:
Now I wander why this has happened?
I don't know as I don't reproduce this. What may help you is that the name
%T%E%S... looks like the result of name mapping upper case letters by OA
when mapping upper to a name space which is case insensitive such as
Windows file system.
Yours,
That was my guess too - you're using a Windows File System to store the library,
which is not a recommended use model, by any stretch of the imagination!

Regards,

Andrew.



I am using the latest version of cadence only.

[pratap@hollerith designs]$ icfb -W
sub-version 5.10.41.500.6.132

Also I want to clarify that the libraries are stored in linux
partition only. But one more strange thing is happening. The same
files if I rename to normal names and copy to another new blank
library it works fine. Where as in the same library it gives problem
i.e. It's not detected properly by the library manager.
So I guess the library is some how got corrupted. Any clue how can I
recover a corrupted library?
Thanks,
Pratap
Click to expand...
Not really sure, because I've never seen this before.

I wonder if at some point the library was copied onto a Windows File System?

Regards,

Andrew.
 
On Oct 8, 10:40 am, Andrew Beckett <andr...@DcEaLdEeTnEcTe.HcIoSm>
wrote:
Pratap wrote, on 10/08/09 02:12:



On Oct 7, 1:28 pm, Andrew Beckett <andr...@DcEaLdEeTnEcTe.HcIoSm
wrote:
Jean-Marc Bourguet wrote, on 10/07/09 07:47:

Pratap <pratap.i...@gmail.com> writes:
Now I wander why this has happened?
I don't know as I don't reproduce this.  What may help you is that the name
%T%E%S... looks like the result of name mapping upper case letters by OA
when mapping upper to a name space which is case insensitive such as
Windows file system.
Yours,
That was my guess too - you're using a Windows File System to store the library,
which is not a recommended use model, by any stretch of the imagination!

Regards,

Andrew.

I am using the latest version of cadence only.

[pratap@hollerith designs]$ icfb -W
sub-version 5.10.41.500.6.132

Also I want to clarify that the libraries are stored in linux
partition only. But one more strange thing is happening. The same
files if I rename to normal names and copy to another new blank
library it works fine. Where as in the same library it gives problem
i.e. It's not detected properly by the library manager.
So I guess the library is some how got corrupted. Any clue how can I
recover a corrupted library?
Thanks,
Pratap

Not really sure, because I've never seen this before.

I wonder if at some point the library was copied onto a Windows File System?

Regards,

Andrew.
Click to expand...
Yes Andrew,
You are absolutely right.
Finally a cadence representative pointed out the error. The library
was created in windows partition and later moved to the linux
partition.
I had to edit the cdsinfo.tag file for the libraries which are there
on the LINUX system, earlier it has following setting: NAMESPACE
LibraryNT and when I changed it to: NAMESPACE LibraryUnix it started
working fine...No more funky symbols for folders of cells. I had to
rename the % affected files though to get them listed in Library
manager.
Thanks,
Pratap
 
You must log in or register to reply here.

Welcome to EDABoard.com

Sponsor

Back
Top