MrChromebox

@Rampaging-Mongoose does your device use eMMC, UFS, or NVMe for internal storage?

then it's almost certainly eMMC

> I thought so but the output differs substantially from another Chromebook I'm running your FW on so I wasn't absolutely sure. not sure what you mean - different devices...

if you have a SuzyQ cable, I can have you flash a debug build and get a log to try and see what's going on. But that's about it

here's a serial/debug enabled build. flash it (`--fmap -i COREBOOT`is sufficient), and have a minicom session open to `/dev/ttyUSB1`. Enable logging and save to file, then attach here. Do not...

> I've included three different captures: two failed boots, one with a CRC error and another with a "device" error. A successfull boot is also included. The order these caps...

OS? kernel?

anything interesting in the dmesg log? I'm not able to reproduce here on my JSL test device (maglia)

> I'm afraid you would need to flash debug build and see what happens on resume in this situation (using SuzyQ). AFAIK neither of us own any JasperLake devices, so...

ELEMI uses a PCIe-->eMMC bridge, which coreboot properly initializes. So it seems the problem is with edk2 not detecting it. The easiest solution is to swap the eMMC board for...