-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not booting from SD card #12
Comments
I have noticed problems even with gcc-13, so I now build with gcc-12. Give gcc-12 a try. Do the known working images work for you? |
Thanks,
I'll try it with GCC. I work on Marvell SoCs and we use gcc-12 for that,
though my distro supports gcc-14 for the AARCH64 toolchain.
Note that with the older release I was able to enable HS400ES mode for eMMC
and that appears to work. For many years I maintained the Cavium MIPS U-Boot
and I now do some work on the OcteonTX U-Boot.
I can get U-Boot compiled with gcc-14 working if I load it from the shipped U-
Boot to 0xa00000 and jump to it. I will try the new binaries, though.
…-Aaron
On Saturday, June 22, 2024 3:07:55 AM PDT John Clark wrote:
I have noticed problems even with gcc-13, so I now build with gcc-12. Give
gcc-12 a try.
Do the known working images work for you?
https://github.com/inindev/uboot-rockchip/releases/tag/v2024.07-rc4
|
I am unsure there is an issue with gcc-13 (the one I had trouble with), but I did see it sporadically hang on the boot prompt rather than default boot (I would need to select an option from the menu). I just assumed there was a new optimization flag or setting that u-boot has not accounted for at this point. Let me know if gcc-12 makes a difference for you. |
I will when I get a chance. I'm in the process of migrating my main
computer to new hardware.
…On Sat, Jun 22, 2024, 4:54 PM John Clark ***@***.***> wrote:
I am unsure there is an issue with gcc-13 (the one I had trouble with),
but I did see it sporadically hang on the boot prompt rather than default
boot (I would need to select an option from the menu). I just assumed there
was a new optimization flag or setting that u-boot has not accounted for at
this point. Let me know if gcc-12 makes a difference for you.
—
Reply to this email directly, view it on GitHub
<#12 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADJUAEZEHS7W2V657TYEJNDZIYFCDAVCNFSM6AAAAABJXJJ5DSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBUGI2TGOBRGE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I am trying the official release and while it boots to a prompt it looks like USB is
not working. usb scan hangs.
=> usb start
starting USB...
Bus ***@***.***: USB EHCI 1.00
Bus ***@***.***:
I am also able to build my own U-Boot but I see the same behavior.
…-Aaron
On Saturday, June 22, 2024 3:07:55 AM PDT John Clark wrote:
I have noticed problems even with gcc-13, so I now build with gcc-12. Give
gcc-12 a try.
Do the known working images work for you?
https://github.com/inindev/uboot-rockchip/releases/tag/v2024.07-rc4
|
my output is a little different than yours:
|
I am attempting to upgrade U-Boot on my board but there is no output after it starts. I did change v2024.01 instead of the release candidate.
DDR 9fffbe1e78 cym 24/02/04-10:09:20,fwver: v1.16
LPDDR4X, 2112MHz
channel[0] BW=16 Col=10 Bk=8 CS0 Row=17 CS1 Row=17 CS=2 Die BW=8 Size=4096MB
channel[1] BW=16 Col=10 Bk=8 CS0 Row=17 CS1 Row=17 CS=2 Die BW=8 Size=4096MB
channel[2] BW=16 Col=10 Bk=8 CS0 Row=17 CS1 Row=17 CS=2 Die BW=8 Size=4096MB
channel[3] BW=16 Col=10 Bk=8 CS0 Row=17 CS1 Row=17 CS=2 Die BW=8 Size=4096MB
Manufacturer ID:0x1
CH0 RX Vref:29.3%, TX Vref:23.8%,22.8%
CH1 RX Vref:27.9%, TX Vref:21.8%,21.8%
CH2 RX Vref:29.3%, TX Vref:22.8%,21.8%
CH3 RX Vref:29.7%, TX Vref:23.8%,21.8%
change to F1: 528MHz
change to F2: 1068MHz
change to F3: 1560MHz
change to F0: 2112MHz
out
U-Boot SPL board init
U-Boot SPL 2017.09-g1b1171b7c71-220418 #fa (Apr 18 2024 - 11:12:44)
Trying to boot from MMC2
SPL: A/B-slot: _a, successful: 0, tries-remain: 7
Trying fit image at 0x4000 sector
Verified-boot: 0
Checking atf-1 0x00040000 ... sha256(bb1bbbc832...) + OK
Checking u-boot 0x00a00000 ... sha256(0903e8ca8a...) + OK
Checking fdt-1 0x00acd868 ... sha256(e7f2834e1d...) + OK
Checking atf-2 0x000f0000 ... sha256(30812190d0...) + OK
Checking atf-3 0xff100000 ... sha256(cb7bdbec2b...) + OK
Jumping to U-Boot(0x00a00000) via ARM Trusted Firmware(0x00040000)
Total: 721.912/886.428 ms
Note that I am quite familiar with U-Boot since I am a developer who works on U-Boot and ATF for a different ARM SoC vendor.
My toolchain is also gcc-14, if that makes any difference.
The text was updated successfully, but these errors were encountered: