Download PPrASIC Design review

Transcript
PPrASIC Design review
5.
Design Guide
1.
General
1.
Nice piece of documentation
2.
Figure 3.1 Coding example a bad one with a signal called 'Output'.
2.
Simulation
1.
Does not seem that there is a full list of timing constraints and checks for
setup and hold times, both internally and externally
2.
Do simulations check setup and hold time violations?
3.
Have simulations been made with LHC clock and SerialCLK
asynchronous to each other?
4.
It would have been much better if the top level simulation model was a
board-level simulation including the MCM and other environments. That
way system-level errors could be found.
5.
Are all two or four channels simulated? How is it verified that you really
test the independent channels and that they don't get all the same data
and settings? Especially simulations have to be done with the
Daisychaining active.
6.
Has the chip been simulated against software? I.e. are there
routines/programs written in C that can be used to drive the simulated
chip (and later to test the real chip)?
7.
Are any coverage statistics for the simulations available?
8.
Have all border cases been tested (highest address, lowest address,
highest bit, lowest bit etc)?
9.
How is checked that the JTAG or scanpath insertion is done correctly?
This is not simulated
10.
Note: the TESTDONE and CHECKLIST files in the CVS repository are all
from last year, so it doesn't seem that they have been used.
6.
Specification of the PPrASIC
1.
Registers
1.
Spec p16. InputControl.2 5 bit only is range 0x00-0x1F to me. In spec is
written 0x3F. Where is each field placed?
2.
From section 4 of the specification, it is not clear how many bits the
different points of readout are. I don't see the correspondance with the
main block diagram, figure 2.
2.
Serial interface
1.
Spec 5.1.1: Daisy chaining not clear (FRAME has to be divided by
number of chips). How does the second chip know where his data starts?
FRAME is not shifted, so I believe you need seperate FRAME signals for
each chip and even then it is not clear what happens with the data. Have
several chips in series been simulated?
2.
Spec 5.1.1: I think any engineer connect the following signals for a daisy
chain: DataOut -> DataIn and DaisyOut -> DaisyIn. This is wrong, so this
is a serious risk when the MCM or other boards are designed. Make sure
this will be checked in the reviews of the MCM and other boards.
3.
I don't understand how is synchronised between the async domains of the
LHC clock and the SerialClk. Have simulations been made of those two
clocks in different domains? May the SerialClk be faster and slower?
Printed 15:04 5/6/00
2