JSpec Output

TBD...

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, Jrdl-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).

While jspec input can specify constants to be used elsewhere in the design or software, constant definitions will not be included in jspec generated from rdl.

#####Ordt properties for jspec output Ordt allows the category and sub_category properties to be defined in rdl. Values of these properties will be included in the jspec output.
Registers defined with the rdl donttest property will be given an attributes = JS_ATTRIB_DO_NOT_TEST designation in jspec output.
Registers defined with the rdl dontcompare property will be given an attributes = JS_ATTRIB_TEST_ACCESS_ONLY designation in jspec output. Registers defined with one or more interrupt fields will be given an attributes = JS_ATTRIB_INT_STATUS designation in jspec output.
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 generated jspec.