Early splash screen on
v2 cover Early splash screen on
This series is to enable out-of-box early splash screen on AM62x devices with wic images compiled using meta-ti.
With this, u-boot SPL or u-boot proper can load TI logo from boot partition
and display it while board is being booted.
Devarsh Thakkar (2):
u-boot-ti-staging_2023.04: Copy bitmap file to boot partition for
AM62x
conf: machine: am62xx: Add TI logo as image boot file
meta-ti-bsp/conf/machine/include/am62xx.inc | 3 +++ .../recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb | 9 +++++++++ 2 files changed, 12 insertions(+)
---
V2: Rename ti logo file to include metadata
Signature · 1 line
2.34.1
PATCH v2 1/2 u-boot-ti-staging_2023.04: Copy bitmap file to boot partition for AM62x
Early splash screen support for AM62x has been enabled in u-boot and it requires bitmap tarball to be present in boot partition as per the default environment settings done in u-boot [1].
Copy the ti logo bitmap tarball to boot partition of wic image in order to enable out of box early display on AM62x.
[1] https://git.ti.com/cgit/ti-u-boot/ti-u-boot/tree/board/ti/am62x/am62x.env
---
V2: Rename ti logo tarball as per suggested changes (same is being
done in ti-u-boot too)
--- .../recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb | 9 +++++++++ 1 file changed, 9 insertions(+)
meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb +9 -0
@@ -8,3 +8,12 @@ BRANCH = "ti-u-boot-2023.04" SRCREV = "1f510931dcc90e6f28f7fed757ad5000d4382e22" +do_install:append:am62xx() { + install -d ${D}/boot + install -m 0644 ${S}/tools/logos/ti_logo_414x97_32bpp.bmp.gz ${D}/boot +} + +do_deploy:append:am62xx() { + install -d ${DEPLOYDIR} + install -m 0644 ${S}/tools/logos/ti_logo_414x97_32bpp.bmp.gz ${DEPLOYDIR} +}
Signature · 1 line
2.34.1
PATCH v2 2/2 conf: machine: am62xx: Add TI logo as image boot file
In reply to Devarsh ThakkarAdd TI logo bitmap image as image boot file so that it gets copied to boot partition and A53 SPL or U-boot proper can load it and display during board bootup.
---
V2: Rename ti logo bitmap image as per suggested changes (same is being done in ti-u-boot repo)
--- meta-ti-bsp/conf/machine/include/am62xx.inc | 3 +++ 1 file changed, 3 insertions(+)
meta-ti-bsp/conf/machine/include/am62xx.inc +3 -0
@@ -15,6 +15,9 @@ IMAGE_BOOT_FILES += "tiboot3-am62x-gp-evm.bin" # Since default tiboot3.bin on AM62x is for HS-FS, add a version for HS-SE IMAGE_BOOT_FILES += "tiboot3-am62x-hs-evm.bin" +# Bitmap image tarball for early splashscreen +IMAGE_BOOT_FILES += "ti_logo_414x97_32bpp.bmp.gz" + TFA_BOARD = "lite" TFA_K3_SYSTEM_SUSPEND = "1"
Signature · 1 line
2.34.1
Re: [meta-ti] [kirkstone] [PATCH v2 1/2] u-boot-ti-staging_2023.04: Copy bitmap file to boot partition for AM62x
In reply to Devarsh ThakkarQuoted 23 lines · Devarsh Thakkar via lists.yoctoproject.org
Early splash screen support for AM62x has been enabled in u-boot and it requires bitmap tarball to be present in boot partition as per the default environment settings done in u-boot [1].
Copy the ti logo bitmap tarball to boot partition of wic image in order to enable out of box early display on AM62x.
[1] https://git.ti.com/cgit/ti-u-boot/ti-u-boot/tree/board/ti/am62x/am62x.env
Signed-off-by Devarsh Thakkar <[email protected]>---
V2: Rename ti logo tarball as per suggested changes (same is being
done in ti-u-boot too)--- .../recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb | 9 +++++++++ 1 file changed, 9 insertions(+)meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb +0
-0@@ -8,3 +8,12 @@ BRANCH = "ti-u-boot-2023.04"
meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb BRANCH = "ti-u-boot-2023.04" · line 18
Quoted 10 lines
meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb +8
-0SRCREV = "1f510931dcc90e6f28f7fed757ad5000d4382e22" +do_install:append:am62xx() { + install -d ${D}/boot + install -m 0644 ${S}/tools/logos/ti_logo_414x97_32bpp.bmp.gz ${D}/boot +} + +do_deploy:append:am62xx() { + install -d ${DEPLOYDIR} + install -m 0644 ${S}/tools/logos/ti_logo_414x97_32bpp.bmp.gz ${DEPLOYDIR}
Any specific reason you also need to deploy this loose file?
Signature · 1 line
Denys
Re: [meta-ti] [kirkstone] [PATCH v2 1/2] u-boot-ti-staging_2023.04: Copy bitmap file to boot partition for AM62x
Hi Denys,
Thanks for the review,
Quoted 26 lines · Denys Dmytriyenko
Quoted 25 lines · Devarsh Thakkar via lists.yoctoproject.org
Early splash screen support for AM62x has been enabled in u-boot and it requires bitmap tarball to be present in boot partition as per the default environment settings done in u-boot [1].
Copy the ti logo bitmap tarball to boot partition of wic image in order to enable out of box early display on AM62x.
[1] https://git.ti.com/cgit/ti-u-boot/ti-u-boot/tree/board/ti/am62x/am62x.env
Signed-off-by Devarsh Thakkar <[email protected]>---
V2: Rename ti logo tarball as per suggested changes (same is being
done in ti-u-boot too)--- .../recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb | 9 +++++++++ 1 file changed, 9 insertions(+)meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb +0
-0@@ -8,3 +8,12 @@ BRANCH = "ti-u-boot-2023.04" SRCREV = "1f510931dcc90e6f28f7fed757ad5000d4382e22"
Quoted 11 lines
meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb BRANCH = "ti-u-boot-2023.04" · line 18
Quoted 8 lines
meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb +8
-0+do_install:append:am62xx() { + install -d ${D}/boot + install -m 0644 ${S}/tools/logos/ti_logo_414x97_32bpp.bmp.gz ${D}/boot +} + +do_deploy:append:am62xx() { + install -d ${DEPLOYDIR} + install -m 0644 ${S}/tools/logos/ti_logo_414x97_32bpp.bmp.gz ${DEPLOYDIR}Any specific reason you also need to deploy this loose file?
I think the boot partition script which is ran as part of do_image_wic expects IMAGE_BOOTFILES to be present in deploy directory, I remember getting below error without doing so :
| ERROR: _exec_cmd: install -m 0644 -D /home/devarsht/ti/yocto_sdk_am62/oe-layersetup/build/arago-tmp-default-glibc/deploy/images/am62xx-evm/ti.gz /home/devarsht/ti/yocto_sdk_am62/oe-layersetup/build/arago-tmp-default-glibc/work/am62xx_evm-oe-linux/tisdk-default-image/1.0-r0/tmp-wic/hdd/boot/ti.gz returned '1' instead of 0
| output: install: cannot stat '/home/devarsht/ti/yocto_sdk_am62/oe-layersetup/build/arago-tmp-default-glibc/deploy/images/am62xx-evm/ti.gz':
No such file or directory
| WARNING:/home/devarsht/ti/yocto_sdk_am62/oe-layersetup/build/arago-tmp-default-glibc/work/am62xx_evm-oe-linux/tisdk-default-image/1.0-r0/temp/run.do_image_wic.1581619:162 exit 1 from 'BUILDDIR="/home/devarsht/ti/yocto_sdk_am62/oe-layersetup/build"
PSEUDO_UNLOAD=1 wic create "$wks" --vars "/home/devarsht/ti/yocto_sdk_am62/oe-layersetup/build/arago-tmp-default-glibc/sysroots/am62xx-evm/imgdata/"
-e "tisdk-default-image" -o "$build_wic/" -w "$tmp_wic"'
One more reason to do so was to allow user ease of use, to copy the logo too from deploy folder along with other boot files (if not flashing from wic image) since the same is set in am62x.env and if logo is not present in boot partition then it throws some error message although the device still boots.
Regards
Devarsh
Re: [meta-ti] [kirkstone] [PATCH v2 1/2] u-boot-ti-staging_2023.04: Copy bitmap file to boot partition for AM62x
Quoted 47 lines · Devarsh Thakkar
Hi Denys,
Thanks for the review,
Quoted 26 lines · Denys Dmytriyenko
Quoted 25 lines · Devarsh Thakkar via lists.yoctoproject.org
Early splash screen support for AM62x has been enabled in u-boot and it requires bitmap tarball to be present in boot partition as per the default environment settings done in u-boot [1].
Copy the ti logo bitmap tarball to boot partition of wic image in order to enable out of box early display on AM62x.
[1] https://git.ti.com/cgit/ti-u-boot/ti-u-boot/tree/board/ti/am62x/am62x.env
Signed-off-by Devarsh Thakkar <[email protected]>---
V2: Rename ti logo tarball as per suggested changes (same is being
done in ti-u-boot too)--- .../recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb | 9 +++++++++ 1 file changed, 9 insertions(+)meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb +0
-0@@ -8,3 +8,12 @@ BRANCH = "ti-u-boot-2023.04" SRCREV = "1f510931dcc90e6f28f7fed757ad5000d4382e22"Quoted 11 lines
meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb BRANCH = "ti-u-boot-2023.04" · line 18
Quoted 8 lines
meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb +8
-0+do_install:append:am62xx() { + install -d ${D}/boot + install -m 0644 ${S}/tools/logos/ti_logo_414x97_32bpp.bmp.gz ${D}/boot +} + +do_deploy:append:am62xx() { + install -d ${DEPLOYDIR} + install -m 0644 ${S}/tools/logos/ti_logo_414x97_32bpp.bmp.gz ${DEPLOYDIR}Any specific reason you also need to deploy this loose file?
I think the boot partition script which is ran as part of
do_image_wicexpectsIMAGE_BOOTFILESto be present in deploy directory, I remember getting below error without doing so :
Quoted 13 lines
| ERROR:
_exec_cmd: install -m 0644 -D/home/devarsht/ti/yocto_sdk_am62/oe-layersetup/build/arago-tmp-default-glibc/deploy/images/am62xx-evm/ti.gz/home/devarsht/ti/yocto_sdk_am62/oe-layersetup/build/arago-tmp-default-glibc/work/am62xx_evm-oe-linux/tisdk-default-image/1.0-r0/tmp-wic/hdd/boot/ti.gzreturned '1' instead of 0
| output: install: cannot stat '/home/devarsht/ti/yocto_sdk_am62/oe-layersetup/build/arago-tmp-default-glibc/deploy/images/am62xx-evm/ti.gz':
No such file or directory
| WARNING:/home/devarsht/ti/yocto_sdk_am62/oe-layersetup/build/arago-tmp-default-glibc/work/am62xx_evm-oe-linux/tisdk-default-image/1.0-r0/temp/run.do_image_wic.1581619:162exit 1 from 'BUILDDIR="/home/devarsht/ti/yocto_sdk_am62/oe-layersetup/build"
PSEUDO_UNLOAD=1 wic create "$wks" --vars "/home/devarsht/ti/yocto_sdk_am62/oe-layersetup/build/arago-tmp-default-glibc/sysroots/am62xx-evm/imgdata/"
-e "tisdk-default-image" -o "$build_wic/" -w "$tmp_wic"'
So, is this logo expected by U-boot to reside in the boot partition of SD card, or in the /boot directory of the rootfs?
The first is handled by do_deploy and IMAGE_BOOTFILES, while the second is handled by do_install. I wonder if doing both is going to be confusing...
Quoted 4 lines
One more reason to do so was to allow user ease of use, to copy the logo too from deploy folder along with other boot files (if not flashing from wic image) since the same is set in am62x.env and if logo is not present in boot partition then it throws some error message although the device still boots.
Re: [meta-ti] [kirkstone] [PATCH v2 1/2] u-boot-ti-staging_2023.04: Copy bitmap file to boot partition for AM62x
Quoted 62 lines · Denys Dmytriyenko
Quoted 47 lines · Devarsh Thakkar
Hi Denys,
Thanks for the review,
Quoted 26 lines · Denys Dmytriyenko
Quoted 25 lines · Devarsh Thakkar via lists.yoctoproject.org
Early splash screen support for AM62x has been enabled in u-boot and it requires bitmap tarball to be present in boot partition as per the default environment settings done in u-boot [1].
Copy the ti logo bitmap tarball to boot partition of wic image in order to enable out of box early display on AM62x.
[1] https://git.ti.com/cgit/ti-u-boot/ti-u-boot/tree/board/ti/am62x/am62x.env
Signed-off-by Devarsh Thakkar <[email protected]>---
V2: Rename ti logo tarball as per suggested changes (same is being
done in ti-u-boot too)--- .../recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb | 9 +++++++++ 1 file changed, 9 insertions(+)meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb +0
-0@@ -8,3 +8,12 @@ BRANCH = "ti-u-boot-2023.04" SRCREV = "1f510931dcc90e6f28f7fed757ad5000d4382e22"Quoted 11 lines
meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb BRANCH = "ti-u-boot-2023.04" · line 18
Quoted 8 lines
meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb +8
-0+do_install:append:am62xx() { + install -d ${D}/boot + install -m 0644 ${S}/tools/logos/ti_logo_414x97_32bpp.bmp.gz ${D}/boot +} + +do_deploy:append:am62xx() { + install -d ${DEPLOYDIR} + install -m 0644 ${S}/tools/logos/ti_logo_414x97_32bpp.bmp.gz ${DEPLOYDIR}Any specific reason you also need to deploy this loose file?
I think the boot partition script which is ran as part of
do_image_wicexpectsIMAGE_BOOTFILESto be present in deploy directory, I remember getting below error without doing so :Quoted 13 lines
| ERROR:
_exec_cmd: install -m 0644 -D/home/devarsht/ti/yocto_sdk_am62/oe-layersetup/build/arago-tmp-default-glibc/deploy/images/am62xx-evm/ti.gz/home/devarsht/ti/yocto_sdk_am62/oe-layersetup/build/arago-tmp-default-glibc/work/am62xx_evm-oe-linux/tisdk-default-image/1.0-r0/tmp-wic/hdd/boot/ti.gzreturned '1' instead of 0
| output: install: cannot stat '/home/devarsht/ti/yocto_sdk_am62/oe-layersetup/build/arago-tmp-default-glibc/deploy/images/am62xx-evm/ti.gz':
No such file or directory
| WARNING:/home/devarsht/ti/yocto_sdk_am62/oe-layersetup/build/arago-tmp-default-glibc/work/am62xx_evm-oe-linux/tisdk-default-image/1.0-r0/temp/run.do_image_wic.1581619:162exit 1 from 'BUILDDIR="/home/devarsht/ti/yocto_sdk_am62/oe-layersetup/build"
PSEUDO_UNLOAD=1 wic create "$wks" --vars "/home/devarsht/ti/yocto_sdk_am62/oe-layersetup/build/arago-tmp-default-glibc/sysroots/am62xx-evm/imgdata/"
-e "tisdk-default-image" -o "$build_wic/" -w "$tmp_wic"'
Quoted 6 lines
So, is this logo expected by U-boot to reside in the boot partition of SD card, or in the /boot directory of the rootfs?
The first is handled bydo_deployandIMAGE_BOOTFILES, while the second is handled bydo_install. I wonder if doing both is going to be confusing...
Yes, this logo is expected to reside in boot partition of SD only per current implementation in ti-u-boot.
Regards
Devarsh
Quoted 4 lines
Quoted 4 lines
One more reason to do so was to allow user ease of use, to copy the logo too from deploy folder along with other boot files (if not flashing from wic image) since the same is set in am62x.env and if logo is not present in boot partition then it throws some error message although the device still boots.
Re: [meta-ti] [kirkstone] [PATCH v2 1/2] u-boot-ti-staging_2023.04: Copy bitmap file to boot partition for AM62x
Quoted 66 lines · Devarsh Thakkar
Quoted 63 lines · Denys Dmytriyenko
Quoted 61 lines · Devarsh Thakkar
Hi Denys,
Thanks for the review,
Quoted 29 lines · Denys Dmytriyenko
Quoted 28 lines · Devarsh Thakkar via lists.yoctoproject.org
Early splash screen support for AM62x has been enabled in u-boot and it requires bitmap tarball to be present in boot partition as per the default environment settings done in u-boot [1].
Copy the ti logo bitmap tarball to boot partition of wic image in order to enable out of box early display on AM62x.
[1] https://git.ti.com/cgit/ti-u-boot/ti-u-boot/tree/board/ti/am62x/am62x.env
Signed-off-by Devarsh Thakkar <[email protected]>---
V2: Rename ti logo tarball as per suggested changes (same is being done in ti-u-boot too)
---
.../recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb | 9
+++++++++1 file changed, 9 insertions(+)meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb +0
-0@@ -8,3 +8,12 @@ BRANCH = "ti-u-boot-2023.04"SRCREV = "
1f510931dcc90e6f28f7fed757ad5000d4382e22" +do_install:append:am62xx() {
+ install -d ${D}/boot
+ install -m 0644 ${S}/tools/logos/ti_logo_414x97_32bpp.bmp.gz ${D}/bootQuoted 9 lines
Quoted 6 lines
meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb +5
-0+} + +do_deploy:append:am62xx() { + install -d ${DEPLOYDIR} + install -m 0644 ${S}/tools/logos/ti_logo_414x97_32bpp.bmp.gz${DEPLOYDIR}
Any specific reason you also need to deploy this loose file?
I think the boot partition script which is ran as part of
do_image_wicexpectsIMAGE_BOOTFILESto be present in deploy directory, I remember getting below error without doing so :| ERROR:
_exec_cmd: install -m 0644 -D/home/devarsht/ti/yocto_sdk_am62/oe-layersetup/build/arago-tmp-default-glibc/deploy/images/am62xx-evm/ti.gz/home/devarsht/ti/yocto_sdk_am62/oe-layersetup/build/arago-tmp-default-glibc/work/am62xx_evm-oe-linux/tisdk-default-image/1.0-r0/tmp-wic/hdd/boot/ti.gzreturned '1' instead of 0
| output: install: cannot stat '/home/devarsht/ti/yocto_sdk_am62/oe-layersetup/build/arago-tmp-default-glibc/deploy/images/am62xx-evm/ti.gz':
No such file or directory
| WARNING:/home/devarsht/ti/yocto_sdk_am62/oe-layersetup/build/arago-tmp-default-glibc/work/am62xx_evm-oe-linux/tisdk-default-image/1.0-r0/temp/run.do_image_wic.1581619:162exit 1 from 'BUILDDIR="/home/devarsht/ti/yocto_sdk_am62/oe-layersetup/build"
PSEUDO_UNLOAD=1 wic create "$wks" --vars "/home/devarsht/ti/yocto_sdk_am62/oe-layersetup/build/arago-tmp-default-glibc/sysroots/am62xx-evm/imgdata/"
-e "tisdk-default-image" -o "$build_wic/" -w "$tmp_wic"'
Quoted 8 lines
Quoted 6 lines
So, is this logo expected by U-boot to reside in the boot partition of SD card, or in the /boot directory of the rootfs?
The first is handled bydo_deployandIMAGE_BOOTFILES, while the second is handled bydo_install. I wonder if doing both is going to be confusing...Yes, this logo is expected to reside in boot partition of SD only per current implementation in ti-u-boot.
So then it only requires do_deploy and IMAGE_BOOTFILES since that puts items into the boot partition... Do we need the do_install?
Quoted 7 lines
Regards
DevarshQuoted 4 lines
Quoted 4 lines
One more reason to do so was to allow user ease of use, to copy the logo too from deploy folder along with other boot files (if not flashing from wic image) since the same is set in am62x.env and if logo is not present in boot partition then it throws some error message although the device still boots.
Signature · 3 lines
Ryan Eatmon [email protected] ----------------------------------------- Texas Instruments, Inc. - LCPD - MGTS
Re: [meta-ti] [kirkstone] [PATCH v2 1/2] u-boot-ti-staging_2023.04: Copy bitmap file to boot partition for AM62x
Quoted 84 lines · Ryan Eatmon
Quoted 81 lines · Devarsh Thakkar
Quoted 77 lines · Denys Dmytriyenko
Quoted 54 lines · Devarsh Thakkar
Hi Denys,
Thanks for the review,
Quoted 33 lines · Denys Dmytriyenko
Quoted 31 lines · Devarsh Thakkar via lists.yoctoproject.org
Early splash screen support for AM62x has been enabled in u-boot and it requires bitmap tarball to be present in boot partition as per the default environment settings done in u-boot [1].
Copy the ti logo bitmap tarball to boot partition of wic image in order
to enable out of box early display on AM62x.[1] https://git.ti.com/cgit/ti-u-boot/ti-u-boot/tree/board/ti/am62x/am62x.env
Signed-off-by Devarsh Thakkar <[email protected]>---
V2: Rename ti logo tarball as per suggested changes (same is being done in ti-u-boot too)
---
.../recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb
| 9 +++++++++1 file changed, 9 insertions(+)diff --git a/meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb b/meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb index
e6da84cb..c948e1ed100644meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb +0
-0@@ -8,3 +8,12 @@ BRANCH = "ti-u-boot-2023.04"SRCREV = "
1f510931dcc90e6f28f7fed757ad5000d4382e22" +do_install:append:am62xx() {
+ install -d ${D}/boot
+ install -m 0644 ${S}/tools/logos/ti_logo_414x97_32bpp.bmp.gz ${D}/bootQuoted 9 lines
Quoted 6 lines
meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb +5
-0+} + +do_deploy:append:am62xx() { + install -d ${DEPLOYDIR} + install -m 0644${S}/tools/logos/ti_logo_414x97_32bpp.bmp.gz ${DEPLOYDIR}
Any specific reason you also need to deploy this loose file?
I think the boot partition script which is ran as part of
do_image_wicexpectsIMAGE_BOOTFILESto be present in deploy directory, I remember getting below
error without doing so :Quoted 14 lines
| ERROR:
_exec_cmd: install -m 0644 -D/home/devarsht/ti/yocto_sdk_am62/oe-layersetup/build/arago-tmp-default-glibc/deploy/images/am62xx-evm/ti.gz/home/devarsht/ti/yocto_sdk_am62/oe-layersetup/build/arago-tmp-default-glibc/work/am62xx_evm-oe-linux/tisdk-default-image/1.0-r0/tmp-wic/hdd/boot/ti.gzreturned '1' instead of 0
| output: install: cannot stat '/home/devarsht/ti/yocto_sdk_am62/oe-layersetup/build/arago-tmp-default-glibc/deploy/images/am62xx-evm/ti.gz':
No such file or directory
| WARNING:/home/devarsht/ti/yocto_sdk_am62/oe-layersetup/build/arago-tmp-default-glibc/work/am62xx_evm-oe-linux/tisdk-default-image/1.0-r0/temp/run.do_image_wic.1581619:162exit 1 from
'BUILDDIR="/home/devarsht/ti/yocto_sdk_am62/oe-layersetup/build"
PSEUDO_UNLOAD=1 wic create "$wks" --vars "/home/devarsht/ti/yocto_sdk_am62/oe-layersetup/build/arago-tmp-default-glibc/sysroots/am62xx-evm/imgdata/"
-e "tisdk-default-image" -o "$build_wic/" -w "$tmp_wic"'So, is this logo expected by U-boot to reside in the boot partition of SD card, or in the /boot directory of the rootfs?
The first is handled bydo_deployandIMAGE_BOOTFILES, while the second is
handled bydo_install. I wonder if doing both is going to be confusing...
Quoted 5 lines
Quoted 2 lines
Yes, this logo is expected to reside in boot partition of SD only per current implementation in ti-u-boot.
So then it only requires
do_deployandIMAGE_BOOTFILESsince that puts items into the boot partition... Do we need thedo_install?
Well, thinking a bit more about this, we do the same for all other binaries from U-boot build in u-boot-ti.inc and even upstream u-boot.inc - we install and deploy them. The installed files go into /boot directory and end up in corresponding IPK package, but we do not install it, hence the files are not in the rootfs. So this should be fine as is...
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
One more reason to do so was to allow user ease of use, to copy the logo too
from deploy folder along with other boot files (if not flashing from wic image) since the same is set in am62x.env and if logo is not present in boot
partition then it throws some error message although the device still boots.
Re: [meta-ti] [kirkstone] [PATCH v2 1/2] u-boot-ti-staging_2023.04: Copy bitmap file to boot partition for AM62x
In reply to Devarsh ThakkarQuoted 24 lines · Devarsh Thakkar
Early splash screen support for AM62x has been enabled in u-boot and it requires bitmap tarball to be present in boot partition as per the default environment settings done in u-boot [1].
Copy the ti logo bitmap tarball to boot partition of wic image in order to enable out of box early display on AM62x.
[1] https://git.ti.com/cgit/ti-u-boot/ti-u-boot/tree/board/ti/am62x/am62x.env
Signed-off-by Devarsh Thakkar <[email protected]>---
V2: Rename ti logo tarball as per suggested changes (same is being
done in ti-u-boot too)--- .../recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb | 9 +++++++++ 1 file changed, 9 insertions(+)meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb +0
-0@@ -8,3 +8,12 @@ BRANCH = "ti-u-boot-2023.04" SRCREV = "1f510931dcc90e6f28f7fed757ad5000d4382e22"
meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb BRANCH = "ti-u-boot-2023.04" · line 19
Quoted 10 lines
meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb +9
-0+do_install:append:am62xx() { + install -d ${D}/boot + install -m 0644 ${S}/tools/logos/ti_logo_414x97_32bpp.bmp.gz ${D}/boot +} + +do_deploy:append:am62xx() { + install -d ${DEPLOYDIR} + install -m 0644 ${S}/tools/logos/ti_logo_414x97_32bpp.bmp.gz ${DEPLOYDIR} +}
Denys,
In the longer term, should this be in the u-boot.inc file and not in the recipe itself? That's were all of the other do_* appends are...
Signature · 3 lines
Ryan Eatmon [email protected] ----------------------------------------- Texas Instruments, Inc. - LCPD - MGTS
Re: [meta-ti] [kirkstone] [PATCH v2 1/2] u-boot-ti-staging_2023.04: Copy bitmap file to boot partition for AM62x
Quoted 40 lines · Ryan Eatmon
Quoted 27 lines · Devarsh Thakkar
Early splash screen support for AM62x has been enabled in u-boot and it requires bitmap tarball to be present in boot partition as per the default environment settings done in u-boot [1].
Copy the ti logo bitmap tarball to boot partition of wic image in order to enable out of box early display on AM62x.
[1] https://git.ti.com/cgit/ti-u-boot/ti-u-boot/tree/board/ti/am62x/am62x.env
Signed-off-by Devarsh Thakkar <[email protected]>---
V2: Rename ti logo tarball as per suggested changes (same is being done in ti-u-boot too)
---
.../recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb | 9 +++++++++1 file changed, 9 insertions(+)meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb +0
-0@@ -8,3 +8,12 @@ BRANCH = "ti-u-boot-2023.04"SRCREV = "
1f510931dcc90e6f28f7fed757ad5000d4382e22" +do_install:append:am62xx() {
+ install -d ${D}/boot
+ install -m 0644 ${S}/tools/logos/ti_logo_414x97_32bpp.bmp.gz ${D}/bootmeta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb BRANCH = "ti-u-boot-2023.04" · line 19
Quoted 6 lines
meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb +6
-0+} + +do_deploy:append:am62xx() { + install -d ${DEPLOYDIR} + install -m 0644 ${S}/tools/logos/ti_logo_414x97_32bpp.bmp.gz ${DEPLOYDIR} +}Denys,
Quoted 3 lines
In the longer term, should this be in the u-boot.inc file and not in the recipe itself? That's were all of the other do_* appends are...
This I think is specific to u-boot 2023.04 version only as the logos were recently added and are not available in previous versions of u-boot and hence I thought to have the changes in u-boot-ti-staging_2023.04.bb
Regards
Devarsh
Quoted 2 lines
Re: [meta-ti] [kirkstone] [PATCH v2 1/2] u-boot-ti-staging_2023.04: Copy bitmap file to boot partition for AM62x
Quoted 43 lines · Devarsh Thakkar
Quoted 40 lines · Ryan Eatmon
Quoted 23 lines · Devarsh Thakkar
Early splash screen support for AM62x has been enabled in u-boot and it requires bitmap tarball to be present in boot partition as per the default environment settings done in u-boot [1].
Copy the ti logo bitmap tarball to boot partition of wic image in order to enable out of box early display on AM62x.
[1] https://git.ti.com/cgit/ti-u-boot/ti-u-boot/tree/board/ti/am62x/am62x.env
Signed-off-by Devarsh Thakkar <[email protected]>---
V2: Rename ti logo tarball as per suggested changes (same is being
done in ti-u-boot too)--- .../recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb | 9 +++++++++ 1 file changed, 9 insertions(+)meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb +0
-0meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb BRANCH = "ti-u-boot-2023.04" · line 17
Quoted 10 lines
meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb +8
-0@@ -8,3 +8,12 @@ BRANCH = "ti-u-boot-2023.04" SRCREV = "1f510931dcc90e6f28f7fed757ad5000d4382e22" +do_install:append:am62xx() { + install -d ${D}/boot + install -m 0644 ${S}/tools/logos/ti_logo_414x97_32bpp.bmp.gz ${D}/boot +} + +do_deploy:append:am62xx() { + install -d ${DEPLOYDIR} + install -m 0644 ${S}/tools/logos/ti_logo_414x97_32bpp.bmp.gz ${DEPLOYDIR} +}Denys,
Quoted 7 lines
Quoted 3 lines
In the longer term, should this be in the u-boot.inc file and not in the recipe itself? That's were all of the other do_* appends are...
This I think is specific to u-boot 2023.04 version only as the logos were recently added and are not available in previous versions of u-boot and hence I thought to have the changes in u-boot-ti-staging_2023.04.bb
But they will be there going forward and the only other version is mainline which is meant to track the latest of u-boot which theoretically will contain the logos.
Maybe the best plan would be to create a ti-logos.inc and put these statements in there and add an include to that file in the recipe. Just trying to keep the spirit of the recipe. We can then not include the logos in mainline if they are not working.
Quoted 4 lines
Regards
DevarshQuoted 2 lines
Signature · 3 lines
Ryan Eatmon [email protected] ----------------------------------------- Texas Instruments, Inc. - LCPD - MGTS
Re: [meta-ti] [kirkstone] [PATCH v2 1/2] u-boot-ti-staging_2023.04: Copy bitmap file to boot partition for AM62x
In reply to Ryan EatmonQuoted 39 lines · Ryan Eatmon via lists.yoctoproject.org
Quoted 22 lines · Devarsh Thakkar
Early splash screen support for AM62x has been enabled in u-boot and it requires bitmap tarball to be present in boot partition as per the default environment settings done in u-boot [1].
Copy the ti logo bitmap tarball to boot partition of wic image in order to enable out of box early display on AM62x.
[1] https://git.ti.com/cgit/ti-u-boot/ti-u-boot/tree/board/ti/am62x/am62x.env
Signed-off-by Devarsh Thakkar <[email protected]>---
V2: Rename ti logo tarball as per suggested changes (same is being
done in ti-u-boot too)--- .../recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb | 9 +++++++++ 1 file changed, 9 insertions(+)meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb +0
-0meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb BRANCH = "ti-u-boot-2023.04" · line 17
Quoted 10 lines
meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb +9
-0@@ -8,3 +8,12 @@ BRANCH = "ti-u-boot-2023.04" SRCREV = "1f510931dcc90e6f28f7fed757ad5000d4382e22" +do_install:append:am62xx() { + install -d ${D}/boot + install -m 0644 ${S}/tools/logos/ti_logo_414x97_32bpp.bmp.gz ${D}/boot +} + +do_deploy:append:am62xx() { + install -d ${DEPLOYDIR} + install -m 0644 ${S}/tools/logos/ti_logo_414x97_32bpp.bmp.gz ${DEPLOYDIR} +}Denys,
Quoted 2 lines
In the longer term, should this be in the u-boot.inc file and not in the recipe itself? That's were all of the other do_* appends are...
In the longer term I was going to ask if this logo should be enabled for all TI platforms, instead of just am62x?
Signature · 1 line
Denys
Re: [meta-ti] [kirkstone] [PATCH v2 1/2] u-boot-ti-staging_2023.04: Copy bitmap file to boot partition for AM62x
Quoted 40 lines · Denys Dmytriyenko
Quoted 39 lines · Ryan Eatmon via lists.yoctoproject.org
Quoted 22 lines · Devarsh Thakkar
Early splash screen support for AM62x has been enabled in u-boot and it requires bitmap tarball to be present in boot partition as per the default environment settings done in u-boot [1].
Copy the ti logo bitmap tarball to boot partition of wic image in order to enable out of box early display on AM62x.
[1] https://git.ti.com/cgit/ti-u-boot/ti-u-boot/tree/board/ti/am62x/am62x.env
Signed-off-by Devarsh Thakkar <[email protected]>---
V2: Rename ti logo tarball as per suggested changes (same is being
done in ti-u-boot too)--- .../recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb | 9 +++++++++ 1 file changed, 9 insertions(+)meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb +0
-0meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb BRANCH = "ti-u-boot-2023.04" · line 17
Quoted 10 lines
meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb +9
-0@@ -8,3 +8,12 @@ BRANCH = "ti-u-boot-2023.04" SRCREV = "1f510931dcc90e6f28f7fed757ad5000d4382e22" +do_install:append:am62xx() { + install -d ${D}/boot + install -m 0644 ${S}/tools/logos/ti_logo_414x97_32bpp.bmp.gz ${D}/boot +} + +do_deploy:append:am62xx() { + install -d ${DEPLOYDIR} + install -m 0644 ${S}/tools/logos/ti_logo_414x97_32bpp.bmp.gz ${DEPLOYDIR} +}Denys,
Quoted 5 lines
Quoted 2 lines
In the longer term, should this be in the u-boot.inc file and not in the recipe itself? That's were all of the other do_* appends are...
In the longer term I was going to ask if this logo should be enabled for all TI platforms, instead of just am62x?
Valid question.
Signature · 3 lines
Ryan Eatmon [email protected] ----------------------------------------- Texas Instruments, Inc. - LCPD - MGTS
Re: [meta-ti] [kirkstone] [PATCH v2 1/2] u-boot-ti-staging_2023.04: Copy bitmap file to boot partition for AM62x
Quoted 46 lines · Ryan Eatmon
Quoted 43 lines · Denys Dmytriyenko
Quoted 41 lines · Ryan Eatmon via lists.yoctoproject.org
Quoted 32 lines · Devarsh Thakkar
Early splash screen support for AM62x has been enabled in u-boot and it requires bitmap tarball to be present in boot partition as per the default environment settings done in u-boot [1].
Copy the ti logo bitmap tarball to boot partition of wic image in order to enable out of box early display on AM62x.
[1] https://git.ti.com/cgit/ti-u-boot/ti-u-boot/tree/board/ti/am62x/am62x.env
Signed-off-by Devarsh Thakkar <[email protected]>---
V2: Rename ti logo tarball as per suggested changes (same is being done in ti-u-boot too)
---
.../recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb | 9 +++++++++1 file changed, 9 insertions(+)meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb +0
-0@@ -8,3 +8,12 @@ BRANCH = "ti-u-boot-2023.04"SRCREV = "
1f510931dcc90e6f28f7fed757ad5000d4382e22"meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb +8
-0+do_install:append:am62xx() { + install -d ${D}/boot + install -m 0644 ${S}/tools/logos/ti_logo_414x97_32bpp.bmp.gz ${D}/boot +} + +do_deploy:append:am62xx() { + install -d ${DEPLOYDIR} + install -m 0644 ${S}/tools/logos/ti_logo_414x97_32bpp.bmp.gzQuoted 2 lines
${DEPLOYDIR}
+}Denys,
Quoted 8 lines
Quoted 5 lines
Quoted 2 lines
In the longer term, should this be in the u-boot.inc file and not in the recipe itself? That's were all of the other do_* appends are...
In the longer term I was going to ask if this logo should be enabled for all TI platforms, instead of just am62x?
Valid question.
I am not sure about all but I see it as possibility for many TI K3 platforms having display support displaying logo during bootup in future, although they may use different files for logo depending upon resolution, memory e.t.c.
Regards
Devarsh