dsphdl.FIRFilter
Finiteimpulse response filter
Description
The dsphdl.FIRFilter
System object™ models finiteimpulse response filter architectures optimized for HDL code
generation. The object accepts scalar or vector input, supports multichannel input, and
provides an option for programmable coefficients by using a parallel interface or a memory
interface. It provides a hardwarefriendly interface with input and output control signals. To
provide a cycleaccurate simulation of the generated HDL code, the object models architectural
latency including pipeline registers and resource sharing.
The object provides three filter structures.
The direct form systolic architecture provides a fully parallel implementation that makes efficient use of Intel^{®} and Xilinx^{®} DSP blocks.
The direct form transposed architecture is a fully parallel implementation and is suitable for FPGA and ASIC applications.
The partly serial systolic architecture provides a configurable serial implementation that makes efficient use of FPGA DSP blocks.
For a filter implementation that matches multipliers, pipeline registers, and preadders to the DSP configuration of your FPGA vendor, specify your target device when you generate HDL code.
All singlechannel filter structures remove multipliers for zerovalued coefficients, such as in halfband filters and Hilbert transforms. The object also provides an option to implement +/ 1 and power of 2 coefficients without a multiplier, and an option to implement all coefficients with CSD or factoredCSD logic. When you use scalar or multichannel input data, the filter shares multipliers for symmetric and antisymmetric coefficients. Framebased filters do not implement symmetry optimization. Multichannel filters do not remove multipliers for zerovalued coefficients. Multichannel filters share resources between channels, even if the filter coefficients are different across the channels.
The latency between valid input data and the corresponding valid output data depends on the filter structure, serialization options, the number of coefficients, and whether the coefficient values provide optimization opportunities. For details of structure and latency, see FIR Filter Architectures for FPGAs and ASICs.
To filter input data with an HDLoptimized FIR filter:
Create the
dsphdl.FIRFilter
object and set its properties.Call the object with arguments, as if it were a function.
To learn more about how System objects work, see What Are System Objects?
Creation
Syntax
Description
creates an
HDLoptimized discrete FIR filter System object, firFilt
= dsphdl.FIRFilterfirFilt
, with default properties.
sets properties using one or more namevalue arguments. firFilt
= dsphdl.FIRFilter(___,Name=Value
)
For example:
Numerator = firpm(10,[0,0.1,0.5,1],[1,1,0,0]); fir = dsphdl.FIRFilter(Numerator,FilterStructure='Direct form transposed'); ... [dataOut,validOut] = fir(dataIn,validIn);
Properties
Unless otherwise indicated, properties are nontunable, which means you cannot change their
values after calling the object. Objects lock when you call them, and the
release
function unlocks them.
If a property is tunable, you can change its value at any time.
For more information on changing property values, see System Design in MATLAB Using System Objects.
Main
NumeratorSource
— Source of filter coefficients
'Property'
(default)  'Input port (Parallel interface)'
 'Input port (Memory interface)'
You can enter constant filter coefficients as a property, provide timevarying filter coefficients using an input argument, or provide timevarying filter coefficients using a memorystyle interface.
You cannot use programmable coefficients with multichannel data.
When you select 'Input port (Parallel interface)'
, the object
has the coeff
argument.
When you select 'Input port (Memory interface)'
, the object has
a memorystyle interface with the coeff
,
caddr
, cwren
, and
cdone
arguments.
Setting this property to 'Input port (Parallel interface)'
or
'Input port (Memory interface)'
enables the
NumeratorPrototype
property. Specify a prototype to enable the
object to optimize the filter implementation according to the values of the
coefficients.
When you use programmable coefficients with framebased input, the object does not optimize the filter for coefficient symmetry. Also, the output after a change of coefficient values might not match the output in the scalar case exactly. This difference occurs because the subfilter calculations are performed at different times relative to the input coefficient values, compared with the scalar implementation.
Dependencies
Before R2023b: To use 'Input port (Parallel
interface)'
, set the FilterStructure
property to
'Direct form systolic'
or 'Direct form
transposed'
.
Numerator
— Discrete FIR filter coefficients
[0.5 0.5]
(default)  row vector  multichannel matrix
Discrete FIR filter coefficients, specified as a row vector of real or complex values. You can specify multichannel coefficients with a KbyL matrix of real or complex values, where K is the number of channels and L is the filter length. To enable symmetry optimization, the symmetry characteristics of all channels must align. For example, if one channel is evensymmetric, all channels must be evensymmetric.
You can also specify the vector as a workspace variable, or as a call to a filter
design function. When the input data type is a floatingpoint type, the object casts
the coefficients to the same data type as the input. When the input data type is an
integer type or a fixedpoint type, you can set the coefficient data type by using the
CoefficientsDataType
property.
Example: dsphdl.FIRFilter('Numerator',firpm(30,[0 0.1 0.2 0.5]*2,[1 1 0
0]))
defines coefficients using a linearphase filter design
function.
Dependencies
To enable this property, set NumeratorSource
to
'Property'
.
NumeratorPrototype
— Prototype filter coefficients
[]
(default)  real or complex vector
Prototype filter coefficients, specified as a vector of real or complex values.
The prototype specifies a sample coefficient vector that is representative of the
symmetry and zerovalue locations of the expected input coefficients. If all input
coefficient vectors have the same symmetry and zerovalue coefficient locations, set
NumeratorPrototype
to one of those vectors. The object uses the
prototype to optimize the filter by sharing multipliers for symmetric or antisymmetric
coefficients and by removing multipliers for zerovalue coefficients.
When you use framebased input data, the object does not optimize the filter for
coefficient symmetry. The object still uses the
NumeratorPrototype
property to remove multipliers for
zerovalued coefficients.
NumeratorSource  Input Size  If No Prototype 

'Input port (Parallel interface)'  When you use scalar input data, coefficient optimizations affect
the expected size of the vector in the When you use framebased input data, specify a
 If your coefficients are unknown or not expected to share symmetry
or zerovalued locations, you can set the

'Input port (Memory interface)'  Write the same number of coefficient values as the size of the prototype.  The NumeratorPrototype property cannot be empty. The
object uses the prototype to determine the size of the coefficient memory. If
your coefficients are unknown or not expected to share symmetry or zerovalued
locations, set NumeratorPrototype to a vector with the
same length as your expected coefficients, which does not contain symmetry or
zero values, for example [1:1:NumCoeffs] . 
Dependencies
To enable this property, set NumeratorSource
to
'Input port (Parallel interface)'
or 'Input port
(Memory interface)'
.
FilterStructure
— HDL filter architecture
'Direct form systolic'
(default)  'Direct form transposed'
 'Partly serial systolic'
HDL filter architecture, specified as one of these structures:
'Direct form systolic'
— This architecture provides a fully parallel filter implementation that makes efficient use of Intel and Xilinx DSP blocks. For architecture details, see Fully Parallel Systolic Architecture. When you specify multichannel coefficients with this architecture (with interleaved input samples), the object interleaves the channel coefficients over a single parallel filter.'Direct form transposed'
— This architecture is a fully parallel implementation that is suitable for FPGA and ASIC applications. For architecture details, see Fully Parallel Transposed Architecture. When you specify multichannel coefficients with this architecture (with interleaved input samples), the object interleaves the channel coefficients over a single parallel filter.'Partly serial systolic'
— This architecture provides a serial filter implementation and options for tradeoffs between throughput and resource utilization. The architecture makes efficient use of Intel and Xilinx DSP blocks. The object implements a serial Lcoefficient filter with M multipliers and requires input samples that are at least N cycles apart, such that L = N×M. You can specify either M or N. For this implementation, the object provides theready
output argument which indicates when the object is ready for new input data. For architecture and performance details, see Partly Serial Systolic Architecture (1 < N < L) and Fully Serial Systolic Architecture (N ≥ L). You cannot use framebased input with the partly serial architecture.When you specify multichannel coefficients with a serial architecture, you must specify the serialization factor as the number of cycles between valid input samples.
For multichannel input that is scalar and interleaved over the channels, the object implements these serial architectures:
When N < L: Partly serial filter with L/N multipliers.
When N >= L: Fully serial filter.
When your multichannel input is a 1byK vector, where K is the number of channels, the object implements these serial architectures:
When N = 1: Filter bank of fully parallel filters.
When 1 < N < K: Filter bank of partly serial filters. (since R2024a)
When N = K: Fully parallel filter with channel coefficients interleaved.
When K < N < L×K: Partly serial filter with L×K/N multipliers.
When N >= L×K: Fully serial filter.
If any filter is symmetric, the architecture shares multipliers for matching
coefficients, so effectively L becomes
L/2
. To enable the symmetry optimization for
multichannel filters, the symmetry characteristics of all channels must align.
All singlechannel implementations remove multipliers for zerovalued coefficients. Multichannel filters do not optimize for zerovalued coefficients. When you use scalar or multichannel input data, the filter shares multipliers for symmetric and antisymmetric coefficients. Framebased filters do not implement symmetry optimization. Multichannel filters share resources between channels, even if the filter coefficients are different across the channels.
SerializationOption
— Rule to define serial implementation
'Minimum number of cycles between valid input
samples'
(default)  'Maximum number of multipliers'
Specify the rule that the object uses to serialize the filter as either:
'Minimum number of cycles between valid input samples'
— Specify a requirement for input data timing by using theNumCycles
property.'Maximum number of multipliers'
— Specify a requirement for resource usage by using theNumberOfMultipliers
property. This option is not supported when you have multichannel coefficients.
For a filter with L coefficients, the object implements a serial filter with not more than M multipliers and requires input samples that are at least N cycles apart, such that L = N×M. The object might remove additional multipliers when it applies coefficient optimizations, so the actual M or N values of the filter implementation might be lower than the specified value.
If the filter is symmetric, the architecture shares multipliers for matching
coefficients, so effectively L =
L/2
.
When you use complex input data and/or complex coefficients with a singlechannel partly serial architecture, the object implements complex interleaving to share the multipliers over inactive input cycles. For complex input and complex coefficients, the object needs at least L×3 cycles to implement the filter with a single multiplier. For complex input with real coefficients or complex coefficients with real input, the object needs at least L×2 cycles to implement the filter with a single multiplier. (since R2023b)
Dependencies
To enable this property, set FilterStructure
to
'Partly serial systolic'
.
NumCycles
— Serialization requirement for input timing
2
(default)  positive integer
Serialization requirement for input timing, specified as a positive integer. This
property represents N, the minimum number of cycles between valid
input samples. In this case, the object calculates M =
L/N. To implement a fully serial architecture,
set NumCycles
to a value greater than the filter length,
L, or to Inf
. To implement a fully serial
architecture for a multichannel filter with 1byK vector input,
set NumCycles
to a value greater than
L×K, where K is the number
of channels.
To implement a fully serial architecture for a single channel filter with complex
input and complex coefficients, set NumCycles
greater than
L×3. If you have complex input with real coefficients or complex
coefficients with real input, set NumCycles
greater than
L×2.
If the filter is symmetric, the architecture shares multipliers for matching
coefficients, so effectively L =
L/2
.
The object might remove multipliers when it applies coefficient optimizations, so the actual M and N values of the filter might be lower than the specified value.
Dependencies
To enable this property, set FilterStructure
to
'Partly serial systolic'
and set
SerializationOption
to 'Minimum number of cycles
between valid input samples'
.
NumberOfMultipliers
— Serialization requirement for resource usage
2
(default)  positive integer
Serialization requirement for resource usage, specified as a positive integer.
This property represents M, the maximum number of multipliers in
the filter implementation. In this case, the object calculates N =
L/M. If the input data is complex, the object
allocates floor(M/2)
multipliers for the real
part of the filter and floor(M/2)
multipliers
for the imaginary part of the filter. To implement a fully serial architecture, set
NumberOfMultipliers
to 1
for real input with
real coefficients, 2
for complex input and real coefficients or
real coefficients with complex input, or 3
for complex input and
complex coefficients.
If the filter is symmetric, the architecture shares multipliers for matching
coefficients, so effectively L =
L/2
.
When you use complex input data and/or complex coefficients with a singlechannel partly serial architecture, the object implements complex interleaving to share the multipliers over inactive input cycles. For complex input and complex coefficients, the object needs at least L×3 cycles to implement the filter with a single multiplier. For complex input with real coefficients or complex coefficients with real input, the object needs at least L×2 cycles to implement the filter with a single multiplier.
The object might remove multipliers when it applies coefficient optimizations, so the actual M and N values of the filter might be lower than the specified value.
Dependencies
To enable this property, set the FilterStructure
to
'Partly serial systolic'
, and set
SerializationOption
to 'Maximum number of
multipliers'
.
You cannot use this property when you specify multichannel coefficients. Use the
NumCycles
property instead.
Data Types
RoundingMethod
— Rounding method for typecasting the output
'Floor'
(default)  'Ceiling'
 'Convergent'
 'Nearest'
 'Round'
 'Zero'
Rounding method for typecasting the output, specified as
'Floor'
, 'Ceiling'
,
'Convergent'
, 'Nearest'
,
'Round'
, or 'Zero'
. The rounding method is
used when casting the output to the data type specified by the
OutputDataType
property. When the input data type is floating
point, the object ignores the RoundingMethod
property. For more
details, see Rounding Modes.
OverflowAction
— Overflow handling for typecasting the output
'Wrap'
(default)  'Saturate'
Overflow handling for typecasting the output, specified as
'Wrap'
or 'Saturate'
. Overflow handling is
used when casting the output to the data type specified by the
OutputDataType
property. When the input data type is floating
point, the object ignores the OverflowAction
property. For more
details, see Overflow Handling.
CoefficientsDataType
— Data type of discrete FIR filter coefficients
'Same word length as input'
(default)  numerictype
object
Data type of discrete FIR filter coefficients, specified as 'Same word
length as input'
or a numerictype
object. To specify a numerictype
object,
call numerictype(s,w,f)
, where:
s
is1
for signed and0
for unsigned.w
is the word length in bits.f
is the number of fractional bits.
When the input is a fixedpoint or integer type, the object casts the filter coefficients using the rule or data type in this property. The quantization rounds to the nearest representable value and saturates on overflow. When the input data type is floating point, the object ignores this property and all internal arithmetic uses the same data type as the input.
The recommended setting for this property is 'Same word length as
input'
.
The object returns a warning or error if:
The coefficients data type does not have enough fractional length to represent the coefficients accurately.
The coefficients data type is unsigned and the coefficients include negative values.
Dependencies
To enable this property, set NumeratorSource
to
'Property'
.
OutputDataType
— Data type of discrete FIR filter output
'Full precision'
(default)  'Same word length as input'
 numerictype
object
Data type of discrete FIR filter output, specified as 'Same word length
as input'
, 'Full precision'
, or a numerictype
object. To specify a numerictype
object,
call numerictype(s,w,f)
, where:
s
is1
for signed and0
for unsigned.w
is the word length in bits.f
is the number of fractional bits.
When the input is a fixedpoint or integer type, the object casts the
output of the filter using the rule or data type in this property. The quantization
uses the settings of the RoundingMethod
and
OverflowAction
properties. When the input data type is floating
point, the object ignores this parameter and returns output in the same data type as
the input.
The object increases the word length for full precision inside each filter tap and casts the final output to the specified type. The maximum final internal data type (WF) depends on the input data type (WI), the coefficient data type (WC), and the number of coefficients (L), and is given by
WF = WI + WC +
ceil(log2(L))
.
When you specify a fixed set of coefficients, the actual fullprecision internal word length is usually smaller than WF because the values of the coefficients limit the potential growth. When you use programmable coefficients, the object cannot calculate the dynamic range, and the internal data type is always WF.
Control Arguments
ResetInputPort
— Option to enable reset input
argument
false
(default)  true
Option to enable the
reset
input argument, specified as true
or
false
. When you set this property to true
, the
object expects a value for the reset
input argument. The reset signal
implements a local synchronous reset of the data path registers.
For more reset considerations, see the Reset Signal section on the Hardware Control Signals page.
HDLGlobalReset
— Option to connect data path registers to generated HDL global reset signal
false
(default)  true
Option to connect the data path registers to
the generated HDL global reset signal, specified as true
or
false
. Set this property to true
to connect the
generated HDL global reset signal to the data path registers. This property does not
change the arguments of the object or modify simulation behavior in MATLAB^{®}. When you set this property to false
, the generated HDL
global reset clears only the control path registers. The generated HDL global reset can be
synchronous or asynchronous depending on your HDL code generation settings.
For more reset considerations, see the Reset Signal section on the Hardware Control Signals page.
Implementation
CoeffMultiplier
— Coefficient multiplier implementation in hardware
'Multiplier'
(default)  'CSD/FactoredCSD'
Since R2023b
By default, the object implements coefficient multipliers using a hardware
multiplier. Select 'CSD/FactoredCSD'
to replace coefficient
multipliers with a CSD or factoredCSD implementation. A CSD or factoredCSD
implementation uses shift and add operations rather than multipliers. When you select
CSD, coefficients of +/ 1 and power of 2 are also implemented with shift
logic.
The latency of the block does not change with multiplier implementation. Each multiplier has the same number of pipeline stages around it in either implementation
Dependencies
To enable this parameter, set FilterStructure
property to
'Direct form transposed'
. Using CSD multipliers with systolic
architecture is not supported because it can prevent efficient use of FPGA DSP
blocks.
CSD implementations are not supported for multichannel or programmable filters.
UseMultForPow2Coeff
— Specialvalue coefficient multiplier implementation in hardware
true
(default)  false
Since R2023b
By default, the object implements specialvalue coefficient multipliers using a hardware multiplier. Set this property to false to replace specialvalue coefficient multipliers with a shift implementation.
Dependencies
To enable this property, set the FilterStructure
property
to 'Direct form transposed'
, and set
CoeffMultiplier
to 'Multiplier'
,
or set FilterStructure
to 'Direct form
systolic'
.
CSD implementations are not supported for multichannel or programmable filters.
CoeffMultiplierSystolic
— Internal property for coefficient multiplier implementation in hardware
'Multiplier'
(default)
Since R2023b
This property is readonly.
The object uses this constant property when you set
FilterStructure
to 'Direct form systolic'
.
Using CSD multipliers with systolic architecture is not supported because it can
prevent efficient use of FPGA DSP blocks.
Usage
Syntax
Description
[
returns dataOut
,validOut
,ready
]
= firFilt(dataIn
,validIn
)ready
set to true
when the object is ready
to accept new input data on the next call.
The object returns the ready
argument only when you set the
FilterStructure
property to 'Partly serial
systolic'
. For example:
firFilt = dsphdl.FIRFilter(Numerator,... FilterStructure='Partly serial systolic',... SerializationOption='Minimum number of cycles between valid input samples',... NumCycles=8) ... for k=1:length(dataIn) [dataOut,validOut,ready] = firFilt(dataIn(k),validIn(k));
[
filters data using the coefficients dataOut
,validOut
]
= firFilt(dataIn
,validIn
,coeff
)coeff
. Use this syntax when you
set the NumeratorSource
property to 'Input port (Parallel
interface)'
. For example:
firFilt = dsphdl.FIRFilter(NumeratorSource='Input Port (Parallel interface)') Numerator = myGetNumerator(); % calculate coefficients for k=1:length(dataIn) [dataOut(x),validOut(x++)] = firFilt(dataIn(k),validIn(k),Numerator);
[
loads the coefficient value dataOut
,validOut
]
= firFilt(dataIn
,validIn
,coeff
,caddr
,cwren
,cdone
)coeff
to the caddr
memory location, when cwren
is 1
(true
). Set cdone
to 1
(true
) after you finish writing coefficients. The object ignores any
input data provided when cwren
is 1
(true
), but still returns dataOut
with
validOut
until it clears the filter pipeline. Use this syntax when
you set the NumeratorSource
property to 'Input port (Memory
interface)'
. For example:
firFilt = dsphdl.FIRFilter(NumeratorSource='Input Port (Memory interface)') ... for k=1:length(Numerator) [dataOut(x),validOut(x++)] = firFilt(0,0,Numerator(k),k,true,(k==length(Numerator)); for k=1:length(dataIn) [dataOut(x),validOut(x++)] = firFilt(dataIn(k),validIn(k),0,0,false,false);
[
filters data when dataOut
,validOut
]
= firFilt(dataIn
,validIn
,reset
)reset
is false
. When
reset
is true
, the object resets the filter
registers. The object expects the reset
argument only when you set
the ResetInputPort
property to true
. For example:
firFilt = dsphdl.FIRFilter(Numerator,ResetInputPort=true) ... % reset the filter firFilt(0,false,true); for k=1:length(dataIn) [dataOut(x),validOut(x++)] = firFilt(dataIn(k),validIn(k),false);
For more reset considerations, see the Reset Signal section on the Hardware Control Signals page.
Input Arguments
dataIn
— Input data
scalar  column vector  row vector
Input data, specified as a scalar, column vector, or row vector of real or complex values. Use a column vector to increase throughput by processing samples in parallel.
You can use a row vector to represent multiple channels, or you can provide scalar multichannel data with the channels interleaved. The channels can have independent filter coefficients. (since R2023a)
In R2023a and R2023b: you can use
multichannel rowvector input only if there are at least as many invalid cycles
between inputs as there are channels. When the input is a multichannel vector, the
FilterStructure
must be set to
'Partly serial systolic'
, and
NumberOfCycles
must be equal to or greater
than the number of channels. This time allows the block to implement a partlyserial
architecture that shares resources between the channels.
Frame based (column vector) input is not supported with multichannel coefficients.
The size of the row or column vector must be less than or equal to 64 elements. To implement a multichannel filter with more than 64 channels, you must use interleaved scalar input.
When the input data type is an integer type or a fixedpoint type, the object uses fixedpoint arithmetic for internal calculations and provides properties to customize the data types. When the input data type is a floatingpoint type, the object uses that input floatingpoint type for internal calculations and the output data type.
The software supports double
and
single
data types for simulation, but not for HDL code generation.
Data Types: fi
 single
 double
 int8
 int16
 int32
 uint8
 uint16
 uint32
Complex Number Support: Yes
validIn
— Indicates valid input data
scalar
Control signal that indicates if the input data is valid. When
validIn
is 1
(true
), the
object captures the values from the dataIn
argument. When
validIn
is 0
(false
), the
object ignores the values from the dataIn
argument.
Data Types: logical
coeff
— Filter coefficients (Parallel interface)
real or complex vector
Filter coefficients, specified as a vector of real or complex values. You can
change the input coefficients at any time. When you use scalar input data, the size of
the vector depends on the size and symmetry of the sample coefficients specified in
the NumeratorPrototype
property. The prototype specifies a sample
coefficient vector that is representative of the symmetry and zerovalue locations of
the expected input coefficients. The object uses the prototype to optimize the filter
by sharing multipliers for symmetric or antisymmetric coefficients, and by removing
multipliers for zerovalue coefficients. Therefore, provide only the nonduplicate
coefficients in the argument. For example, if you set the
NumeratorPrototype
property to a symmetric 14tap filter, the
object expects a vector of 7 values for the coeff
argument. You
must still provide zeros in the input coeff
vector for the
nonduplicate zerovalue coefficients.
When you use framebased input data, the object does not optimize the filter for
coefficient symmetry. The object still uses the
NumeratorPrototype
property to remove multipliers for
zerovalued coefficients. Specify an input coeff
vector that is
the same size as the prototype.
If the input data
is a fixedpoint type, the
coeff
values must also be of a fixed point type. If the input
data
is a floatingpoint data type, the
coeff
values must be of the same data type.
The software supports double
and
single
data types for simulation, but not for HDL code generation.
Dependencies
To enable this argument, set the NumeratorSource
property
to 'Input port (Parallel interface)'
.
Data Types: fi
 single
 double
 int8
 int16
 int32
 uint8
 uint16
 uint32
coeff
— Filter coefficients (Memory interface)
real or complex scalar
Since R2023a
Filter coefficients, specified as a real or complex scalar value to write to
internal memory. To load a single coefficient value to internal memory, specify a
coeff
value with a corresponding address in the
caddr
argument and an enable signal in the
cwren
argument. You can change the input coefficients at any
time.
While you write new coefficients into memory, the object ignores any input data,
but still returns dataOut
with validOut
until it clears the filter pipeline. The object resumes accepting input one cycle
after cdone
is set to 1
(true
).
The
coefficient memory has the same number of addresses as the size of the
NumeratorPrototype
property. The prototype specifies a sample
coefficient vector that is representative of the symmetry and zerovalued locations of
the expected input coefficients.
When you use
scalar input data, the object uses the prototype to optimize the filter by sharing
multipliers for symmetric or antisymmetric coefficients, and by removing multipliers
for zerovalued coefficients.
You must write the
entire set of coefficients to the memory, including symmetric or zerovalue
coefficients. For example, if you set the NumeratorPrototype
property to a symmetric 14tap filter, you must write 14 values to the memory
interface.
When you use framebased input data, the object does not optimize the filter for
coefficient symmetry. The block still uses the NumeratorPrototype
property to remove multipliers for zerovalued coefficients. The coefficient memory
has the same number of locations as the size of the prototype.
If the input data
is a fixedpoint type, the
coeff
values must also be of a fixed point type. If the input
data
is a floatingpoint data type, the
coeff
values must be of the same data type.
The software supports double
and
single
data types for simulation, but not for HDL code generation.
Dependencies
To enable this argument, set the NumeratorSource
property
to 'Input port (Memory interface)'
.
Data Types: fi
 single
 double
 int8
 int16
 int32
 uint8
 uint16
 uint32
caddr
— Filter coefficient address (Memory interface)
scalar
Since R2023a
Specify the filter coefficient address as a scalar integer value represented as an
unsigned fixedpoint type with zero fractional bits. The object derives the size of
this integer value, and the size of the internal memory, from the number of unique
coefficients in the NumeratorPrototype
property value.
The software supports double
and
single
data types for simulation, but not for HDL code generation.
Dependencies
To enable this argument, set the NumeratorSource
property
to 'Input port (Memory interface)'
.
Data Types: fi(0,N,0)
cwren
— Filter coefficient write enable (Memory interface)
scalar
Since R2023a
Set this argument to 1
(true
) to write the
value of the coeff
argument into the caddr
location in internal memory.
The software supports double
and
single
data types for simulation, but not for HDL code generation.
Dependencies
To enable this argument, set the NumeratorSource
property
to 'Input port (Memory interface)'
.
Data Types: fi(0,N,0)
cdone
— Filter coefficients write complete (Memory interface)
scalar
Since R2023a
Set this argument to 1
(true
) to indicate
that the current arguments write the final coefficient value to memory.
The software supports double
and
single
data types for simulation, but not for HDL code generation.
Dependencies
To enable this argument, set the NumeratorSource
property
to 'Input port (Memory interface)'
.
Data Types: fi(0,N,0)
reset
— Clears internal states
logical scalar
Control signal that clears internal states. When reset
is
1
(true
), the object stops the current
calculation and clears internal states. When the reset
is
0
(false
) and the input
valid
is 1
(true
), the
block captures data for processing.
For more reset considerations, see the Reset Signal section on the Hardware Control Signals page.
Dependencies
To enable this argument, set the ResetInputPort
property to
true
.
Data Types: logical
Output Arguments
dataOut
— Filtered output data
scalar  column vector  row vector
Filtered output data, returned as a scalar, column vector, or row vector of real
or complex values. The dimensions of the output data match the dimensions of the input
data. When the input data is floating point, the output data inherits the data type of
the input data. When the input data is an integer type or fixedpoint type, the
OutputDataType
property determines the output data type.
Data Types: fi
 single
 double
 int8
 int16
 int32
 uint8
 uint16
 uint32
Complex Number Support: Yes
validOut
— Indicates valid output data
scalar
Control signal that indicates if the output data is valid. When
validOut
is 1
(true
), the
object returns valid data from the dataOut
argument. When
validOut
is 0
(false
),
values from the dataOut
argument are not valid.
Data Types: logical
ready
— Indicates object is ready for new input data
scalar
Control signal that indicates that the object is ready for new input data sample
on the next cycle. When ready
is 1
(true
), you can specify the dataIn
and validIn
inputs for the next
time step. When ready
is 0
(false
), the object ignores any input data in the next time step.
When using the partly serial architecture, the object processes one sample at a
time. If your design waits for the object to return ready
set to
0
(false
) before setting
validIn
to 0
(false
), then
one additional input data value arrives at the object. The object stores this
additional data while processing the current data, and does not set
ready
to 1
(true
) until the
additional input is processed.
Dependencies
To enable this argument, set the FilterStructure
property
to 'Partly serial systolic'
.
Data Types: logical
Object Functions
To use an object function, specify the
System object as the first input argument. For
example, to release system resources of a System object named obj
, use
this syntax:
release(obj)
Specific to dsphdl.FIRFilter
getLatency  Latency of FIR filter 
Examples
Create HDL FIR Filter System Object for HDL Code Generation
To generate HDL code from a System object™, create a function that contains and calls the object.
Create Function
Write a function that creates and calls an 11tap HDL FIR filter System object. You can generate HDL code from this function.
function [dataOut,validOut] = HDLFIR11Tap(dataIn, validIn) %HDLFIR11Tap % Process one sample of data by using the dsphdl.FIRFilter System % object. % dataIn is a fixedpoint scalar value. % You can generate HDL code from this function. persistent fir if isempty(fir) Numerator = firpm(10,[0 0.1 0.5 1],[1 1 0 0]); fir = dsphdl.FIRFilter(Numerator); end [dataOut,validOut] = fir(dataIn,validIn); end % Copyright 20172023 The MathWorks, Inc.
Create Test Bench for Function
Clear the workspace, create an input signal of random noise, and allocate memory for outputs.
clear variables clear HDLFIR11Tap L = 200; dataIn = fi(randn(L,1),1,16); validIn = ones(L,1,'logical'); dataOut = fi(zeros(L,1),1,16); validOut = false(L,1);
Call the function on the input signal.
for k = 1:L [dataOut(k),validOut(k)] = HDLFIR11Tap(dataIn(k), validIn(k)); end
Plot the signals with the Logic Analyzer.
la = dsp.LogicAnalyzer(NumInputPorts=4,SampleTime=1,TimeSpan=L); tags = getDisplayChannelTags(la); modifyDisplayChannel(la,tags{1},'Name','validIn'); modifyDisplayChannel(la,tags{2},'Name','dataIn'); modifyDisplayChannel(la,tags{3},'Name','dataOut'); modifyDisplayChannel(la,tags{4},'Name','validOut'); la(validIn,dataIn,dataOut,validOut)
Implement a PartlySerial Streaming FIR Filter
This example shows how to configure the dsphdl.FIRFilter
System object™ as a partlyserial 31tap lowpass filter.
Design the filter coefficients. Then create an HDL FIR filter System object. Set the FilterStructure
to 'Partly serial systolic'
. By default, the SerializationOption
property is 'Minimum number of cycles between valid input samples'
, and so you must specify the serialization rule using the NumCycles
property. To share each multiplier between 10 coefficients, set the NumCycles
to 10.
numerator = firpm(30,[0 0.1 0.2 0.5]*2,[1 1 0 0]); numCycles = 10; firFilt = dsphdl.FIRFilter(numerator, ... FilterStructure='Partly serial systolic', ... NumCycles=numCycles);
This serial filter implementation requires 10 time steps to calculate each output. Create input signals dataIn
and validIn
such that new data is applied only every NumCycles
time steps.
L = 16;
x = fi(randn(L,1),1,16);
dataIn = zeros(L*numCycles,1,'like',x);
dataIn(1:numCycles:end) = x;
validIn = false(L*numCycles,1);
validIn(1:numCycles:end) = true;
Create a LogicAnalyzer
object to view the inputs and output signals.
la = dsp.LogicAnalyzer(NumInputPorts=5, ... SampleTime=1, ... TimeSpan=length(dataIn)); tags = getDisplayChannelTags(la); modifyDisplayChannel(la,tags{1},'Name','dataIn'); modifyDisplayChannel(la,tags{2},'Name','validIn'); modifyDisplayChannel(la,tags{3},'Name','dataOut'); modifyDisplayChannel(la,tags{4},'Name','validOut'); modifyDisplayChannel(la,tags{5},'Name','ready');
Call the filter System object on the input signals, and view the results in the Logic Analyzer. The object models HDL pipeline registers and resource sharing, so the waveform shows an initial delay before the object returns valid output samples.
for k=1:length(dataIn) [dataOut,validOut,ready] = firFilt(dataIn(k),validIn(k)); la(dataIn(k),validIn(k),dataOut,validOut,ready) end
Explore Latency of FIR Object
The latency of the dsphdl.FIRFilter
System object™ varies with filter structure, serialization options, input vector size, and whether the coefficient values provide optimization opportunities. Use the getLatency
function to find the latency of a particular configuration. The latency is the number of cycles between the first valid input and the first valid output.
Create a dsphdl.FIRFilter
System object™ and request the latency. The default architecture is fully parallel systolic. The default data type for the coefficients is 'Same word length as input'
. Therefore, when you call the getLatency
object function, you must specify an input data type. The object casts the coefficient values to the input data type, and then checks for symmetric coefficients. This Numerator
has 31 symmetric coefficients, so the object optimizes for the shared coefficients, and implements 16 multipliers.
Numerator = firpm(30,[0 0.1 0.2 0.5]*2,[1 1 0 0]);
Input_type = numerictype(1,16,15); % object uses only the word length for coefficient type cast
hdlfir = dsphdl.FIRFilter(Numerator);
L_sysp = getLatency(hdlfir,Input_type)
L_sysp = 23
For the same fully parallel filter with vector input, the latency is lower. Call getLatency
with an input vector size of four to check the latency for that case. The empty arguments are placeholders for when you use programmable coefficients or complex input data.
L_syspv = getLatency(hdlfir,Input_type,[],[],4)
L_syspv = 17
Check the latency for a partly serial systolic implementation of the same filter. By default, the SerializationOption
property is 'Minimum number of cycles between valid input samples'
, and so you must specify the serialization rule using the NumCycles
property. To share each multiplier between 8 coefficients, set the NumCycles
to 8. The object then optimizes based on the coefficient symmetry, so there are 16 unique coefficients shared 8 times each over 2 multipliers. This serial filter implementation requires input samples that are valid every 8 cycles.
hdlfir = dsphdl.FIRFilter(Numerator,FilterStructure='Partly serial systolic', ... NumCycles=8); L_syss = getLatency(hdlfir,Input_type)
L_syss = 19
Check the latency of a nonsymmetric fully parallel systolic filter. The Numerator
has 31 coefficients.
Numerator = sinc(0.4*[30:0]); hdlfir = dsphdl.FIRFilter(Numerator); L_sysp = getLatency(hdlfir,Input_type)
L_sysp = 37
Check the latency of the same nonsymmetric filter implemented as a partly serial systolic filter. In this case, specify the SerializationOption
by the number of multipliers. The object implements a filter that has 2 multipliers and requires 8 cycles between input samples.
hdlfir = dsphdl.FIRFilter(Numerator,FilterStructure='Partly serial systolic', ... SerializationOption='Maximum number of multipliers', ... NumberOfMultipliers=2); L_syss = getLatency(hdlfir,Input_type)
L_syss = 37
Check the latency of a fully parallel transposed architecture. The latency for this filter structure with scalar input is always 6 cycles.
hdlfir = dsphdl.FIRFilter(Numerator,FilterStructure='Direct form transposed');
L_trans = getLatency(hdlfir,Input_type)
L_trans = 6
The latency of the transposed filter increases with input vector size.
L_transv4 = getLatency(hdlfir,Input_type,[],[],4)
L_transv4 = 9
L_transv8 = getLatency(hdlfir,Input_type,[],[],16)
L_transv8 = 11
Algorithms
This System object implements the algorithms described on the Discrete FIR Filter block reference page.
Extended Capabilities
C/C++ Code Generation
Generate C and C++ code using MATLAB® Coder™.
This System object supports C/C++ code generation for accelerating MATLAB simulations, and for DPI component generation.
HDL Code Generation
Generate VHDL, Verilog and SystemVerilog code for FPGA and ASIC designs using HDL Coder™.
The software supports double
and
single
data types for simulation, but not for HDL code generation.
To generate HDL code from predefined System objects, see HDL Code Generation from Viterbi Decoder System Object (HDL Coder).
Version History
Introduced in R2017aR2024a: Use multichannel vector input with fully parallel filters
Starting in R2024a, the object supports multichannel vector input for 'Direct form systolic'
and 'Direct form transposed'
filter structures. The object also now supports multichannel vector input for 'Partly serial systolic'
filters with NumberOfCycles
less than the number of channels.
R2023b: Multichannel optimization for symmetric filters
When you use multichannel input data, the object shares multipliers between odd or evensymmetric filter coefficients. To enable the symmetry optimization, the symmetry characteristics of all channels must align. For example, if one channel is evensymmetric, all channels must be evensymmetric.
R2023b: Partly serial FIR filter optimization for complex multipliers
When you use complex input data and/or complex coefficients with a partly serial architecture, the object implements complex interleaving to share the multipliers over inactive input cycles. This optimization uses fewer multipliers and increases the latency of the filter.
For complex input and complex coefficients, the object needs at least NumCycles
= 3*FilterLength
to implement the filter with a single multiplier. For complex
input with real coefficients or complex coefficients with real input, the object needs at
least NumCycles = 2*FilterLength
to implement the filter with a single
multiplier. The effective filter length is FilterLength/2
if the filter
is symmetrical.
R2023b: Programmable coefficients with serial architecture
The object supports using the parallel coefficients input port with the 'Partly
serial systolic'
architecture.
R2023b: Canonical signed digit implementation
The object provides an option to replace coefficient multipliers with a CSD or
factoredCSD implementation when you use the 'Direct form transposed'
architecture. A CSD or factoredCSD implementation uses shift and add operations rather than
multipliers. When you use 'Direct form systolic'
or 'Direct form
transposed'
, you can optionally replace multipliers with a shift implementation
for coefficients that have values equal to 1, 1, or a power of 2.
CSD implementations are not supported for multichannel or programmable filters.
R2023a: Load coefficients using memorystyle interface
This object offers an optional memorystyle interface to load coefficients. To use this
interface, set the NumeratorSource
property to 'Input port
(Memory interface)'
. You can use this coefficient interface with any filter
architecture.
R2023a: Multichannel support
Specify coefficients as a KbyL matrix, where K is the number of channels and L is the
filter length. You can supply input data as a Kby1 rowvector or as scalar input with the
channels interleaved in time. The filter shares resources between channels, even if the
filter coefficients are different across the channels. If the input data channels have
enough cycles between valid input samples, the object can implement the multichannel filter
as a single fullyserial FIR filter. When the input is a multichannel vector, the
FilterStructure
property must be set to 'Partly serial
systolic'
, and NumberOfCycles
must be equal to or greater
than the number of channels.
R2022a: Moved to DSP HDL Toolbox from DSP System Toolbox
Before R2022a, this System object was named dsp.HDLFIRFilter
and was part of the DSP System Toolbox™ product.
R2022a: Highthroughput interface
This object supports highthroughput data. You can apply input data as an Nby1 vector, where N can be up to 64 values. You cannot use framebased input with the partly serial architecture.
R2022a: Input coefficients must be a row vector
When you use programmable coefficients with this object, you must supply the
coefficients as a row vector (1byN matrix). Before R2022a, the object
accepted a onedimensional array (for example, ones(5)
), a column vector
(Mby1 matrix), or a row vector of coefficients.
R2022a: RAMbased partly serial architecture
This object uses a RAMbased partly serial architecture, which uses fewer resources than
the former registerbased architecture. Uninitialized RAM locations can result in
X
values at the start of your HDL simulation. You can avoid
X
values by having your test initialize the RAM. Another option to
avoid transient effects from uninitialized RAM locations is to hold reset for
L/M cycles, where L is the number
of coefficients and M is the number of multipliers in the filter
implementation. This operation sets the RAM locations to zeros.
R2019b: Complex coefficients
The object supports complexvalued coefficients. If both coefficients and input data are complex, the object implements each filter tap with three multipliers. If either data or coefficients are complex but not both, the object uses two multipliers for each filter tap. You can use complex coefficients with all architectures and with programmable coefficients.
R2019a: Programmable coefficients
The object provides the option to specify coefficients using an input argument when you
set the FilterStructure
to 'Direct form systolic'
.
You cannot use programmable coefficients with transposed or partly serial systolic
architectures.
R2019a: Optimize symmetric coefficients
The object provides optimization of symmetric and antisymmetric coefficients. This optimization reduces the number of multipliers and makes efficient use of FPGA DSP resources.
In R2018b, the object performed these optimizations only for fully parallel architectures.
R2019a: Optional reset argument
The object provides an optional reset argument for any architecture, including a serial
systolic architecture with resource sharing. The reset
argument
provides a local synchronous reset of the data path registers.
In R2018b, the object supported the reset
argument only for fully
parallel architectures.
R2019a: Changes to serial filter parameters
Before R2019a, you specified the serial implementation by setting a requirement for input timing. Starting in R2019a, you can specify the serialization requirement based on either input timing or resource usage.
For a filter with L coefficients, the object implements a serial filter with not more than M multipliers and requires input samples that are at least N cycles apart, such that L = N×M.
Serial Filter Requirement  Configuration Before R2019a  Configuration in R2019a 

Specify a serialization rule based on input timing, that is, N cycles. 


Specify a serialization rule based on resource usage, that is, M multipliers.  Serialization by resource usage is not supported before R2019a. However, you can calculate N based on your multiplier requirement.


R2018b: Transposed architecture
The object provides an option to select a direct form transposed architecture.
R2018b: Changes to parallel filter architecture
The
validIn
argument is mandatory. TheValidInPort
property is no longer available.The
ready
argument is enabled when you setSharingFactor
totrue
and disabled when you setSharing
tofalse
. TheReadyPort
property is no longer available.When you set the
FilterStructure
property to'Direct form systolic'
withSharing
set tofalse
, the object implements an improved fully parallel architecture compared to previous releases. This architecture might have different latency than in previous versions. Use thevalidOut
signal to align with parallel delay paths. When using this architecture, the default global HDL reset now clears only the control path registers. Previous releases connected the global HDL reset to the data path registers and the control path registers. This change improves hardware performance and lowers the resources used. To implement the same fully parallel architecture as previous releases, setSharing
tofalse
and setSharingFactor
to1
.When you set the
FilterStructure
property to'Direct form systolic'
, setSharingFactor
totrue
, and use anySerializationOption
, the implemented filter has the same latency and uses the same hardware resources as in previous releases. The reset behavior for this architecture is also the same as in previous releases.
MATLAB 명령
다음 MATLAB 명령에 해당하는 링크를 클릭했습니다.
명령을 실행하려면 MATLAB 명령 창에 입력하십시오. 웹 브라우저는 MATLAB 명령을 지원하지 않습니다.
Select a Web Site
Choose a web site to get translated content where available and see local events and offers. Based on your location, we recommend that you select: .
You can also select a web site from the following list:
How to Get Best Site Performance
Select the China site (in Chinese or English) for best site performance. Other MathWorks country sites are not optimized for visits from your location.
Americas
 América Latina (Español)
 Canada (English)
 United States (English)
Europe
 Belgium (English)
 Denmark (English)
 Deutschland (Deutsch)
 España (Español)
 Finland (English)
 France (Français)
 Ireland (English)
 Italia (Italiano)
 Luxembourg (English)
 Netherlands (English)
 Norway (English)
 Österreich (Deutsch)
 Portugal (English)
 Sweden (English)
 Switzerland
 United Kingdom (English)