nda_adaptive_equaliser_xs HDL Worker

Detail

Worker Properties

  • ocpi_buffer_size_output

    • Type: ushort

    • Access:

      • Parameter: False

      • Writable: False

      • Initial: True

      • Volatile: False

      • Read back: False

    • Default value: 0

  • ocpi_blocked_output

    • Type: ulong

    • Access:

      • Parameter: False

      • Writable: False

      • Initial: False

      • Volatile: True

      • Read back: False

    • Default value: None

  • ocpi_max_latency_output

    • Type: ushort

    • Access:

      • Parameter: True

      • Writable: False

      • Initial: False

      • Volatile: False

      • Read back: False

    • Default value: None

  • ocpi_latency_output

    • Type: ushort

    • Access:

      • Parameter: False

      • Writable: False

      • Initial: False

      • Volatile: True

      • Read back: False

    • Default value: None

  • ocpi_messages_output

    • Type: ulong

    • Access:

      • Parameter: False

      • Writable: False

      • Initial: False

      • Volatile: True

      • Read back: False

    • Default value: None

  • ocpi_bytes_output

    • Type: ulong

    • Access:

      • Parameter: False

      • Writable: False

      • Initial: False

      • Volatile: True

      • Read back: False

    • Default value: None

Worker Ports

    Inputs:

  • input

    • Protocol: complex_short_timed_sample

    • Optional: False

    • Outputs:

  • output

    • Protocol: complex_short_timed_sample

    • Optional: False

Limitations

The limitations of nda_adaptive_equaliser_xs are:

  • The 2 least significant bits of the step_size property are ignored when using the MMA estimator, because the adaptive equaliser primitive divides the step size by 4 internally for MMA (compensating for the extra fractional bits it retains in the MMA error path). The RCC worker uses full-precision arithmetic and is not affected.

  • The protocol interface FIFO primitive has a fixed depth of 8 meaning too many (more than 8) short messages input back to back may cause an overflow.

  • The processing pipeline only advances on valid sample data, so the final samples of a message (up to the pipeline depth) remain internal until further sample data, a flush or discontinuity opcode, or an end-of-file arrives. Non-sample opcodes (time, sample interval and metadata) do not advance the pipeline and are queued, in order, behind any sample data still held within it.

Utilisation

Utilization reporting is not currently implemented.