8 Star 55 Fork 25

wilson_chen/HDLGen

Create your Gitee Account
Explore and code with more than 12 million developers,Free private repositories !:)
Sign up
Clone or Download
contribute
Sync branch
Cancel
Notice: Creating folder will generate an empty file .keep, because not support in Git
Loading...
README
Apache-2.0

HDLGen from Wilson Chen 2022~2023

Overview

  HDLGen is a tool for HDL(mainly for Verilog) generation, it enables embedded Perl or Python scripts in Verilog source code, and support Perl style variable anyway, to generate desired HDL in an easy and efficient way.
  It supports all syntax and data structure of Perl or Python, and has a few predefined functions for signal define, module instance, port connection etc.
  This tool also supports extended API functions in Perl style, for any function or module that you want or have from previous knowledge or project.
  HDL and script mixed design file can be any name, while final generated RTL file will be Verilog only( as .v).
  This tool can achieve all functions of EMACS veirlog-mode,while support more as emdedded regular-express, IPXACT/XML,Interface,JSON,Hash,and the working mode is very similiar or even idential to HDL design, but not DSL or HLS.

  From function or working mode, this tool is much more efficient than commercial integration tools, with zero learning curve.

License

                     Copyright 2022~2023 Wilson Chen                                                     
        Licensed under the Apache License, Version 2.0 (the "License");                            
        You may not use this file except in compliance with the License.                          
        You may obtain a copy of the License at                                                  
                http://www.apache.org/licenses/LICENSE-2.0                                      
        Unless required by applicable law or agreed to in writing, software                    
        distributed under the License is distributed on an "AS IS" BASIS,                     
        WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.             
        See the License for the specific language governing permissions and                 
        limitations under the License.                                                     

any feedback, suggestion, requirement, solution, contribution, is always welcome


Working Flow

Different level design can use this tool with different functions a/o inputs/outputs, the main working flow is as below
Working Flow

What you can do with HDLGen

RTL stitch

  • Instance module from RTL or IPXACT or JSON file as what Verilog does
  • Connect module's port to wires with native regular express
  • Automatically generate instance's wires definitions
  • Automatically generate reg or wire definictions(not perfect but really helpful)
  • Warning out any Instance signals which has no connection
  • Use embedded native Perl or Python to generate(print) whatever code you want (replace structure/for/generate)

Interface manipulate

  • Add interface from IPXACT, JSON, RTL, SV code, or hash array
  • Add port to interface by name
  • Remove port from interface by name
  • Print or show interface signals for design or debug

IPXACT manipulate

  • Read in IPXACT or JSON and import all interfaces & ports
  • Show all interfaces defined in IPXACT ( for debug )
  • Translate IPXACT into JSON file ( for debug & integration)
  • Export Interface to JSON with name changing
  • Export port or remove port to/from JSON file
  • Generator module JSON with name,interface,port for up-level integration
  • Export interface to IPXACT by name ( abolished )
  • Export port to IPXACT by name ( abolished )
  • Export standard IPXACT for current top module ( abolished )

Function generation

  • Use embedded functions to generate differnt module or loigc you want
    • Clk, Reset, Fuse, Pmu, Fifo, Async-interface, Memories etc ( flow done, can custom design by anyone)
  • Extend your own module/logic by standard config ( in development )
    • config can be in Verilog, JSON, YAML, EXCEL etc.
    • then generate these logic with parameters by just a simple function call

Based on above functions, this tool can generate a SOC in an easy and flexible way

What you cannot do with HDLGen

  • Detail logic design: you still need to write RTL to implement your ideas
  • Synthesis or simulation or verification: you need to use other EDA tools to handle

Directory Structure

├── HDLGen.bin                # Tool binary for easy adopt
├── HDLGen.pl                 # Tool source code
├── plugins                   # Tool plugin funcitons in Perl module
    ├── Design_Template         # custom module design template files
├── test                      # Source design code for testing
    ├── cfg                     # JSON and XML for config
    ├── incr                    # necessary design files
├── doc                       # usage introduction 

Usage

first you need to set shell ENV of HDLGEN_ROOT, otherwise tool will report error.
plese refer to setenv.sh
then run command as simple as:
cd test
../HDLGen.pl -i NV_NVDLA_CMAC_CORE_mac.src or ../HDLGen.bin -i NV_NVDLA_CMAC_CORE_mac.src
or ../HDLGen.pl -f ./src.list
for help message you can run:
HDLGen.pl -usage

NOTE:

  • Verilog-mode for EMACS or VIM is very powerful to do AUTO Port,Reg/Wire, and Instance, but it has some limitations or inconvenient things:
    --- mostly used in GUI mode but no batch mode -- seems NOT TURE
    --- Instance port/wire name change is manual hard mapping but no Regular Express --- NOT TRUE, RE is supproted but need 3rd file
    --- No Warning for unconnected instance signals
    --- No Interface a/o IPXACT support
    --- No embedded Perl/Python support
    --- no function generation for inhouse/customer design
  • this tool only test on Ubuntu 18.04.05 & 20.04.5 with Perl-5.34, but should work on any system have Perl5 installed
  • Python script only support python3 but no python2.x (one more reason for why not Python ;-) )
  • several Perl Modules are required, can refer to the package head in source code, here listed:
    Getopt
    JSON
    Text::Template
    File::Basename
    File::Find
    Verilog::Netlist
    XML::Simple
    XML::SAX::Expat; #this is strange as not used at all, but pp need it
    Dumper
    Text::ParseWords
    Term::ANSIColor

Suggestion:
You can first run HDLGen.pl, then install any package according to the error message,
or just run HDLGen.bin for results

Samples

AutoDef Sample:

AutoInstSig Sample:

AutoWarning Sample:

Verilog Instance Sample:

IPXACT Instance Sample:

JSON Instance Sample:

Design Template File Sample:

Why need this tool?

  For any ASIC or SOC engineer with over 10 years experience, we may hate Verilog sometime, as Verilog HDL's syntax is TOO simple or TOO basic, it's Register Transfer Level description, we're not writing code, we're indeed designing circuit, it's very cool, but sometime we will be bored, especially when instancing module, do wire connections.
  We're very excited when seeing System Verilog for design, because some new syntax like structure,for,generator can impove coding efficiency dramatically,but unfortuantely these syntax will really cause pain when debugging, because ability of EDA tools. Evenmore, some time engineer may need to manually change code to workaround EDA tool on RTL or netlist, this really cause risk to projects.
   Then, in order to reduce manual work and improve efficiency, we'll try to use script to generate bulk of structural code, or for module/chip integration, the script we tried includes Perl,Python,Shell, or Vim/Emacs language. But, these ways often need manual run a/o copy in flow, it will cause big risk if any version is not aligned or any manual step is missed.   So we will try new different ways, we may study and learn Chisel, SpinalHDL, MyHDL PyHDL, or PyGear recently. But, when we learned, tried, finally we gave up, because they're DSL, they're not HDL! DSL is totally new language, DSL is more like a high level software language, we have to write code in a new style, no Verilog or HDL at all.
  We'll ask: is it safe for a project to abandon Verilog HDL? Is it safe for an experienced engineer to abandon previous skills and design logic with non-HDL code? Is it easy or friendly to learn a new language? Is that language widely used or accepted and will evolve in long term? Is that language suitable and safe for IP/SOC/ASIC development? Is there any different way to help us?
  Yes, we have a different way! And it is easy to use, smoothly to move, seamlessly to adopt.
  The tool is going to support you keep writing HDL while give the ability to improve your efficiency, and with ZERO learning curve, is here, named as "HDLGen".
  The way you're going to work is writing Verilog or VHDL code, the tool helps you on most boring tasks: signal define for wire a/o reg, instance modules by connections with auto wire signals defined and easy name change, connect signals with regular expression, instance JSON and IPXACT xml file as simple as HDL code natively. If any task/logic/design which is not friendly written in HDL, then you can use high level script language like Perl or Python for any code or task you want, wherever and whenever in the HDL source file, as long as you know Perl or Python script, or even shell script.
  This tool supports standard AMBA bus interfaces natively. This tool also support you to manually define an interface, through SystemVerilog, Verilog, IPXACT or XML, JSON, or Hash array.
  If there is any inhouse developed or accumulated design which is common for your designs, you can put as a template in this tool, then instance with any parameters you want by just as simple as one function call in HDL.

*** The most intuitive and effective design is "what you see is what you coding" ***
*** In most cases, Verilog is the most secure design ***
*** At the system level, the use of parameters requires extreme caution ***

*** DSL is really cool ***
*** But Verilog is still the King ***
*** Connection is what you need ***
*** And Fexibility is really helpful ***

Thanks

Thanks NVIDIA for giving me the chance to know how Perl is powerful to run big ASIC factory,
Thanks NVIDIA's VIVA to let me know how Perl makes Verilog intersting and amazing.
Thanks NVIDIA's open sourced NVDLA as a test source.

Note:

This tool was developed from scratch during the special spring time in Shanghai in 2022
The things related to NVIDIA are:

  • 2 functions' name(Instance,Connect) are identical;
  • several HDL files of open sourced NVDLA are used to be test source

Please kindly let me know if there is any license issue


Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

About

HDLGen是一个HDL/RTL生成工具,支持在Verilog里内嵌Perl或Python script来帮助快速、高效地生成期望的设计,支持Perl或者Python的所有数据结构和语法,有若干内嵌函数来提高效率,也支持扩展API,支持自动Instance、自动信号生成、IPXACT、JSON、XML、模板等输入来减少手动工作、提高开发效率、降低出错几率,大大提高IP开发和SOC集成的效率 expand collapse
Perl and 2 more languages
Apache-2.0
Cancel

Releases (1)

All

Contributors

All

Activities

Load More
can not load any more
马建仓 AI 助手
尝试更多
代码解读
代码找茬
代码优化
Perl
1
https://gitee.com/wilson_chen/HDLGen.git
git@gitee.com:wilson_chen/HDLGen.git
wilson_chen
HDLGen
HDLGen
master

Search