Sundance PARS User Manual
Page 42
Revision 11-wip-7
Page 42 of 70
Sundance Digital Signal Processing, Inc.
4790 Caughlin Parkway 233, Reno, NV 89519-0907, U.S.A.
email:
Tel: +1 (775) 827-3103
www.sundancedsp.com
For FPGA-to-FPGA connections, PARS includes an interface called ‘SCom’ which
allows for aggregating N:N connections over a single wire. This has the effect of
relaxing the restriction when making models that spread out onto multiple FPGA
subsystems. To use these, just use the SCom blocks provided in the ‘PARS Diamond
Blockset’. Please see sections “3.6.3. SCOM PB Tasks” and “4.4.6. SCOM Tasks”,
below for specific details.
3.4.3.
Data Types for Connections
Another aspect of PARS that needs consideration when partitioning is the fact that PARS (currently)
can only interpret as relatively limited set of data types for connections.
Simulink Type Element size (bytes)
Notes
‘double’
8
‘single’
4
‘int8’
1
Must be vectorized into groups of 4, or complex groups of 2
‘uint8’
1
Must be vectorized into groups of 4, or complex groups of 2
‘int16’
2
Must be vectorized into groups of 2, or complex
‘uint16’
2
Must be vectorized into groups of 2, or complex
‘int32’
4
‘uint32’
4
Table 3 - Allowable connection data types in PARS
Keep in mind that there is no restriction with data types used within a subsystem apart from those
imposed by RTW, RTW-EC (for DSP targets) and HDLCoder or Sysgen (for FPGA targets).
Figure 44 - Setting data types on Input/Output ports
Typically, one can set the output or input port data type to a specific type to ensure that the type is
appropriate for any given subsystem.