Daniel Zhu

This commit **limits EEPROM reads to a maximum of 512 bytes**, primarily affecting the **`fboss/platform/weutil`** utility and the **`fboss/platform/platform_manager`** module. It **refactors** `ParserUtils::loadEeprom` to enforce this `kMaxEepromDataRegionSize` and enhances error handling for file operations, preventing oversized reads. Additionally, the change **fixes** platform-specific EEPROM access by adjusting read offsets for IDPROM data and setting the offset to 0 for SCM/SMB EEPROMs on MERU800BFA/BIA and ICECUBE800BANW platforms. This improves the **robustness and safety** of hardware data retrieval, ensuring more reliable platform identification and component information. New unit tests were added to thoroughly verify the correct implementation of these read limits and offset handling.

This commit **adds a new feature** by introducing the **SPI master configuration** to the `platform_manager.json` file for the **`BLACKWOLF800BANW`** platform. This **platform configuration update** enables the `platform_manager` to correctly discover and initialize a specific SPI device. Specifically, it maps `SpiDevice SMB_SPI_MASTER0_DEVICE1` to `/dev/spidev2010.0`. This change ensures that the platform can properly interact with hardware components connected via SPI, making the device available for system operations.

This commit **enables support** for the **`SMB_FPGA_INFO_ROM`** on the **`BLACKWOLF800BANW`** platform by introducing its configuration into the **`platform_manager.json`**. This **new capability** allows the system to properly discover and manage the `SMB_FPGA_INFO_ROM` device. Specifically, it adds the necessary `infoRomConfig` and device map entries, making details like the firmware version accessible via the device map. This ensures the platform manager can correctly interact with and report on the `SMB_FPGA_INFO_ROM`'s status.

This commit introduces the **initial definitions and basic support for the Qumran4D ASIC**, a crucial **new capability** for FBOSS. It adds the `Qumran4DAsic` class and integrates its type across various **hardware abstraction layers (BCM and SAI)**, utility functions, and build configurations within the `fboss/agent` module. Specifically, it updates `AsicUtils`, `PortUpdateHandler`, `SaiAclTableManager`, and `SaiBufferManager` to recognize and handle the new ASIC type. This foundational work extends FBOSS's hardware compatibility, enabling the recognition and fundamental interaction with Qumran4D devices. It is a prerequisite for subsequent PRs that will build out full **BLACKWOLF800BANW platform mappings** and functionality for the Qumran4D ASIC.

This commit introduces a **new platform support** by adding the `fw_util` configuration file for the **BLACKWOLF800BANW** platform. This **new capability** enables the `fw_util` tool to manage firmware for various critical components, including `bios`, `scm_cpld`, `chassis_cpld`, `smb_fpga`, and `fan_cpld`. The configuration defines the necessary settings for programming and querying firmware versions on these targets. This significantly enhances the **firmware management** capabilities for the **BLACKWOLF800BANW** hardware.

This commit introduces an optional `eepromOffset` field to **i2cDeviceConfig** to correctly handle EEPROM data stored at specific offsets, primarily addressing a **bug on the darwin48v platform**. The **PlatformExplorer** now utilizes this offset when creating `FbossEepromInterface` objects, and **weutil ConfigUtils** has been updated to check for it. Additionally, **ConfigValidator** enforces that `eepromOffset` can only be defined if `isEeprom` is true, and the `FANSPINNER_EEPROM` symlink generation is removed for `darwin48v` due to its lack of a valid Meta EEPROM. This **enhancement and bug fix** ensures proper EEPROM reading and platform initialization for devices with offset-based EEPROM configurations, such as `darwin48v`.

This commit **corrects** the **I2C adapter block configurations** for the **SMB_FPGA** on the **Blackwolf800BANW** platform. It specifically adjusts the `numAdapters` and `numBusesPerAdapter` values within the `i2cAdapterBlockConfigs` in `platform_manager.json`. This **configuration fix** ensures accurate I2C bus enumeration and management for accelerators 0 and 1, which is crucial for proper hardware interaction and platform stability.

This commit introduces the **fan_service configuration** for the **BLACKWOLF800BANW** platform, marking a **new capability** for this hardware. It adds the `fboss/platform/configs/blackwolf800banw/fan_service.json` file, which defines critical parameters for PWM, optics, sensors, and fan operation, including a conservative 70% minimum duty cycle. This work is part of a series of changes to enable initial platform support for **BLACKWOLF800BANW**, ensuring proper thermal management. A corresponding test case was also added to `fboss/platform/config_lib/ConfigLibTest.cpp` to validate the configuration's retrievability.

This commit introduces the complete **sensor_service configuration** for the **BLACKWOLF800BANW** platform, a crucial step in its initial hardware enablement. It provides all necessary sensor definitions, thresholds, and ASIC temperature configurations within `fboss/platform/configs/blackwolf800banw/sensor_service.json`. This **new capability** allows the system to properly monitor and manage environmental and component health for the new hardware. A corresponding test case was also added to `ConfigLibTest.cpp` to ensure the correct retrieval of this platform-specific configuration.

This commit introduces **platform_manager support** for the new **BLACKWOLF800BANW** platform, enabling comprehensive hardware management and exploration. It integrates configurations for all i2c devices, spidev, and ports (XCVRs and LEDs), along with an initial `bsp_tests.json` for the platform. Updates to `PlatformExplorer.cpp` and `ConfigUtils.cpp` in `weutil` ensure proper identification and handling of the platform's IDPROMs, specifically addressing potential conflicts with the Intel i2c-i801 driver. This **new platform enablement** is a critical step in bringing up the `BLACKWOLF800BANW` hardware, allowing its components to be correctly discovered and managed.

This commit introduces a **new capability** by updating the **Platform Manager** configurations to **load the ADC rail driver**. Specifically, it enables the driver for the **`meru800bfa` SCM unit** and both the **`meru800bia` SCM and SMB units** by modifying their respective `platform_manager.json` files. This **feature enablement** is crucial for **hardware health monitoring**, as it allows the system to accurately read and report voltage levels. Consequently, correct voltage readings will now be available via the `sensors` utility for these platforms.

This commit **enhances the `rackmon` platform monitoring system** by **updating the I2C address ranges** for **ORv3 BBU and PSU devices**. It modifies the configuration files `fboss/platform/rackmon/configs/register_map/orv3_bbu.json` and `fboss/platform/rackmon/configs/register_map/orv3_psu.json` to achieve parity with OpenBMC's device discovery. This **maintenance update** allows `rackmon` to discover a **wider range of ORv3 hardware components**, improving the robustness and compatibility of system monitoring. Consequently, more ORv3 BBU and PSU units can be reliably identified and managed within the system.

This commit introduces a **bug fix** for the **Darwin platform** by updating the `fboss/platform/configs/darwin/platform_manager.json` configuration. It adds a new entry to the **Platform Manager (PM)** to automatically generate a symlink for `PEM_EEPROM`. This change resolves an issue where `weutil` hardware tests were failing on Darwin due to the absence of this critical symlink, which was expected by the `weutil` configuration. The update ensures that `weutil` can now properly access the PEM EEPROM, guaranteeing correct hardware diagnostics and test execution on Darwin systems.

This commit **updates the platform configuration** for the **Meru800bfa platform** by modifying `fboss/platform/configs/meru800bfa/platform_manager.json`. It specifically changes the kernel device names for four **ISL power management drivers** from `isl68226` to `bp4a_isl68226`. This **maintenance change** ensures that the system correctly utilizes the **backported ISL drivers**, enabling proper detection and management of these power controllers on the Meru800bfa hardware. The update is crucial for accurate **I2C device enumeration** and **power management functionality** on this platform.

This commit **updates the temperature sensor critical and alarm thresholds** for multiple **MAX6581 inputs** within the `fboss/platform/configs/meru800bia/sensor_service.json` configuration. This **configuration update** aligns the system's thermal monitoring with **Broadcom hardware guidance**, setting maximum excursion temperatures at 115°C for core/serdes and 105°C for HBM, while also accounting for the accuracy of the **MAX6581 sensor**. The change ensures that the **thermal monitoring and alerting system** accurately reflects safe operating limits, preventing potential hardware damage due to overheating by triggering warnings and critical events at appropriate, hardware-defined thresholds.

This commit performs a **refactoring** to **remove an unnecessary platform reference** for `meru800biab` within the **platform manager**'s `PlatformExplorer.cpp`. Specifically, it updates the `getPmUnitNameFromSlot` function by eliminating a conditional check for `meru800biab`, as recent platform logic changes dictate that `meru800biab` now utilizes `meru800bia` configurations. This **maintenance** task streamlines the platform identification process, ensuring `meru800biab` correctly inherits its configuration. Other `meru800biab` references in `agent` and `qsfp_service` are intentionally preserved as they remain critical for product differentiation. The change has been verified to have no adverse impact on `platform_manager` or `qsfp_service`.

This commit **consolidates platform configurations** by directing `MERU800BIAB` systems to utilize the existing configurations designed for `MERU800BIA`. This **configuration simplification** is implemented within the `fboss/platform/helpers/PlatformNameLib.cpp` module, where the `sanitizePlatformName` function now includes logic to map 'MERU800BIAB' to 'MERU800BIA'. By removing redundant configuration files for `MERU800BIAB`, this change streamlines the **platform configuration system** and ensures consistent behavior across these similar hardware platforms. The primary impact is on `MERU800BIAB` systems, which will now correctly load and operate using the `MERU800BIA` settings.