Discussion:
[meta-arago] [rocko/master][PATCH] u-boot-k3-r5: update SYSFW to 2018.08b
Denys Dmytriyenko
2018-09-13 19:17:25 UTC
Permalink
Also install and deploy versioned SYSFW binary with short symlink.

Signed-off-by: Denys Dmytriyenko <***@ti.com>
---
.../recipes-bsp/u-boot/u-boot-k3-r5_2018.01.bb | 17 +++++++++++------
1 file changed, 11 insertions(+), 6 deletions(-)

diff --git a/meta-arago-distro/recipes-bsp/u-boot/u-boot-k3-r5_2018.01.bb b/meta-arago-distro/recipes-bsp/u-boot/u-boot-k3-r5_2018.01.bb
index 0ff5658..57055c7 100644
--- a/meta-arago-distro/recipes-bsp/u-boot/u-boot-k3-r5_2018.01.bb
+++ b/meta-arago-distro/recipes-bsp/u-boot/u-boot-k3-r5_2018.01.bb
@@ -7,10 +7,12 @@ PKG_${PN}-dbg = "${PN}-dbg"

COMPATIBLE_MACHINE = "k3"

-SYSFW_VER = "2018.07a"
-SYSFW_BIN_am65xx-evm = "ti-sci-firmware-am6x-gp.bin"
+SYSFW_VER = "2018.08b"
+SYSFW_TISCI_am65xx-evm = "ti-sci-firmware-am65x-gp.bin"
+SYSFW_BINARY = "sysfw.bin"
+SYSFW_IMAGE = "sysfw-${SYSFW_VER}.bin"

-SRCREV_sysfw = "2035022224dcc885ac2cd0b11f8c76190f5af962"
+SRCREV_sysfw = "463b1b4a50e8e361fa333f87caf74d2e05bc0a82"
SYSFW_BRANCH = "ti-linux-firmware-4.1.y"
SRCREV_FORMAT = "sysfw"

@@ -33,13 +35,16 @@ UBOOT_SYMLINK = "tiboot3-${MACHINE}.bin"
SPL_BINARY_k3 = ""

do_configure_append() {
- ${WORKDIR}/gen_x509_cert.sh -m rom -c m3 -b ${WORKDIR}/fw/ti-sysfw/${SYSFW_BIN} -o ${WORKDIR}/sysfw.bin -l 0x40000
+ ${WORKDIR}/gen_x509_cert.sh -m rom -c m3 -b ${WORKDIR}/fw/ti-sysfw/${SYSFW_TISCI} -o ${WORKDIR}/sysfw.bin -l 0x40000
}

do_install_append() {
- install -m 644 ${WORKDIR}/sysfw.bin ${D}/boot/
+ install -m 644 ${WORKDIR}/${SYSFW_BINARY} ${D}/boot/${SYSFW_IMAGE}
+ ln -sf ${SYSFW_IMAGE} ${D}/boot/${SYSFW_BINARY}
}

do_deploy_append() {
- install -m 644 ${WORKDIR}/sysfw.bin ${DEPLOYDIR}/
+ install -m 644 ${WORKDIR}/${SYSFW_BINARY} ${DEPLOYDIR}/${SYSFW_IMAGE}
+ rm -f ${DEPLOYDIR}/${SYSFW_BINARY}
+ ln -sf ${SYSFW_IMAGE} ${DEPLOYDIR}/${SYSFW_BINARY}
}
--
2.7.4
Jacob Stiffler
2018-09-13 19:30:27 UTC
Permalink
Post by Denys Dmytriyenko
Also install and deploy versioned SYSFW binary with short symlink.
---
.../recipes-bsp/u-boot/u-boot-k3-r5_2018.01.bb | 17 +++++++++++------
1 file changed, 11 insertions(+), 6 deletions(-)
diff --git a/meta-arago-distro/recipes-bsp/u-boot/u-boot-k3-r5_2018.01.bb b/meta-arago-distro/recipes-bsp/u-boot/u-boot-k3-r5_2018.01.bb
index 0ff5658..57055c7 100644
--- a/meta-arago-distro/recipes-bsp/u-boot/u-boot-k3-r5_2018.01.bb
+++ b/meta-arago-distro/recipes-bsp/u-boot/u-boot-k3-r5_2018.01.bb
@@ -7,10 +7,12 @@ PKG_${PN}-dbg = "${PN}-dbg"
COMPATIBLE_MACHINE = "k3"
-SYSFW_VER = "2018.07a"
-SYSFW_BIN_am65xx-evm = "ti-sci-firmware-am6x-gp.bin"
+SYSFW_VER = "2018.08b"
+SYSFW_TISCI_am65xx-evm = "ti-sci-firmware-am65x-gp.bin"
+SYSFW_BINARY = "sysfw.bin"
+SYSFW_IMAGE = "sysfw-${SYSFW_VER}.bin"
-SRCREV_sysfw = "2035022224dcc885ac2cd0b11f8c76190f5af962"
+SRCREV_sysfw = "463b1b4a50e8e361fa333f87caf74d2e05bc0a82"
SYSFW_BRANCH = "ti-linux-firmware-4.1.y"
SRCREV_FORMAT = "sysfw"
@@ -33,13 +35,16 @@ UBOOT_SYMLINK = "tiboot3-${MACHINE}.bin"
SPL_BINARY_k3 = ""
do_configure_append() {
- ${WORKDIR}/gen_x509_cert.sh -m rom -c m3 -b ${WORKDIR}/fw/ti-sysfw/${SYSFW_BIN} -o ${WORKDIR}/sysfw.bin -l 0x40000
+ ${WORKDIR}/gen_x509_cert.sh -m rom -c m3 -b ${WORKDIR}/fw/ti-sysfw/${SYSFW_TISCI} -o ${WORKDIR}/sysfw.bin -l 0x40000
Should "${SYSFW_BINARY}" be used here instead of "sysfw.bin" to match
do_install()?
Post by Denys Dmytriyenko
}
do_install_append() {
- install -m 644 ${WORKDIR}/sysfw.bin ${D}/boot/
+ install -m 644 ${WORKDIR}/${SYSFW_BINARY} ${D}/boot/${SYSFW_IMAGE}
+ ln -sf ${SYSFW_IMAGE} ${D}/boot/${SYSFW_BINARY}
}
do_deploy_append() {
- install -m 644 ${WORKDIR}/sysfw.bin ${DEPLOYDIR}/
+ install -m 644 ${WORKDIR}/${SYSFW_BINARY} ${DEPLOYDIR}/${SYSFW_IMAGE}
+ rm -f ${DEPLOYDIR}/${SYSFW_BINARY}
+ ln -sf ${SYSFW_IMAGE} ${DEPLOYDIR}/${SYSFW_BINARY}
}
Denys Dmytriyenko
2018-09-13 19:36:55 UTC
Permalink
Post by Jacob Stiffler
Post by Denys Dmytriyenko
Also install and deploy versioned SYSFW binary with short symlink.
---
.../recipes-bsp/u-boot/u-boot-k3-r5_2018.01.bb | 17 +++++++++++------
1 file changed, 11 insertions(+), 6 deletions(-)
diff --git a/meta-arago-distro/recipes-bsp/u-boot/u-boot-k3-r5_2018.01.bb b/meta-arago-distro/recipes-bsp/u-boot/u-boot-k3-r5_2018.01.bb
index 0ff5658..57055c7 100644
--- a/meta-arago-distro/recipes-bsp/u-boot/u-boot-k3-r5_2018.01.bb
+++ b/meta-arago-distro/recipes-bsp/u-boot/u-boot-k3-r5_2018.01.bb
@@ -7,10 +7,12 @@ PKG_${PN}-dbg = "${PN}-dbg"
COMPATIBLE_MACHINE = "k3"
-SYSFW_VER = "2018.07a"
-SYSFW_BIN_am65xx-evm = "ti-sci-firmware-am6x-gp.bin"
+SYSFW_VER = "2018.08b"
+SYSFW_TISCI_am65xx-evm = "ti-sci-firmware-am65x-gp.bin"
+SYSFW_BINARY = "sysfw.bin"
+SYSFW_IMAGE = "sysfw-${SYSFW_VER}.bin"
-SRCREV_sysfw = "2035022224dcc885ac2cd0b11f8c76190f5af962"
+SRCREV_sysfw = "463b1b4a50e8e361fa333f87caf74d2e05bc0a82"
SYSFW_BRANCH = "ti-linux-firmware-4.1.y"
SRCREV_FORMAT = "sysfw"
@@ -33,13 +35,16 @@ UBOOT_SYMLINK = "tiboot3-${MACHINE}.bin"
SPL_BINARY_k3 = ""
do_configure_append() {
- ${WORKDIR}/gen_x509_cert.sh -m rom -c m3 -b ${WORKDIR}/fw/ti-sysfw/${SYSFW_BIN} -o ${WORKDIR}/sysfw.bin -l 0x40000
+ ${WORKDIR}/gen_x509_cert.sh -m rom -c m3 -b ${WORKDIR}/fw/ti-sysfw/${SYSFW_TISCI} -o ${WORKDIR}/sysfw.bin -l 0x40000
Should "${SYSFW_BINARY}" be used here instead of "sysfw.bin" to match
do_install()?
Sure, would make sense.
Post by Jacob Stiffler
Post by Denys Dmytriyenko
do_install_append() {
- install -m 644 ${WORKDIR}/sysfw.bin ${D}/boot/
+ install -m 644 ${WORKDIR}/${SYSFW_BINARY} ${D}/boot/${SYSFW_IMAGE}
+ ln -sf ${SYSFW_IMAGE} ${D}/boot/${SYSFW_BINARY}
}
do_deploy_append() {
- install -m 644 ${WORKDIR}/sysfw.bin ${DEPLOYDIR}/
+ install -m 644 ${WORKDIR}/${SYSFW_BINARY} ${DEPLOYDIR}/${SYSFW_IMAGE}
+ rm -f ${DEPLOYDIR}/${SYSFW_BINARY}
+ ln -sf ${SYSFW_IMAGE} ${DEPLOYDIR}/${SYSFW_BINARY}
}
Loading...