Difference between revisions of "DAQ/FADC firmware History"

From HallCWiki
Jump to: navigation, search
 
Line 1: Line 1:
 
=Manual=
 
=Manual=
 
*[https://coda.jlab.org/drupal/system/files/pdfs/HardwareManual/fADC250/FADC250_Processing_FPGA_Firmware_ver_0x0C0D_Description_Instructions.pdf FADC DAQ manual ]
 
*[https://coda.jlab.org/drupal/system/files/pdfs/HardwareManual/fADC250/FADC250_Processing_FPGA_Firmware_ver_0x0C0D_Description_Instructions.pdf FADC DAQ manual ]
 +
 +
= 08/02/2021 Updating FADC to 0x0c14 =
 +
* See log [https://logbooks.jlab.org/entry/3889989 entry].
 +
* The new firmware has a few fixes
 +
** the most important one is that it will now emit the digitized pulse data for cases where the firmware 'pulse identification' fails due to pile-up in the pedelstal samples.  ** This update should make it straight forward to understand what is happening in this type of anomalous event, and recover the pulse ADC information during analysis.
 +
**  This has been enabled in the ROCs by adding the line 'faSetRoguePTWFallBack(FA_SLOT,0xffff);'  in Download() and Prestart().
  
 
= 04/24/2018 Updating FADC firmware to 0xC0F =
 
= 04/24/2018 Updating FADC firmware to 0xC0F =

Latest revision as of 09:35, 7 September 2023

Manual

08/02/2021 Updating FADC to 0x0c14

  • See log entry.
  • The new firmware has a few fixes
    • the most important one is that it will now emit the digitized pulse data for cases where the firmware 'pulse identification' fails due to pile-up in the pedelstal samples. ** This update should make it straight forward to understand what is happening in this type of anomalous event, and recover the pulse ADC information during analysis.
    • This has been enabled in the ROCs by adding the line 'faSetRoguePTWFallBack(FA_SLOT,0xffff);' in Download() and Prestart().

04/24/2018 Updating FADC firmware to 0xC0F

09/22/2017 DAQ libraries updated

03/20/2017 Updating FADC firmware on SHMS DAQ

09/29/2016 Updating to '0xC01' firmware

12:52 2016-06-08

  • F250 Firmware updated to 0x908
  • There was a lot of back and forth with the FE group in 2016 finding and squashing firmware and library bugs...