I spent today trying to get the Supermicro X11SSH-TF working with
the latest Coreboot 4.14 from git.
Board is at vendor firmware 2.5 (latest) and also most recent BMC firmware.
Luckily, writing the image has been possible via the vendor BMC (which
preferably I would like to also replace with u-bmc once Coreboot runs).
After reboot into CB, the screen stays blank. I do not have a serial
connection available at the moment. I do have the BMC, though:
The vendor BMC recognizes the Coreboot image and correctly displays
header information such as build time and version (4.14). Also, the
BMC does read the POST code from Coreboot. It rather quickly cycles
through values and ends up at 0xE3 every time. And stops there.
According to the sources, that step is related to memory init. So to
be sure, I swapped out the Samsung 2x16GB ECC modules with standard
Non-ECC Corsair DDR4. Both functional with the Supermicro firmware,
both POSTing to 0xE3 with Coreboot.
Is there any chance a recent commit has broken stuff with this board?
I read reports that this board worked for some people, so I must have
made a mistake?
Basically I followed the documentation, used the provided configuration
options and supplied the me.bin and descriptor.bin extracted from the
original firmware and kept the rest to defaults. Fsp is taken from the
3rd party repo. Is that fine for this platform?
I would appreciate any pointers or ideas what might hinder success. Will
there be debug output written to the serial console?
If anybody has the board working, could he/she share his
configuration, Coreboot version and 3rd party blobs used?
Also, once I get to run I would love to improve the documentation, so
that people new to the subject like me have an easier time. I went
through a couple of pitfalls that I would like to explain so others
can follow in my footsteps.