Closed bykeat closed 1 year ago
@bykeat - the image comes by default with a peach pit u-boot installed - for peach pi you'll have to write the uboot.kpart.cbe-peach-pi file from the extra dir of the /boot partition (3rd partition) to the kernel partition (1st partition) of the image ... i do not have a peach pi (only a peach pit), so it should work with that u-boot written to the kernel partition but i cannot guarantee it ... this should bring you the u-boot boot menu onto the screen where you can (and have to) select peach pi for your system
best wishes, good luck and please let me know if you get it working - hexdump
@hexdump0815 Thanks for your response. But I'm new to this so I'm not sure where to start. I have background on web dev but on kernel is a whoelpe new world to me.
Feed me some link and I'll try to learn from there. Thanks in advance!
@bykeat - lets see, i'll try to find some time to desribe it in more detail but it might take some days - please let me know if you do not hear from me for too many days :)
Your instructions above for booting on Peach Pi are not possible as their is only 1 file in the extra folder of the /boot partition. That file is uboot.kpart.cbe-peach-pit. This is true for both the 220619-02 and 210725-01 releases. I downloaded https://github.com/hexdump0815/u-boot-chainloading-for-arm-chromebooks/releases/download/v2018.11-cbe/uboot.kpart.cbe-peach-pi.gz and uncompressed then wrote to the 1st partition using dd. This worked and the XE503C32 appears to function properly.
After some time I realized I was using the 210725-01 release. Performed the same steps on the 220619-02 release and it indeed boots Linux, but then I get a black screen. Waited for over 10 minutes and never got an X desktop. Holding the power button results in seeing linux shutdown so it appears to be a graphics related issue. I'm reverting to the 210725-01 release for now.
I must have done something wrong in my initial testing. I started over with the 220619-02 release image. Downloaded https://github.com/hexdump0815/u-boot-chainloading-for-arm-chromebooks/releases/download/v2018.11-cbe/uboot.img.cbe-peach-pi.gz and wrote it to the 1st partition. It is now booting successfully into the X Desktop and I am beginning testing.
Thanks @RaylynnKnight, I'll try to make my chromebook to work too! I'm new to this so writing partition has to use dd command instead of those image writers in Windows?
I don't use Windows, so I'm not aware if there is a tool that can be used to write to the 1st partition of the sd card. Using linux the steps are as follows (assumes your sd card is recognized as mmcblk1):
wget https://github.com/hexdump0815/u-boot-chainloading-for-arm-chromebooks/releases/download/v2018.11-cbe/uboot.img.cbe-peach-pi.gz
gunzip uboot.img.cbe-peach-pi.gz
dd if=uboot.img.cbe-peach-pi.gz of=/dev/mmcblk1p1
You should then eject the sd card and insert into the Chromebook and follow instructions for booting.
Not sure if I am doing this correctly.
I created 2 partitions using fdisk and followed steps to write into mmcblk1p1 of my SD card and mmcblk1p2 for the chromebook_peach-armv7l-focal.img.gz file.
I'm still getting loud beep at the developer white screen thing after CTRL U.
Do I need to gunzip the img.gz and dd it to partition 2?
@bykeat - you'll have to write the focal image to thw whole disk and the result should be that you have four partitions on it afterwards - then you need to write the proper u-boot to the first of those partitions
For update after many retries.
On Chromebook's terminal: I had ensured all partitions in SD card are deleted using fdisk.
Anything I missed out in the steps above please do let me know. Thank you.
Here's the screen I get booting via uboot.kpart.cbe-peach-pi.
@bykeat - some comments:
good luck and best wishes - hexdump
MMC list shows as follows: EXYNOS DWMMC: 0 (eMMC) EXYNOS DWMMC: 1 (SD)
I think based on the previous screenshot there's SCRIPT FAILED after reading file /extlinux/extlinux.conf
@bykeat - can you please try "sysboot mmc 1:3 any" on the u-boot prompt? and maybe "ls mmc 1:3" in case that does not work ...
Here it is.
@bykeat - maybe the full cmd is required (i tested it on snow and there it worked in the short way already) - can you please try: "sysboot mmc 1:3 any ${scriptaddr} extlinux/extlinux.conf" and maybe the value of scriptaddr via printenv would be interesting ...
scriptaddr returns 0x30000000 invalid filesystem
@bykeat - can you please try:
setenv scriptaddr 0x50000000
sysboot mmc 1:3 any
Set and nothing happens.
And I reran "sysboot mmc 1:3 any &{scriptaddr} /extlinux/extlinux.conf" as I noticed we missed out the backward slash in your previous comment regarding this command.
Able to read the file but nothing happens.
Here's the current values on printenv:
ok - will have to think some more about this :)
@bykeat - can you please do the same as in the last step and then do "run bootcmd_mmc1"?
i meanwhile got my hands on a peach-pi as well and at least gave booting it a try: i flashed the bullseye image from https://github.com/hexdump0815/imagebuilder/releases/tag/220619-02 to an sd card, wrote the proper uboot.img.cbe-peach-pi to the first partition as you described and did it above as well and booted and then selected the peach-pi menu entry and it booted and seems to run just fine - just the audio setup seems to need a bit of tweaking to work it seems ... can you maybe try it as i did from scratch once more to see if it still does not work?
good luck and best wishes - hexdump
I noticed you are using uboot.img.cbe-peach-pi.
Mines doesn't work unfortunately, getting black screen.
As usual my steps are as follows just in case I missed out anything.
strange - the steps look right - i think you had it booting already before - right? do you maybe have another sd card to test? older and smaller is usually better for those devices.
It only boots when I'm using uboot.kpart.cbe-peach-pi. I'm currently using 16GB SD card. Will try to look for 8GB one or some usb drive.
So far I have fried my old usb drive and another 16GB SD card when testing this ;)
I'm thinking another possible issue is I'm using Chromebook terminal to write the SD card. I'm gonna try to get a Ubuntu os to do the disk writing.
Good news, able to boot in my old Samsung SD card 16GB (previously was using Kingston 16GB bought in year 2021) on uboot.kpart.cbe-peach-pi But what's the default password for the login?
Ok found on Google.
linux/changeme
Thank you so much for your help.
cool - happy to hear that it worked in the end - as mentioned it can be that sound is not working yet, but i'll look into this and will most probably build newer (linux v6.1 based) kernels and images over the next months ...
best wishes - hexdump
Bought 2nd hand to try out chromeOS and try to flash to linux. I have tried chromium arnoldthebat, arch Linux, crouton but all hits a dead end where it doesn't recognise the USB or SD card to boot. Hence, I end up here and hope this would work.
At least a small progress for me when it able to boot on USB/SD instead of high pitch beep and return to that default dev screen to ctrl D boot to chromeOS. Unfortunately it doesn't show up and UI or text.
I flashed my USB/SD card on Etcher using bullseye latest version.
I'll try on other flash software or other OS images this weekend to see if I could resolve it.