The properties section of a protocol describes
properties such as, for example, version or base class.
Some properties might only be relevant for a specific tool. All properties are optional.
Example 4.1 shows the syntax of the properties section:
Example 4.1. Properties section
protocol MyProtocol
{
...
properties
{
version = “1.1.1”;
description = “my protocol”;
...
}
}
Table 4.1 lists the supported properties:
Table 4.1. Property values
| Property | Default | Description |
|---|---|---|
description | "" | This is a description of the protocol. |
version | "1.0" | This is the version number of the protocol. |
documentation_file | "" | Filename or http link for the protocol documentation. For filenames, the path can be absolute
or relative to the LISA+ file for the protocol. Supported file formats
are |
sc_slave_base_class_name | "" | Name of the SystemC base class for slave ports (slave exports and sockets for both TLM1 and TLM2). |
sc_slave_export_class_name | "" | Name of the SystemC class for slave ports (slave exports for TLM1 only). |
sc_master_port_class_name | "" | Name of the SystemC class for master ports (TLM1 only). |
sc_master_base_class_name | "" | Name of the SystemC base class for master ports (master sockets for TLM2 only). |
sc_master_socket_class_name | "" | Name of the SystemC class for master ports (master sockets for TLM2 only). |
sc_slave_socket_class_name | "" | Name of the SystemC class for slave ports (master sockets for TLM2 only). |