• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Digital Implementation
  3. Error Saving Database caused by wires created during EC...

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 91
  • Views 13084
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Error Saving Database caused by wires created during ECO

spalley68
spalley68 over 9 years ago

It seems like old nets are kept in the database even if they are not in the new eco netlist. For example, I had a change that made this code:

 

   DTC23 \otpData_o_reg[spare2][0]  (.Q(\otpData_o[spare2] [0]),

               .D(n_18),

               .CLRZ(p4),

               .CLK(clkTrim17Lo));

   DTC23 \otpData_o_reg[spare2][1]  (.Q(\otpData_o[spare2] [1]),

               .D(n_17),

               .CLRZ(p4),

               .CLK(clkTrim17Lo));

   DTC23 \otpData_o_reg[spare2][2]  (.Q(\otpData_o[spare2] [2]),

               .D(n_15),

               .CLRZ(p4),

               .CLK(clkTrim17Lo));

   DTC23 \otpData_o_reg[spare2][3]  (.Q(\otpData_o[spare2] [3]),

               .D(n_16),

               .CLRZ(FE_OFN235_porZ),

               .CLK(clkTrim17Lo));

 

Change to this:

 

   DTC23 \otpData_o_reg[spare2][0]  (.Q(NVM_TRACKER_SEL),

               .D(n_18),

               .CLRZ(p4),

               .CLK(clkTrim17Lo));

   DTC23 \otpData_o_reg[spare2][1]  (.Q(NVM_BOOST_DIS),

               .D(n_17),

               .CLRZ(p4),

               .CLK(clkTrim17Lo));

   DTC23 \otpData_o_reg[spare2][2]  (.Q(NVM_SYS_ALT_SEL),

               .D(n_15),

               .CLRZ(p4),

               .CLK(clkTrim17Lo));

   DTC23 \otpData_o_reg[spare2][3]  (.Q(otpData_spare2_3),

               .D(n_16),

               .CLRZ(FE_OFN235_porZ),

               .CLK(clkTrim17Lo));

 

So, I am only changing the output net to a new name. When I do this, Encounter takes the old names (i.e. \otpData_o[spare2] [0]) and defines internal wires for them like this:

   wire \SPARE[19] ;

   wire \SPARE[20] ;

   wire \SPARE[21] ;

   wire \\otpData_o[spare2] [0] ;

   wire \\otpData_o[spare2] [1] ;

   wire \\otpData_o[spare2] [2] ;

   wire \\otpData_o[spare2] [3] ;

 

The “\\” is keeping the database from saving. I get this error when trying to save:

**ERROR: (ENCOAX-156):  OA Exception : Input name (or member): \\otpData_o[spare2] [0]  has improper bus syntax..

**ERROR: (ENCOAX-426):  Error in creating EMH hierarchy.

TIMER: oaOut total process: 0h 0m  0.05s cpu {0h 0m 0s elapsed} Memory = 0.0

**ERROR: (ENCIMEX-7323):        Could not save design into OA database.

 

 

Does anyone know a way to tell Encounter not to name it with \\ or how to remove the old physical wires from the database??  This is a postMask ECO, so I cannot re-synthesize. 

Thanks!

  • Cancel
Parents
  • Kari
    Kari over 8 years ago
    i would file a service request. you should not get an error when trying to save the database.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Kari
    Kari over 8 years ago
    i would file a service request. you should not get an error when trying to save the database.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information