1 / 5

Trigger and JAM Report

Trigger and JAM Report. Cristiano Santoni Mauro Piccini (INFN – Sezione di Perugia). JAM/JBI Report. These tools are used mainly to configure the flash devices from which the FPGAs will get the firmware during the boot.

zoltan
Download Presentation

Trigger and JAM Report

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Trigger and JAMReport Cristiano Santoni Mauro Piccini (INFN – Sezione di Perugia)

  2. JAM/JBI Report These tools are used mainly to configure the flash devices from which the FPGAs will get the firmware during the boot. The tests done with the JAM Player have shown that the time required to configure the memories with this tool is too long, so we decided to use the JBI software that is equivalent to the JAM Player but that use a compiled version of the .jam files (.jbc) Using the JBI tool it is possible to configure each memory (or group of memory) in about 10 minutes. It is not possible to configure all the memories of the system in a single operation due to excessive memory consumption. In the Twiki, under the “CCPC software” section there is a guide to use the JBI software and a report of the allowed groups of firmware that can be combined in a single .jbc file with the time required to perform the operation. https://twiki.cern.ch/twiki/bin/view/NA62/TDAQSoftwareCcpc

  3. JAM/JBI installation The JAM Player and the JBI Player can be installed along with the JTAGlib library. The latest version of the JTAGlib available in the LHCb repository (2.4.2) is a debug version so, in order to use it, it was created a new version (2.4.3) with all the debug stuff removed and some bugscorrected. To avoid compatibility issues with other software that use the JTAGlib, this latest version was not installed, so now in the server there is a modified version of the older 2.2 version which has some bugs. However JTAGlib 2.4.3 is available in the directory /src of the server and it can be installed. First it must be compiled using the CCPC and then the library files can be copied by hand in the CCPC library folder. The main thing to verify before to officially adopt the 2.4.3 version of the JTAGlib is the compatibility with the TDSpy software, however there should not be problems because, looking at the changelog, the modifications from version 2.2 to 2.4.3 are related only to the JAM and the JBI, not to the part controlling the JTAG lines.

  4. Firmware Status The majority of the building blocks of the firmware have been developed. Logic simulations are on going and post-route simulation are scheduled after them. To get the information needed for the GPU trigger there is a missing block that will be developed as soon as possible. -Development - Simulation GPU Trigger Time-Multiplicity Retriever - Development - Simulation - Development - Simulation from Binning Logic Time Sorting Event Oriented Bin Generation - Development - Simulation Plane-based Sorting - Development - Simulation - Development - Simulation - Development - Simulation - Development - Simulation L0 Trigger Pairs Generation Impact Point Correction Event Discovering Output Formatting

  5. Firmware Integration Even if the trigger firmware is not in a stable version, the inputs and the outputs of the block are already fixed, so during the dry run we have integrated the trigger block within the TEL62 framework. Thanks to Bruno Angelucci, we have updated the CHOD version of the PP firmware to the latest PP firmware available, adding the trigger block. After the simulations on the trigger firmware in his standalone version, we will procede with the simulation on the complete PP firmware to verify the correctness of the behavior of the trigger inside the global firmware

More Related