... | @@ -95,7 +95,15 @@ block. The name is used for commenting the generated code and producing |
... | @@ -95,7 +95,15 @@ block. The name is used for commenting the generated code and producing |
|
documentation. |
|
|
documentation. |
|
|
|`description` | optional | Longer description of the block, used by the
|
|
|`description` | optional | Longer description of the block, used by the
|
|
documentation generator. May contain inline HTML code. |
|
|
documentation generator. May contain inline HTML code. |
|
|
|`c_prefix`, `hdl_prefix`, `prefix` | mandatory | |
|
|
|`c_prefix`, `hdl_prefix`, `prefix` | mandatory | contains a short
|
|
|
|
prefix for each block which is used for generation of VHDL port/signal
|
|
|
|
names and C macros. Names are generated by concatenating the prefixes:
|
|
|
|
`peripheral_reg_field`. In this
|
|
|
|
[example](WB-file-syntax-examples#gpioport), the signal name of register
|
|
|
|
"DDR" would be `gpio_ddr_o`. The format of `prefix` value must follow
|
|
|
|
the HDL/C language syntax rules and your coding style. Note that you can
|
|
|
|
provide either separate prefixes for C/HDL languages `c_prefix`,
|
|
|
|
`hd_prefix` a single `prefix` for both. |
|
|
|
|
|
|
|
|
|
|
|
|
|
... | | ... | |