Hi Glenn
> Regarding the test suite, one thing I've been thinking of that could help a > lot with designing test benches is to invest in some code (or blocks) for > the tedious boiler plate that is often needed for this work. One extremely > useful function would automatically extract sync in and sync out signals and > then break out the associated frames of input and output data for comparison > with expected results. Similarly, a test input generator that would take a > frame of data and create an appropriately demultiplexed array and a sync > signal to feed into a block using "from workspace" or the like. > The basic goal is to make it easier to check the input/output relationship > of a block without having to deal with things that don't matter like demux > factor and overall latency. > I have a function that takes in data and syncs as output from Simulink, extracts the data appropriately, makes complex samples (or leaves the samples real), merges the parallel streams and presents an array of vectors. I wrote this for the fft and pfb_fir tests I am developing and I can package them up and release them quite soon. One possible drawback is that they are not Simulink blocks but scripts. This makes the simulation models easier - literally just 'From Workspace' blocks, input ports, the block under test, output ports and 'To Workspace' blocks. There is also a 'generic_adc' block in the bee_xps (yellow block) library that will parallelise input data into as many streams as specified. It is meant to simulate design ideas, future ADCs etc. Regards Andrew
