Re: [OpenBMC] Guidance on Getting Started with OpenBMC and Choosing a Development Board

[Prasanth]

Hi Kavya,

Thanks for sharing your platform details and starting a separate thread.

I am also Working On OpenBMC through ASRock Rack B650D4U enablement.
My work is still in progress, and I have not worked on the Gigabyte
MZ32-AR0 or evaluated development boards within your budget, so I
cannot recommend a specific platform confidently.

For the vendor-restricted shell, I would suggest contacting Gigabyte
support about supported debugging access and recovery procedures.

My practical recovery experience is limited to the ASRock Rack B650D4U
that I am currently working on. I use a CH341A external SPI flash
programmer for BMC firmware recovery.

I have not worked on the Gigabyte MZ32-AR0, so I cannot confirm its
recovery procedure or programmer compatibility. Please verify the
flash device, required voltage, and board-specific recovery
instructions before attempting external programming.

On Mon, Oct 26, 2026 at 4:07 PM KAVYA M M <kavyamadarsh@xxxxxxxxx> wrote:
>
> Hello OpenBMC Team,
>
> I am new to OpenBMC development and would appreciate your guidance on getting started with developing and validating an OpenBMC image for a server platform.
>
> I have a few general questions:
>
> 1. What hardware documentation is normally required to develop a reliable OpenBMC image for a new motherboard? Are the user manual and BMC reference schematic sufficient, or are the complete motherboard schematic and board-specific signal mappings essential?
> 2. If the original BMC firmware is available only as a binary and the motherboard schematic is unavailable, what is the recommended approach for identifying the hardware configuration and developing the initial image?
> 3. Which existing OpenBMC reference platforms are suitable for beginners who want to learn the Yocto/BitBake build system, device trees, machine configuration, sensor integration, and required services?
> 4. Which hardware platforms provide good support for testing sensor monitoring, fan PWM/tachometer control, Redfish, GPIO, host power control, and power sequencing?
> 5. Which functions can be tested in QEMU, and what hardware documentation and recovery facilities are necessary before proceeding with physical-board testing?
>
> Request for Guidance on Restricted BMC SSH Access
>
> I would also like to understand how to access the underlying Linux shell on a BMC when SSH access is restricted by the vendor firmware.
>
> For example, some BMCs provide SSH access but expose only a restricted interface, such as SMASH-CLP, instead of a standard Linux shell. In such cases, what is the recommended and authorized method for accessing the underlying Linux environment for debugging, inspecting system configuration, and understanding the running services?
>
> Are there standard OpenBMC debugging methods or configuration options for enabling SSH shell access during development? If access is restricted by the vendor firmware, what documentation or permissions would be required to investigate this further?
>
> My current hardware
>
> I currently have access to a Gigabyte MZ32-AR0-00 motherboard with an ASPEED AST2500 BMC.
>
> I am considering using this board for my OpenBMC development. However, I do not have access to the complete motherboard schematic, and some board-specific hardware mappings are difficult to confirm from the available documentation and original vendor firmware.
>
> I would appreciate your advice on whether this is a suitable platform for learning and developing OpenBMC, or whether a different, better-documented development platform would be a more practical starting point.
>
> Request for development-board recommendations
>
> My budget for purchasing a BMC development board is approximately ₹5,000–₹10,000.
>
> Could you recommend a specific development board or server motherboard that is affordable, well documented, and preferably has an existing upstream OpenBMC machine configuration?
>
> Ideally, I would like a platform that supports learning and testing:
>
> - OpenBMC image building using Yocto/BitBake.
> - Hardware sensor monitoring and integration.
> - Fan PWM/tachometer control and cooling failsafe behavior.
> - Redfish and other BMC management interfaces.
> - GPIO, host power control, and power sequencing.
> - QEMU-based software testing followed by physical-board validation.
>
> My preference is for a platform with an existing reference implementation, accessible hardware documentation, and a reliable firmware recovery method. Used development boards or server motherboards would also be suitable if they are available within my budget.
>
> My goal is to choose the most practical platform, build and validate an initial OpenBMC image, and gradually learn the hardware integration process before attempting to flash a physical BMC.
>
> I would be grateful for any recommendations on suitable hardware, existing reference platforms, documentation, or practical guidance from developers experienced in OpenBMC platform development.
>
> Thank you for your time and support.
>
> Best regards,
> Kavya M M