febv2_fw_req
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
febv2_fw_req [2019/06/04 09:45] acqilc [GBT synchronisation] |
febv2_fw_req [2021/07/10 23:21] (current) |
||
|---|---|---|---|
| Line 7: | Line 7: | ||
| * I2C configuration | * I2C configuration | ||
| + | A bonus will be to have a first version of the SEU mitigation but it's not compulsory at this stage. | ||
| ===== Master FPGA needs ===== | ===== Master FPGA needs ===== | ||
| Line 77: | Line 78: | ||
| * 3 I2C buses with mechanism to write and read remote registers | * 3 I2C buses with mechanism to write and read remote registers | ||
| - | * GBT interface | + | * GBT interface: |
| + | * decode incoming GBT frames to write I2C transfer | ||
| + | * encode I2C response to GBT frame | ||
| It should be simple but the GBT interface is not trivial. | It should be simple but the GBT interface is not trivial. | ||
| Line 92: | Line 95: | ||
| === Wiznet (Ethernet) communication === | === Wiznet (Ethernet) communication === | ||
| - | It's being implemented by Shirley, 3 separated sockets mechanism | + | It's being implemented currently but not yet tested, 3 separated sockets mechanism |
| * 10001 Slow control PETIROC | * 10001 Slow control PETIROC | ||
| Line 99: | Line 102: | ||
| Each socket should have a block to decode incoming data to register and a block to encode outgoing buffer | Each socket should have a block to decode incoming data to register and a block to encode outgoing buffer | ||
| - | (packet structure) | + | (packet structure) |
| === FTDI (USB2) readout === | === FTDI (USB2) readout === | ||
| - | Additional debug port , firmware can be inherited from SDHCAL (ILC) DIF boards | + | Additional debug port , firmware can be inherited from SDHCAL (ILC) DIF boards. It's a low priority |
| ===== TDC FPGA firmware ===== | ===== TDC FPGA firmware ===== | ||
| Line 109: | Line 112: | ||
| ==== EPort TDC transmission ==== | ==== EPort TDC transmission ==== | ||
| - | Data collection from all TDCs is done via a switch IP , Shirley is implementing it on FEBV1. | + | Data collection from all TDCs is done via a switch IP , a first version is being implemented on FEBV1. |
| The EPort IP should be part of the GBT-FPGA firmware from CERN and should be interfaced to the the switch. | The EPort IP should be part of the GBT-FPGA firmware from CERN and should be interfaced to the the switch. | ||
| - | BUSY is generated by an OR of all TDC channel (almost Full FIFO) | + | BUSY is generated by an OR of all TDC channel (almost Full FIFO) and should be propagated to Master FPGA |
| ==== I2C slow control communication ==== | ==== I2C slow control communication ==== | ||
| Line 133: | Line 136: | ||
| - | Shirley is working on those blocks for a new version of FEBV1 | + | Ongoing work on those blocks for a new version of FEBV1 |
| ==== PETIROC FSM ==== | ==== PETIROC FSM ==== | ||
febv2_fw_req.1559641541.txt.gz · Last modified: 2021/07/10 23:20 (external edit)
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
