JSpec Output

Ordt will generate Jspec code from rdl input to allow use of existing Jspec filters. Note that generated Jspec will include detail of specified external register areas so that complete documentation can be generated from Jspec. Thus, Ordt-generated Jspec output is not suitable for generation of verilog headers (since external registers will also be auto-generated rather than tagged as an external interface). The jspec output is "unrolled", ie no typedefs or constant defines are generated. Rather, output is a set of nested instances.

Several ordt parameters can be specified to control jspec output. These include:

root_regset_is_instanced (type=boolean, default=true): if false, the root jspec register_set will be output as a typedef rather than an instance.

add_js_include (type=string, default=null): if specified, a #include of the given file will be added to jspec output. Multiple add_js_includes are allowed.

---

Rdl property translation to jspec output

SystemRDL properties are converted to jsec as follows:

• category and sub_category property strings are converted to like-named jspec properties.
• register donttest properties are converted to jspec attributes = JS_ATTRIB_DO_NOT_TEST
• register dontcompare properties are converted to jspec attributes = JS_ATTRIB_TEST_ACCESS_ONLY
• registers with one or more fields having intr property are assigned attributes = JS_ATTRIB_INT_STATUS

Generation of JS_ATTR* values from rdl properties can be overridden by assigning a string value to the js_attributes property in rdl source. If specified, the value will passed as-is to the attributes assignment in the generated jspec.