<linkmauve>
Hi, I’m trying to build tf-a for a rk3399, but it complains that arm-none-eabi-gcc isn’t available. I’m already building on an ARM build machine, but it’s in AArch64. Do I need to be in AArch32 in order to build tf-a for this device?
<jakllsch>
aa32 and aa64 are entirely different instruction sets, and gcc treats it as such
System_Error has quit [Remote host closed the connection]
<jakllsch>
(unlike x86 and x86_64 which are somehow unified in the same gcc)
<jakllsch>
(despite being mostly-different ISAs)
<linkmauve>
Yeah, that makes sense, but it seems I have to have both AArch32 and AArch64 compilers in order to build tf-a for the rk3399?
<linkmauve>
Is it part of the boot process, or is it a build issue?
<jakllsch>
quite possibly
<jakllsch>
not sure what mode the cpus in rk3399 are in at coming out of the mask rom
xha has quit [Ping timeout: 265 seconds]
System_Error has joined #linux-rockchip
xha has joined #linux-rockchip
<linkmauve>
When booting to btrfs, how does u-boot determine which subvolume to boot from?
<linkmauve>
Which one to load the extlinux.conf stuff?
raster has quit [Quit: Gettin' stinky!]
naoki has joined #linux-rockchip
naoki1 has joined #linux-rockchip
naoki has quit [Quit: naoki]
naoki1 is now known as naoki
naoki1 has joined #linux-rockchip
naoki has quit [Ping timeout: 276 seconds]
naoki1 is now known as naoki
naoki has quit [Client Quit]
naoki has joined #linux-rockchip
naoki has quit [Read error: Connection reset by peer]
naoki has joined #linux-rockchip
naoki1 has joined #linux-rockchip
naoki has quit [Client Quit]
naoki1 is now known as naoki
naoki has quit [Client Quit]
naoki1 has joined #linux-rockchip
naoki1 is now known as naoki
naoki has quit [Client Quit]
naoki has joined #linux-rockchip
naoki has quit [Client Quit]
naoki1 has joined #linux-rockchip
naoki1 has quit [Client Quit]
naoki has joined #linux-rockchip
naoki has quit [Client Quit]
naoki1 has joined #linux-rockchip
naoki1 is now known as naoki
<linkmauve>
And also, most guides mention separate idbloader.img and u-boot.itb, is that still needed with u-boot-rockchip.bin?
franoosh has quit [Remote host closed the connection]
naoki1 has joined #linux-rockchip
naoki has quit [Ping timeout: 265 seconds]
<CounterPillow>
nope
naoki has joined #linux-rockchip
naoki1 has quit [Client Quit]
<CounterPillow>
idbloader.img was separate ddr init + spl
<CounterPillow>
(and tf-a I guess)
<CounterPillow>
u-boot-rockchip.bin is the combined ddr init + spl + tf-a + u-boot proper
<CounterPillow>
you just flash it to byte 32768 ("sector" 64) like you would the spl, except of course it's larger and takes up the size of both separate binaries
naoki has quit [Read error: Connection reset by peer]
naoki has joined #linux-rockchip
<linkmauve>
Right, 9.1 MiB currently.
naoki1 has joined #linux-rockchip
naoki1 has quit [Client Quit]
naoki has quit [Read error: Connection reset by peer]
<CounterPillow>
I think reserving like 16 MiB to 32 MiB for it by placing a partition there (so no well-meaning tools go "oh look free space" and overwrite it) is the way to go.
naoki has joined #linux-rockchip
naoki has quit [Client Quit]
naoki1 has joined #linux-rockchip
naoki1 has quit [Client Quit]
naoki has joined #linux-rockchip
naoki has quit [Client Quit]
naoki has joined #linux-rockchip
alpernebbi has quit [Ping timeout: 252 seconds]
<linkmauve>
If u-boot doesn’t find its configuration on the btrfs partition, should it still display anything on screen if it has been compiled with CONFIG_DISPLAY_ROCKCHIP_HDMI=y?
chewitt has joined #linux-rockchip
alpernebbi has joined #linux-rockchip
<sigmaris>
linkmauve: yes, it should display some messages, assuming stdout is set to vidconsole
<sigmaris>
also from earlier, TF-A needs arm-none-eabi-gcc to compile some firmware for Cortex-M low power cores in the RK3399