On 8/2/25 02:13, David Heidelberg wrote:
Introduce a fragment config for the Pixel 3 and Pixel 3 XL. On these devices, U-Boot must be chainloaded via Fastboot. However, due to
s/must be/is/g (be descriptive rather than prescriptive).
a Fastboot bug, U-Boot won’t start unless a specific condition is met.
additional requirements added by google, the image header must have a specific value for the text offset.>
To work around this, U-Boot must provide a TEXT_OFFSET of 0x00080000,
this is solved by setting CONFIG_TEXT_OFFSET in U-Boot. Kind regards, // Casey (she/they)
which allows Fastboot to successfully launch U-Boot. Instead of: $ make CROSS_COMPILE=aarch64-linux-gnu- O=.output qcom_defconfig qcom-phone.config do $ make CROSS_COMPILE=aarch64-linux-gnu- O=.output qcom_defconfig google-pixel3.config qcom-phone.config Signed-off-by: David Heidelberg <da...@ixit.cz> --- board/qualcomm/google-pixel3.config | 3 +++ 1 file changed, 3 insertions(+) create mode 100644 board/qualcomm/google-pixel3.config diff --git a/board/qualcomm/google-pixel3.config b/board/qualcomm/google-pixel3.config new file mode 100644 index 00000000000..2dc71c65d23 --- /dev/null +++ b/board/qualcomm/google-pixel3.config @@ -0,0 +1,3 @@ +# Pixel 3 (blueline) and Pixel 3 XL (crosshatch) will fail to +# chainload u-boot on the Q or R bootloader if TEXT_BASE offset is missing. +CONFIG_TEXT_BASE=0x80080000
