• 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. PCB Design
  3. Controlling the Device Type value when I running Export...

Stats

  • Locked Locked
  • Replies 0
  • Subscribers 163
  • Views 13459
  • Members are here 0
More Content
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

Controlling the Device Type value when I running Export Physical

archive
archive over 19 years ago

ConceptHDL 15.5.1, Front to Back Flow, question.

I would like to control the Device Type value during Packaging such that I can specify
an explicit value. Currently, the Device Name value formed by Packager-XL appears
to be formed by the concatenation of the PART_NAME, Key Properties and Injected Properties.
The resulting Device Type value is very long and contains illegal characters that will
break downstream tools.  I thought I addressed this issue by specifying an explicit
value for the Row Name inside of the Part Table (PTF) but all it did was add it as
a suffix followed by Key and Injected Properties.

Has anyone ran into this before and found a workaround.

In the PTF File a specify the Row Name (~explicit row name)

{=========================================
: PART_NUMBER    | JEDEC_TYPE                               =
{=========================================
'IXX0005606'       | 'TSOP56_0196_01C' (~IXX0005606) =

(Note this is a partial PTF file - Injected properties omitted for clarity.)

Device Type value using Show Element in Allegro:
Resulting value
Device Type:   IXX0005606-TSOP56_0196_01C,VCCA

Expected value
Device Type:   IXX0005606

We just migrated over to ConceptHDL for DxDesigner (EPD)
and most of our programs key off of the Device Type value
which was previously driven by the Device file names.

I have a case open with Cadence but I figured I would
bounce it off all of you just in case you have dealt with
this in the past.

Thanks is advance,
Michael Catrambone
UTStarcom, Inc.


Originally posted in cdnusers.org by mcatramb91
  • Cancel
Cadence Guidelines

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