|
Bugzilla – Full Text Bug Listing |
| Summary: | [request] u-boot for soquartz | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Bret Towe <bret.towe> |
| Component: | Bootloader | Assignee: | Guillaume GARDET <guillaume.gardet> |
| Status: | IN_PROGRESS --- | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | mbrugger |
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Bret Towe
2023-10-27 21:50:24 UTC
I built upstream u-boot for quartz64-b-rk3566 config here: https://download.opensuse.org/repositories/home:/Guillaume_G:/branches:/hardware:/boot:/staging/openSUSE_Factory_ARM/aarch64/ Could you try it, please? Also, the board has an SPI flash, which may hold u-boot (or other boot firmware) to allow to boot regular EFI openSUSE images, maybe? (In reply to Guillaume GARDET from comment #1) > I built upstream u-boot for quartz64-b-rk3566 config here: > https://download.opensuse.org/repositories/home:/Guillaume_G:/branches:/ > hardware:/boot:/staging/openSUSE_Factory_ARM/aarch64/ > > Could you try it, please? will do. > > Also, the board has an SPI flash, which may hold u-boot (or other boot > firmware) to allow to boot regular EFI openSUSE images, maybe? the SPI interface is something that requires the user to solder on a chip themself as I recall, doesn't come preinstalled. I currently just have a emmc chip attached to hold /boot/efi and /boot. once uboot loads it does load up the grub efi image and normal grub boot process finishes from there. I installed and tested it on one of my soblade carrier boards and u-boot does load and pass off to grub, kernel loads and boots but it doesn't finish boot fully and stalls before loading full userspace (no console login or ssh). looking at the install name it might be for the model b tho? so I'll test that carrier board next I miss-remembered I have the model A carrier board not B I couldn't get it to boot the installer iso image no idea its issue as I also couldn't get the serial console to give useful output serial did function as expected on the soblade, so might an issue with my usb serial device as i have a different one for the model A than what I use for the soblade I built more u-boot packages: quartz64-a-rk3566 quartz64-b-rk3566 soquartz-blade-rk3566 soquartz-cm4-rk3566 if you want to try them. Same place: https://download.opensuse.org/repositories/home:/Guillaume_G:/branches:/hardware:/boot:/staging/openSUSE_Factory_ARM/aarch64/ ok I've tested the blade and model a packages. the model a I did figure out my serial issue (ttl cable i had couldn't deal with 1500000 baud) so I can see whats going on better. the kernel is loading but shortly after loading board powers off. I've put in a question on the quartz dev channels to see if my earlycon command line is correct as I'm not seeing full kernel boot info. currently I'm unsure what is causing shutdown. the blade package worked it boots normally. as it works I do have a question of what is the normal way uboot is updated for opensuse? on manjaro they just echo'd to console during update the commands required and the user would choose to run them or not. at the moment I'm running the 2 commands below manually dd if=/boot/idbloader.img of=/dev/mmcblk0 seek=64 conv=notrunc,fsync dd if=/boot/u-boot.itb of=/dev/mmcblk0 seek=16384 conv=notrunc,fsync |