This is Kactus2 extension
System view is a
usually associated with a component including multiple CPUs. It
is hierarchical reference to system design which is also
a Kactus-extension and defines the mapping of SW onto HW
resources. One component, such as multiprocessor SoC (MPSoC),
can have multiple system views, i.e. multiple stored mappings,
and hence it is easy to switch between them. System design
defines how SW is mapped onto CPUs and it shows all HW
components that include a CPU definition. Mapping is
necessary if there are multiple CPUs or HW accelerators that
support the optional COM interfaces.
Each system view has mandatory name and hierarchy reference. Note that the latter cannot be edited here, but in view's own editor. Note also that a system view is always hierarchical, unlike regular view.Display name is optional and typically a few words providing a more detailed and/or user-friendly name for display. Optional description contains a textual description of the interface.
EXAMPLE. A product includes two programmable CPUS: Nios on FPGA
and a regular PC. One system design performs the application
mapping so that discrete cosine transfrom (dct) is executed on PC
whereas the main function H.263 video encoder is on
Nios. Communication between these is done using MCAPI endpoints
and channels. Therefore Nios also includes the MCAPI SW component.
We notice that interface symbols are different in COM interfaces
(main - dct) and API interfaces (main - mcapi). Note also that
system design shows CPUs together although they appear on
different levels of product's hiearchy.