• 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. Custom IC Design
  3. mapping logical libraries in AMS Designer (VHDL)

Stats

  • Locked Locked
  • Replies 7
  • Subscribers 125
  • Views 16744
  • 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

mapping logical libraries in AMS Designer (VHDL)

FedericoPI
FedericoPI over 13 years ago

 Hi all,

 I am using a vhdl description where i put the directive:

library pippo; 

use pippo.VTABLES.all;

 

pippo is defined in cds.lib, and inside pippo i have imported the package VTABLES with vhdlin.

I tried to simulate with AMS a schematic where is some spectre and the vhdl description with this directory (the VHDL has been succesfully imported). It gives me the error on library directive:

 logical library must be mapped to design library

(or something very close)

i can-t understand why. in my cds.lib the library is referenced. maybe i should compile the package during import, but i don-t know how to set the correct work library. Can you help me with the right procedure?

 Note that i have succesfully simulated in AMS other vhdl blocks, i use OSS netlister, and cells in pippo library that don-t gives library pippo; as a directive correctly work. 

  • Cancel
Parents
  • FedericoPI
    FedericoPI over 13 years ago
    that I am still in trouble and i re upped the post, some days after the moment i added the version of the software.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • FedericoPI
    FedericoPI over 13 years ago
    that I am still in trouble and i re upped the post, some days after the moment i added the version of the software.
    • 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