Hardware Reference
In-Depth Information
Real Time Control Applications
IT Applications
Steering
Controller
Audio
Navi
Telematics
Engine
Transmission
Brake
Steering
Sensor
Multimedia
GUI
Database
Network
Engine
RTOS
Versatile OS
Trans-
mission
CPU #0
DMAC
INTC
Timer
SCIF
CPU #1
Brake
GPIO
ROM Con
RAM Con
DU
PCI
CAN
Dev
ROM
RAM
Display
Net
: IT domain
: RT domain
Fig. 5.7
Multidomain system architecture for embedded multicore processors
coordinate tasks, but there is no dynamic load balancing. The task assignment is fixed,
and hardware resources can be dedicated to the domains, resulting in a more determin-
istic performance. Despite some possible memory overhead due to multiple operating
system images in the main memory, this feature is one of the system architecture's
most significant advantages for embedded system developers.
As the size and complexity of embedded systems increase, so do the chances that a
system will break down because of software malfunctions or attacks over the network.
Although operating systems isolate software failures within an application, a failure
could affect the operating system itself, causing it to bring down all applications run-
ning on it because operating systems, especially versatile ones, are becoming larger
and more complex.
In developing control subsystems whose failure might endanger a person's life,
such as an automobile's brake control system, an engineer tries to achieve a high
level of safety by every conceivable means. However, even a safe and secure control
subsystem can be affected if it is incorporated with IT subsystems into a multido-
main system on a multicore processor.
Our domain-partitioning approach helps to isolate failures within unreliable IT
domains rather than let them affect control domains on the multidomain embedded
system. This domain partitioning protects a domain from being affected by other
domains in the multidomain system and maintains the system's safety and security by
Allocating multicore processor resources for each domain to let it run its own
operating system and applications [
16
]
Protecting a domain from the effects of software failure in other domains and
ensuring that only the domain causing the failure is affected
Search WWH ::
Custom Search