About this problem: Not reliable boot in PUJJOTEEN (IP slim 3)
To try to fix the boot problem, I bought an m.2 WiFi to NVME adapter to put an nvme on my laptop and the problem was almost solved… The detail is that I did not want to have an external wifi always connected, what I did was take the USB data signals (D-, D+) from the adapter so as not to sacrifice any external port, the 5V, I took them from the USB port.
Still thinking… seems that all platforms alderlake-n with integrated eMMC have random boot failures, ie Refusal to create a boot partition , Pujjo Full UEFI Issues , Strange boot issues with Lenovo Ideapad Slim 3i Chromebook Plus and some others topics, @MrChromebox I have a question for you, if i flash my PUJJOTEEN with another alderlake-n board (PUJJO, PUJJOFLEX, PUJJO1E, etc) with eMMC working fine (without boot issues) is possible fix this behaviour or not there one known bootong good?
I’m working on a completely new SD/eMMC driver for edk2 which will hopefully address all of the issues with the existing one. I’ve already fixed eMMC and SD for devices using the GL9763E/9750 PCIe controllers.
Anyone having an issue with eMMC who wants to test, please DM me
Hi, @MrChromebox flashed MrChromebox-2509.2 Release, same issues (emmc random detected in edk2), Question, The fixes in this release were are only for Genesys Logic controllers? The pujjoteen chrome has a Intel SD Host Controller (8086:54c4), that controller is similar to SD/MMC Card reader? This laptop not have one (coolstar site says “yes” but isnt true).
Thanks.
Alderlake-N devices like PUJJO* have an eMMC controller built into the PCH; Alderlake-U/P devices like TAEKO or GLADIOS do not, so they have to use a PCIe bridge controller like the GL9763E. Neither platform supports a SD card reader natively, so all Alderlake Chromebooks use a GL9750/9755 for that.
ADL-N boards having eMMC issues could be a hardware tuning thing, could be a edk2 driver issue (though I can’t reproduce on CRAASK), hard to say. Without reproducing on an affected board and having debug logging from edk2, will be impossible to diagnose.
I again (sorry for many questions) What could happen if flash (forced or with external programmer) my pujjoteen with craaskov firmware? are almost identical machines.
they’re not almost identical, as the coreboot board definitions show.
there are a lot of differences, mainly with GPIO routing, which could potentially damage the board if incorrectly configured. RAM strapping is different, so the GPIOs that tell coreboot which memory modules are installed will be wrong.
basically, other than both being ADL-N based devices, they couldn’t be more different
