Decoder and child region interface options
###Decoder and child region interface options
Example rdl showing use of different decoder interfaces is here.
###Secondary uP interfaces
It is useful at times to be able to access some/all of the register space from multiple hosts. A secondary uP interface will be added to generated decoder logic if the secondary_decoder_interface is specified. Arbitration between primary and secondary interfaces is simple round-robin and currently atomic read-modify-write transactions are not supported on the uP interface protocols. Options are available to specify a different base address seen by the secondary interface as well as limit access by the secondary interface to a specified address range (see here).
###Assist Engine as a secondary uP interface
If secondary_decoder_interface = engine1 is specified, an assist state machine will be created on the secondary interface capable of generating a simple sequence of reads or writes. Intent is to provide offload of the uP when performing tasks such as: writing a number of address locations to a particular value, scrubbing sram data (rmw), or polling to capture the max/min value of a particular register while the primary uP interface is busy with other tasks. The engine has three primary modes: read-only, write_only, or read-modify-write, which is determined by the *_cntl_mode input signal. Other inputs... tbd. Assist engine inputs can be controlled by external RTL or connected to generated register ports (rdl describing compatible control and status registers is written to stdout and can be embedded in an input rdl file to simplify this process).