pith. sign in

arxiv: 2310.19742 · v2 · submitted 2023-10-30 · ⚛️ physics.ins-det

Novel Developments on the OpenIPMC Project

Luigi Calligaris , Carlos R. Dell'Aquila , Antono Vitor Grossi Bassi , Andr\'e Cascadan , Luis E. Ardila-Perez , Marvin Fuchs , Alp Akpinar , Andrew Peck
show 2 more authors
Daniel Gastler Giacomo Fedi
This is my paper

Pith reviewed 2026-05-24 06:12 UTC · model grok-4.3

classification ⚛️ physics.ins-det
keywords OpenIPMCIPMCATCAfirmwaremezzanine cardboard managementparticle physics experiments
0
0 comments X

The pith

OpenIPMC firmware now supports additional protocols and features for ATCA board control.

A machine-rendered reading of the paper's core claim, the machinery that carries it, and where it could break.

The paper describes recent updates to the OpenIPMC project, which supplies open-source software and a mezzanine card for intelligent platform management on ATCA electronics. It reports on running the system on prototype boards built for upgrades at particle physics experiments and details the new firmware capabilities added to the controller card. A reader would care because these changes allow the hardware to handle more communication standards during operation in demanding environments. The work focuses on extending the existing controller rather than introducing an entirely new design.

Core claim

The OpenIPMC project has incorporated new features and support for additional protocols into the firmware of its controller mezzanine card, as shown through operational experience on prototype boards for CERN experiment upgrades.

What carries the argument

The updated firmware on the controller mezzanine card, which implements the new features and protocol support for managing ATCA boards.

If this is right

  • The mezzanine card can now communicate using a wider set of protocols during board management.
  • Prototype boards for experiment upgrades can incorporate the updated firmware without changing the underlying hardware design.
  • The open-source software stack gains compatibility with more standards used in large electronics systems.

Where Pith is reading between the lines

These are editorial extensions of the paper, not claims the author makes directly.

  • Wider testing across different board designs could reveal edge cases not seen on the CERN prototypes.
  • The changes might reduce the need for custom firmware in similar management controllers outside particle physics.
  • Long-term monitoring of deployed boards would help confirm whether the new protocol support holds up under sustained use.

Load-bearing premise

Operational experience on prototype boards is sufficient to show that the added features and protocol support work reliably.

What would settle it

A test run on a prototype board that encounters failures or incompatibilities when using one of the newly supported protocols.

read the original abstract

We present the recent developments in the context of the OpenIPMC project, which proposes a free and open-source Intelligent Platform Management Controller (IPMC) software and an associated controller mezzanine card for use in ATCA electronic boards. We discuss our experience in the operation of OpenIPMC on prototype boards designed for the upgrades of particle physics experiments at CERN and we show the addition of new features and support for new protocols in the firmware of the controller mezzanine card.

Editorial analysis

A structured set of objections, weighed in public.

Desk editor's note, referee report, simulated authors' rebuttal, and a circularity audit. Tearing a paper down is the easy half of reading it; the pith above is the substance, this is the friction.

Referee Report

2 major / 2 minor

Summary. The manuscript describes recent developments in the OpenIPMC project, an open-source Intelligent Platform Management Controller (IPMC) software and associated controller mezzanine card for ATCA electronic boards. It reports operational experience using the system on prototype boards for upgrades of particle physics experiments at CERN and details the addition of new features together with support for new protocols in the firmware of the mezzanine card.

Significance. If the operational claims are substantiated, the work would provide a useful open-source contribution to instrumentation and control hardware for large-scale detector systems at CERN and similar facilities. As presented, however, the manuscript is a descriptive engineering report whose significance is limited by the absence of quantitative validation metrics.

major comments (2)
  1. [Abstract] Abstract: the central assertion that 'operational experience on prototype boards ... demonstrates the reliability and utility' of the new firmware features and protocol support is unsupported by any quantitative data (uptime statistics, error rates, protocol-compliance test results, or enumerated failure modes). This renders the demonstration claim untestable.
  2. [Experience/Results section] Experience/Results section (wherever the CERN prototype operation is described): without tabulated metrics, test procedures, or failure-mode analysis, the reported experience cannot serve as evidence that the added features improve reliability or utility over prior versions.
minor comments (2)
  1. Define all acronyms (IPMC, ATCA, etc.) at first use and consider adding a table that enumerates the newly supported protocols and features with their implementation status.
  2. Clarify the hardware/firmware versioning and the exact boards on which the reported experience was obtained.

Simulated Author's Rebuttal

2 responses · 0 unresolved

We thank the referee for the detailed review and for highlighting the need for clearer substantiation of claims. We address each major comment below and will revise the manuscript accordingly.

read point-by-point responses

  1. Referee: [Abstract] Abstract: the central assertion that 'operational experience on prototype boards ... demonstrates the reliability and utility' of the new firmware features and protocol support is unsupported by any quantitative data (uptime statistics, error rates, protocol-compliance test results, or enumerated failure modes). This renders the demonstration claim untestable.

    Authors: We agree that the abstract's phrasing asserts a demonstration of reliability and utility that is not supported by quantitative data in the manuscript. The operational experience described is qualitative, based on deployment and continued function of the prototypes at CERN. We will revise the abstract to remove the unsubstantiated claim and instead state that the experience shows successful integration and operation of the new features and protocols. revision: yes

  2. Referee: [Experience/Results section] Experience/Results section (wherever the CERN prototype operation is described): without tabulated metrics, test procedures, or failure-mode analysis, the reported experience cannot serve as evidence that the added features improve reliability or utility over prior versions.

    Authors: We acknowledge that the Experience/Results section is descriptive and does not include tabulated metrics, explicit test procedures, or failure-mode analysis. This means the section cannot quantitatively demonstrate improvements over prior versions. We will revise the section to clarify the nature of the reported experience, remove any implication of quantified reliability gains, and focus on the implementation details of the new firmware features and protocol support. revision: yes

Circularity Check

0 steps flagged

No derivations, equations or predictions present; purely descriptive project report

full rationale

The manuscript is a status report on firmware and protocol additions to the OpenIPMC controller. It contains no equations, no fitted parameters, no claimed predictions, and no uniqueness theorems. The central statements are narrative descriptions of code changes and operational experience on prototypes. Because no derivation chain exists, none of the enumerated circularity patterns can apply. The absence of quantitative metrics is a separate correctness or completeness concern, not a circularity issue.

Axiom & Free-Parameter Ledger

0 free parameters · 0 axioms · 0 invented entities

No mathematical model, free parameters, axioms, or invented entities; this is a technical development report on software and firmware.

pith-pipeline@v0.9.0 · 5634 in / 898 out tokens · 27445 ms · 2026-05-24T06:12:44.389429+00:00 · methodology

discussion (0)

Sign in with ORCID, Apple, or X to comment. Anyone can read and Pith papers without signing in.

Reference graph

Works this paper leans on

23 extracted references · 23 canonical work pages

  1. [1]

    High-Luminosity Large Hadron Collider (HL-LHC): Technical design report,

    I. Zurbano Fernandezet al., “High-Luminosity Large Hadron Collider (HL-LHC): Technical design report,” CERN, 2020, ISBN 978-92-9083-586-8, 978-92-9083-587-5, doi:10.23731/CYRM-2020-0010

    work page doi:10.23731/cyrm-2020-0010 2020

  2. [2]

    PICMG 3.0 - AdvancedTCA Base Specification

    PICMG, “PICMG 3.0 - AdvancedTCA Base Specification”, Revision 3.0, March 24, 2008

    work page 2008

  3. [3]

    The Apollo ATCA Platform,

    A. Albertet al.“The Apollo ATCA Platform,” PoS TWEPP2019 (2020), 120, doi:10.22323/1.370.0120 [arXiv:1911.06452 [physics.ins-det]]

    work page doi:10.22323/1.370.0120 2020

  4. [4]

    Serenity: An ATCA prototyping platform for CMS Phase-2,

    A. Roseet al.“Serenity: An ATCA prototyping platform for CMS Phase-2,” PoS TWEPP2018 (2019), 115 doi:10.22323/1.343.0115

    work page doi:10.22323/1.343.0115 2019

  5. [5]

    The New Small Wheel electronics,

    G. Iakovidis, L. Levinson, Y. Afik, C. Alexa, T. Alexopoulos, J. Ameel, D. Amidei, D. Antrim, A. Badea and C. Bakalis,et al.“The New Small Wheel electronics,” JINST18 (2023) no.05, P05012 doi:10.1088/1748-0221/18/05/P05012 [arXiv:2303.12571 [hep-ex]]

    work page doi:10.1088/1748-0221/18/05/p05012 2023

  6. [6]

    CMS phase-2 DAQ and timing hub prototyping results and perspectives,

    V. Amoiridiset al.[CMS], “CMS phase-2 DAQ and timing hub prototyping results and perspectives,” JINST17(2022) no.05, C05003 doi:10.1088/1748-0221/17/05/C05003

    work page doi:10.1088/1748-0221/17/05/c05003 2022

  7. [7]

    OpenIPMC repository

    “OpenIPMC repository”,https://gitlab.com/openipmc/openipmc.Accessed Oct 24, 2023

    work page 2023

  8. [8]

    IEEE Transactions on Human-Machine Systems51(4), 335–345 (2021) https://doi

    L. Calligaris, A. Cascadan, L. E. Ardila-Perez, B. Casu, A. F. da Costa, A. A. Shinoda, L. Arruda Ramalho and O. Sander, “OpenIPMC: A Free and Open-Source Intelligent Platform Management Controller Software,” IEEE Trans. Nucl. Sci.68(2021) no.8, 2105-2112 doi:10.1109/TNS.2021.3092689 [arXiv:2011.01088 [physics.ins-det]]

    work page doi:10.1109/tns.2021.3092689 2021

  9. [9]

    A flexible and low-cost open-source IPMC mezzanine for ATCA boards based on OpenIPMC,

    L. Calligaris, A. Cascadan, L. E. Ardila-Perez, M. Pesaresi, G. Fedi, A. Peck and D. Gastler, “A flexible and low-cost open-source IPMC mezzanine for ATCA boards based on OpenIPMC,” JINST 17(2022) no.03, C03007 doi:10.1088/1748-0221/17/03/C03007 [arXiv:2112.12888 [physics.ins-det]]

    work page doi:10.1088/1748-0221/17/03/c03007 2022

  10. [10]

    A Full Mesh ATCA-based General Purpose Data Processing Board (Pulsar II),

    S. Ahujaet al., “A Full Mesh ATCA-based General Purpose Data Processing Board (Pulsar II),” doi:10.2172/1431570

    work page doi:10.2172/1431570

  11. [11]

    The BSD syslog Protocol,

    C. Lonvick, IETF Network Working Group, “The BSD syslog Protocol,” The Internet Society (2001), https://datatracker.ietf.org/doc/html/rfc3164

    work page 2001

  12. [12]

    The Syslog Protocol,

    R. Gerhards, IETF Network Working Group, “The Syslog Protocol,” IETF Trust and the authors (2009), https://datatracker.ietf.org/doc/html/rfc5424

    work page 2009

  13. [13]

    Grafana Loki OSS,

    Grafana Labs, “Grafana Loki OSS,”https://grafana.com/oss/loki/

    work page

  14. [14]

    Intelligent Platform Management Interface Specification v1.5,

    Intel Hewlett-Packard NEC Dell, “Intelligent Platform Management Interface Specification v1.5,” Document Revision 1.1, February 20, 2002

    work page 2002

  15. [15]

    Intelligent Platform Management Interface Specification v2.0,

    Intel Hewlett-Packard NEC Dell, “Intelligent Platform Management Interface Specification v2.0,” Document Revision 1.1, February 20, 2002

    work page 2002

  16. [16]

    Zynq UltraScale+ Device TRM,

    AMD Xilinx, “Zynq UltraScale+ Device TRM,” UG1085 (v2.3.1) January 4, 2023, https://docs.xilinx.com/r/en-US/ug1085-zynq-ultrascale-trm

    work page 2023

  17. [17]

    ipmitool,

    The ipmitool developers, “ipmitool,”https://codeberg.org/IPMITool/ipmitool

    work page

  18. [18]

    YAFFS2 Specification,

    Charles Manning, Aleph One Ltd., “YAFFS2 Specification,” https://yaffs.net/yaffs-2-specification

    work page

  19. [19]

    The TFTP Protocol (revision 2),

    K. Sollins, IETF Network Working Group, “The TFTP Protocol (revision 2),” IETF Trust and the authors (1992),https://datatracker.ietf.org/doc/html/rfc1350. – 6 –

    work page 1992

  20. [20]

    Dynamic Host Configuration Protocol,

    R. Droms, IETF Network Working Group, “Dynamic Host Configuration Protocol,” IETF Trust and the authors (1997),https://datatracker.ietf.org/doc/html/rfc2131

    work page 1997

  21. [21]

    DHCP Options and BOOTP Vendor Extensions,

    S. Alexander, IETF Network Working Group, “DHCP Options and BOOTP Vendor Extensions,” IETF Trust and the authors (1997),https://datatracker.ietf.org/doc/html/rfc2132

    work page 1997

  22. [22]

    PICMG HPM.3 R2.0P - LAN-Attached IPM Controller Specification

    PICMG, “PICMG HPM.3 R2.0P - LAN-Attached IPM Controller Specification”, Revision 2.0, May 4, 2016

    work page 2016

  23. [23]

    Design and Assembly Process Implementation for Bottom Termination Components (BTCs)

    IPC, “Design and Assembly Process Implementation for Bottom Termination Components (BTCs)”, IPC-7093A, 2016, – 7 –

    work page 2016