Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
minLevel1
maxLevel4

Overview

When processing the Parts In a Design, it is very useful to be able to assign a PART_TYPE based on properties extracted for each Part. NetBom provides the user a flexible system to control the PART TYPES and how parts are assigned to a Part Type.

...

For each part in the design, NetBom iterates through these tables in the configured sequence. It builds a list of every pattern match in the mapping table. The list of match patterns is sorted by the length of (so that the most specific matches will be checked first) and the first match that matches the current part property is used to assign the Part Type for that part. If no match is found for the Property, then NetBom chooses the next property in the priority list, and checks all the pattern map matches set for it until an actual match is found. If no matches are found the final PART_TYPE for that part is left blank.

Related CSETS

...

When defining different Part Types, it is important to remember that the NetBom Net Tracing and Power Rail Identification Functions rely on Part Types.

NET_TRACE_COMPONENT_STOP

This CSET is very important as it is used to identify starting and stopping points for the Net Traces. If you add a specialized Part Type like Memory, NPU, or Power Module for high pin count parts, you should add them to this CSET.

POLAR_CAP_PART_TYPES

This CSET is used to map the Names you used to identify Polarized Capacitors from your netlists to NetBoms view of Polarized Capacitors.

POWER_RAIL_CAP_PART_TYPES

This CSET is used to identify what PART_TYPES should be considered a CAPACITOR when NetBom is identifying Power Rails.

Helpful Hints

When configuring your Part Type Mapping Rules, It helps to run the Convert Operation (or Diff Netlists) on the design with the default Mapping Rules. The PartList Report can be used to see what Part Types need to be adjusted.

...