I am getting back to create a gentoo for the Beagleplay
I have created u-boot but am confused as to what u-boot is the one to use.
I I have followed the instructions and there is two u-boot, one for the R5 and the other A53
When compiling for the R5 I get u-boot.img and tiboot3.bin
and for the A53 I get u-boot.img and tispl.bin
You can see how I compile it on my gentoo wiki which you can get to on my website
https://suzielinux.com/
Hi @MichelC it’s a multi-stage with multple cores… Here is the readme, look at the Boot Flow picture: u-boot/doc/board/beagle/am62x_beagleplay.rst at master · u-boot/u-boot · GitHub
Here are the a current stable branches/tags: build_u-boot.sh · main · BeagleBoard.org / u-boot-beagleplay · GitLab
Regards,
Interesting, well i have it here… build_u-boot.sh · main · BeagleBoard.org / u-boot-beagleplay · GitLab
Regards,
Cool, thank you.
Am I correct to assume defconfig for the ai-64 and am67a will work with that script?
The am67a beagley-ai will not boot with the evm u-boot + arago. Will the beagley-ai deconfig work with arago so it will boot.
Also, where is the master sysconfig file for both those boards so I can load that up into sysconfig tool and make changes.
beagley-ai isn’t on mainline u-boot yet, i need to fix that, it also use hs-fs silicon vs Plays’ gp, so some differences…
Here’s my script: build_u-boot.sh · main · BeagleY-AI / u-boot-beagley-ai · GitLab
AI64 is similar to Play https://openbeagle.org/beagleboard/u-boot-beagleboneai64/-/blob/main/build_u-boot.sh?ref_type=heads accept for the sysfw.itb
I’m not touching arago…
Will I get a surprise package with that? I have not been able to begin testing it other than the console works. Need to get i/o on the header up first, and that 10 second boot is nice.
U-Boot on K3 is a complex build…
First build trusted-firmware-a (bl31.bin) then optee for (tee-pager_v2.bin)
Build U-Boot for R5 which needs ti-linux-firmware… Which gives you tiboot3.bin (and if needed sysfw.itb)
Finally Build U-Boot for A53 which needs bl31.bin, tee-pager_v2.bin and ti-linux-firmware… Which gives you the final tispl.bin and u-boot.img
(it was even worse when we launched the bbai64, as there was special k3-image-gen repo that got moved into u-boot’s binman infrastructure…)
Regards,
Thanks
I was able to compile u-boot with your script after I modified it
I had to change CC64=aarch64-linux-gnu- to CC64=aarch64-unknown-linux-gnu-
because the cross compiler on gentoo has a different name
In the line to compile trusted-firmware-a I added ENABLE_PIE=0
It fails compiling on gentoo unless that is done
/usr/libexec/gcc/aarch64-unknown-linux-gnu/ld: attention: création de DT_TEXTREL dans un PIE
I am not sure what that PIE is about.
I was looking for a holder for the debug connector and found one at digikey for $18
a bit pricy. I did find a file to print one on my 3D printer. Is that thing good?
pie: position-independent executable (PIE) thinking in head… that’s loaded by u-boot when building u-boot… might not be a good thing…
Debug Connector, don’t spend more then ($12) https://www.digikey.com/en/products/detail/raspberry-pi/SC0889/17877576
At this point every board we make uses a PI standard jst now… the play still used the old 2.54mm header which the PI debugger has in the box…
The PI debug probe can be picked up almost anywhere today.
Regards,
I was talking about the JTAG cable.
Tag Connect Retaining Clip
looks like they’ve removed this going forward… fix(rme): remove ENABLE_PIE restriction · TrustedFirmware-A/trusted-firmware-a@e126ed1 · GitHub
Regards,
