Page 1 of 6
ESKI - MODULE DOCUMENTATION MOTIONDET
CLK
DIMI_CAM<7:0>
PIXSI FSYNCI
LEVEL<7:0>
MOTIONDET
ALARM
RESET DIMI_MEM<7:0>
TH<7:0>
Module responsible _______________________
Specification responsible Bengt Oelmann
Designers ____________________________________________
General description: The MotionDet module detects differences in two images in a video sequence. The output is an alarm signal indicating that the difference between the two images is larger than a certain threshold value (TH). The image difference is also indicated as an 8-bit value on the output LEVEL.
CONTENTS
Page
1. SPECIFICATION...3
1.1 INTERFACEDESCRIPTIONDIGITALSIGNALS...3
1.2 HIERARCHY...4
1.3 FUNCTIONALITY...4
1.4 DESIGNGOALS...4
DESCRIPTION OF IMPLEMENTATION...5
2. VERIFICATION...5
3. DELIVERABLES...6
3.1 DIGITALMODULES...6
Rev Date Description of modification Sign
0 Initial issue
Page 2 of 6
1. Specification
1.1 Interface description digital signals Inputs and outputs in alphabetic order.
Input signals
Signal name From Input delay Description
CLK External - Clock
DIMI_MEM<7:0> CamIF 20 ns Image data from memory DIMI_CAM<7:0> CamIF 20 ns Image data from camera
PIXSI CamIF 20 ns Data valid input
FSYNCI CamIF 20 ns Frame synchronization
RESET External 20 ns Reset
TH<7:0> Processor 20 ns Alarm Threshold-value Output signals
Signal name To Output delay Description
Level<7:0> Processor 20 ns Difference level
ALARM Processor 20 ns Alarm signal
Page 3 of 6
1.2 Hierarchy Hierarchy of module -
1.3 Functionality
The MotionDet module detects differences in two images in a video sequence. The output is an alarm signal indicating that the difference between the two images is larger than a certain threshold value (TH). The image difference is also indicated as an 8-bit value on the output LEVEL.
1.4 Design goals Frequency: 15 MHz
Page 4 of 6
Description of implementation
The implementation strategy should be described here. If special techniques have been used to fulfill the Design goal demands, this should be pointed out.
2. Verification
Describe the strategy used for verifying that the module works according to specification.
How is the module simulated?
Which functions and parameters are covered and which are not covered by the simulations? (referred to specification)
How is the other functions and parameters verified?
What are the results compared to (Matlab model, C-program, Behavioral model, manually from specification, other)
Page 5 of 6
3. Deliverables
3.1 Digital modules
The following documents should be included in the module documentation:
RTL-code(s)
Schematics
Test bench(es)
The following documents may be included in the module documentation (optional):
Result from simulation
Synthesis script
Synthesis constraints (if other than project common constraints)
Synthesis report(s)
Page 6 of 6