• 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. Need help in verilog file creation

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 165
  • Views 13625
  • 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

Need help in verilog file creation

mahee424
mahee424 over 10 years ago

I have a file which is extended to .tdf (Text Design File) from altera library.  I want to convert it to traditional verilog code.

Can anyone help in this regard?

thanks,

mahee

  • Cancel
  • wijnaldum
    wijnaldum over 9 years ago
    Open PSoC® Creator™.
    2. Create a new project or open an existing project (for any PSoC device)
    This guide will use the project name “MyComponent”.
    3. Click on the „Components‟ tab of the Workspace Explorer.
    Right-Click on Project, and select Add Component Item from the context menu.
    4. Select Symbol Wizard and change the component name to what you want – this guide
    uses Component1_v1_0 as the component name. Click Create New.PSoC Creator supports versioning by adding _vX_Y to the Component name; where X is
    the major version, and Y is the minor version.
    5. Add terminals to the component as required. You can always add more later. Click OK
    6. Right-click on a blank space in the symbol file. Select Generate Verilog from the context
    menu. Click Generate on the window that appears.
    7. Enter the code for your Component anywhere between the `#start and `#end
    comments in the file.
    Regenerating Verilog
    8. After generating the Verilog code for the first time, if you add a terminal or parameter,
    you may want to regenerate the Verilog to bring the newly added parameter or terminal
    to the Verilog file. You can regenerate the Verilog by right-clicking on an empty space on
    the schematic, and selecting Generate Verilog. However, you will lose all Verilog code
    written outside the `#start and `#end comments.
    You will never need to regenerate the Verilog, because you can manually add the
    parameter or terminal name to the Verilog code.
    Adding Terminals
    9. In the symbol file, either use hotkeys (I, O, B) or the buttons shown in the following figure
    to add terminals to the symbol.
    10. For these terminals to show up in the Verilog file, generate the Verilog file again.
    Alternatively, you can manually add these terminals as inputs or outputs to the module
    port list.
    Adding Parameters
    Parameters are used to configure the component from the Component customizer.
    11. Right-click on an empty space in the symbol file. Select Symbol Parameters from the
    context menu.
    12. Add the parameter name, type, initial value. If you will use this parameter in the Verilog,
    set the Hardware to True. You can also add the parameter Description, Validator,
    and so on in this window. For more information on parameters and validators, see
    Component Author Guide in PSoC Creator Help > Documentation.
    13. Regenerate the Verilog code. The parameter appears in the Verilog code if you have set
    Hardware to True.
    Adding A Datapath Instance
    14. Open the Datapath configuration tool from Tools>Datapath Config Tool.
    15. Open the Verilog file that you have created in the Datapath Config Tool from File>Open.
    16. Add a new datapath instance to this Verilog file by choosing Edit>New Datapath and
    select a Datapath instance type from the generic, 8, 16, 24 and 32-bit Datapath instance
    types.
    17. When you complete your changes in the Datapath Config Tool, save the file (File>Save)
    before you switch to the Verilog file. Similarly, save your changes in the Verilog file
    before returning to the Datapath Configuration Tool.
    • Cancel
    • Vote Up 0 Vote Down
    • 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