Test strategy
Will do some intensive and some extensive tests
Extensive is easy, “just software”. Will do with whatever boards will be available.
I call extensive tests “slow”, since duty cycle is poor. Do not misunderstand: board clock still ticks at design frequency: data flow at 30 MHz, but system is idle 99.999% of the time.
Intensive is hard, needs to build the hardware with the test in mind, special issue for the Merger, also need care for which boards to install in the test stand and how to connect them.
Two degrees in “intensiveness”
- run fast, check slow
- run fast, check fast