Uploaded image for project: 'SAFe Program'
  1. SAFe Program
  2. SP-2007

Correlator IP Tango Device and Visibility Transport FW

Details

    • Feature
    • Must have
    • PI12
    • None
    • Obs Mgt & Controls
    • Hide

      Integration of the correlator is the next step towards end-to-end processing and will reduce the risk of integration during TDC AA0.5 Build 1.  The sync buffer is the next component in the signal chain after the fine channel packetizer and optical interconnect.

       

      Show
      Integration of the correlator is the next step towards end-to-end processing and will reduce the risk of integration during TDC AA0.5 Build 1.  The sync buffer is the next component in the signal chain after the fine channel packetizer and optical interconnect.  
      1. Visibility message assembly / UDP packetizer firmware is developed and test bench passes in simulation.
      2. Correlator Tango device is designed and implemented with test cases passing.
    • 2
    • 3
    • 13
    • 6.5
    • Team_CIPA
    • Sprint 5
    • Hide

      Correlator (X-part) firmware state machines were updated to support the TDC/AA1 firmware integration where 20 fine channels are correlated simultaneously (for 8 receptors) giving each FPGA 200 MHz of correlation BW.  The full SKA1 configuration will do a single channel at a time, 10 MHz BW per FPGA for 200 receptors.

      Visibility output formatting and packetisation is implemented as per the current CSP-SDP ICD - i.e. SPEAD with 35 byte visibility records per baseline. Each FPGA will output 744 SPEAD streams, each consisting of heaps with 36 baselines * 20 channels as a 2 dimensional array. Four FPGA will provide the full 800MHz correlated BW for AA0.5/AA1.

      Visibility packetisation implemented as two firmware modules.

      1. visibility_packetiser which performs visibility formatting and SPEAD packet creation.
      2. visibility_pkt_streams_to_ethernet which aggregates SPEAD packets from several sources (FPGA) to a single 100GbE connection, adding appropriate UDP/IP/Ethernet headers.

      Trial synthesis of these modules (synthesised on the Stratix10 FPGA independently) gives the following resource usage and maximum operating frequencies (Fmax).

      visibility_packetiser
      ==== Resource Usage ====
      ALMs 4673.5
      ALMs used for memory 150
      M20Ks 28
      DSP Blocks 19
      ==== Performance =======
      -------- Fmax Summary –
      i_clk 510.73 MHz 
      Comfortably meets required clock rate >= 390 MHz.

      visibility_pkt_streams_to_ethernet - 4 stream merge (sized for AA0.5)
      ==== Resource Usage ====
      ALMs : 4652.9
      ALMs used for memory: 210
      M20Ks : 65
      DSP Blocks : 0
      ==== Performance =======
      -------- Fmax Summary –
      i_clk : 417.89 MHz
      Meets Requires required clock rate >= 390 MHz. Although more headroom would be beneficial.

      Tango Device Servers were written for the HPS to configure the correlator long term accumulator (LTA) firmware, which controls the reading out of data from the correlator, and either accumulating it, or dumping it to the visibility packetiser. The Tango Device takes a JSON configuration string as input, interprets it to write an entry into the LTA DDR4 external memory for each baseline and channel configuration. The entries and their order instruct the firmware when to dump visibilities and in what order.

      These modules are the last in the chain for an end-to-end minimum processing FPGA bitstream, and are ready for integration in a future PI.

      Show
      Correlator (X-part) firmware state machines were updated to support the TDC/AA1 firmware integration where 20 fine channels are correlated simultaneously (for 8 receptors) giving each FPGA 200 MHz of correlation BW.  The full SKA1 configuration will do a single channel at a time, 10 MHz BW per FPGA for 200 receptors. Visibility output formatting and packetisation is implemented as per the current CSP-SDP ICD - i.e. SPEAD with 35 byte visibility records per baseline. Each FPGA will output 744 SPEAD streams, each consisting of heaps with 36 baselines * 20 channels as a 2 dimensional array. Four FPGA will provide the full 800MHz correlated BW for AA0.5/AA1. Visibility packetisation implemented as two firmware modules. visibility_packetiser which performs visibility formatting and SPEAD packet creation. visibility_pkt_streams_to_ethernet  which aggregates SPEAD packets from several sources (FPGA) to a single 100GbE connection, adding appropriate UDP/IP/Ethernet headers. Trial synthesis of these modules (synthesised on the Stratix10 FPGA independently) gives the following resource usage and maximum operating frequencies (Fmax). visibility_packetiser ==== Resource Usage ==== ALMs 4673.5 ALMs used for memory 150 M20Ks 28 DSP Blocks 19 ==== Performance ======= -------- Fmax Summary – i_clk 510.73 MHz  Comfortably meets required clock rate >= 390 MHz. visibility_pkt_streams_to_ethernet - 4 stream merge (sized for AA0.5) ==== Resource Usage ==== ALMs : 4652.9 ALMs used for memory: 210 M20Ks : 65 DSP Blocks : 0 ==== Performance ======= -------- Fmax Summary – i_clk : 417.89 MHz Meets Requires required clock rate >= 390 MHz. Although more headroom would be beneficial. Tango Device Servers were written for the HPS to configure the correlator long term accumulator (LTA) firmware, which controls the reading out of data from the correlator, and either accumulating it, or dumping it to the visibility packetiser. The Tango Device takes a JSON configuration string as input, interprets it to write an entry into the LTA DDR4 external memory for each baseline and channel configuration. The entries and their order instruct the firmware when to dump visibilities and in what order. These modules are the last in the chain for an end-to-end minimum processing FPGA bitstream, and are ready for integration in a future PI.
    • 12.6
    • Stories Completed, Integrated, Outcomes Reviewed, NFRS met, Satisfies Acceptance Criteria, Accepted by FO
    • PI22 - UNCOVERED

    Description

      Correlator FW IP was worked on in PI10 to bring it to the point where it is ready for integration, however, two key activities remain outstanding.

      1. Visibility format and protocol was up in the air so this aspect of the FW was deferred.  A decision has been made to continue to use SPEAD over UDP as indicated in the current ICD so visibility message assembly and UDP packet creation can now be implemented.
      2. Tango Device software to configure and monitor the correlator needs to be developed prior to integration.

       

       

       

       

       

      Attachments

        Issue Links

          Structure

            Activity

              People

                v.mohile Mohile, Vivek
                S.Harrison Harrison,Stephen
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (100.00%)

                  Feature Estimate: 2.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete518.0
                  Total518.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel