User Tools

Site Tools


febv2_fw_req

This is an old revision of the document!


FEBV2 Firmware structure and requirements

One main idea is to keep the possibility to replace the Master FPGA with an LpGBT chip on the final design So we need to use:

  • elink data transmission
  • I2C configuration

Master FPGA needs

It is responsible of all communication, synchronisation and data formatting

GBT communication

Protocol

The underlying protocol is provided by the CERN IP

Messages

Backend to Frontend

The message structure is the following:

  • 84 bits
  • 82-83 : reserved
  • 81-80: EC (unused)
  • 0-79: 5 last payload long words (16 bits)
  • Extra data:
    • 0-8: register address
    • 9-11: nword
    • 12-15: unused
    • 16-31: first payload long word
Frontend to Backend

The message structure is the following:

  • 84 bits
  • 82-83 : reserved
  • 81-80: EC (unused)
    • 0 never happens
    • 1 register response
    • 2 data
    • 3 never happens
  • 0-79: 5 last payload long words (16 bits)
  • Extra data:
    • If register response:
      • 0-8: register address
      • 9-11: nword
      • 12-15: unused
      • 16-31: first payload long word
    • if data:
      • 2 first payload words

GBT synchronisation

I2C slow control to TDC

Backup readout

DCC synchronisation

Wiznet (Ethernet) communication

FTDI (USB2) readout

TDC FPGA firmware

I2C slow control communication

TDC blocks

PETIROC FSM

febv2_fw_req.1558529181.txt.gz · Last modified: 2021/07/10 23:20 (external edit)