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

DSP Builder Advanced Error Messages

Device

Can't find devices directory

Much of the device information used to drive timing triven and device specific optimization is data-driven from a an XML file quartus\dspba\devices\device.xml. The error relates to this file being not found. This may have arisen from a corrupt install or from inadvertantly deleting it. The suggested course of action would be to reinstall. 

Error parsing device.xml Line <N> column <M>

Much of the device information used to drive timing triven and device specific optimization is data-driven from a an XML file quartus\dspba\devices\device.xml. The error relates to a problem reading this file. This may have arisen from a corrupt install or from inadvertantly editing it. The suggested course of action would be to reinstall, or undo any user edits recently committed. Note that is it not recommended that users edit the device specification file.

Cannot find device <name>

Much of the device information used to drive timing triven and device specific optimization is data-driven from a an XML file quartus\dspba\devices\device.xml. The error relates to a problem finding the device specified by the device block within this devices.xml file. This may have arisen from a corrupt install or from inadvertantly editing it. The suggested course of action would be to reinstall, or undo any user edits recently committed to device.xml. Note that is it not recommended that users edit the device specification file.

No definition found for speed grade <N> in family <name>

Much of the device information used to drive timing triven and device specific optimization is data-driven from a an XML file quartus\dspba\devices\device.xml. The error relates to a problem finding the information for the speed grade / device combination specified by the device block within this devices.xml file. This may have arisen from a corrupt install or from inadvertantly editing it. The suggested course of action would be to reinstall, or undo any user edits recently committed to device.xml. Note that is it not recommended that users edit the device specification file. Alternatively try a different speed grade. 


FIR

Symmetry type <type> did not correspond to symmetry size <N>

For a FIR filter of a given number of taps, there will be an expected number of coefficients specified. The relationship between coefficients specified and the number of taps varies according to whether the filter has symmetry (symmetric or anti-symmetric) or no symmetry. The error relates to finding a different number of coefficents that expected. Check that your filter size, symmetry type and coefficients are consistent for the FIR filters in the design.

Coefficient bank <bank>, Half band and L-th band filters require reset coefficients to have zeros at the correct place. Coeficient(s) <coeff> {is / are} not 0

The coefficient values specified for the filter are incompatible with the filter type specified. The inconsistency has to be corrected before simulation and generation can proceed. 

Coefficient bank <bank>, {Antisymmetric / Symmetric} filters require reset coefficients to be matched. Coefficient pair(s) <coeff> {does / do} not match

The coefficient values specified for the filter are incompatible with the filter type specified. The inconsistency has to be corrected before simulation and generation can proceed.

Coefficient bank <bank>, the middle coefficient <index> in an odd length, anti-symmetric filter must be 0

The middle coefficient value specified for the filter is incompatible with the filter type specified. The inconsistency has to be corrected before simulation and generation can proceed.

Coefficient bank <bank>, cannot have anti-symmetric FIR with only one tap as that tap must be 0

The number of taps specified for the filter is incompatible with the filter type specified. The inconsistency has to be corrected before simulation and generation can proceed.

FIRs must have at least 1 coefficient. You requested <num coeffs> coefficients

Must have more than one coefficient. Check the parameter definining the coefficients for the highlighted filter. 

FIR interpolation factor must be at least 1. You requested an interpolation factor of <interp>

The interpolation factor for the highlighted filter is less than 1. Check the parameter definining the interpolation for the highlighted filter. 

FIR decimation factor must be at least 1. You requested an decimation factor of <decim>

The decimation factor for the highlighted filter is less than 1. Check the parameter definining the decimation for the highlighted filter. 

FIRs support up to a maximum of a 64th-band filter. You requested a <N> band filter

Here N > 64 is not supported. DSPBA can only generate filters up to 64th-band. In practice anything beyond around 7th band should be unnecessary. 

FIRs support input data widths of 2 to 32 bits. You requested a <width> bit input

The input data width is outside of the supported range. The suggested action is to use a Scale block to reduce the precision and bit width of the input data type.

FIRs support coefficient widths of 2 to 32 bits. You requested a <width> bit coefficient

The coefficient data width is outside of the supported range. The suggested action is to use a specify a reduced precision and bit width for the coefficients.

The FIR filters are restricted to no more than 256 channels per input wire or output wire. Please contact Altera if you need this capability

DSPBA only supports up to 256 channels per input wire or output wire (limited by the 8-bit Channel signal). If you have need for more than this many channels on a single wire, let Altera know.

FIRs support output widths of 2 to 64 bits. Your requested settings would require an output bit width of <width>

The output width required for the highlighted filter is outside the supported range. Consider using a scale block to reduce the precision and bit width of the input data type, or specifing a reduced precision and bit width for the coefficients.

Fractional FIR: interpolation and decimation factors have a common divisor <factor>. This is not supported

Interpolation and Decimation rates have to be co-prime - i.e. share no common factors. Check that this is the case for the highlighted filter.

Decimation is only supported for FIRs with a sample rate lower than the clock rate

Decimation of super-sample inputs is not currently supported. 

Cannot have fewer taps then the amount of interpolation

This derives from the mathematics or FIR filters. The number of taps has to be increased to support the specified interpolation rate on the highlighted filter. 

Illegal settings have lead to not having inputs or outputs in your system?

Check the parameterization of the highlighted FIR filter. For the parameters specified either the input or output data will be NULL. 

Input sample rate must be an integer multiple of clock rate if greater than the clock rate

Non-integer ratios of input sample rate to clock rate are not currently supported. Check the parameterization of the highlighted filter. 

Half band and L-th band filters require symmetric, odd length filters

The coefficient values specified for the filter are incompatible with the filter type specified. The inconsistency has to be corrected before simulation and generation can proceed.

Block <name>: Too many coefficients specified (<N>). maximum is <MAX COEFF>

The named FIR filter block has more than the maximum number of coefficients. The number of coefficients for this filter has to be reduced before simulation and generation can continue.



Version history
Revision #:
1 of 1
Last update:
‎06-25-2019 10:58 PM
Updated by:
 
Contributors