Stats

  • Replies 6
  • Subscribers 160
  • Views 14024
  • Members are here 0
More Content

Create component

Ejlersen

Hi

Is there a axl function to create a component without a device file

or alternatively an axl command to generate a device file from a symbol (.dra) file. I could probably do it with a script but would prefer an axl command.

Best regards

Ole

Parents

  • In the board:

    •    axlDBCreateComponent but it requires a device file which wouldn't be that hard to create in Skill
    •    also there is axlWriteDeviceFile if you already have a comp that matches your requirement.

    To generate a device file require logical data which is is not part of a dra.

    You can make a template by trying the following:

     Use the non-public function: _writeDeviceFile(t_deviceName, t_className lt_pinNumbers)

          t_className is the device entry for CLASS

          You can get make up the pin numbers by iterating on the pins in the DRA, skipping mech pins and making a list of 'number' attribute from the pin ids.

     Other device file data like functions, properties. etc., in the symbol editor, you would need to obtain from other sourc.

Reply

  • In the board:

    •    axlDBCreateComponent but it requires a device file which wouldn't be that hard to create in Skill
    •    also there is axlWriteDeviceFile if you already have a comp that matches your requirement.

    To generate a device file require logical data which is is not part of a dra.

    You can make a template by trying the following:

     Use the non-public function: _writeDeviceFile(t_deviceName, t_className lt_pinNumbers)

          t_className is the device entry for CLASS

          You can get make up the pin numbers by iterating on the pins in the DRA, skipping mech pins and making a list of 'number' attribute from the pin ids.

     Other device file data like functions, properties. etc., in the symbol editor, you would need to obtain from other sourc.

Children
No Data
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.