Community
cancel
Showing results for 
Search instead for 
Did you mean: 

DSP Builder Advanced Checklists

DSP Builder Advanced Checklists


Top Level DesignEssential Checklists

  1. There must be a Control block and a Signals block at the top level
  2. The synthesizable part of your design must be a subsystem or contained within a subsystem of the top level.
  3. There must be a Device block at the hierarchical level of the synthesizable part of the design.
  4. Test-bench stimulus data-types feeding into the synthesizable design will be propagated – so ensure they are correct. Switch on all of ‘Port Data Types’, ‘Signal Dimensions’ and ‘Wide Non-Scalar Lines’ from the Simulink model Format > Port/Signal Displays menu to have these annotated to your model so they are visible. 

Primitive Subsystems

  1. Don’t try to pipeline the system yourself – this is what the tool does for you using its internal timing models and integer linear programming. Only add Sample Delays where they are part of the algorithm; that it where your algorithm explicitly requires you to think about combining data samples from different clock cycles. This can include feedback loops. If your design is not meeting timing, you may want to consider using the Clock Margin parameter on the top level Signals block, or on a LocalThreshold block.
  2. Primitive subsystems must contain a SynthesisInfo block with style set to Scheduled, and the boundaries delimitied with ChannelIn/Out or GPIn/Out blocks.
  3. Primitive subsystems cannot contain ModelIP blocks.
  4. All subsystem inputs with associated ‘Valid’ and ‘Channel’ signals that are to be scheduled together should be routed through the same ChannelIn blocks immediately following the subsystem inputs. Any other subsystem inputs should be routed through GPIn blocks.
  5. All subsystem outputs with associated ‘Valid’ and ‘Channel’ signals that are to be scheduled together should be routed through the same ChannelOut blocks immediately before the subsystem outputs. Any other subsystem outputs should be routed through GPOut blocks.
  6. Use Convert blocks to change data type preserving real-world value.
  7. Use Set Via Dialog options to change data type preserving bit-pattern (with no bits added or removed), or to fix a data type.
  8. Use Reinterpret Cast to change data type preserving bit-pattern (with no bits added or removed); for example if converting a ‘uint32’ to ‘single’
  9. The valid signal is a scalar boolean or ufix(1).
  10. The channel signal is a scalar uint(8).
  11. Only a limited number of primitive blocks can be used outside of Primitive Subsystems but still within the synthesizable system. These are the blocks that amount to just signal routing or are explicit about their delay: SampleDelay, Constant, BitCombine, BitExtract, BitReverse, Not, Or, Xor, And, Nand, Nor, Xnor. Other primitive blocks should only be used within scheduled primitive subsystems or outside of the synthesizable part of the design.


Verification

  1. Turn on ‘Create Automatic Testbenches’ and ‘Coverage in Testbenches’ on the Control block to use. Note that stimulus capture for test-benches is done on the inputs and outputs of ModelIP blocks and by ChannelIn, ChannelOut, GPIn and GPOut blocks.
  2. Run all testbenches with

run_all_atbs(<model name>, <run simulation first? 1 : 0>, <run Quartus afterwards ? 1 : 0)

  1. Run and individual subsystem / ModelIP block testbench with

run_modelsim_atb(<path to subsystem> or <’gcb’ if currently selected>)

  1. Run the single device-level testbench from the Run ModelSim block.
  2. Look at generated resource summaries. After simulation, right click and select ‘Help’ – on the ModelIP block for ModelIP blocks, on the SynthesisInfo block for primitive subsystems, or on the Control block for a top level design summary.
  3. Use the Run All Testbenches block to control test-benches – and to access the override feature, where ModelSim results can be automatically imported back in the Matlab and a custom Matlab function used to verify and provide the pass/fail criteria. (See appendix).


Recommendation Checklists


Simulink Design settings

  1. Set Simulation > Configuration Parameters > Solver Options to “Fixed-step” / “discrete (no continuous states)”, unless folding, or you have multiple clocks in your test-bench in which case set to “Variable-step” / “discrete (no continuous states)”. This gives faster simulation than continuous solvers and also correct results round loops.
  2. Tick all options on Format > Port/Signal Displays, except “Storage Class”. It is then clear which signals are complex, which are vectors, and the data types.
  3. Hide the names of unimportant blocks to de-clutter your design using Format > hide name
  4. If using From and Goto blocks, color linked blocks the same by selecting all linked Froms & Gotos (hold down shift while clicking on each block), then right click > background color. This makes tracing the connectivity easier to see.
  5. Annotate your designs. Just double click anywhere on the background and start typing. Use Simulink Documentation blocks to link to external documentation.
  6. Matlab Window > File & Folder comparisons is a great way to see what has changed between versions of your design. 

Top Level Design

  1. Use workspace variables to set parameters you may want to vary; including clock rates, sample rates, bit-widths, channels, etc.
  2. Set workspace variables in initialization scripts. It is suggested that these are executed on the model’s PreLoadFnc and InitFcn callbacks, such that the design opens with parameters set, and any changes will be reflected in the next simulation, without having to explicitly run the script or open & close the model.
  3. Call your main initialization script for the model ‘setup_<model name>’, and – as a shortcut to editing it – include the Edit Params block in the top level of your design. (This can be found by right-clicking on the Base Blocks library in the Simulink Library Browser and Selecting ‘Open Library’.)
  4. Build a test-bench that is parameterizable – i.e. will vary correctly with system parameters such as Sample Rate, Clock Rate, and number of channels. The Channelizer block in Beta Utilities Library may be useful for this.
  5. Use the model’s StopFnc call back to run any analysis scripts automatically
  6. Build systems that make use of the valid and channel signals for control and synchronization; not latency matching. For example by capturing valid output in FIFOs to manage data-flow.
  7. Build up and use your own libraries of reusable components. You can even use the “Configurable Subsystem block” in libraries to provide a single link from which you can select library implementations in place. (See “Configurable Subsystem block” in the Simulink help).
  8. Keep block and subsystem names short, but descriptive. Avoid names with special characters, slashes or beginning with numbers.
  9. Use LocalThreshold blocks, in conjunction with the top level thresholds, for localized trade-offs or pipelining effort tweaks if necessary. 

Primitive Subsystems

  1. Make use of vectors to build parameterizable designs – that don’t need redrawing when parameters such as number of channels changes.
  2. Ensure there is sufficient Sample Delays around loops to allow for pipelining to the desired Fmax. 
  3. Data-type, complexity and vector width propagation is done by Simulink. Sometimes this is not successfully resolved round loops, particularly multiple nested loops. If unsuccessful, look for where data-types are not annotated. You may have to explicitly set data types. Else Simulink provides a library of functions to help in such situations, which duplicate data types etc. This is fixpt_dtprop (type ‘open fixpt_dtprop’ from the Matlab command prompt to open). The ‘Data Type Prop Duplicate’ block is used in the Control library latches, for example. These are guides to Simulink on data-type propagation, and do not produce hardware.
  4. If routing within a Primitive Subsystem is getting complex, you might consider using Simulink From / Goto blocks to replace connections. Make sure that the Tag Visibility on the Goto blocks is Global if crossing subsystems within a primitive subsystems. You can color code blocks too (right click > background color) to make connections more obvious. 

Design Style

  1. Don’t try to pipeline the design yourself – this is what the tool does for you using mathematical linear programming techniques. If you need more pipelining, use a positive Clock Margin (see Signals block).
  2. Don’t try to synchronize the output of different parallel subsystems using explicit delays. Use FIFOs, as this will give a more device-portable, fmax target independent design.
  3. Break designs up hierarchically to make your design understandable. However, keep consecutive primitive subsystems together within single ChannelIn/Out blocks, as this gives greater scope for scheduling and pipelining optimizations.
  4. If you think you need complex control with complex feedback or cycle-counting from the data path, think again. Look at the Mandelbrot design and understand what it is doing. It creates command instructions which are placed in a FIFO. The instructions are consumed by the data-path as fast as it can run. The result is a design that runs as fast as it can and is portable between device families, and which reduces the complexity of the control logic. 

Verification

  1. Remember that output is only guaranteed to match hardware when valid is high.
  2. run_modelsim_atb displays the command it executes. This command can be cut and paste into an open ModelSim UI open at the same directory and run manually. Using this you can analyze the behavior of particular subsystems in detail, and can force simulation to continue past errors if necessary.
  3. If using FIFOs within multiple feedback loops, it is possible that while the data-throughput and frequency of invalid cycles is the same, their distribution over a frame of data many vary (due to the final distribution of delays around the loop). If a mismatch is found, it is therefore worth stepping past errors using the above process to check whether this is the case.
  4. Floating point simulation is compared to within a tolerance. Differences are likely to be in the few least significant bits only, but could potentially be higher if the function you are implementing is ill-conditioned. Larger relative differences can also arise in complex multiplication with large complex numbers that lie close to the real or imaginary axis
  5. Use the Run All Testbenches block to control test-benches – and to access the override feature, where ModelSim results can be automatically imported back in the Matlab and a custom Matlab function used to verify and provide the pass/fail criteria. (See appendix of DSP_Builder_Advanced_Blockset_-_Flow_Control,_Design_Style_and_Floating_Point).
Version history
Revision #:
1 of 1
Last update:
‎06-25-2019 09:11 PM
Updated by:
 
Contributors