View
213
Download
0
Category
Preview:
Citation preview
Alon Horn and Oren IerushalmiSupervised by Mony Orbach
Winter 2010Characterization Presentation
Implementation of an Engine Control Unit over Many-Core System
Project Objectives
Implement an Engine Control Unit (ECU) over a Many Core System.
Understand Plurality's HAL Architecture. Write Parallel Code using Task Oriented
Programming. Simulate the Code Using Plurality's cycle
accurate HAL simulator. Achieve Fast, Accurate, Robust and Efficient
system.
Engine Control
An ECU reads data from various engine sensors, processes them to calculate fuel injection pulse and spark timing, then sends back 3 control signals:
Fuel pulse width. Spark timing. Stepper IAC – Idle air controller.
ECU
Engine
1) Engine Main Sensors M.A.P sensor – Manifold Absolute Pressure. C.P.S – Crankshaft Position Sensor. Sync Signal – synchronization signal from the
distributor. M.A.T – Manifold Absolute Temperature. T.P.S – Throttle Position Sensor. E.G.O – Exhaust Gas Oxygen feedback.
Project Top Level
Project's Main Blocks:
HAL Simulator
Engine Sensors
Outputs Checker
Golden Model
1
2
4
5
TOP C code
3
2) HAL
HAL - Plurality's HyperCore Architecture Line Main Features:
16 to 256 32-bit RISC cores supports a task-oriented programing.
Shared memory architecture. Hardware-Based scheduler.
HAL simulator is a GDB based cycle-accurate simulator for Plurality's Many Core architecture.
2) HAL
3) TOP C Code
TOP – Task Oriented Programming. Task is a code section that runs sequentially. Different or duplicable Tasks can runs
simultaneously. A Task Map defines the relations and
conditions between tasks.
3) TOP C Code – Main BlocksInputs - sensors
Tasks – outputs (Realtime)
Tasks - sensor calculations
Outputs -Control signals
Tasks – sync
3) TOP C Code – ECU
Sensor and Outputs level granularity. Independent calculations will be done in
separate tasks. Each output has separate task. Syncronization / scheduler tasks as needed. Simple and logical design. Readable code.
4) Golden Model
An independent model that calculates the outputs of the simulator.
Should be simpler to code and debug. Will be implemented by an off-line Matlab
script or an on-line/off-line C code.
5) Outputs Checker
The Checker will compare the outputs from the HAL simulator and the Golden model and will write the result to a text file.
It will be done by collecting the outputs timing and comparing on-line with the Golden Model outputs.
6) Time Plan
http://diglab.technion.ac.il/Projects/Folders/D01109/project-A.html
Recommended