ELEMI: MicroSD & eMMC not bootable / not able to be recognized by the firmware and lead to ' failed: verify it contains a 64-bit UEFI OS ' error, RECURRENT of #572 with extra eMMC non-bootable malfunction

[PD-Kerman]

Hellow there, this is a copy of a comment i posted in the following issue which was closed and considering the previous thread was rather old so im posting this thread and the original thread would be mentioned below

--it behaves almost the same as it was in the issue #572 which should be fixed months ago

I just got a elemi / hp c640 g2 here and seems like the issue still remains on this model, which it doesnt seem like i could boot the system from the microsd card in the slot~

• ill first paste the brief post on discord (chrultraboook) but unfortunately there r no support on the discord server~
  

So after reading all previous comments/discussions under this thread, i guess ill just firstly post these infos cuz they should be related most:

• FW_VER: Okey so firstly, i just ran the installation script today, and the date of the firmware seems to be 06/15/2024 as its been shown here

• BOOTMENU: And according to the previous discussion i noticed that i the device should still being displayed in the boot menu regardless of whether its bootable so the following attachment show that the microsd card was nicely plugged in and i can confirm that it was recognized in all installation media and its been tested usable
  

• MISCELLANEOUS: Here's some additional screenshots about the blank file explorer and the UEFI Shell with map: No mapping found. notice which seems like no devices were even detected even tho the microsdcard had been inserted

What have i been trying :

Well i was originally wanted to install the entire operating system on the microsd card in the built in slot cuz the slot could get it locked inside which should be save enough and my internal storage was like i only got 64GB which wasnt enought and speaking of which the internal eMMC didnt displayed on the firmware as well

**and i tried both ubuntu and arch linux and the USB installation media works both perfectectly fine, and ive attempted to install it to both eMMC and microsd card separately both didnt boot **

which means yea even tho the microsdcard is bootable/freshly installed, it is still not detectable

and about the microsd card its a sandisk extreme 256GB and again works perfectly fine ive been tested it for several times~

P.S. A: the firmware seemed to be taking abnormally long time to boot (the icon phase) after booted without any bootable option for a few times

P.S. B: just tested again and confirmed that the internal eMMC doesnt seem to be boot-able as well, error remains the same

its kind of a really important feature and i really wish it could be fixed
please let me know if any other infos were required :D

All kinds of help at all would be very much appreciated!~
Thanks in advance

Originally posted by @PD-Kerman in #572 (comment)

[PD-Kerman]

Attaching cbmem.log, dumped using ubuntu live booted from usb flash drive cuz due to the non-boot-able issue of both emmc and microsd we cant really get into the os and dump logs in that kind of scenario for it, hope it would still be useful

cbmem.log

[PD-Kerman]

Also posted on chrultrabook forum with a reformatted and briefer description regarding the issue

https://forum.chrultrabook.com/t/elemi-issue-with-uefi-full-rom-emmc-microsd-non-bootable/3042

[MrChromebox]

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 a NVMe one, assuming it's socketed. Otherwise, will need to flash a debug build with edk2 logging and log via a SuzyQ cable

[PD-Kerman]

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 a NVMe one, assuming it's socketed. Otherwise, will need to flash a debug build with edk2 logging and log via a SuzyQ cable

Thank you for your reply,

Well but I mean like some other device could boot from it properly right?~ [for example seems like other volteer devices could boot from it as well right~ according to the discord discussion, or is it just ELEMI was an exception~? :D] so is it because ELEMI uses that kind of bridge that made it different or the other devices wasn't ought to be able to boot via eMMC as well~?

And is or will there be a new firmware-release/simple-fix that could get this issue fixed and let edk2 got it detected~?
Thanks

Best regards,
PD-Kerman

[MrChromebox]

Well but I mean like some other device could boot from it properly right?~ [for example seems like other volteer devices could boot from it as well right~ according to the discord discussion, or is it just ELEMI was an exception~? :D] so is it because ELEMI uses that kind of bridge that made it different or the other devices wasn't ought to be able to boot via eMMC as well~?

I have no idea. I only have a single TGL device with NVMe and it has no issues. I think most volteer devices use NVMe, not eMMC. I'm not sure if other volteer devices use eMMC, I'd have to check.

And is or will there be a new firmware-release/simple-fix that could get this issue fixed and let edk2 got it detected~?
Thanks

without an edk2 debug log, I have no idea what the issue is or how to potentially fix it

[PD-Kerman]

Well but I mean like some other device could boot from it properly right?~ [for example seems like other volteer devices could boot from it as well right~ according to the discord discussion, or is it just ELEMI was an exception~? :D] so is it because ELEMI uses that kind of bridge that made it different or the other devices wasn't ought to be able to boot via eMMC as well~?

I have no idea. I only have a single TGL device with NVMe and it has no issues. I think most volteer devices use NVMe, not eMMC. I'm not sure if other volteer devices use eMMC, I'd have to check.

And is or will there be a new firmware-release/simple-fix that could get this issue fixed and let edk2 got it detected~?

Thanks

without an edk2 debug log, I have no idea what the issue is or how to potentially fix it

Okey i get that now, so I'll have to get a debug build of edk2 firmware flashed into it in order to get a better figure of what went wrong right~? :D Well that indeed cleared things up~

Although I don't personally got a SuzyQ here but I've got a brief review from a contributor/moderator from chrultrabook discord server: general channel mentioned that he's got several volteer devices and I think he did mentioned that some of them have eMMC storage so, if some of his volteer devices had indeed got eMMC storages then is it possible that he could run the test and get the logs from some volteer devices as reference in case of that it's got the same non-bootable eMMC storage issue as well~?

Again thanks for your reply
Best regards,
Pd-Kerman

[PD-Kerman]

Attatching the detailed conversation log in the discord server
P.S. Jamie had got some point of view regarding RP9 in the device tree of ELEMI in this case might need your review as well

Thanks in advance