2.1.3 (* synthesize *)
Items contained within (* and *) are BSV attributes, used to guide the compiler in its decisions.
The (*synthesize*) attribute specifies that the module that follows is synthesized separately into a
hardware (Verilog) module. The top-level module of a design must be a synthesis boundary. Interior
modules can also represent synthesis boundaries. The design in this example has only one module.
You can also use the -g command-line flag when compiling to specify modules that are synthesis
boundaries, but we recommend using the (* synthesize *) attribute in the source text instead.
2.1.4 Module definition
The statement:
module mkTb (Empty);
defines a module named mkTb providing an Empty interface. By convention, we call our modules
“mkFoo”, for “make Foo”, to suggest that the module can be instantiated multiple times, possibly
with different parameters. Empty is a pre-defined interface with no methods. The keyword Empty is
not required, the statement could also be written as:
module mkTb();
BSV does not have input, output, and inout pins like Verilog and VHDL. Signals and buses are
driven in and out of modules with methods; these methods are grouped together into interfaces. An
Empty interface has no inputs or outputs.
Modules and interfaces form the heart of BSV. Modules and interfaces turn into actual hardware.
A module consists of three things: state, rules that operate on that state, and an interface to
the outside world (surrounding hierarchy). A module definition specifies a scheme that can be
instantiated multiple times.
2.1.5 Rule
The statement:
rule greet;
$display ("Hello World!");
$finish (0);
endrule
defines a rule named greet with no explicit rule condition. (An explicit rule condition is a boolean
expression in parentheses after the rule name; when omitted, it defaults to True.)
Rules are used to describe how data is moved from one state to another, instead of the Verilog
method of using always blocks. Rules have two components:
• Rule conditions: Boolean expressions which determine when the rule is enabled.
• Rule body: a set of actions which describe state transitions
16
剩余239页未读，继续阅读
weixin_41881193
- 粉丝: 0
- 资源: 1
我的内容管理
展开
最新资源
- 多模态联合稀疏表示在视频目标跟踪中的应用
- Kubernetes资源管控与Gardener开源软件实践解析
- MPI集群监控与负载平衡策略
- 自动化PHP安全漏洞检测：静态代码分析与数据流方法
- 青苔数据CEO程永：技术生态与阿里云开放创新
- 制造业转型： HyperX引领企业上云策略
- 赵维五分享：航空工业电子采购上云实战与运维策略
- 单片机控制的LED点阵显示屏设计及其实现
- 驻云科技李俊涛：AI驱动的云上服务新趋势与挑战
- 6LoWPAN物联网边界路由器：设计与实现
- 猩便利工程师仲小玉：Terraform云资源管理最佳实践与团队协作
- 类差分度改进的互信息特征选择提升文本分类性能
- VERITAS与阿里云合作的混合云转型与数据保护方案
- 云制造中的生产线仿真模型设计与虚拟化研究
- 汪洋在PostgresChina2018分享：高可用 PostgreSQL 工具与架构设计
- 2018 PostgresChina大会：阿里云时空引擎Ganos在PostgreSQL中的创新应用与多模型存储
资源上传下载、课程学习等过程中有任何疑问或建议，欢迎提出宝贵意见哦~我们会及时处理！
点击此处反馈
