Scribd
Upload
40 views

Design Issues

1. Models are used to capture system characteristics at different phases of design, with the objective varying for each phase. The designer may switch between models. 2. Architectures like controller, datapath, RISC, CISC specify how the system will be implemented and include elements like state machines, functional units, and instruction sets. 3. Factors like complexity, memory usage, pipelining, and parallelism must be considered to select the appropriate architecture, such as finite state machine datapath or VLIW.

Uploaded by

Anonymous uspYoqE
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
40 views

Design Issues

1. Models are used to capture system characteristics at different phases of design, with the objective varying for each phase. The designer may switch between models. 2. Architectures like controller, datapath, RISC, CISC specify how the system will be implemented and include elements like state machines, functional units, and instruction sets. 3. Factors like complexity, memory usage, pipelining, and parallelism must be considered to select the appropriate architecture, such as finite state machine datapath or VLIW.

Uploaded by

Anonymous uspYoqE
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 12

SELECTING THE MODEL

In hardware software co-design,models


are used for capturing and describing
the characteristics of E.S
• A model is formal system consist of object and
composition rules.
• It is hard to decide which model is used for
particular system design.
• Most often the designer switch b/w variety of
model during implementation.
• The reason being, the objective varies with
each phase.
Selecting the architecture
• A model only capture the system characteristics and does
not provide information on how the system can be
manufactured?
• A architecture specifies how the system is going to
implement.
• i. Controller architecture
• Ii. Datapath architecture
• Iii. RISC
• Iv. CISC
• V. SIMD(Single instruction Multiple data)
• VI.MIMD(Multiple instruction Multiple Data)
• Are the commonly used architecture in system design
Controller architecture

• Controller architecture
• This architecture implements the state machine
model.
• State machine model: is used for modelling event
driven embedded systems whose processing
behavior are depends on state transition.
• Example: Embedded system used in control and
industrial applications
• The sate machine model describes the system
behavior with ’state’, ‘event’, ‘action’ and
transition.
• Data path architecture: Is best suited for
implements the data flow graph model where
the outputs is generated as a result of a set of
predefined computations on the input data.
• Data path represents a channel b/w the input
and output and in data path architecture the
data path may contain register, counters,
register files, memories and ports.
• Finite state machine data path: This architecture
combines the controller architecture with data
path architecture
• The controller generates the control input
whereas data path processes the data.
• Data path contains two types of I/O ports
• Ist: Acts as a control port for receiving/sending
control signals from/to the controller unit
• 2nd: Interface the data path with external world
for data input and data output
• CISC: instruction set representing a complex
operations.
• For example: CJNE in 8051
• Greatly reduce the memory access and number
of cycles.
• But it may require additional chip for decoding
the complex instructions
• RISC: Require more simple instruction to perform
complex task.
• RISC support extensive pipelining.
• Very long instruction word(VLIW) architecture
implements multiple functional units like
multiplier, adder, shifter in data path.
• Parallel processing architecture: Implements
multiple concurrent processing elements(PEs)
and each processing element may associate a
data path containing register and local memory.
• Example: MIMD, SIMD architecture.
• MMID:PEs execute different instructions at a
given point of time .
Cntd..

• Short for single instruction, multiple data. A type


of parallelcomputing architecture.
• A single computer instruction perform the same
identical action (retrieve, calculate, or store)
simultaneously on two or more pieces of data.
• pically this consists of many simple processors,
each with a local memory in which it keeps the
data which it will work on.
• Each processor simultaneously performs the
same instruction on its local data progressing
through the instructions in lock-step,
• Short for multiple instruction, multiple data. A
type of parallelcomputing architecture that is
classified under Flynn's taxonomy. Multiple
computer instructions, which may or may not
be the same, and which may or may not be
synchronized with each other, perform actions
simultaneously on two or more pieces of data.
• Selecting a language
• C,C++, java, C# for software implementations
• VHDL and System c Verilog etc for hardware
implementations
• Partitioning system requirements into
hardware and software:
• So for we discussed about the models for
capturing the system requirement and the
architecture for implementing system.
• The system implements can be done by either
software or hardware.
• Various trade-offs are used for making a
decision on the H/D-S/F parrtitioning.

You might also like