[meta-ti] [master][PATCH] cm3-pm-firmware: bump SRCREV for -ffreestanding fix

[Denys Dmytriyenko]

Rework original patch from Khem Raj by upstreaming the Makefile fix
instead of carrying it locally.

Signed-off-by: Denys Dmytriyenko 
---
 recipes-bsp/cm3-pm-firmware/amx3-cm3_git.bb | 6 ++
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/recipes-bsp/cm3-pm-firmware/amx3-cm3_git.bb 
b/recipes-bsp/cm3-pm-firmware/amx3-cm3_git.bb
index 1dcc021..93cebd7 100644
--- a/recipes-bsp/cm3-pm-firmware/amx3-cm3_git.bb
+++ b/recipes-bsp/cm3-pm-firmware/amx3-cm3_git.bb
@@ -6,17 +6,15 @@ LIC_FILES_CHKSUM = 
"file://License.txt;md5=7bdc54a749ab7a7dea999d25d99a41b8"
 PV = "1.9.2"
 PR = "r0"
 
-SRCREV = "7eb9c0856a9e8b3b42bf64f761da135852b8eea7"
+SRCREV = "fb484c5e54f2e31cf0a338d2927a06a2870bcc2c"
 BRANCH ?= "ti-v4.1.y"
 
 SRC_URI = 
"git://git.ti.com/processor-firmware/ti-amx3-cm3-pm-firmware.git;protocol=git;branch=${BRANCH}"
 
 S = "${WORKDIR}/git"
 
-FLOATABI = "${@bb.utils.contains("TUNE_FEATURES", "vfp", 
bb.utils.contains("TUNE_FEATURES", "callconvention-hard", " -mfloat-abi=hard", 
" -mfloat-abi=softfp", d), "" ,d)}"
-
 do_compile() {
-   make CROSS_COMPILE="${TARGET_PREFIX}" CC="${TARGET_PREFIX}gcc 
${TOOLCHAIN_OPTIONS} ${FLOATABI} ${SECURITY_NOPIE_CFLAGS}"
+   make CROSS_COMPILE="${TARGET_PREFIX}" CC="${TARGET_PREFIX}gcc 
${TOOLCHAIN_OPTIONS} ${SECURITY_NOPIE_CFLAGS}"
 }
 
 do_install() {
-- 
2.7.4

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

[meta-ti] [master][PATCH] ti-sgx-ddk-km: fix/workaround new gcc8 checks

[Denys Dmytriyenko]

Signed-off-by: Denys Dmytriyenko 
---
 ...-buildvars.mk-pass-Wno-cast-function-type.patch | 26 +
 ...inux-osfunc.c-fix-gcc8-stringop-truncatio.patch | 34 ++
 .../powervr-drivers/ti-sgx-ddk-km_1.14.3699939.bb  |  4 ++-
 3 files changed, 63 insertions(+), 1 deletion(-)
 create mode 100644 
recipes-bsp/powervr-drivers/ti-sgx-ddk-km/0001-buildvars.mk-pass-Wno-cast-function-type.patch
 create mode 100644 
recipes-bsp/powervr-drivers/ti-sgx-ddk-km/0001-srvkm-env-linux-osfunc.c-fix-gcc8-stringop-truncatio.patch

diff --git 
a/recipes-bsp/powervr-drivers/ti-sgx-ddk-km/0001-buildvars.mk-pass-Wno-cast-function-type.patch
 
b/recipes-bsp/powervr-drivers/ti-sgx-ddk-km/0001-buildvars.mk-pass-Wno-cast-function-type.patch
new file mode 100644
index 000..e1d2d10
--- /dev/null
+++ 
b/recipes-bsp/powervr-drivers/ti-sgx-ddk-km/0001-buildvars.mk-pass-Wno-cast-function-type.patch
@@ -0,0 +1,26 @@
+From 287ca27cdf9004b4ba9bb0ce30d6139f707246f9 Mon Sep 17 00:00:00 2001
+From: Denys Dmytriyenko 
+Date: Sun, 14 Oct 2018 19:53:14 -0400
+Subject: [PATCH] buildvars.mk: pass -Wno-cast-function-type
+
+Signed-off-by: Denys Dmytriyenko 
+---
+ eurasia_km/eurasiacon/build/linux2/buildvars.mk | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/eurasia_km/eurasiacon/build/linux2/buildvars.mk 
b/eurasia_km/eurasiacon/build/linux2/buildvars.mk
+index f30e467..f00f852 100644
+--- a/eurasia_km/eurasiacon/build/linux2/buildvars.mk
 b/eurasia_km/eurasiacon/build/linux2/buildvars.mk
+@@ -48,7 +48,7 @@
+ 
+ # These flags are used for kernel, User C and User C++
+ #
+-COMMON_FLAGS := -W -Wall
++COMMON_FLAGS := -W -Wall -Wno-cast-function-type
+ 
+ # Some GCC warnings are C only, so we must mask them from C++
+ #
+-- 
+2.7.4
+
diff --git 
a/recipes-bsp/powervr-drivers/ti-sgx-ddk-km/0001-srvkm-env-linux-osfunc.c-fix-gcc8-stringop-truncatio.patch
 
b/recipes-bsp/powervr-drivers/ti-sgx-ddk-km/0001-srvkm-env-linux-osfunc.c-fix-gcc8-stringop-truncatio.patch
new file mode 100644
index 000..96e657d
--- /dev/null
+++ 
b/recipes-bsp/powervr-drivers/ti-sgx-ddk-km/0001-srvkm-env-linux-osfunc.c-fix-gcc8-stringop-truncatio.patch
@@ -0,0 +1,34 @@
+From 353d8b9313abc492e5938171cea4ac697fd991f0 Mon Sep 17 00:00:00 2001
+From: Denys Dmytriyenko 
+Date: Sun, 14 Oct 2018 19:41:49 -0400
+Subject: [PATCH] srvkm/env/linux/osfunc.c: fix gcc8 stringop-truncation error
+
+gcc8 now checks for strncpy function that potentially truncate the terminating
+NUL charcter from the source string. Fails like this:
+
+.../services4/srvkm/env/linux/osfunc.c:3051:13: error: 'strncpy' specified 
bound 50 equals destination size [-Werror=stringop-truncation]
+|  strncpy(psEventObject->szName, pszName, EVENTOBJNAME_MAXLENGTH);
+|  ^~~
+| cc1: all warnings being treated as errors
+
+Signed-off-by: Denys Dmytriyenko 
+---
+ eurasia_km/services4/srvkm/env/linux/osfunc.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/eurasia_km/services4/srvkm/env/linux/osfunc.c 
b/eurasia_km/services4/srvkm/env/linux/osfunc.c
+index 02dfe9b..02c8e3b 100644
+--- a/eurasia_km/services4/srvkm/env/linux/osfunc.c
 b/eurasia_km/services4/srvkm/env/linux/osfunc.c
+@@ -3048,7 +3048,7 @@ PVRSRV_ERROR OSEventObjectCreateKM(const IMG_CHAR 
*pszName, PVRSRV_EVENTOBJECT *
+ if(pszName)
+ {
+ /* copy over the event object name */
+-strncpy(psEventObject->szName, pszName, EVENTOBJNAME_MAXLENGTH);
++strncpy(psEventObject->szName, pszName, EVENTOBJNAME_MAXLENGTH-1);
+ }
+ else
+ {
+-- 
+2.7.4
+
diff --git a/recipes-bsp/powervr-drivers/ti-sgx-ddk-km_1.14.3699939.bb 
b/recipes-bsp/powervr-drivers/ti-sgx-ddk-km_1.14.3699939.bb
index a4eb82a..e84c11b 100644
--- a/recipes-bsp/powervr-drivers/ti-sgx-ddk-km_1.14.3699939.bb
+++ b/recipes-bsp/powervr-drivers/ti-sgx-ddk-km_1.14.3699939.bb
@@ -22,7 +22,9 @@ RCONFLICTS_${PN} = "omapdrm-pvr"
 
 BRANCH = "ti-img-sgx/${PV}/k4.14"
 
-SRC_URI = 
"git://git.ti.com/graphics/omap5-sgx-ddk-linux.git;protocol=git;branch=${BRANCH}"
+SRC_URI = 
"git://git.ti.com/graphics/omap5-sgx-ddk-linux.git;protocol=git;branch=${BRANCH}
 \
+   file://0001-srvkm-env-linux-osfunc.c-fix-gcc8-stringop-truncatio.patch \
+   file://0001-buildvars.mk-pass-Wno-cast-function-type.patch"
 
 S = "${WORKDIR}/git"
 
-- 
2.7.4

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [PATCH] beaglebone.conf: temporarily use generic am335x_evm_config for U-boot

[Denys Dmytriyenko]

On Sat, Oct 13, 2018 at 01:17:12AM -0700, Khem Raj wrote:
> On Fri, Oct 12, 2018 at 8:00 PM Denys Dmytriyenko  wrote:
> >
> > There have been reports recently that am335x_beaglebone_config generates 
> > bad SPL.
> > Until that is debugged and fixed, use generic am335x_evm_config that covers 
> > all
> > AM335x platforms, including BeagleBone variants.
> >
> 
> it fails to link
> 
> | arm-yoe-linux-gnueabi-ld.bfd: u-boot-spl section `.rodata' will not
> fit in region `.sram'
> | arm-yoe-linux-gnueabi-ld.bfd: region `.sram' overflowed by 5772 bytes
> | make[2]: *** 
> [/mnt/a/yoe/build/tmp/work/beaglebone-yoe-linux-gnueabi/u-boot-ti-staging/2018.01+gitAUTOINC+2cc52408bf-r24/git/scripts/Makefile.spl:349:
> spl/u-boot-spl] Error 1

FWIW, just built u-boot-ti-staging with gcc7 and gcc8 from oe-core, as well as 
Linaro gcc7 - no problems.


> > Signed-off-by: Denys Dmytriyenko 
> > ---
> >  conf/machine/beaglebone.conf | 3 ++-
> >  1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/conf/machine/beaglebone.conf b/conf/machine/beaglebone.conf
> > index 49edfd6..2514792 100644
> > --- a/conf/machine/beaglebone.conf
> > +++ b/conf/machine/beaglebone.conf
> > @@ -13,7 +13,8 @@ MACHINE_GUI_CLASS = "bigscreen"
> >
> >  SERIAL_CONSOLE = "115200 ttyS0"
> >
> > -UBOOT_MACHINE = "am335x_boneblack_config"
> > +# fall back on generic am335x_evm_config for now
> > +#UBOOT_MACHINE = "am335x_boneblack_config"
> >
> >  WKS_FILE = "sdimage-bootpart.wks"
> >  IMAGE_BOOT_FILES = "MLO u-boot.img"
> > --
> > 2.7.4
> >
> > --
> > ___
> > meta-ti mailing list
> > meta-ti@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [PATCH 2/2] beaglebone.conf: Switch u-boot provider to mainline from oe-core

[Denys Dmytriyenko]

This is should be a less dramatic workaround for now :)
https://lists.yoctoproject.org/pipermail/meta-ti/2018-October/011363.html

Thanks for confirming SPL breakage with am335x_beaglebone_config


On Fri, Oct 12, 2018 at 06:57:21PM -0700, Khem Raj wrote:
> use beaglebone specific wic template
> 
> Signed-off-by: Khem Raj 
> ---
>  conf/machine/beaglebone.conf | 22 --
>  1 file changed, 16 insertions(+), 6 deletions(-)
> 
> diff --git a/conf/machine/beaglebone.conf b/conf/machine/beaglebone.conf
> index 49edfd61..25b9998a 100644
> --- a/conf/machine/beaglebone.conf
> +++ b/conf/machine/beaglebone.conf
> @@ -1,6 +1,6 @@
>  #@TYPE: Machine
>  #@NAME: BeagleBone machine
> -#@DESCRIPTION: Machine configuration for the http://beagleboard.org/bone 
> board 
> +#@DESCRIPTION: Machine configuration for the http://beagleboard.org/bone 
> board
>  
>  require conf/machine/include/ti33x.inc
>  
> @@ -11,15 +11,25 @@ KERNEL_DEVICETREE = "am335x-bone.dtb am335x-boneblue.dtb \
>  # Only has DVI connector for external screen
>  MACHINE_GUI_CLASS = "bigscreen"
>  
> -SERIAL_CONSOLE = "115200 ttyS0"
> +SERIAL_CONSOLES = "115200;ttyS0 115200;ttyO0"
>  
>  UBOOT_MACHINE = "am335x_boneblack_config"
>  
> -WKS_FILE = "sdimage-bootpart.wks"
> -IMAGE_BOOT_FILES = "MLO u-boot.img"
> -IMAGE_FSTYPES += "tar.xz wic.xz"
> +WKS_FILE = "beaglebone.wks"
>  
> -do_image_wic[depends] += "mtools-native:do_populate_sysroot 
> dosfstools-native:do_populate_sysroot"
> +IMAGE_BOOT_FILES ?= "u-boot.${UBOOT_SUFFIX} MLO zImage am335x-bone.dtb 
> am335x-boneblack.dtb am335x-bonegreen.dtb"
> +
> +IMAGE_FSTYPES += "tar.xz wic.xz"
>  
>  # Refine the list of device targets for ti-pdk class recipes
>  TI_PDK_LIMIT_BOARDS = "bbbAM335x"
> +
> +SPL_BINARY = "MLO"
> +UBOOT_SUFFIX = "img"
> +
> +IMAGE_INSTALL_append = " kernel-devicetree kernel-image-zimage"
> +do_image_wic[depends] += "mtools-native:do_populate_sysroot 
> dosfstools-native:do_populate_sysroot"
> +
> +PREFERRED_PROVIDER_virtual/bootloader = "u-boot"
> +PREFERRED_PROVIDER_u-boot = "u-boot"
> +
> -- 
> 2.19.1
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

[meta-ti] [PATCH] beaglebone.conf: temporarily use generic am335x_evm_config for U-boot

[Denys Dmytriyenko]

There have been reports recently that am335x_beaglebone_config generates bad 
SPL.
Until that is debugged and fixed, use generic am335x_evm_config that covers all
AM335x platforms, including BeagleBone variants.

Signed-off-by: Denys Dmytriyenko 
---
 conf/machine/beaglebone.conf | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/conf/machine/beaglebone.conf b/conf/machine/beaglebone.conf
index 49edfd6..2514792 100644
--- a/conf/machine/beaglebone.conf
+++ b/conf/machine/beaglebone.conf
@@ -13,7 +13,8 @@ MACHINE_GUI_CLASS = "bigscreen"
 
 SERIAL_CONSOLE = "115200 ttyS0"
 
-UBOOT_MACHINE = "am335x_boneblack_config"
+# fall back on generic am335x_evm_config for now
+#UBOOT_MACHINE = "am335x_boneblack_config"
 
 WKS_FILE = "sdimage-bootpart.wks"
 IMAGE_BOOT_FILES = "MLO u-boot.img"
-- 
2.7.4

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [PATCH] beaglebone-getting-started: Use cp options to not alter file mode

[Denys Dmytriyenko]

On Fri, Oct 12, 2018 at 02:14:23PM -0700, Khem Raj wrote:
> On Fri, Oct 12, 2018 at 2:01 PM Denys Dmytriyenko  wrote:
> >
> > On Fri, Oct 12, 2018 at 01:49:05PM -0700, Khem Raj wrote:
> > > On Fri, Oct 12, 2018 at 1:37 PM Denys Dmytriyenko  wrote:
> > > >
> > > > On Fri, Oct 12, 2018 at 01:34:13PM -0700, Khem Raj wrote:
> > > > > On Fri, Oct 12, 2018 at 1:31 PM Denys Dmytriyenko  
> > > > > wrote:
> > > > > >
> > > > > > On Fri, Oct 12, 2018 at 01:01:41PM -0700, Khem Raj wrote:
> > > > > > > On Fri, Oct 12, 2018 at 12:58 PM Denys Dmytriyenko  
> > > > > > > wrote:
> > > > > > > >
> > > > > > > > Are you still trying to do world builds? :)
> > > > > > > >
> > > > > > >
> > > > > > > yes. with the patches I send in this week meta-ti seems to behave 
> > > > > > > in
> > > > > > > multi-BSP setup
> > > > > > > I will soon add it to bblayers.conf for Yoe distro and it will 
> > > > > > > start
> > > > > > > testing on meta-openembedded CI builds, atleast for not nosing 
> > > > > > > other
> > > > > > > BSPs, I dont have infra to do world build for all the machines
> > > > > > >
> > > > > > > but if you were to pick Yoe distro and run with it for machines 
> > > > > > > you
> > > > > > > are interested in
> > > > > > > that would be awesome.
> > > > > > >
> > > > > > > See. https://github.com/YoeDistro/yoe-distro, everyone having 
> > > > > > > interesting boards
> > > > > > > is welcome to run world builds using that and report problems.
> > > > > >
> > > > > > I can probably add it to my CI loop as well - I already do 
> > > > > > extensive builds
> > > > > > and tests on Arago, Poky and distroless.
> > > > >
> > > > > Cool thanks. Although you wont need all of above
> > > > > after this :)
> > > >
> > > > Meaning?
> > >
> > > Yoe is a superset
> >
> > Uhm, hardly. Do you mean just BSP pieces?
> 
> not only that but we have added lot
> of common layers too

Still, it may only replace basic BSP testing, not a whole Distro with custom 
apps, etc...
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [PATCH] beaglebone-getting-started: Use cp options to not alter file mode

[Denys Dmytriyenko]

On Fri, Oct 12, 2018 at 01:49:05PM -0700, Khem Raj wrote:
> On Fri, Oct 12, 2018 at 1:37 PM Denys Dmytriyenko  wrote:
> >
> > On Fri, Oct 12, 2018 at 01:34:13PM -0700, Khem Raj wrote:
> > > On Fri, Oct 12, 2018 at 1:31 PM Denys Dmytriyenko  wrote:
> > > >
> > > > On Fri, Oct 12, 2018 at 01:01:41PM -0700, Khem Raj wrote:
> > > > > On Fri, Oct 12, 2018 at 12:58 PM Denys Dmytriyenko  
> > > > > wrote:
> > > > > >
> > > > > > Are you still trying to do world builds? :)
> > > > > >
> > > > >
> > > > > yes. with the patches I send in this week meta-ti seems to behave in
> > > > > multi-BSP setup
> > > > > I will soon add it to bblayers.conf for Yoe distro and it will start
> > > > > testing on meta-openembedded CI builds, atleast for not nosing other
> > > > > BSPs, I dont have infra to do world build for all the machines
> > > > >
> > > > > but if you were to pick Yoe distro and run with it for machines you
> > > > > are interested in
> > > > > that would be awesome.
> > > > >
> > > > > See. https://github.com/YoeDistro/yoe-distro, everyone having 
> > > > > interesting boards
> > > > > is welcome to run world builds using that and report problems.
> > > >
> > > > I can probably add it to my CI loop as well - I already do extensive 
> > > > builds
> > > > and tests on Arago, Poky and distroless.
> > >
> > > Cool thanks. Although you wont need all of above
> > > after this :)
> >
> > Meaning?
> 
> Yoe is a superset

Uhm, hardly. Do you mean just BSP pieces?
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [PATCH] beaglebone-getting-started: Use cp options to not alter file mode

[Denys Dmytriyenko]

On Fri, Oct 12, 2018 at 01:34:13PM -0700, Khem Raj wrote:
> On Fri, Oct 12, 2018 at 1:31 PM Denys Dmytriyenko  wrote:
> >
> > On Fri, Oct 12, 2018 at 01:01:41PM -0700, Khem Raj wrote:
> > > On Fri, Oct 12, 2018 at 12:58 PM Denys Dmytriyenko  wrote:
> > > >
> > > > Are you still trying to do world builds? :)
> > > >
> > >
> > > yes. with the patches I send in this week meta-ti seems to behave in
> > > multi-BSP setup
> > > I will soon add it to bblayers.conf for Yoe distro and it will start
> > > testing on meta-openembedded CI builds, atleast for not nosing other
> > > BSPs, I dont have infra to do world build for all the machines
> > >
> > > but if you were to pick Yoe distro and run with it for machines you
> > > are interested in
> > > that would be awesome.
> > >
> > > See. https://github.com/YoeDistro/yoe-distro, everyone having interesting 
> > > boards
> > > is welcome to run world builds using that and report problems.
> >
> > I can probably add it to my CI loop as well - I already do extensive builds
> > and tests on Arago, Poky and distroless.
> 
> Cool thanks. Although you wont need all of above
> after this :)

Meaning?


> > > > Most of the places with this QA warning that are part of our builds 
> > > > were fixed
> > > > before, but there are some outdated recipes like this one which were 
> > > > left out.
> > > >
> > > >
> > > > On Fri, Oct 12, 2018 at 12:50:00PM -0700, Khem Raj wrote:
> > > > > Fixes do_package_qa warnings
> > > > >  is owned by uid 1000, which is the same as the user running 
> > > > > bitbake. This may be due to host contamination
> > > > >
> > > > > Signed-off-by: Khem Raj 
> > > > > ---
> > > > >  recipes-ti/beagleboard/beaglebone-getting-started.bb | 2 +-
> > > > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > > > >
> > > > > diff --git a/recipes-ti/beagleboard/beaglebone-getting-started.bb 
> > > > > b/recipes-ti/beagleboard/beaglebone-getting-started.bb
> > > > > index 603a01a7..6c61a4e9 100644
> > > > > --- a/recipes-ti/beagleboard/beaglebone-getting-started.bb
> > > > > +++ b/recipes-ti/beagleboard/beaglebone-getting-started.bb
> > > > > @@ -14,7 +14,7 @@ S = "${WORKDIR}/git"
> > > > >
> > > > >  do_install() {
> > > > >   install -d ${D}${datadir}/${PN}
> > > > > - cp -a ${S}/* ${D}${datadir}/${PN}
> > > > > + cp -R --no-dereference --preserve=mode,links ${S}/* 
> > > > > ${D}${datadir}/${PN}
> > > > >  }
> > > > >
> > > > >  FILES_${PN} += "${datadir}/${PN}"
> > > > > --
> > > > > 2.19.1
> > > > >
> > > > > --
> > > > > ___
> > > > > meta-ti mailing list
> > > > > meta-ti@yoctoproject.org
> > > > > https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [PATCH] beaglebone-getting-started: Use cp options to not alter file mode

[Denys Dmytriyenko]

On Fri, Oct 12, 2018 at 01:01:41PM -0700, Khem Raj wrote:
> On Fri, Oct 12, 2018 at 12:58 PM Denys Dmytriyenko  wrote:
> >
> > Are you still trying to do world builds? :)
> >
> 
> yes. with the patches I send in this week meta-ti seems to behave in
> multi-BSP setup
> I will soon add it to bblayers.conf for Yoe distro and it will start
> testing on meta-openembedded CI builds, atleast for not nosing other
> BSPs, I dont have infra to do world build for all the machines
> 
> but if you were to pick Yoe distro and run with it for machines you
> are interested in
> that would be awesome.
> 
> See. https://github.com/YoeDistro/yoe-distro, everyone having interesting 
> boards
> is welcome to run world builds using that and report problems.

I can probably add it to my CI loop as well - I already do extensive builds 
and tests on Arago, Poky and distroless.


> > Most of the places with this QA warning that are part of our builds were 
> > fixed
> > before, but there are some outdated recipes like this one which were left 
> > out.
> >
> >
> > On Fri, Oct 12, 2018 at 12:50:00PM -0700, Khem Raj wrote:
> > > Fixes do_package_qa warnings
> > >  is owned by uid 1000, which is the same as the user running 
> > > bitbake. This may be due to host contamination
> > >
> > > Signed-off-by: Khem Raj 
> > > ---
> > >  recipes-ti/beagleboard/beaglebone-getting-started.bb | 2 +-
> > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/recipes-ti/beagleboard/beaglebone-getting-started.bb 
> > > b/recipes-ti/beagleboard/beaglebone-getting-started.bb
> > > index 603a01a7..6c61a4e9 100644
> > > --- a/recipes-ti/beagleboard/beaglebone-getting-started.bb
> > > +++ b/recipes-ti/beagleboard/beaglebone-getting-started.bb
> > > @@ -14,7 +14,7 @@ S = "${WORKDIR}/git"
> > >
> > >  do_install() {
> > >   install -d ${D}${datadir}/${PN}
> > > - cp -a ${S}/* ${D}${datadir}/${PN}
> > > + cp -R --no-dereference --preserve=mode,links ${S}/* 
> > > ${D}${datadir}/${PN}
> > >  }
> > >
> > >  FILES_${PN} += "${datadir}/${PN}"
> > > --
> > > 2.19.1
> > >
> > > --
> > > ___
> > > meta-ti mailing list
> > > meta-ti@yoctoproject.org
> > > https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [PATCH] beaglebone-getting-started: Use cp options to not alter file mode

[Denys Dmytriyenko]

Are you still trying to do world builds? :)

Most of the places with this QA warning that are part of our builds were fixed 
before, but there are some outdated recipes like this one which were left out.


On Fri, Oct 12, 2018 at 12:50:00PM -0700, Khem Raj wrote:
> Fixes do_package_qa warnings
>  is owned by uid 1000, which is the same as the user running bitbake. 
> This may be due to host contamination
> 
> Signed-off-by: Khem Raj 
> ---
>  recipes-ti/beagleboard/beaglebone-getting-started.bb | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/recipes-ti/beagleboard/beaglebone-getting-started.bb 
> b/recipes-ti/beagleboard/beaglebone-getting-started.bb
> index 603a01a7..6c61a4e9 100644
> --- a/recipes-ti/beagleboard/beaglebone-getting-started.bb
> +++ b/recipes-ti/beagleboard/beaglebone-getting-started.bb
> @@ -14,7 +14,7 @@ S = "${WORKDIR}/git"
>  
>  do_install() {
>   install -d ${D}${datadir}/${PN}
> - cp -a ${S}/* ${D}${datadir}/${PN}
> + cp -R --no-dereference --preserve=mode,links ${S}/* ${D}${datadir}/${PN}
>  }
>  
>  FILES_${PN} += "${datadir}/${PN}"
> -- 
> 2.19.1
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [PATCH] recipes: Limit ti specific recipes under ti-soc override

[Denys Dmytriyenko]

On Tue, Oct 09, 2018 at 03:40:40PM -0700, Khem Raj wrote:
> No, it doesn't AFAICT
> 
> On Tue, Oct 9, 2018 at 1:49 PM Denys Dmytriyenko  wrote:
> 
> > Does this make packages machine-specific?
> >
> > On Tue, Oct 09, 2018 at 01:45:03PM -0700, Khem Raj wrote:
> > > This helps in multi-BSP scenario, where other BSP layers are also
> > > present in the layermix

I'm not specifically against this patch, but want to understand better - are 
there any specific conflicts these packages have with other BSPs?


> > > Signed-off-by: Khem Raj 
> > > ---
> > >  recipes-bsp/cuia/cuia_1.0.0.13.bb  | 3 +++
> > >  recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb | 3 +++
> > >  recipes-bsp/x-load/x-load_git.bb   | 3 +++
> > >  recipes-graphics/gbm/libgbm_10.0.0.bb  | 3 +++
> > >  recipes-graphics/libgal/ti-gc320-libs_5.0.11.p7.bb | 3 +++
> > >  recipes-graphics/omapfbplay/omapfbplay.inc | 2 ++
> > >  recipes-multimedia/libdce/libdce_3.00.14.00.bb | 2 ++
> > >  recipes-ti/bios/ti-biosutils_1.02.02.bb| 3 +++
> > >  recipes-ti/dmai/ti-dmai_svn.bb | 3 +++
> > >  recipes-ti/dsplib/dsplib.inc   | 2 ++
> > >  recipes-ti/hdvpss/ti-hdvpss_01.00.01.27.bb | 2 ++
> > >  recipes-ti/includes/ti-unpack.inc  | 5 +
> > >  recipes-ti/ipc/ti-ipc-common.inc   | 2 ++
> > >  recipes-ti/linuxutils/ti-linuxutils_2.26.01.02.bb  | 3 +++
> > >  recipes-ti/mathlib/mathlib.inc | 2 ++
> > >  recipes-ti/ndk/ti-ndk_3.40.01.01.bb| 3 +++
> > >  recipes-ti/swtools/swtools_git.bb  | 2 ++
> > >  17 files changed, 46 insertions(+)
> > >
> > > diff --git a/recipes-bsp/cuia/cuia_1.0.0.13.bb b/recipes-bsp/cuia/
> > cuia_1.0.0.13.bb
> > > index e048f6aa..a7caf504 100644
> > > --- a/recipes-bsp/cuia/cuia_1.0.0.13.bb
> > > +++ b/recipes-bsp/cuia/cuia_1.0.0.13.bb
> > > @@ -23,3 +23,6 @@ do_install() {
> > >   cd ${S}
> > >   oe_runmake DESTDIR=${D} libdir=${libdir} includedir=${includedir}
> > install
> > >  }
> > > +
> > > +COMPATIBLE_HOST ?= "null"
> > > +COMPATIBLE_HOST_ti-soc = "(.*)"
> > > diff --git a/recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb
> > b/recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb
> > > index 94485b6a..d29b6496 100644
> > > --- a/recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb
> > > +++ b/recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb
> > > @@ -22,3 +22,6 @@ do_install() {
> > >  install -d ${D}/${base_libdir}/modules/${KERNEL_VERSION}/extra
> > >  install -m 644 ${S}/galcore.ko
> > ${D}/${base_libdir}/modules/${KERNEL_VERSION}/extra
> > >  }
> > > +
> > > +COMPATIBLE_HOST ?= "null"
> > > +COMPATIBLE_HOST_ti-soc = "(.*)"
> > > diff --git a/recipes-bsp/x-load/x-load_git.bb b/recipes-bsp/x-load/
> > x-load_git.bb
> > > index dd8bce2d..1ce1b0f0 100644
> > > --- a/recipes-bsp/x-load/x-load_git.bb
> > > +++ b/recipes-bsp/x-load/x-load_git.bb
> > > @@ -17,3 +17,6 @@ CONFIG_HEADER_beagleboard = "1"
> > >  XLOAD_MACHINE_omap3-touchbook = "omap3530beagle_config"
> > >
> > >  PACKAGE_ARCH = "${MACHINE_ARCH}"
> > > +
> > > +COMPATIBLE_HOST ?= "null"
> > > +COMPATIBLE_HOST_ti-soc = "(.*)"
> > > diff --git a/recipes-graphics/gbm/libgbm_10.0.0.bb
> > b/recipes-graphics/gbm/libgbm_10.0.0.bb
> > > index 38715ccf..9e3c7ed0 100644
> > > --- a/recipes-graphics/gbm/libgbm_10.0.0.bb
> > > +++ b/recipes-graphics/gbm/libgbm_10.0.0.bb
> > > @@ -16,3 +16,6 @@ SRC_URI = "git://
> > git.ti.com/glsdk/libgbm.git;protocol=git;branch=${BRANCH}
> > <http://git.ti.com/glsdk/libgbm.git;protocol=git;branch=$%7BBRANCH%7D> \
> > >
> > file://0001-gbm.c-include-sys-sysmacros.h-for-minor-major-in-new.patch"
> > >
> > >  S = "${WORKDIR}/git"
> > > +
> > > +COMPATIBLE_HOST ?= "null"
> > > +COMPATIBLE_HOST_ti-soc = "(.*)"
> > > diff --git a/recipes-graphics/libgal/ti-gc320-libs_5.0.11.p7.bb
> > b/recipes-graphics/libgal/ti-gc320-libs_5.0.11.p7.bb
> > > index dafaac1e..a2f8f192 100644
> > > --- a/recipes-graphics/li

Re: [meta-ti] [PATCH] recipes: Limit ti specific recipes under ti-soc override

[Denys Dmytriyenko]

Does this make packages machine-specific?

On Tue, Oct 09, 2018 at 01:45:03PM -0700, Khem Raj wrote:
> This helps in multi-BSP scenario, where other BSP layers are also
> present in the layermix
> 
> Signed-off-by: Khem Raj 
> ---
>  recipes-bsp/cuia/cuia_1.0.0.13.bb  | 3 +++
>  recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb | 3 +++
>  recipes-bsp/x-load/x-load_git.bb   | 3 +++
>  recipes-graphics/gbm/libgbm_10.0.0.bb  | 3 +++
>  recipes-graphics/libgal/ti-gc320-libs_5.0.11.p7.bb | 3 +++
>  recipes-graphics/omapfbplay/omapfbplay.inc | 2 ++
>  recipes-multimedia/libdce/libdce_3.00.14.00.bb | 2 ++
>  recipes-ti/bios/ti-biosutils_1.02.02.bb| 3 +++
>  recipes-ti/dmai/ti-dmai_svn.bb | 3 +++
>  recipes-ti/dsplib/dsplib.inc   | 2 ++
>  recipes-ti/hdvpss/ti-hdvpss_01.00.01.27.bb | 2 ++
>  recipes-ti/includes/ti-unpack.inc  | 5 +
>  recipes-ti/ipc/ti-ipc-common.inc   | 2 ++
>  recipes-ti/linuxutils/ti-linuxutils_2.26.01.02.bb  | 3 +++
>  recipes-ti/mathlib/mathlib.inc | 2 ++
>  recipes-ti/ndk/ti-ndk_3.40.01.01.bb| 3 +++
>  recipes-ti/swtools/swtools_git.bb  | 2 ++
>  17 files changed, 46 insertions(+)
> 
> diff --git a/recipes-bsp/cuia/cuia_1.0.0.13.bb 
> b/recipes-bsp/cuia/cuia_1.0.0.13.bb
> index e048f6aa..a7caf504 100644
> --- a/recipes-bsp/cuia/cuia_1.0.0.13.bb
> +++ b/recipes-bsp/cuia/cuia_1.0.0.13.bb
> @@ -23,3 +23,6 @@ do_install() {
>   cd ${S}
>   oe_runmake DESTDIR=${D} libdir=${libdir} includedir=${includedir} 
> install
>  }
> +
> +COMPATIBLE_HOST ?= "null"
> +COMPATIBLE_HOST_ti-soc = "(.*)"
> diff --git a/recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb 
> b/recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb
> index 94485b6a..d29b6496 100644
> --- a/recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb
> +++ b/recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb
> @@ -22,3 +22,6 @@ do_install() {
>  install -d ${D}/${base_libdir}/modules/${KERNEL_VERSION}/extra
>  install -m 644 ${S}/galcore.ko 
> ${D}/${base_libdir}/modules/${KERNEL_VERSION}/extra
>  }
> +
> +COMPATIBLE_HOST ?= "null"
> +COMPATIBLE_HOST_ti-soc = "(.*)"
> diff --git a/recipes-bsp/x-load/x-load_git.bb 
> b/recipes-bsp/x-load/x-load_git.bb
> index dd8bce2d..1ce1b0f0 100644
> --- a/recipes-bsp/x-load/x-load_git.bb
> +++ b/recipes-bsp/x-load/x-load_git.bb
> @@ -17,3 +17,6 @@ CONFIG_HEADER_beagleboard = "1"
>  XLOAD_MACHINE_omap3-touchbook = "omap3530beagle_config"
>  
>  PACKAGE_ARCH = "${MACHINE_ARCH}"
> +
> +COMPATIBLE_HOST ?= "null"
> +COMPATIBLE_HOST_ti-soc = "(.*)"
> diff --git a/recipes-graphics/gbm/libgbm_10.0.0.bb 
> b/recipes-graphics/gbm/libgbm_10.0.0.bb
> index 38715ccf..9e3c7ed0 100644
> --- a/recipes-graphics/gbm/libgbm_10.0.0.bb
> +++ b/recipes-graphics/gbm/libgbm_10.0.0.bb
> @@ -16,3 +16,6 @@ SRC_URI = 
> "git://git.ti.com/glsdk/libgbm.git;protocol=git;branch=${BRANCH} \
>  
> file://0001-gbm.c-include-sys-sysmacros.h-for-minor-major-in-new.patch"
>  
>  S = "${WORKDIR}/git"
> +
> +COMPATIBLE_HOST ?= "null"
> +COMPATIBLE_HOST_ti-soc = "(.*)"
> diff --git a/recipes-graphics/libgal/ti-gc320-libs_5.0.11.p7.bb 
> b/recipes-graphics/libgal/ti-gc320-libs_5.0.11.p7.bb
> index dafaac1e..a2f8f192 100644
> --- a/recipes-graphics/libgal/ti-gc320-libs_5.0.11.p7.bb
> +++ b/recipes-graphics/libgal/ti-gc320-libs_5.0.11.p7.bb
> @@ -37,3 +37,6 @@ do_install() {
>  }
>  
>  INSANE_SKIP_${PN} += "ldflags"
> +
> +COMPATIBLE_HOST ?= "null"
> +COMPATIBLE_HOST_ti-soc = "(.*)"
> diff --git a/recipes-graphics/omapfbplay/omapfbplay.inc 
> b/recipes-graphics/omapfbplay/omapfbplay.inc
> index df166dd3..744eb8f7 100644
> --- a/recipes-graphics/omapfbplay/omapfbplay.inc
> +++ b/recipes-graphics/omapfbplay/omapfbplay.inc
> @@ -14,6 +14,8 @@ SRC_URI = "git://git.mansr.com/omapfbplay;protocol=git \
>  S = "${WORKDIR}/git"
>  
>  PACKAGE_ARCH = "${MACHINE_ARCH}"
> +COMPATIBLE_HOST ?= "null"
> +COMPATIBLE_HOST_ti-soc = "(.*)"
>  
>  # We want a kernel header for armv7a, but we don't want to make mplayer 
> machine specific for that
>  STAGING_KERNEL_DIR = 
> "${STAGING_DIR}/${MACHINE_ARCH}${TARGET_VENDOR}-${TARGET_OS}/kernel"
> diff --git a/recipes-multimedia/libdce/libdce_3.00.14.00.bb 
> b/recipes-multimedia/libdce/libdce_3.00.14.00.bb
> index 04c0b718..0deec7ab 100644
> --- a/recipes-multimedia/libdce/libdce_3.00.14.00.bb
> +++ b/recipes-multimedia/libdce/libdce_3.00.14.00.bb
> @@ -13,3 +13,5 @@ PR = "r1"
>  
>  S = "${WORKDIR}/git"
>  EXTRA_OECONF += "IPC_HEADERS=${STAGING_INCDIR}/ti/ipc/mm"
> +COMPATIBLE_HOST ?= "null"
> +COMPATIBLE_HOST_ti-soc = "(.*)"
> diff --git a/recipes-ti/bios/ti-biosutils_1.02.02.bb 
> b/recipes-ti/bios/ti-biosutils_1.02.02.bb
> index 5b6b4f43..01c070d7 100644
> --- a/recipes-ti/bios/ti-biosutils_1.02.02.bb
> +++ b/rec

Re: [meta-ti] [ti2018.03/rocko/master][PATCH] ti-cgt-arm: prevent build of existing library

[Denys Dmytriyenko]

On Wed, Oct 03, 2018 at 01:29:45PM -0400, Jacob Stiffler wrote:
> 
> On 10/3/2018 1:17 PM, Denys Dmytriyenko wrote:
> >On Tue, Oct 02, 2018 at 03:19:00PM -0400, Jacob Stiffler wrote:
> >>On 10/2/2018 3:17 PM, Denys Dmytriyenko wrote:
> >>>I believe this mklib call was added recently due to a race condition and it
> >>>was not built before it was needed - any chance to fix the race properly
> >>>instead of all the workarounds?
> >>
> >>Not sure about fixing the race, but I just found out that there are plans to
> >>have that library available in the default package.
> >So, in the meantime, do we need to merge this workaround?
> 
> 
> Yes. This will fix the failure when do_compile is re-run on existing
> sources.
> 
> 
> Now I think it makes more sense to try to remove the library in
> do_configure, similar to how base.bbclass calls "make clean" if the state of
> the dependencies change.

Sounds good, let's "clean" the library before rebuild.


> >>>On Tue, Oct 02, 2018 at 02:38:00PM -0400, Jacob Stiffler wrote:
> >>>>On 10/2/2018 8:29 AM, Jacob Stiffler wrote:
> >>>>>I recently ran into this error, so I sent this out in a hurry to get it
> >>>>>fixed. But now I am thinking that it may be better to remove this library
> >>>>>in do_configure, similar to base class calls make clean
> >>>>>
> >>>>After thinking about it some more, I would prefer to remove the library in
> >>>>do_configure() to be safe in the unlikely scenario that there are
> >>>>dependencies involved.
> >>>>
> >>>>
> >>>>As it is now, this is hardcoded to a single library. While I am making
> >>>>changes, should I enhance this to take a list of libraries so that it can 
> >>>>be
> >>>>easily extended in the future?
> >>>>
> >>>>
> >>>>>Any suggestions?
> >>>>>
> >>>>>
> >>>>>Thanks,
> >>>>>
> >>>>>Jake
> >>>>>
> >>>>>On 10/2/2018 7:36 AM, Jacob Stiffler wrote:
> >>>>>>* Prevent a potential error as mklib will return an error if the
> >>>>>>   library already exists.
> >>>>>>* The error encountered is the following:
> >>>>>>
> >>>>>>| >> ERROR: mklib: destination library 
> >>>>>>.../work/x86_64-linux/ti-cgt-arm-native/16.9.2-r1/ti-cgt-arm-16.9.2/ti-cgt-arm_16.9.2.LTS/lib/rtsv7R4_A_le_v3D16_eabi.lib
> >>>>>> already exists
> >>>>>>| WARNING: 
> >>>>>>.../work/x86_64-linux/ti-cgt-arm-native/16.9.2-r1/temp/run.do_compile.13758:1
> >>>>>> exit 1 from 'lib/mklib --pattern=rtsv7R4_A_le_v3D16_eabi.lib'
> >>>>>>
> >>>>>>Signed-off-by: Jacob Stiffler
> >>>>>>---
> >>>>>>  recipes-ti/devtools/ti-cgt-arm.inc | 10 +++---
> >>>>>>  1 file changed, 7 insertions(+), 3 deletions(-)
> >>>>>>
> >>>>>>diff --git a/recipes-ti/devtools/ti-cgt-arm.inc 
> >>>>>>b/recipes-ti/devtools/ti-cgt-arm.inc
> >>>>>>index b9f7566..e83973b 100644
> >>>>>>--- a/recipes-ti/devtools/ti-cgt-arm.inc
> >>>>>>+++ b/recipes-ti/devtools/ti-cgt-arm.inc
> >>>>>>@@ -9,7 +9,7 @@ require recipes-ti/includes/ti-paths.inc
> >>>>>>  S = "${WORKDIR}/ti-cgt-arm-${PV}"
> >>>>>>-PR = "r1"
> >>>>>>+PR = "r2"
> >>>>>>  SRC_URI 
> >>>>>> ="http://software-dl.ti.com/codegen/esd/cgt_public_sw/TMS470/${PV}.LTS/${BINFILE};name=${BINFILE_NAME}";
> >>>>>>@@ -19,8 +19,12 @@ TI_BIN_UNPK_CMDS = ""
> >>>>>>  do_compile_append() {
> >>>>>>  cd ${S}/ti-cgt-arm_${PV}.LTS
> >>>>>>-export PATH=${PATH}:${S}/ti-cgt-arm_${PV}.LTS/bin
> >>>>>>-lib/mklib --pattern=rtsv7R4_A_le_v3D16_eabi.lib
> >>>>>>+
> >>>>>>+if [ ! -f "./lib/rtsv7R4_A_le_v3D16_eabi.lib" ]
> >>>>>>+then
> >>>>>>+export PATH=${PATH}:${S}/ti-cgt-arm_${PV}.LTS/bin
> >>>>>>+lib/mklib --pattern=rtsv7R4_A_le_v3D16_eabi.lib
> >>>>>>+fi
> >>>>>>  }
> >>>>>>  do_install() {
> >>>>-- 
> >>>>___
> >>>>meta-ti mailing list
> >>>>meta-ti@yoctoproject.org
> >>>>https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [ti2018.03/rocko/master][PATCH] ti-cgt-arm: prevent build of existing library

[Denys Dmytriyenko]

On Tue, Oct 02, 2018 at 03:19:00PM -0400, Jacob Stiffler wrote:
> 
> On 10/2/2018 3:17 PM, Denys Dmytriyenko wrote:
> >I believe this mklib call was added recently due to a race condition and it
> >was not built before it was needed - any chance to fix the race properly
> >instead of all the workarounds?
> 
> 
> Not sure about fixing the race, but I just found out that there are plans to
> have that library available in the default package.

So, in the meantime, do we need to merge this workaround?


> >On Tue, Oct 02, 2018 at 02:38:00PM -0400, Jacob Stiffler wrote:
> >>On 10/2/2018 8:29 AM, Jacob Stiffler wrote:
> >>>I recently ran into this error, so I sent this out in a hurry to get it
> >>>fixed. But now I am thinking that it may be better to remove this library
> >>>in do_configure, similar to base class calls make clean
> >>>
> >>After thinking about it some more, I would prefer to remove the library in
> >>do_configure() to be safe in the unlikely scenario that there are
> >>dependencies involved.
> >>
> >>
> >>As it is now, this is hardcoded to a single library. While I am making
> >>changes, should I enhance this to take a list of libraries so that it can be
> >>easily extended in the future?
> >>
> >>
> >>>Any suggestions?
> >>>
> >>>
> >>>Thanks,
> >>>
> >>>Jake
> >>>
> >>>On 10/2/2018 7:36 AM, Jacob Stiffler wrote:
> >>>>* Prevent a potential error as mklib will return an error if the
> >>>>   library already exists.
> >>>>* The error encountered is the following:
> >>>>
> >>>>| >> ERROR: mklib: destination library 
> >>>>.../work/x86_64-linux/ti-cgt-arm-native/16.9.2-r1/ti-cgt-arm-16.9.2/ti-cgt-arm_16.9.2.LTS/lib/rtsv7R4_A_le_v3D16_eabi.lib
> >>>> already exists
> >>>>| WARNING: 
> >>>>.../work/x86_64-linux/ti-cgt-arm-native/16.9.2-r1/temp/run.do_compile.13758:1
> >>>> exit 1 from 'lib/mklib --pattern=rtsv7R4_A_le_v3D16_eabi.lib'
> >>>>
> >>>>Signed-off-by: Jacob Stiffler
> >>>>---
> >>>>  recipes-ti/devtools/ti-cgt-arm.inc | 10 +++---
> >>>>  1 file changed, 7 insertions(+), 3 deletions(-)
> >>>>
> >>>>diff --git a/recipes-ti/devtools/ti-cgt-arm.inc 
> >>>>b/recipes-ti/devtools/ti-cgt-arm.inc
> >>>>index b9f7566..e83973b 100644
> >>>>--- a/recipes-ti/devtools/ti-cgt-arm.inc
> >>>>+++ b/recipes-ti/devtools/ti-cgt-arm.inc
> >>>>@@ -9,7 +9,7 @@ require recipes-ti/includes/ti-paths.inc
> >>>>  S = "${WORKDIR}/ti-cgt-arm-${PV}"
> >>>>-PR = "r1"
> >>>>+PR = "r2"
> >>>>  SRC_URI 
> >>>> ="http://software-dl.ti.com/codegen/esd/cgt_public_sw/TMS470/${PV}.LTS/${BINFILE};name=${BINFILE_NAME}";
> >>>>@@ -19,8 +19,12 @@ TI_BIN_UNPK_CMDS = ""
> >>>>  do_compile_append() {
> >>>>  cd ${S}/ti-cgt-arm_${PV}.LTS
> >>>>-export PATH=${PATH}:${S}/ti-cgt-arm_${PV}.LTS/bin
> >>>>-lib/mklib --pattern=rtsv7R4_A_le_v3D16_eabi.lib
> >>>>+
> >>>>+if [ ! -f "./lib/rtsv7R4_A_le_v3D16_eabi.lib" ]
> >>>>+then
> >>>>+export PATH=${PATH}:${S}/ti-cgt-arm_${PV}.LTS/bin
> >>>>+lib/mklib --pattern=rtsv7R4_A_le_v3D16_eabi.lib
> >>>>+fi
> >>>>  }
> >>>>  do_install() {
> >>-- 
> >>___
> >>meta-ti mailing list
> >>meta-ti@yoctoproject.org
> >>https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

[meta-ti] [rocko/master][PATCH] linux-ti-staging: update with K3 boot lockup fix

[Denys Dmytriyenko]

Signed-off-by: Denys Dmytriyenko 
---
 recipes-kernel/linux/linux-ti-staging-rt_4.14.bb | 2 +-
 recipes-kernel/linux/linux-ti-staging_4.14.bb| 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/recipes-kernel/linux/linux-ti-staging-rt_4.14.bb 
b/recipes-kernel/linux/linux-ti-staging-rt_4.14.bb
index a638772a..2c685fc8 100644
--- a/recipes-kernel/linux/linux-ti-staging-rt_4.14.bb
+++ b/recipes-kernel/linux/linux-ti-staging-rt_4.14.bb
@@ -6,5 +6,5 @@ FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-4.14:"
 
 BRANCH = "ti-rt-linux-4.14.y"
 
-SRCREV = "a6b7e0608adb4e4b2fab789bcf85cedfb7129bc6"
+SRCREV = "a98caa023bd8a22df170c9f6286da56aa94d876d"
 PV = "4.14.71+git${SRCPV}"
diff --git a/recipes-kernel/linux/linux-ti-staging_4.14.bb 
b/recipes-kernel/linux/linux-ti-staging_4.14.bb
index 89fb7e73..2ad19f5c 100644
--- a/recipes-kernel/linux/linux-ti-staging_4.14.bb
+++ b/recipes-kernel/linux/linux-ti-staging_4.14.bb
@@ -55,8 +55,8 @@ S = "${WORKDIR}/git"
 
 BRANCH = "ti-lsk-linux-4.14.y"
 
-SRCREV = "6b9a910162e783108031f976d930cc3f1da72c8a"
-PV = "4.14.71+git${SRCPV}"
+SRCREV = "acb86730297664e233528e5da192b7154a6ad1b4"
+PV = "4.14.73+git${SRCPV}"
 
 # Append to the MACHINE_KERNEL_PR so that a new SRCREV will cause a rebuild
 MACHINE_KERNEL_PR_append = "a"
-- 
2.17.1

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [ti2018.03/rocko/master][PATCH] ti-cgt-arm: prevent build of existing library

[Denys Dmytriyenko]

I believe this mklib call was added recently due to a race condition and it 
was not built before it was needed - any chance to fix the race properly 
instead of all the workarounds?


On Tue, Oct 02, 2018 at 02:38:00PM -0400, Jacob Stiffler wrote:
> 
> On 10/2/2018 8:29 AM, Jacob Stiffler wrote:
> >
> >I recently ran into this error, so I sent this out in a hurry to get it
> >fixed. But now I am thinking that it may be better to remove this library
> >in do_configure, similar to base class calls make clean
> >
> 
> After thinking about it some more, I would prefer to remove the library in
> do_configure() to be safe in the unlikely scenario that there are
> dependencies involved.
> 
> 
> As it is now, this is hardcoded to a single library. While I am making
> changes, should I enhance this to take a list of libraries so that it can be
> easily extended in the future?
> 
> 
> >Any suggestions?
> >
> >
> >Thanks,
> >
> >Jake
> >
> >On 10/2/2018 7:36 AM, Jacob Stiffler wrote:
> >>* Prevent a potential error as mklib will return an error if the
> >>   library already exists.
> >>* The error encountered is the following:
> >>
> >>| >> ERROR: mklib: destination library 
> >>.../work/x86_64-linux/ti-cgt-arm-native/16.9.2-r1/ti-cgt-arm-16.9.2/ti-cgt-arm_16.9.2.LTS/lib/rtsv7R4_A_le_v3D16_eabi.lib
> >> already exists
> >>| WARNING: 
> >>.../work/x86_64-linux/ti-cgt-arm-native/16.9.2-r1/temp/run.do_compile.13758:1
> >> exit 1 from 'lib/mklib --pattern=rtsv7R4_A_le_v3D16_eabi.lib'
> >>
> >>Signed-off-by: Jacob Stiffler
> >>---
> >>  recipes-ti/devtools/ti-cgt-arm.inc | 10 +++---
> >>  1 file changed, 7 insertions(+), 3 deletions(-)
> >>
> >>diff --git a/recipes-ti/devtools/ti-cgt-arm.inc 
> >>b/recipes-ti/devtools/ti-cgt-arm.inc
> >>index b9f7566..e83973b 100644
> >>--- a/recipes-ti/devtools/ti-cgt-arm.inc
> >>+++ b/recipes-ti/devtools/ti-cgt-arm.inc
> >>@@ -9,7 +9,7 @@ require recipes-ti/includes/ti-paths.inc
> >>  S = "${WORKDIR}/ti-cgt-arm-${PV}"
> >>-PR = "r1"
> >>+PR = "r2"
> >>  SRC_URI 
> >> ="http://software-dl.ti.com/codegen/esd/cgt_public_sw/TMS470/${PV}.LTS/${BINFILE};name=${BINFILE_NAME}";
> >>@@ -19,8 +19,12 @@ TI_BIN_UNPK_CMDS = ""
> >>  do_compile_append() {
> >>  cd ${S}/ti-cgt-arm_${PV}.LTS
> >>-export PATH=${PATH}:${S}/ti-cgt-arm_${PV}.LTS/bin
> >>-lib/mklib --pattern=rtsv7R4_A_le_v3D16_eabi.lib
> >>+
> >>+if [ ! -f "./lib/rtsv7R4_A_le_v3D16_eabi.lib" ]
> >>+then
> >>+export PATH=${PATH}:${S}/ti-cgt-arm_${PV}.LTS/bin
> >>+lib/mklib --pattern=rtsv7R4_A_le_v3D16_eabi.lib
> >>+fi
> >>  }
> >>  do_install() {

> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

[meta-ti] [rocko/master][PATCH] am65xx-evm: update DTBOs

[Denys Dmytriyenko]

Signed-off-by: Denys Dmytriyenko 
---
 conf/machine/am65xx-evm.conf | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/conf/machine/am65xx-evm.conf b/conf/machine/am65xx-evm.conf
index 82ee02c1..4bf8993e 100644
--- a/conf/machine/am65xx-evm.conf
+++ b/conf/machine/am65xx-evm.conf
@@ -13,7 +13,8 @@ SERIAL_CONSOLE = "115200 ttyS2"
 KERNEL_DEVICETREE = " \
 ti/k3-am654-base-board.dtb \
 ti/k3-am654-evm-csi2-ov490.dtbo ti/k3-am654-evm-oldi-lcd1evm.dtbo \
-ti/k3-am654-idk.dtbo ti/k3-am654-pcie-usb2.dtbo ti/k3-am654-pcie-usb3.dtbo"
+ti/k3-am654-gp.dtbo ti/k3-am654-idk.dtbo \
+ti/k3-am654-pcie-usb2.dtbo ti/k3-am654-pcie-usb3.dtbo"
 
 UBOOT_MACHINE = "am65x_evm_a53_defconfig"
 
-- 
2.17.1

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

[meta-ti] [rocko/master][PATCH v2] u-boot-ti-staging: update to version with separated SYSFW

[Denys Dmytriyenko]

Signed-off-by: Denys Dmytriyenko 
---
v2 - use official release branch

 recipes-bsp/u-boot/u-boot-ti-staging_2018.01.bb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/recipes-bsp/u-boot/u-boot-ti-staging_2018.01.bb 
b/recipes-bsp/u-boot/u-boot-ti-staging_2018.01.bb
index 98e9a7d0..54ede901 100644
--- a/recipes-bsp/u-boot/u-boot-ti-staging_2018.01.bb
+++ b/recipes-bsp/u-boot/u-boot-ti-staging_2018.01.bb
@@ -1,7 +1,7 @@
 require u-boot-ti.inc
 
-PR = "r21"
+PR = "r22"
 
 BRANCH = "ti-u-boot-2018.01"
 
-SRCREV = "9b8c6b92b7cbbbe027cf73743686de46d1f1574b"
+SRCREV = "81382d1d66dfbe11f7bd8a0df95519812049b26f"
-- 
2.17.1

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [PATCH] dsplib/mathlib: remove .metadata folder from packages

[Denys Dmytriyenko]

On Fri, Sep 28, 2018 at 01:38:13PM -0400, Xu, Jianzhong wrote:
> -Original Message-
> From: Dmytriyenko, Denys 
> Sent: Friday, September 28, 2018 1:32 PM
> To: Xu, Jianzhong
> Cc: meta-ti@yoctoproject.org
> Subject: Re: [meta-ti] [PATCH] dsplib/mathlib: remove .metadata folder from 
> packages
> 
> On Fri, Sep 28, 2018 at 01:25:48PM -0400, Jianzhong Xu wrote:
> > dsplib/mathlib: remove .metadata folder from dsplib and mathlib packages
> 
> The log says "remove", but that's not what the code does, it seems...
> 
> - Yeah. Maybe "don't add .metadata to packages" is better. Should I resend 
> the patch?

Ok, do not install/deploy .metadata would be clearer.


> > Remove .metadata folder from dsplib and mathlib packages.
> > This folder prevents CCS from finding and installing dsplib and mathlib.
> > 
> > Signed-off-by: Jianzhong Xu 
> > ---
> >  recipes-ti/dsplib/dsplib.inc   | 2 --
> >  recipes-ti/mathlib/mathlib.inc | 2 --
> >  2 files changed, 4 deletions(-)
> > 
> > diff --git a/recipes-ti/dsplib/dsplib.inc b/recipes-ti/dsplib/dsplib.inc
> > index 7180c4a..f369679 100644
> > --- a/recipes-ti/dsplib/dsplib.inc
> > +++ b/recipes-ti/dsplib/dsplib.inc
> > @@ -49,7 +49,6 @@ do_install() {
> >  
> > find -name "${DSPLIB_PACKAGE_NAME}.zip" -exec unzip -o {} -d 
> > ${D}${DSPLIB_INSTALL_DIR_RECIPE} \;
> > mv ${D}${DSPLIB_INSTALL_DIR_RECIPE}/dsplib/* 
> > ${D}${DSPLIB_INSTALL_DIR_RECIPE}
> > -   mv ${D}${DSPLIB_INSTALL_DIR_RECIPE}/dsplib/.metadata 
> > ${D}${DSPLIB_INSTALL_DIR_RECIPE}
> > rm -r ${D}${DSPLIB_INSTALL_DIR_RECIPE}/dsplib
> >  }
> >  
> > @@ -62,7 +61,6 @@ do_deploy() {
> > # and place the zip file in ${DEPLOYDIR}
> > mkdir ./${DSPLIB_PACKAGE_NAME}
> > cp -r ${D}${DSPLIB_INSTALL_DIR_RECIPE}/* ./${DSPLIB_PACKAGE_NAME}
> > -   cp -r ${D}${DSPLIB_INSTALL_DIR_RECIPE}/.metadata 
> > ./${DSPLIB_PACKAGE_NAME}
> > zip -9 -y -r -q ${DEPLOYDIR}/${DSPLIB_PACKAGE_NAME}.zip 
> > ./${DSPLIB_PACKAGE_NAME}
> > rm -r ./${DSPLIB_PACKAGE_NAME}
> >  }
> > diff --git a/recipes-ti/mathlib/mathlib.inc b/recipes-ti/mathlib/mathlib.inc
> > index 3e981e4..6aea085 100644
> > --- a/recipes-ti/mathlib/mathlib.inc
> > +++ b/recipes-ti/mathlib/mathlib.inc
> > @@ -48,7 +48,6 @@ do_install() {
> >  
> > find -name "${MATHLIB_PACKAGE_NAME}.zip" -exec unzip -o {} -d 
> > ${D}${MATHLIB_INSTALL_DIR_RECIPE} \;
> > mv ${D}${MATHLIB_INSTALL_DIR_RECIPE}/mathlib/* 
> > ${D}${MATHLIB_INSTALL_DIR_RECIPE}
> > -   mv ${D}${MATHLIB_INSTALL_DIR_RECIPE}/mathlib/.metadata 
> > ${D}${MATHLIB_INSTALL_DIR_RECIPE}
> > rm -r ${D}${MATHLIB_INSTALL_DIR_RECIPE}/mathlib
> >  }
> >  
> > @@ -61,7 +60,6 @@ do_deploy() {
> > # and place the zip file in ${DEPLOYDIR}
> > mkdir ./${MATHLIB_PACKAGE_NAME}
> > cp -r ${D}${MATHLIB_INSTALL_DIR_RECIPE}/* ./${MATHLIB_PACKAGE_NAME}
> > -   cp -r ${D}${MATHLIB_INSTALL_DIR_RECIPE}/.metadata 
> > ./${MATHLIB_PACKAGE_NAME}
> > zip -9 -y -r -q ${DEPLOYDIR}/${MATHLIB_PACKAGE_NAME}.zip 
> > ./${MATHLIB_PACKAGE_NAME}
> > rm -r ./${MATHLIB_PACKAGE_NAME}
> >  }
> > -- 
> > 1.9.1
> > 
> > -- 
> > ___
> > meta-ti mailing list
> > meta-ti@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [PATCH] dsplib/mathlib: remove .metadata folder from packages

[Denys Dmytriyenko]

On Fri, Sep 28, 2018 at 01:25:48PM -0400, Jianzhong Xu wrote:
> dsplib/mathlib: remove .metadata folder from dsplib and mathlib packages

The log says "remove", but that's not what the code does, it seems...


> Remove .metadata folder from dsplib and mathlib packages.
> This folder prevents CCS from finding and installing dsplib and mathlib.
> 
> Signed-off-by: Jianzhong Xu 
> ---
>  recipes-ti/dsplib/dsplib.inc   | 2 --
>  recipes-ti/mathlib/mathlib.inc | 2 --
>  2 files changed, 4 deletions(-)
> 
> diff --git a/recipes-ti/dsplib/dsplib.inc b/recipes-ti/dsplib/dsplib.inc
> index 7180c4a..f369679 100644
> --- a/recipes-ti/dsplib/dsplib.inc
> +++ b/recipes-ti/dsplib/dsplib.inc
> @@ -49,7 +49,6 @@ do_install() {
>  
>   find -name "${DSPLIB_PACKAGE_NAME}.zip" -exec unzip -o {} -d 
> ${D}${DSPLIB_INSTALL_DIR_RECIPE} \;
>   mv ${D}${DSPLIB_INSTALL_DIR_RECIPE}/dsplib/* 
> ${D}${DSPLIB_INSTALL_DIR_RECIPE}
> - mv ${D}${DSPLIB_INSTALL_DIR_RECIPE}/dsplib/.metadata 
> ${D}${DSPLIB_INSTALL_DIR_RECIPE}
>   rm -r ${D}${DSPLIB_INSTALL_DIR_RECIPE}/dsplib
>  }
>  
> @@ -62,7 +61,6 @@ do_deploy() {
>   # and place the zip file in ${DEPLOYDIR}
>   mkdir ./${DSPLIB_PACKAGE_NAME}
>   cp -r ${D}${DSPLIB_INSTALL_DIR_RECIPE}/* ./${DSPLIB_PACKAGE_NAME}
> - cp -r ${D}${DSPLIB_INSTALL_DIR_RECIPE}/.metadata 
> ./${DSPLIB_PACKAGE_NAME}
>   zip -9 -y -r -q ${DEPLOYDIR}/${DSPLIB_PACKAGE_NAME}.zip 
> ./${DSPLIB_PACKAGE_NAME}
>   rm -r ./${DSPLIB_PACKAGE_NAME}
>  }
> diff --git a/recipes-ti/mathlib/mathlib.inc b/recipes-ti/mathlib/mathlib.inc
> index 3e981e4..6aea085 100644
> --- a/recipes-ti/mathlib/mathlib.inc
> +++ b/recipes-ti/mathlib/mathlib.inc
> @@ -48,7 +48,6 @@ do_install() {
>  
>   find -name "${MATHLIB_PACKAGE_NAME}.zip" -exec unzip -o {} -d 
> ${D}${MATHLIB_INSTALL_DIR_RECIPE} \;
>   mv ${D}${MATHLIB_INSTALL_DIR_RECIPE}/mathlib/* 
> ${D}${MATHLIB_INSTALL_DIR_RECIPE}
> - mv ${D}${MATHLIB_INSTALL_DIR_RECIPE}/mathlib/.metadata 
> ${D}${MATHLIB_INSTALL_DIR_RECIPE}
>   rm -r ${D}${MATHLIB_INSTALL_DIR_RECIPE}/mathlib
>  }
>  
> @@ -61,7 +60,6 @@ do_deploy() {
>   # and place the zip file in ${DEPLOYDIR}
>   mkdir ./${MATHLIB_PACKAGE_NAME}
>   cp -r ${D}${MATHLIB_INSTALL_DIR_RECIPE}/* ./${MATHLIB_PACKAGE_NAME}
> - cp -r ${D}${MATHLIB_INSTALL_DIR_RECIPE}/.metadata 
> ./${MATHLIB_PACKAGE_NAME}
>   zip -9 -y -r -q ${DEPLOYDIR}/${MATHLIB_PACKAGE_NAME}.zip 
> ./${MATHLIB_PACKAGE_NAME}
>   rm -r ./${MATHLIB_PACKAGE_NAME}
>  }
> -- 
> 1.9.1
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [rocko/master][PATCH v2 01/30] ti-pdk-bbclass: Checking for doxygen support in the correct manner

[Denys Dmytriyenko]

On Fri, Sep 28, 2018 at 10:22:31AM -0400, Radhakrishnan, Mahesh wrote:
> 
> 
> -Original Message-
> From: Dmytriyenko, Denys 
> Sent: Thursday, September 27, 2018 5:37 PM
> To: Radhakrishnan, Mahesh
> Cc: meta-ti@yoctoproject.org
> Subject: Re: [meta-ti] [rocko/master][PATCH v2 01/30] ti-pdk-bbclass: 
> Checking for doxygen support in the correct manner
> 
> On Thu, Sep 27, 2018 at 04:43:00PM -0400, Mahesh Radhakrishnan wrote:
> > Signed-off-by: Mahesh Radhakrishnan 
> > ---
> >  classes/ti-pdk.bbclass | 6 +++---
> >  1 file changed, 3 insertions(+), 3 deletions(-)
> > 
> > diff --git a/classes/ti-pdk.bbclass b/classes/ti-pdk.bbclass
> > index 0716074..f59969f 100644
> > --- a/classes/ti-pdk.bbclass
> > +++ b/classes/ti-pdk.bbclass
> > @@ -9,8 +9,8 @@ DEPENDS_append_omap-a15 = " ti-cgt-arm-native"
> >  DEPENDS_remove_ti33x = "ti-cgt6x-native"
> >  DEPENDS_remove_ti43x = "ti-cgt6x-native"
> >  DEPENDS_append_omapl1 = " ti-cgt-arm-native"
> > -DEPENDS_remove_am65xx-evm = "gcc-arm-none-eabi-native ti-cgt6x-native"
> > -DEPENDS_append_am65xx-evm = " ti-cgt-arm-native 
> > gcc-linaro-baremetal-aarch64-native"
> > +DEPENDS_remove_k3 = "gcc-arm-none-eabi-native ti-cgt6x-native"
> > +DEPENDS_append_k3 = " ti-cgt-arm-native 
> > gcc-linaro-baremetal-aarch64-native"

What about these changes? If you need them, you can send this one patch 
separately, no need to re-send all 30.


> >  S = "${WORKDIR}/git"
> >  B = "${WORKDIR}/build"
> > @@ -72,7 +72,7 @@ PARALLEL_XDC = "--jobs=${BB_NUMBER_THREADS}"
> >  PARALLEL_MAKE = ""
> >  
> >  def get_doxygen_support(d):
> > -if d.getVar('TI_PDK_DOXYGEN_SUPPORT') == '1':
> > +if d.getVar('TI_PDK_DOXYGEN_SUPPORT', True) == '1':
> 
> "Checking for doxygen support in the correct manner"
> 
> Why the change?
> 
> I was thinking it was a bug fix when the doxygen support was added, but I'm 
> wrong .
> I see the commit now which explains why this was removed 
> https://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/commit/classes/ti-pdk.bbclass?h=rocko&id=195d3f7b93b605eccab685b408f354d35a60884e
>  
> Apparently meta-processor-sdk-internal's ti-pdk.bbclass  didn't catch up with 
> this change.
> So, pls ignore this patch.
> 
> >  return ''
> >  return 'DOXYGEN_SUPPORT=no'
> >  
> > -- 
> > 1.9.1
> > 
> > -- 
> > ___
> > meta-ti mailing list
> > meta-ti@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [rocko/master][PATCH v3 08/29] icss-emac-lld: Update to version 01.00.00.13

[Denys Dmytriyenko]

On Fri, Sep 28, 2018 at 12:26:09PM -0400, Mahesh Radhakrishnan wrote:
> Signed-off-by: Mahesh Radhakrishnan 
> ---
>  recipes-bsp/icss-emac-lld/icss-emac-lld.inc | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/recipes-bsp/icss-emac-lld/icss-emac-lld.inc 
> b/recipes-bsp/icss-emac-lld/icss-emac-lld.inc
> index d7ca641..0d1afb8 100644
> --- a/recipes-bsp/icss-emac-lld/icss-emac-lld.inc
> +++ b/recipes-bsp/icss-emac-lld/icss-emac-lld.inc
> @@ -10,7 +10,7 @@ ICSS_EMAC_LLD_GIT_BRANCH = "master"
>  ICSS_EMAC_LLD_GIT_DESTSUFFIX = "git/ti/drv/icss_emac"
>  
>  # Below commit ID corresponds to "DEV.ICSS_EMAC_LLD.01.00.00.13"
> -ICSS_EMAC_LLD_SRCREV = "a4071ded3edb0cfebaa62b1f1f35686ea24585b1"
> +ICSS_EMAC_LLD_SRCREV = "999692b6d60fd54a0390b1cf4724f1620e757fdf"

Do you also have to bump PV here? The log says update to 01.00.00.13...


>  BRANCH = "${ICSS_EMAC_LLD_GIT_BRANCH}"
>  SRC_URI = 
> "${ICSS_EMAC_LLD_GIT_URI};destsuffix=${ICSS_EMAC_LLD_GIT_DESTSUFFIX};protocol=${ICSS_EMAC_LLD_GIT_PROTOCOL};branch=${BRANCH}"
> -- 
> 1.9.1
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [rocko/master][PATCH v2 28/30] ti-ndk: Upgrading to 3.40.01.01

[Denys Dmytriyenko]

On Fri, Sep 28, 2018 at 11:37:16AM -0400, Radhakrishnan, Mahesh wrote:
> 
> 
> -Original Message-
> From: Dmytriyenko, Denys 
> Sent: Thursday, September 27, 2018 5:51 PM
> To: Radhakrishnan, Mahesh
> Cc: meta-ti@yoctoproject.org
> Subject: Re: [meta-ti] [rocko/master][PATCH v2 28/30] ti-ndk: Upgrading to 
> 3.40.01.01
> 
> On Thu, Sep 27, 2018 at 04:43:27PM -0400, Mahesh Radhakrishnan wrote:
> > Signed-off-by: Mahesh Radhakrishnan 
> > ---
> >  recipes-ti/ndk/ti-ndk_2.26.00.08.bb | 13 -
> >  recipes-ti/ndk/ti-ndk_3.40.01.01.bb | 13 +
> 
> Please make it a diff - pass -C/-M to git format-patch
> 
> Is there a specific value for  for the options -M and -C I should 
> use below?
> git send-email --smtp-server=smtp.mail.ti.com --from "Mahesh Radhakrishnan 
> " --to="meta-ti@yoctoproject.org" --confirm=always 
> --cover-letter --annotate  -M  -C  -30 --suppress-cc=all 
> --subject-prefix="rocko/master][PATCH v3"

In this case defaults should work, just -C/-M


> >  2 files changed, 13 insertions(+), 13 deletions(-)
> >  delete mode 100644 recipes-ti/ndk/ti-ndk_2.26.00.08.bb
> >  create mode 100644 recipes-ti/ndk/ti-ndk_3.40.01.01.bb
> > 
> > diff --git a/recipes-ti/ndk/ti-ndk_2.26.00.08.bb 
> > b/recipes-ti/ndk/ti-ndk_2.26.00.08.bb
> > deleted file mode 100644
> > index e587bf9..000
> > --- a/recipes-ti/ndk/ti-ndk_2.26.00.08.bb
> > +++ /dev/null
> > @@ -1,13 +0,0 @@
> > -require ti-ndk.inc
> > -
> > -PV = "2_26_00_08"
> > -PR = "r0"
> > -
> > -LIC_FILES_CHKSUM = 
> > "file://ndk_${PV}_manifest.html;md5=e2a7d40cf1e7207ac3dd6d993d71ee8c"
> > -
> > -SRC_URI[ndkzip.md5sum] = "09c7ffaff305f3083d15c0a0db73d781"
> > -SRC_URI[ndkzip.sha256sum] = 
> > "5b22c6b8bfbf3a22c53f52bf880d5cf49daf386716942a4202569521bb30f4a8"
> > -
> > -INHIBIT_PACKAGE_STRIP = "1"
> > -INHIBIT_PACKAGE_DEBUG_SPLIT = "1"
> > -INHIBIT_SYSROOT_STRIP = "1"
> > diff --git a/recipes-ti/ndk/ti-ndk_3.40.01.01.bb 
> > b/recipes-ti/ndk/ti-ndk_3.40.01.01.bb
> > new file mode 100644
> > index 000..4a494b1
> > --- /dev/null
> > +++ b/recipes-ti/ndk/ti-ndk_3.40.01.01.bb
> > @@ -0,0 +1,13 @@
> > +require ti-ndk.inc
> > +
> > +PV = "3_40_01_01"
> > +PR = "r0"
> > +
> > +LIC_FILES_CHKSUM = 
> > "file://manifest_ndk_${PV}.html;md5=9ddeee8ab01c13f593e6d085cca46b6a"
> > +
> > +SRC_URI[ndkzip.md5sum] = "bbbef445f2d2f84f9bee5d297f77d397"
> > +SRC_URI[ndkzip.sha256sum] = 
> > "e2e5c683c70dfad6f4372c5eeebaf0209b27abb0f77304f14f0359cbc7b3f4b8"
> > +
> > +INHIBIT_PACKAGE_STRIP = "1"
> > +INHIBIT_PACKAGE_DEBUG_SPLIT = "1"
> > +INHIBIT_SYSROOT_STRIP = "1"
> > -- 
> > 1.9.1
> > 
> > -- 
> > ___
> > meta-ti mailing list
> > meta-ti@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [rocko/master][PATCH v2 20/30] pcie-lld-rtos: Update to version 02.03.00.01 and added k3 support

[Denys Dmytriyenko]

On Thu, Sep 27, 2018 at 07:37:58PM -0400, Radhakrishnan, Mahesh wrote:
> 
> 
> -Original Message-
> From: Dmytriyenko, Denys 
> Sent: Thursday, September 27, 2018 5:45 PM
> To: Radhakrishnan, Mahesh
> Cc: meta-ti@yoctoproject.org
> Subject: Re: [meta-ti] [rocko/master][PATCH v2 20/30] pcie-lld-rtos: Update 
> to version 02.03.00.01 and added k3 support
> 
> On Thu, Sep 27, 2018 at 04:43:19PM -0400, Mahesh Radhakrishnan wrote:
> > Signed-off-by: Mahesh Radhakrishnan 
> > ---
> >  recipes-bsp/pcie-lld/pcie-lld-rtos_git.bb | 13 -
> >  1 file changed, 8 insertions(+), 5 deletions(-)
> > 
> > diff --git a/recipes-bsp/pcie-lld/pcie-lld-rtos_git.bb 
> > b/recipes-bsp/pcie-lld/pcie-lld-rtos_git.bb
> > index 1b7218a..35a0cbc 100644
> > --- a/recipes-bsp/pcie-lld/pcie-lld-rtos_git.bb
> > +++ b/recipes-bsp/pcie-lld/pcie-lld-rtos_git.bb
> > @@ -3,9 +3,9 @@ SUMMARY = "TI RTOS low lever driver for Peripheral 
> > Interconnect Express (PCIE)"
> >  inherit ti-pdk
> >  
> >  LICENSE = "BSD-3-Clause"
> > -LIC_FILES_CHKSUM = 
> > "file://pcie.h;beginline=1;endline=34;md5=c094db055596498ba803933936611eb2"
> > +LIC_FILES_CHKSUM = 
> > "file://pcie.h;beginline=1;endline=34;md5=566a784d78790a716d641764d5d60b74"
> 
> Why the change?
> The copyright year changed. Here is the diff

Thanks, please add a brief note in the commit log.


>  @@ -1,6 +1,6 @@
>  /*
>   *
> - * Copyright (C) 2010-2016 Texas Instruments Incorporated - 
> http://www.ti.com/
> + * Copyright (C) 2010-2018 Texas Instruments Incorporated - 
> http://www.ti.com/^M
>   *
>   *
> 
> 
> > -COMPATIBLE_MACHINE = "omap-a15|keystone|c66x"
> > +COMPATIBLE_MACHINE = "omap-a15|keystone|c66x|k3"
> >  PACKAGE_ARCH = "${MACHINE_ARCH}"
> >  
> >  PCIE_LLD_GIT_URI = "git://git.ti.com/keystone-rtos/pcie-lld.git"
> > @@ -13,16 +13,19 @@ PCIE_LLD_GIT_PROTOCOL = "git"
> >  PCIE_LLD_GIT_BRANCH = "master"
> >  PCIE_LLD_GIT_DESTSUFFIX = "git/ti/drv/pcie"
> >  
> > -# Below commit ID corresponds to "DEV.PCIE_LLD.02.02.00.13"
> > -PCIE_LLD_SRCREV = "bf8d3a22c03a5f273321c284fa1737072eca3f77"
> > +# Below commit ID corresponds to "DEV.PCIE_LLD.02.03.00.01"
> > +PCIE_LLD_SRCREV = "61759fc238600e3d5506ce86db1f6b604334edf8"
> >  
> >  BRANCH = "${PCIE_LLD_GIT_BRANCH}"
> >  SRC_URI = 
> > "${PCIE_LLD_GIT_URI};destsuffix=${PCIE_LLD_GIT_DESTSUFFIX};protocol=${PCIE_LLD_GIT_PROTOCOL};branch=${BRANCH}"
> >  
> >  SRCREV = "${PCIE_LLD_SRCREV}"
> > -PV = "02.02.00.13"
> > +PV = "02.03.00.01"
> >  PR = "r0"
> >  
> > +DEPENDS_append_k3 = " udma-lld-rtos \
> > +"
> > +
> >  S = "${WORKDIR}/${PCIE_LLD_GIT_DESTSUFFIX}"
> >  
> >  export PDK_PCIE_ROOT_PATH ="${WORKDIR}/build"
> > -- 
> > 1.9.1
> > 
> > -- 
> > ___
> > meta-ti mailing list
> > meta-ti@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

[meta-ti] [rocko-next][PATCH] u-boot-ti-staging: update to version with separated SYSFW

[Denys Dmytriyenko]

Signed-off-by: Denys Dmytriyenko 
---
 recipes-bsp/u-boot/u-boot-ti-staging_2018.01.bb | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/recipes-bsp/u-boot/u-boot-ti-staging_2018.01.bb 
b/recipes-bsp/u-boot/u-boot-ti-staging_2018.01.bb
index 98e9a7d0..e97156a8 100644
--- a/recipes-bsp/u-boot/u-boot-ti-staging_2018.01.bb
+++ b/recipes-bsp/u-boot/u-boot-ti-staging_2018.01.bb
@@ -1,7 +1,7 @@
 require u-boot-ti.inc
 
-PR = "r21"
+PR = "r22"
 
-BRANCH = "ti-u-boot-2018.01"
+BRANCH = "ti-u-boot-2018.01-next"
 
-SRCREV = "9b8c6b92b7cbbbe027cf73743686de46d1f1574b"
+SRCREV = "1d3ad14e9d5155d3ebfaf9612af62d29a0f903fb"
-- 
2.17.1

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [rocko/master][PATCH v2 28/30] ti-ndk: Upgrading to 3.40.01.01

[Denys Dmytriyenko]

On Thu, Sep 27, 2018 at 04:43:27PM -0400, Mahesh Radhakrishnan wrote:
> Signed-off-by: Mahesh Radhakrishnan 
> ---
>  recipes-ti/ndk/ti-ndk_2.26.00.08.bb | 13 -
>  recipes-ti/ndk/ti-ndk_3.40.01.01.bb | 13 +

Please make it a diff - pass -C/-M to git format-patch


>  2 files changed, 13 insertions(+), 13 deletions(-)
>  delete mode 100644 recipes-ti/ndk/ti-ndk_2.26.00.08.bb
>  create mode 100644 recipes-ti/ndk/ti-ndk_3.40.01.01.bb
> 
> diff --git a/recipes-ti/ndk/ti-ndk_2.26.00.08.bb 
> b/recipes-ti/ndk/ti-ndk_2.26.00.08.bb
> deleted file mode 100644
> index e587bf9..000
> --- a/recipes-ti/ndk/ti-ndk_2.26.00.08.bb
> +++ /dev/null
> @@ -1,13 +0,0 @@
> -require ti-ndk.inc
> -
> -PV = "2_26_00_08"
> -PR = "r0"
> -
> -LIC_FILES_CHKSUM = 
> "file://ndk_${PV}_manifest.html;md5=e2a7d40cf1e7207ac3dd6d993d71ee8c"
> -
> -SRC_URI[ndkzip.md5sum] = "09c7ffaff305f3083d15c0a0db73d781"
> -SRC_URI[ndkzip.sha256sum] = 
> "5b22c6b8bfbf3a22c53f52bf880d5cf49daf386716942a4202569521bb30f4a8"
> -
> -INHIBIT_PACKAGE_STRIP = "1"
> -INHIBIT_PACKAGE_DEBUG_SPLIT = "1"
> -INHIBIT_SYSROOT_STRIP = "1"
> diff --git a/recipes-ti/ndk/ti-ndk_3.40.01.01.bb 
> b/recipes-ti/ndk/ti-ndk_3.40.01.01.bb
> new file mode 100644
> index 000..4a494b1
> --- /dev/null
> +++ b/recipes-ti/ndk/ti-ndk_3.40.01.01.bb
> @@ -0,0 +1,13 @@
> +require ti-ndk.inc
> +
> +PV = "3_40_01_01"
> +PR = "r0"
> +
> +LIC_FILES_CHKSUM = 
> "file://manifest_ndk_${PV}.html;md5=9ddeee8ab01c13f593e6d085cca46b6a"
> +
> +SRC_URI[ndkzip.md5sum] = "bbbef445f2d2f84f9bee5d297f77d397"
> +SRC_URI[ndkzip.sha256sum] = 
> "e2e5c683c70dfad6f4372c5eeebaf0209b27abb0f77304f14f0359cbc7b3f4b8"
> +
> +INHIBIT_PACKAGE_STRIP = "1"
> +INHIBIT_PACKAGE_DEBUG_SPLIT = "1"
> +INHIBIT_SYSROOT_STRIP = "1"
> -- 
> 1.9.1
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [rocko/master][PATCH v2 24/30] sciclient-rtos: SRCREV update

[Denys Dmytriyenko]

On Thu, Sep 27, 2018 at 04:43:23PM -0400, Mahesh Radhakrishnan wrote:
> Signed-off-by: Mahesh Radhakrishnan 
> ---
>  recipes-bsp/sciclient/sciclient-rtos_git.bb | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/recipes-bsp/sciclient/sciclient-rtos_git.bb 
> b/recipes-bsp/sciclient/sciclient-rtos_git.bb
> index 73f642d..1eee3d6 100644
> --- a/recipes-bsp/sciclient/sciclient-rtos_git.bb
> +++ b/recipes-bsp/sciclient/sciclient-rtos_git.bb
> @@ -12,15 +12,15 @@ SCICLIENT_GIT_URI = 
> "git://git.ti.com/keystone-rtos/sciclient.git"
>  SCICLIENT_GIT_PROTOCOL = "git"
>  SCICLIENT_GIT_BRANCH = "master"
>  
> -# Below commit ID corresponds to "DEV.SCICLIENT.01.00.00.00A"
> -SCICLIENT_SRCREV = "cf151766d4cef7f93b47e4822a1ce6f17dfb9339"
> +# Below commit ID corresponds to "DEV.SCICLIENT.01.00.00.00"
> +SCICLIENT_SRCREV = "b865ba8a56b298048e21a26abb087c34113f5da1"

Do you keep moving the same tag?

Sam,

Will this affect R5 IPC?


>  BRANCH = "${SCICLIENT_GIT_BRANCH}"
>  SRC_URI = 
> "${SCICLIENT_GIT_URI};protocol=${SCICLIENT_GIT_PROTOCOL};branch=${BRANCH}"
>  
>  SRCREV = "${SCICLIENT_SRCREV}"
>  PV = "01.00.00.00"
> -PR = "r1"
> +PR = "r2"
>  
>  DEPENDS_append = " osal-rtos common-csl-ip-rtos"
>  
> -- 
> 1.9.1
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [rocko/master][PATCH v2 20/30] pcie-lld-rtos: Update to version 02.03.00.01 and added k3 support

[Denys Dmytriyenko]

On Thu, Sep 27, 2018 at 04:43:19PM -0400, Mahesh Radhakrishnan wrote:
> Signed-off-by: Mahesh Radhakrishnan 
> ---
>  recipes-bsp/pcie-lld/pcie-lld-rtos_git.bb | 13 -
>  1 file changed, 8 insertions(+), 5 deletions(-)
> 
> diff --git a/recipes-bsp/pcie-lld/pcie-lld-rtos_git.bb 
> b/recipes-bsp/pcie-lld/pcie-lld-rtos_git.bb
> index 1b7218a..35a0cbc 100644
> --- a/recipes-bsp/pcie-lld/pcie-lld-rtos_git.bb
> +++ b/recipes-bsp/pcie-lld/pcie-lld-rtos_git.bb
> @@ -3,9 +3,9 @@ SUMMARY = "TI RTOS low lever driver for Peripheral 
> Interconnect Express (PCIE)"
>  inherit ti-pdk
>  
>  LICENSE = "BSD-3-Clause"
> -LIC_FILES_CHKSUM = 
> "file://pcie.h;beginline=1;endline=34;md5=c094db055596498ba803933936611eb2"
> +LIC_FILES_CHKSUM = 
> "file://pcie.h;beginline=1;endline=34;md5=566a784d78790a716d641764d5d60b74"

Why the change?


> -COMPATIBLE_MACHINE = "omap-a15|keystone|c66x"
> +COMPATIBLE_MACHINE = "omap-a15|keystone|c66x|k3"
>  PACKAGE_ARCH = "${MACHINE_ARCH}"
>  
>  PCIE_LLD_GIT_URI = "git://git.ti.com/keystone-rtos/pcie-lld.git"
> @@ -13,16 +13,19 @@ PCIE_LLD_GIT_PROTOCOL = "git"
>  PCIE_LLD_GIT_BRANCH = "master"
>  PCIE_LLD_GIT_DESTSUFFIX = "git/ti/drv/pcie"
>  
> -# Below commit ID corresponds to "DEV.PCIE_LLD.02.02.00.13"
> -PCIE_LLD_SRCREV = "bf8d3a22c03a5f273321c284fa1737072eca3f77"
> +# Below commit ID corresponds to "DEV.PCIE_LLD.02.03.00.01"
> +PCIE_LLD_SRCREV = "61759fc238600e3d5506ce86db1f6b604334edf8"
>  
>  BRANCH = "${PCIE_LLD_GIT_BRANCH}"
>  SRC_URI = 
> "${PCIE_LLD_GIT_URI};destsuffix=${PCIE_LLD_GIT_DESTSUFFIX};protocol=${PCIE_LLD_GIT_PROTOCOL};branch=${BRANCH}"
>  
>  SRCREV = "${PCIE_LLD_SRCREV}"
> -PV = "02.02.00.13"
> +PV = "02.03.00.01"
>  PR = "r0"
>  
> +DEPENDS_append_k3 = " udma-lld-rtos \
> +"
> +
>  S = "${WORKDIR}/${PCIE_LLD_GIT_DESTSUFFIX}"
>  
>  export PDK_PCIE_ROOT_PATH ="${WORKDIR}/build"
> -- 
> 1.9.1
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [rocko/master][PATCH v2 17/30] pm-lld-rtos: Update to version 01.08.00.19 and k3 support

[Denys Dmytriyenko]

On Thu, Sep 27, 2018 at 04:43:16PM -0400, Mahesh Radhakrishnan wrote:
> Signed-off-by: Mahesh Radhakrishnan 
> ---
>  recipes-bsp/pm-lld/pm-lld-rtos_git.bb | 30 +++---
>  1 file changed, 19 insertions(+), 11 deletions(-)
> 
> diff --git a/recipes-bsp/pm-lld/pm-lld-rtos_git.bb 
> b/recipes-bsp/pm-lld/pm-lld-rtos_git.bb
> index 3e4e4f7..4dc43f6 100644
> --- a/recipes-bsp/pm-lld/pm-lld-rtos_git.bb
> +++ b/recipes-bsp/pm-lld/pm-lld-rtos_git.bb
> @@ -5,30 +5,34 @@ inherit ti-pdk
>  LICENSE = "BSD-3-Clause"
>  LIC_FILES_CHKSUM = 
> "file://Power.h;beginline=1;endline=31;md5=527b91fdcd26cd19ac07a754f45dedbe"
>  
> -COMPATIBLE_MACHINE = "ti33x|ti43x|omap-a15|k2g"
> +COMPATIBLE_MACHINE = "ti33x|ti43x|omap-a15|k2g|k3"
>  PACKAGE_ARCH = "${MACHINE_ARCH}"
>  
>  
>  PM_LLD_GIT_URI = "git://git.ti.com/keystone-rtos/pm-lld.git"
>  PM_LLD_GIT_PROTOCOL = "git"
> -PM_LLD_GIT_BRANCH = "int_pm_am335x"
> -PM_LLD_GIT_BRANCH_dra7xx-evm = "master"
> -PM_LLD_GIT_BRANCH_am57xx-evm = "master"
> -PM_LLD_GIT_DESTSUFFIX = "git/ti/drv/pm"
>  
> -# Below commit ID corresponds to "DEV.PM_LLD.01.04.00.05A"
> -PM_LLD_SRCREV = "a5f12b8210ccea4b2e8848e54b4e178534771843"
> +PM_LLD_GIT_BRANCH = "master"
> +
> +PM_LLD_GIT_BRANCH_ti33x = "int_pm_am335x"
> +PM_LLD_GIT_BRANCH_ti43x = "int_pm_am335x"
> +PM_LLD_GIT_BRANCH_k2g = "int_pm_am335x"

Argh, sorry about the confusion - didn't realize am335x branch was also used 
for am437 and k2g. So, it doesn't really make it simpler.

Anyway, let's keep it this way with master as default and am335x as a special 
case...


> +PM_LLD_GIT_DESTSUFFIX = "git/ti/drv/pm"
>  
> -# Below commit ID corresponds to "DEV.PM_LLD.01.08.00.18"
> -PM_LLD_SRCREV_dra7xx-evm = "c1924e4cb882c5500ae012ad2d7d76d1fbe97037"
> -PM_LLD_SRCREV_am57xx-evm = "c1924e4cb882c5500ae012ad2d7d76d1fbe97037"
> +# Below commit ID corresponds to "DEV.PM_LLD.01.08.00.19"
> +PM_LLD_SRCREV = "9095c9d1b479d6d1ad483b8b0cf4568c83e599ec"
>  
> +# Below commit ID corresponds to "DEV.PM_LLD.01.04.00.05B"
> +PM_LLD_SRCREV_ti33x = "bac16125842f08d05156dccabec74947756d831b"
> +PM_LLD_SRCREV_ti43x = "bac16125842f08d05156dccabec74947756d831b"
> +PM_LLD_SRCREV_k2g = "bac16125842f08d05156dccabec74947756d831b"
>  
>  BRANCH = "${PM_LLD_GIT_BRANCH}"
>  SRC_URI = 
> "${PM_LLD_GIT_URI};destsuffix=${PM_LLD_GIT_DESTSUFFIX};protocol=${PM_LLD_GIT_PROTOCOL};branch=${BRANCH}"
>  
>  SRCREV = "${PM_LLD_SRCREV}"
> -PV = "01.04.00.05A"
> +PV = "01.08.00.19"
>  PR = "r0"
>  
>  S = "${WORKDIR}/${PM_LLD_GIT_DESTSUFFIX}"
> @@ -40,6 +44,10 @@ DEPENDS_append_ti33x = " starterware-rtos \
>  "
>  DEPENDS_append_ti43x = " starterware-rtos \
>  "
> +
> +DEPENDS_append_k3 = " sciclient-rtos \
> +"
> +
>  export PDK_PM_ROOT_PATH = "${WORKDIR}/build"
>  export DEST_ROOT="${S}"
>  
> -- 
> 1.9.1
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [rocko/master][PATCH v2 13/30] mcasp-lld-rtos: Update to 01.00.00.11A

[Denys Dmytriyenko]

On Thu, Sep 27, 2018 at 04:43:12PM -0400, Mahesh Radhakrishnan wrote:
> Signed-off-by: Mahesh Radhakrishnan 
> ---
>  recipes-bsp/mcasp-lld/mcasp-lld-rtos_git.bb | 15 ++-
>  1 file changed, 10 insertions(+), 5 deletions(-)
> 
> diff --git a/recipes-bsp/mcasp-lld/mcasp-lld-rtos_git.bb 
> b/recipes-bsp/mcasp-lld/mcasp-lld-rtos_git.bb
> index 902b7a0..440133d 100644
> --- a/recipes-bsp/mcasp-lld/mcasp-lld-rtos_git.bb
> +++ b/recipes-bsp/mcasp-lld/mcasp-lld-rtos_git.bb
> @@ -3,9 +3,9 @@ SUMMARY = "TI RTOS low level driver for Multi channel Audio 
> Serial port (McASP)"
>  inherit ti-pdk
>  
>  LICENSE = "BSD-3-Clause"
> -LIC_FILES_CHKSUM = 
> "file://mcaspver.h;beginline=1;endline=47;md5=cc81a11c1566fe1cf19270744f504619"
> +LIC_FILES_CHKSUM = 
> "file://mcaspver.h;beginline=1;endline=47;md5=25868d96216e5d6f286d5fb05a3be9f4"

Why the change?


> -COMPATIBLE_MACHINE = "ti43x|omap-a15|k2g|ti33x|omapl1"
> +COMPATIBLE_MACHINE = "ti43x|omap-a15|k2g|ti33x|omapl1|k3"
>  PACKAGE_ARCH = "${MACHINE_ARCH}"
>  
>  MCASP_LLD_GIT_URI = "git://git.ti.com/keystone-rtos/mcasp-lld.git"
> @@ -13,14 +13,14 @@ MCASP_LLD_GIT_PROTOCOL = "git"
>  MCASP_LLD_GIT_BRANCH = "master"
>  MCASP_LLD_GIT_DESTSUFFIX = "git/ti/drv/mcasp"
>  
> -# Below commit ID corresponds to "DEV.MCASP_LLD.01.01.00.10"
> -MCASP_LLD_SRCREV = "c44ce7ee06c6cfb698bd12d2fa1b58dca04c1375"
> +# Below commit ID corresponds to "DEV.MCASP_LLD.01.01.00.11A"
> +MCASP_LLD_SRCREV = "3620edb04240b63b50b7b9dcb3da361af8152048"
>  
>  BRANCH = "${MCASP_LLD_GIT_BRANCH}"
>  SRC_URI = 
> "${MCASP_LLD_GIT_URI};destsuffix=${MCASP_LLD_GIT_DESTSUFFIX};protocol=${MCASP_LLD_GIT_PROTOCOL};branch=${BRANCH}"
>  
>  SRCREV = "${MCASP_LLD_SRCREV}"
> -PV = "01.01.00.10"
> +PV = "01.01.00.11A"
>  PR = "r0"
>  
>  S = "${WORKDIR}/${MCASP_LLD_GIT_DESTSUFFIX}"
> @@ -32,6 +32,11 @@ DEPENDS_append_ti43x = " starterware-rtos \
>  "
>  DEPENDS_append_ti33x = " starterware-rtos \
>  "
> +
> +DEPENDS_remove_k3 = "edma3-lld-rtos "
> +DEPENDS_append_k3 = " udma-lld-rtos \
> +"
> +
>  # Build with make instead of XDC
>  TI_PDK_XDCMAKE = "0"
>  
> -- 
> 1.9.1
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [rocko/master][PATCH v2 06/30] board-rtos: Update to version 01.00.10.02 and added support to k3

[Denys Dmytriyenko]

On Thu, Sep 27, 2018 at 04:43:05PM -0400, Mahesh Radhakrishnan wrote:
> Signed-off-by: Mahesh Radhakrishnan 
> ---
>  recipes-bsp/board-rtos/board-rtos_git.bb | 15 ++-
>  1 file changed, 10 insertions(+), 5 deletions(-)
> 
> diff --git a/recipes-bsp/board-rtos/board-rtos_git.bb 
> b/recipes-bsp/board-rtos/board-rtos_git.bb
> index df3e961..0e253d7 100644
> --- a/recipes-bsp/board-rtos/board-rtos_git.bb
> +++ b/recipes-bsp/board-rtos/board-rtos_git.bb
> @@ -5,22 +5,22 @@ inherit ti-pdk
>  LICENSE = "BSD-3-Clause"
>  LIC_FILES_CHKSUM = 
> "file://board.h;beginline=1;endline=32;md5=9bed8e4ac2fb37fc627cefe49eb1c919"
>  
> -COMPATIBLE_MACHINE = "ti33x|ti43x|omap-a15|keystone|omapl1|c66x"
> +COMPATIBLE_MACHINE = "ti33x|ti43x|omap-a15|keystone|omapl1|c66x|k3"
>  PACKAGE_ARCH = "${MACHINE_ARCH}"
>  
>  BOARD_GIT_URI = "git://git.ti.com/keystone-rtos/board.git"
>  BOARD_GIT_PROTOCOL = "git"
>  BOARD_GIT_BRANCH = "master"
>  
> -# Below commit ID corresponds to "DEV.BOARD.01.00.10.01"
> -BOARD_SRCREV = "983d89de8143645571e7893e95632a8be0fab67e"
> +# Below commit ID corresponds to "DEV.BOARD.01.00.10.02"
> +BOARD_SRCREV = "60bde3650d067e4064f93c292c8d9108aa1bf57b"
>  
>  BRANCH ="${BOARD_GIT_BRANCH}"
>  SRC_URI = "${BOARD_GIT_URI};protocol=${BOARD_GIT_PROTOCOL};branch=${BRANCH}"
>  
>  SRCREV = "${BOARD_SRCREV}"
> -PV = "01.00.10.01"
> -PR = "r1"
> +PV = "01.00.10.02"
> +PR = "r0"
>  
>  DEPENDS_append = " i2c-lld-rtos \
> spi-lld-rtos \
> @@ -63,6 +63,11 @@ DEPENDS_append_dra7xx = " pm-lld-rtos \
>mmcsd-lld-rtos \
>  "
>  
> +DEPENDS_append_am65xx-evm = " sciclient-rtos \

_append_k3?


> +  pm-lld-rtos \
> +"
> +
> +
>  # Build with make instead of XDC
>  TI_PDK_XDCMAKE = "0"
>  
> -- 
> 1.9.1
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [rocko/master][PATCH v2 01/30] ti-pdk-bbclass: Checking for doxygen support in the correct manner

[Denys Dmytriyenko]

On Thu, Sep 27, 2018 at 04:43:00PM -0400, Mahesh Radhakrishnan wrote:
> Signed-off-by: Mahesh Radhakrishnan 
> ---
>  classes/ti-pdk.bbclass | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/classes/ti-pdk.bbclass b/classes/ti-pdk.bbclass
> index 0716074..f59969f 100644
> --- a/classes/ti-pdk.bbclass
> +++ b/classes/ti-pdk.bbclass
> @@ -9,8 +9,8 @@ DEPENDS_append_omap-a15 = " ti-cgt-arm-native"
>  DEPENDS_remove_ti33x = "ti-cgt6x-native"
>  DEPENDS_remove_ti43x = "ti-cgt6x-native"
>  DEPENDS_append_omapl1 = " ti-cgt-arm-native"
> -DEPENDS_remove_am65xx-evm = "gcc-arm-none-eabi-native ti-cgt6x-native"
> -DEPENDS_append_am65xx-evm = " ti-cgt-arm-native 
> gcc-linaro-baremetal-aarch64-native"
> +DEPENDS_remove_k3 = "gcc-arm-none-eabi-native ti-cgt6x-native"
> +DEPENDS_append_k3 = " ti-cgt-arm-native gcc-linaro-baremetal-aarch64-native"
>  
>  S = "${WORKDIR}/git"
>  B = "${WORKDIR}/build"
> @@ -72,7 +72,7 @@ PARALLEL_XDC = "--jobs=${BB_NUMBER_THREADS}"
>  PARALLEL_MAKE = ""
>  
>  def get_doxygen_support(d):
> -if d.getVar('TI_PDK_DOXYGEN_SUPPORT') == '1':
> +if d.getVar('TI_PDK_DOXYGEN_SUPPORT', True) == '1':

"Checking for doxygen support in the correct manner"

Why the change?


>  return ''
>  return 'DOXYGEN_SUPPORT=no'
>  
> -- 
> 1.9.1
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [rocko/master][PATCH v2 02/30] common-csl-ip: Update to version 03.03.00.12

[Denys Dmytriyenko]

ACK

On Thu, Sep 27, 2018 at 04:43:01PM -0400, Mahesh Radhakrishnan wrote:
> Signed-off-by: Mahesh Radhakrishnan 
> ---
>  recipes-bsp/common-csl-ip/common-csl-ip.inc | 7 ---
>  1 file changed, 4 insertions(+), 3 deletions(-)
> 
> diff --git a/recipes-bsp/common-csl-ip/common-csl-ip.inc 
> b/recipes-bsp/common-csl-ip/common-csl-ip.inc
> index ed8078d..8c7f237 100644
> --- a/recipes-bsp/common-csl-ip/common-csl-ip.inc
> +++ b/recipes-bsp/common-csl-ip/common-csl-ip.inc
> @@ -4,16 +4,17 @@ LIC_FILES_CHKSUM = 
> "file://COPYING.txt;md5=5857833e20836213677fac33f9aded21"
>  
>  COMPATIBLE_MACHINE = "keystone|dra7xx|ti33x|ti43x|omapl1"
>  
> -PV = "05.01.00.00"
> +PV = "03.03.00.12"
>  INC_PR = "r0"
> +PE = "1"
>  
>  CSL_GIT_URI = "git://git.ti.com/keystone-rtos/common-csl-ip.git"
>  CSL_GIT_PROTOCOL ="git"
>  CSL_GIT_BRANCH = "master"
>  CSL_GIT_DESTSUFFIX = "git"
>  
> -# Below commit ID corresponding to "DEV.CSL_PROCESSOR-SDK.05.01.00.00"
> -CSL_SRCREV = "8db3d673101a504fd7fb36d6c9c4981e1e15ff50"
> +# Below commit ID corresponding to "DEV.CSL_PROCESSOR-SDK.03.03.00.12"
> +CSL_SRCREV = "0c3b2c8a054d2af27fe1683e9aa579d43049a3bf"
>  
>  BRANCH="${CSL_GIT_BRANCH}"
>  SRC_URI = 
> "${CSL_GIT_URI};protocol=${CSL_GIT_PROTOCOL};branch=${BRANCH};destsuffix=${CSL_GIT_DESTSUFFIX}"
> -- 
> 1.9.1
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [rocko/master][PATCH v2 02/30] common-csl-ip: Update to version 03.03.00.12

[Denys Dmytriyenko]

On Thu, Sep 27, 2018 at 04:10:37PM -0400, Radhakrishnan, Mahesh wrote:
> 
> 
> -Original Message-
> From: Dmytriyenko, Denys 
> Sent: Thursday, September 27, 2018 4:08 PM
> To: Radhakrishnan, Mahesh
> Cc: meta-ti@yoctoproject.org
> Subject: Re: [meta-ti] [rocko/master][PATCH v2 02/30] common-csl-ip: Update 
> to version 03.03.00.12
> 
> On Thu, Sep 27, 2018 at 04:04:42PM -0400, Mahesh Radhakrishnan wrote:
> > Signed-off-by: Mahesh Radhakrishnan 
> > ---
> >  recipes-bsp/common-csl-ip/common-csl-ip.inc | 6 +++---
> >  1 file changed, 3 insertions(+), 3 deletions(-)
> > 
> > diff --git a/recipes-bsp/common-csl-ip/common-csl-ip.inc 
> > b/recipes-bsp/common-csl-ip/common-csl-ip.inc
> > index ed8078d..baa7898 100644
> > --- a/recipes-bsp/common-csl-ip/common-csl-ip.inc
> > +++ b/recipes-bsp/common-csl-ip/common-csl-ip.inc
> > @@ -4,7 +4,7 @@ LIC_FILES_CHKSUM = 
> > "file://COPYING.txt;md5=5857833e20836213677fac33f9aded21"
> >  
> >  COMPATIBLE_MACHINE = "keystone|dra7xx|ti33x|ti43x|omapl1"
> >  
> > -PV = "05.01.00.00"
> > +PV = "03.03.00.12"
> 
> Still backwards.
> 
> The previous version up streamed was wrong. It should have been 03.03.00.x 
> consistent with the package.xdc & the versions mentioned in the release 
> notes of CSL throughout.
> This patch corrects it to the right version 03.03.00.12

Cannot easily move version backwards. At least need to bump epoch/PE...


> >  INC_PR = "r0"
> >  
> >  CSL_GIT_URI = "git://git.ti.com/keystone-rtos/common-csl-ip.git"
> > @@ -12,8 +12,8 @@ CSL_GIT_PROTOCOL ="git"
> >  CSL_GIT_BRANCH = "master"
> >  CSL_GIT_DESTSUFFIX = "git"
> >  
> > -# Below commit ID corresponding to "DEV.CSL_PROCESSOR-SDK.05.01.00.00"
> > -CSL_SRCREV = "8db3d673101a504fd7fb36d6c9c4981e1e15ff50"
> > +# Below commit ID corresponding to "DEV.CSL_PROCESSOR-SDK.03.03.00.12"
> > +CSL_SRCREV = "0c3b2c8a054d2af27fe1683e9aa579d43049a3bf"
> >  
> >  BRANCH="${CSL_GIT_BRANCH}"
> >  SRC_URI = 
> > "${CSL_GIT_URI};protocol=${CSL_GIT_PROTOCOL};branch=${BRANCH};destsuffix=${CSL_GIT_DESTSUFFIX}"
> > -- 
> > 1.9.1
> > 
> > -- 
> > ___
> > meta-ti mailing list
> > meta-ti@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [rocko/master][PATCH v2 02/30] common-csl-ip: Update to version 03.03.00.12

[Denys Dmytriyenko]

On Thu, Sep 27, 2018 at 04:04:42PM -0400, Mahesh Radhakrishnan wrote:
> Signed-off-by: Mahesh Radhakrishnan 
> ---
>  recipes-bsp/common-csl-ip/common-csl-ip.inc | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/recipes-bsp/common-csl-ip/common-csl-ip.inc 
> b/recipes-bsp/common-csl-ip/common-csl-ip.inc
> index ed8078d..baa7898 100644
> --- a/recipes-bsp/common-csl-ip/common-csl-ip.inc
> +++ b/recipes-bsp/common-csl-ip/common-csl-ip.inc
> @@ -4,7 +4,7 @@ LIC_FILES_CHKSUM = 
> "file://COPYING.txt;md5=5857833e20836213677fac33f9aded21"
>  
>  COMPATIBLE_MACHINE = "keystone|dra7xx|ti33x|ti43x|omapl1"
>  
> -PV = "05.01.00.00"
> +PV = "03.03.00.12"

Still backwards.


>  INC_PR = "r0"
>  
>  CSL_GIT_URI = "git://git.ti.com/keystone-rtos/common-csl-ip.git"
> @@ -12,8 +12,8 @@ CSL_GIT_PROTOCOL ="git"
>  CSL_GIT_BRANCH = "master"
>  CSL_GIT_DESTSUFFIX = "git"
>  
> -# Below commit ID corresponding to "DEV.CSL_PROCESSOR-SDK.05.01.00.00"
> -CSL_SRCREV = "8db3d673101a504fd7fb36d6c9c4981e1e15ff50"
> +# Below commit ID corresponding to "DEV.CSL_PROCESSOR-SDK.03.03.00.12"
> +CSL_SRCREV = "0c3b2c8a054d2af27fe1683e9aa579d43049a3bf"
>  
>  BRANCH="${CSL_GIT_BRANCH}"
>  SRC_URI = 
> "${CSL_GIT_URI};protocol=${CSL_GIT_PROTOCOL};branch=${BRANCH};destsuffix=${CSL_GIT_DESTSUFFIX}"
> -- 
> 1.9.1
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [EXTERNAL] [rocko/master][PATCH 18/30] udma-lld-rtos: Added support for udma-lld on rtos (initial version)

[Denys Dmytriyenko]

On Thu, Sep 27, 2018 at 07:11:23PM +, Radhakrishnan, Mahesh wrote:
> 
> 
> -Original Message-
> From: Stiffler, Jacob 
> Sent: Thursday, September 27, 2018 12:34 PM
> To: Radhakrishnan, Mahesh; meta-ti@yoctoproject.org
> Subject: Re: [EXTERNAL] [meta-ti] [rocko/master][PATCH 18/30] udma-lld-rtos: 
> Added support for udma-lld on rtos (initial version)
> 
> 
> 
> On 9/27/2018 11:22 AM, Mahesh Radhakrishnan wrote:
> > Signed-off-by: Mahesh Radhakrishnan 
> > ---
> >   recipes-bsp/udma-lld/udma-lld-rtos_git.bb | 81 
> > +++
> >   1 file changed, 81 insertions(+)
> >   create mode 100644 recipes-bsp/udma-lld/udma-lld-rtos_git.bb
> >
> > diff --git a/recipes-bsp/udma-lld/udma-lld-rtos_git.bb 
> > b/recipes-bsp/udma-lld/udma-lld-rtos_git.bb
> > new file mode 100644
> > index 000..1a68aa9
> > --- /dev/null
> > +++ b/recipes-bsp/udma-lld/udma-lld-rtos_git.bb
> > @@ -0,0 +1,81 @@
> > +SUMMARY = "TI RTOS low level driver for UDMA"
> > +DESCRIPTION = "TI RTOS low level driver for Universal DMA module "
> > +
> > +inherit ti-pdk
> > +
> > +LICENSE = "BSD-3-Clause"
> > +LIC_FILES_CHKSUM = 
> > "file://udma.h;beginline=1;endline=31;md5=83d177cf3df55c16b27ae4102b6ade9a"
> > +
> > +COMPATIBLE_MACHINE = "k3"
> > +PACKAGE_ARCH = "${MACHINE_ARCH}"
> > +
> > +UDMA_LLD_GIT_URI = "git://git.ti.com/keystone-rtos/udma-lld.git"
> > +UDMA_LLD_GIT_PROTOCOL = "git"
> > +UDMA_LLD_GIT_BRANCH = "master"
> > +
> > +# Below commit ID corresponds to "DEV.UDMA_LLD.01.00.00.00"
> > +UDMA_LLD_SRCREV = "745f7d3fa12cca6507821489451ffe0cfad4609e"
> > +
> > +BRANCH = "${UDMA_LLD_GIT_BRANCH}"
> > +SRC_URI = 
> > "${UDMA_LLD_GIT_URI};protocol=${UDMA_LLD_GIT_PROTOCOL};branch=${BRANCH}"
> > +
> > +SRCREV = "${UDMA_LLD_SRCREV}"
> > +PV = "01.00.00.00"
> > +PR = "r0"
> > +
> > +DEPENDS_append = " osal-rtos \
> > +   sciclient-rtos \
> > +"
> > +
> > +# Build with make instead of XDC
> > +TI_PDK_XDCMAKE = "0"
> > +
> > +UDMA_PACKAGE_BASE   = "${S}/../udma_base"
> > +UDMA_LLD_ROOTPATH = 
> > "${UDMA_PACKAGE_BASE}/package/all/pdk_/packages/ti/drv/udma"
> > +
> > +export PDK_INSTALL_PATH = "${PDK_INSTALL_DIR}/packages"
> > +export PDK_UDMA_ROOT_PATH = 
> > "${UDMA_PACKAGE_BASE}/package/all/pdk_/packages"
> > +
> > +LIMSOCS = ""
> > +LIMSOCS_am65xx-evm = "am65xx"
> > +
> > +LIMBOARDS = ""
> > +LIMBOARDS_am65xx-evm = "am65xx_evm"
> 
> Can these definitions be added to the machine configuration as was done 
> for all others?
> This would mean, defining as below, correct?
> LIMSOCS_k3 = "am65xx"
> LIMBOARDS_k3 = "am65xx_evm"
> BOARD_PACKAGE_k3 = "am65xx_evm"

No, move them to the machine config in am65xx-evm.conf.


> > +
> > +BOARD_PACKAGE = ""
> > +BOARD_PACKAGE_am65xx-evm = "am65xx_evm"
> > +
> > +# HTML doc link params
> > +PDK_COMP_LINK_TEXT = "UDMA LLD"
> > +
> > +do_configure() {
> > +
> > +   # remove any previous package
> > +rm -rf ${UDMA_PACKAGE_BASE}
> > +
> > +cd ${S}
> > +
> > +# make the release package before building it
> > +make package BOARD=${BOARD_PACKAGE} DEST_ROOT=${UDMA_PACKAGE_BASE} 
> > PDK_UDMA_COMP_PATH=${S}
> > +}
> > +
> > +do_compile() {
> > +
> > +cd ${UDMA_LLD_ROOTPATH}
> > +
> > +# Build am65xx libraries
> > +make clean lib xdc_meta doxygen LIMIT_SOCS="${LIMSOCS}" 
> > LIMIT_BOARDS="${LIMBOARDS}"
> > +
> > +#archive
> > +tar -cf udma_lld.tar --exclude='*.tar' ./*
> > +}
> > +
> > +do_install() {
> > +cd ${UDMA_LLD_ROOTPATH}
> > +install -d ${D}${PDK_INSTALL_DIR_RECIPE}/packages/ti/drv/udma
> > +find -name "*.tar" -exec tar xf {} --no-same-owner -C 
> > ${D}${PDK_INSTALL_DIR_RECIPE}/packages/ti/drv/udma \;
> > +}
> > +
> > +FILES_${PN} += "${PDK_INSTALL_DIR_RECIPE}/packages"
> > +
> > +INSANE_SKIP_${PN} = "arch ldflags"
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [EXTERNAL] [rocko/master][PATCH 17/30] pm-lld-rtos: Update to version 01.04.00.05B and k3 support

[Denys Dmytriyenko]

On Thu, Sep 27, 2018 at 12:32:12PM -0400, Jacob Stiffler wrote:
> 
> 
> On 9/27/2018 11:22 AM, Mahesh Radhakrishnan wrote:
> >Signed-off-by: Mahesh Radhakrishnan 
> >---
> >  recipes-bsp/pm-lld/pm-lld-rtos_git.bb | 20 +---
> >  1 file changed, 13 insertions(+), 7 deletions(-)
> >
> >diff --git a/recipes-bsp/pm-lld/pm-lld-rtos_git.bb 
> >b/recipes-bsp/pm-lld/pm-lld-rtos_git.bb
> >index 3e4e4f7..af3622b 100644
> >--- a/recipes-bsp/pm-lld/pm-lld-rtos_git.bb
> >+++ b/recipes-bsp/pm-lld/pm-lld-rtos_git.bb
> >@@ -5,7 +5,7 @@ inherit ti-pdk
> >  LICENSE = "BSD-3-Clause"
> >  LIC_FILES_CHKSUM = 
> > "file://Power.h;beginline=1;endline=31;md5=527b91fdcd26cd19ac07a754f45dedbe"
> >-COMPATIBLE_MACHINE = "ti33x|ti43x|omap-a15|k2g"
> >+COMPATIBLE_MACHINE = "ti33x|ti43x|omap-a15|k2g|k3"
> >  PACKAGE_ARCH = "${MACHINE_ARCH}"
> >@@ -14,21 +14,23 @@ PM_LLD_GIT_PROTOCOL = "git"
> >  PM_LLD_GIT_BRANCH = "int_pm_am335x"
> >  PM_LLD_GIT_BRANCH_dra7xx-evm = "master"
> >  PM_LLD_GIT_BRANCH_am57xx-evm = "master"
> >+PM_LLD_GIT_BRANCH_am65xx-evm = "master"
> 
> Please extend this to k3 as was done with the PM_LLD_SRCREV below.

I'd also suggest reversing the branches - it seems only am335x uses a special 
branch and all other platforms use master. It would be easier to have a single 
override for am335x/ti33x here.


> >  PM_LLD_GIT_DESTSUFFIX = "git/ti/drv/pm"
> >-# Below commit ID corresponds to "DEV.PM_LLD.01.04.00.05A"
> >-PM_LLD_SRCREV = "a5f12b8210ccea4b2e8848e54b4e178534771843"
> >+# Below commit ID corresponds to "DEV.PM_LLD.01.04.00.05B"
> >+PM_LLD_SRCREV = "bac16125842f08d05156dccabec74947756d831b"
> >-# Below commit ID corresponds to "DEV.PM_LLD.01.08.00.18"
> >-PM_LLD_SRCREV_dra7xx-evm = "c1924e4cb882c5500ae012ad2d7d76d1fbe97037"
> >-PM_LLD_SRCREV_am57xx-evm = "c1924e4cb882c5500ae012ad2d7d76d1fbe97037"
> >+# Below commit ID corresponds to "DEV.PM_LLD.01.08.00.19"
> >+PM_LLD_SRCREV_dra7xx-evm = "9095c9d1b479d6d1ad483b8b0cf4568c83e599ec"
> >+PM_LLD_SRCREV_am57xx-evm = "9095c9d1b479d6d1ad483b8b0cf4568c83e599ec"
> >+PM_LLD_SRCREV_k3 = "9095c9d1b479d6d1ad483b8b0cf4568c83e599ec"
> >  BRANCH = "${PM_LLD_GIT_BRANCH}"
> >  SRC_URI = 
> > "${PM_LLD_GIT_URI};destsuffix=${PM_LLD_GIT_DESTSUFFIX};protocol=${PM_LLD_GIT_PROTOCOL};branch=${BRANCH}"
> >  SRCREV = "${PM_LLD_SRCREV}"
> >-PV = "01.04.00.05A"
> >+PV = "01.04.00.05B"
> >  PR = "r0"
> >  S = "${WORKDIR}/${PM_LLD_GIT_DESTSUFFIX}"
> >@@ -40,6 +42,10 @@ DEPENDS_append_ti33x = " starterware-rtos \
> >  "
> >  DEPENDS_append_ti43x = " starterware-rtos \
> >  "
> >+
> >+DEPENDS_append_k3 = " sciclient-rtos \
> >+"
> >+
> >  export PDK_PM_ROOT_PATH = "${WORKDIR}/build"
> >  export DEST_ROOT="${S}"
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] Poky and meta-ti advice for Beaglebone Black

[Denys Dmytriyenko]

On Wed, Sep 26, 2018 at 06:27:10PM +, Tsai, Matt wrote:
> Leo,
> 
> Thanks for sharing the experience.
> Questions:
> 
>   1.  Do you set MACHINE ?= “am3335x-evm” in local.conf and build 
>   core-image-minimal? Or other image target is used?

Don't use core-image-minimal - it won't install modules or DTBs into rootfs 
automatically. You'd have to install those manually. Or use at least 
core-image-base or some custom image.


>   2.  Do you have to modify anything to make Linux OS (not bootloader) 
>   Ethernet and USB to work?

Shouldn't need to.


> I used poky tag “sumo-19.0.0” and meta-ti tag “ti2018.02” and set MACHINE ?= 
> “beaglebone” to build core-image-minimal.

Please use matching branches - i.e. "rocko" from all branches.
There were recent reports that "beaglebone" machine had some boot issues. 
Use "am335x-evm" instead - it does support Beaglebone.


> The USB host does not work. I  wonder if I am using a good base to start 
> with.

Check if you have corresponding modules installed and loaded.


> Also, a question about the Linux kernel 
> meta-ti/recipes-kernel/linux/linux-ti-staging-4.14/defconfig content:
> The original in “ti2018.02” tag is “use-tisdk-config= ti_sdk_omap2_release”. 
> But I also see people changing it to “use-tisdk-config= 
> ti_sdk_am3x_release”. I tried both, but USB host working. So I wonder what 
> is the correct one to use?

The defconfig is being selected based on the machine you build for. When 
building "am335x-evm" or "beaglebone", the defconfig with ti_sdk_am3x_release 
is used.


> Thank you for your help!
> 
> 
> From: Leo Meza [mailto:leo.e.m...@gmail.com]
> Sent: Wednesday, September 26, 2018 6:28 AM
> To: Tsai, Matt 
> Cc: meta-ti@yoctoproject.org
> Subject: Re: [meta-ti] Poky and meta-ti advice for Beaglebone Black
> 
> CAUTION: This email originated from outside of the organization. Do not click 
> links or open attachments unless you recognize the sender and know the 
> content is safe.
> 
> Matt,
> 
> I've been having some success with the "rocko" branches (meta-ti, etc), and 
> using the "am335x-evm" machine for beaglebone black.
> 
> I haven't done any i2c yet, but Ethernet and USB are working fine. I'm still 
> on the left of the learning curve though, maybe someone else on this thread 
> has better advice.
> 
> -Leo
> 
> On Tue, Sep 25, 2018, 4:19 PM Tsai, Matt 
> mailto:matt.t...@thermofisher.com>> wrote:
> Hi all,
> 
> I am new to Yocto and was trying to use poky and meta-ti to customize Linux 
> to run on Beaglebone Black. There are a couple of questions I encountered, 
> hopefully I can get some advice here:
> 
>   1.  What is the recommended poky and meta-ti branch/tag to use?
>   2.  If we need to enable some common device support such as Ethernet, USB 
> host port, I2C, …etc., what do we need to modify on these recommended poky 
> and meta-ti software?
> 
> Thank you for your help!
> 
> --
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti

> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] Unable to run bitbake -c virtual/kernel menuconfig

[Denys Dmytriyenko]

$ sudo apt install libncurses5-dev


On Mon, Sep 24, 2018 at 10:01:43PM +, Tsai, Matt wrote:
> Hi all,
> 
> I was trying to configure Linux kernel using Yocto and meta-ti layer: Poky 
> branch is sumo-19.0.0; meta-ti branch is sumo. I was able set up the Yocto 
> build system to build the core-image-minimal successfully. My build host is 
> machine Ubuntu 16.04LTS and the target device is Beaglebone Black. However, 
> when I tried to customize the kernel using "bitbake -c virtual/kernel 
> menuconfig", I got the following error:
> 
>   GEN ./Makefile
>   HOSTLD  scripts/kconfig/mconf
> scripts/kconfig/mconf.o: In function `show_help':
> mconf.c:(.text+0x914): undefined reference to `stdscr'
> scripts/kconfig/lxdialog/checklist.o: In function `print_arrows':
> checklist.c:(.text+0x2c): undefined reference to `wmove'
> checklist.c:(.text+0x4c): undefined reference to `acs_map'
> ...
> scripts/kconfig/lxdialog/menubox.o: In function `print_arrows.constprop.0':
> menubox.c:(.text+0x3c3): undefined reference to `wrefresh'
> collect2: error: ld returned 1 exit status
> scripts/Makefile.host:111: recipe for target 'scripts/kconfig/mconf' failed
> make[3]: *** [scripts/kconfig/mconf] Error 1
> .../build/tmp/work-shared/beaglebone/kernel-source/Makefile:512: recipe for 
> target 'menuconfig' failed
> make[2]: *** [menuconfig] Error 2
> Makefile:146: recipe for target 'sub-make' failed
> make[1]: *** [sub-make] Error 2
> Makefile:24: recipe for target '__sub-make' failed
> make: *** [__sub-make] Error 2
> Command failed.
> 
> I wonder if anyone has the same issue and how to solve this problem. Please 
> help. Thank you in advance!
> 
> 
> 

> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [rocko][PATCH] ti-cgt-arm: Update to add rtsv7R4_A_le_v3D16_eabi.lib

[Denys Dmytriyenko]

On Fri, Sep 14, 2018 at 10:50:05PM -0400, Sam Nelson wrote:
> rtsv7R4_A_le_v3D16_eabi.lib library is not included in the cgt package.
> This library is built dynamically during linking during a single build.
> Bu in case of parallel make, dynamic creation of libraries causes
> failures.
> Hence building and adding the library to the package.

Is this applicable to all platforms?


> Signed-off-by: Sam Nelson t
> ---
>  recipes-ti/devtools/ti-cgt-arm.inc | 8 
>  1 file changed, 8 insertions(+)
> 
> diff --git a/recipes-ti/devtools/ti-cgt-arm.inc 
> b/recipes-ti/devtools/ti-cgt-arm.inc
> index 436fab1..b9f7566 100644
> --- a/recipes-ti/devtools/ti-cgt-arm.inc
> +++ b/recipes-ti/devtools/ti-cgt-arm.inc
> @@ -9,12 +9,20 @@ require recipes-ti/includes/ti-paths.inc
>  
>  S = "${WORKDIR}/ti-cgt-arm-${PV}"
>  
> +PR = "r1"
> +
>  SRC_URI = 
> "http://software-dl.ti.com/codegen/esd/cgt_public_sw/TMS470/${PV}.LTS/${BINFILE};name=${BINFILE_NAME}";
>  
>  BINFILE = "ti_cgt_tms470_${PV}.LTS_linux_installer_x86.bin"
>  TI_BIN_UNPK_ARGS = "--prefix ${S}"
>  TI_BIN_UNPK_CMDS = ""
>  
> +do_compile_append() {
> +cd ${S}/ti-cgt-arm_${PV}.LTS
> +export PATH=${PATH}:${S}/ti-cgt-arm_${PV}.LTS/bin
> +lib/mklib --pattern=rtsv7R4_A_le_v3D16_eabi.lib
> +}
> +
>  do_install() {
>  install -d ${D}${M4_TOOLCHAIN_INSTALL_DIR_RECIPE}
>  cp -r ${S}/ti-cgt-arm*/. ${D}${M4_TOOLCHAIN_INSTALL_DIR_RECIPE}
> -- 
> 1.9.1
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [PATCH] swtools: common tools for xdc-based component build

[Denys Dmytriyenko]

Can you please send the patches as an ordered series. Thanks.


On Fri, Sep 14, 2018 at 04:47:06PM -0400, Jianzhong Xu wrote:
> swtools: common tools for xdc-based component build
> 
> Add SWTOOLS which is needed to build xdc-based processor libs such as
> DSPLIB, MATHLIB, etc from source.
> 
> Signed-off-by: Jianzhong Xu 
> ---
>  recipes-ti/includes/ti-paths.inc  |  2 ++
>  recipes-ti/swtools/swtools_git.bb | 44 
> +++
>  2 files changed, 46 insertions(+)
>  create mode 100644 recipes-ti/swtools/swtools_git.bb
> 
> diff --git a/recipes-ti/includes/ti-paths.inc 
> b/recipes-ti/includes/ti-paths.inc
> index a401264..f797a2d 100644
> --- a/recipes-ti/includes/ti-paths.inc
> +++ b/recipes-ti/includes/ti-paths.inc
> @@ -39,6 +39,7 @@ export OSAL_INSTALL_DIR_RECIPE   = 
> "${installdir}/ti-osal-tree"
>  export RTFS_INSTALL_DIR_RECIPE   = "${installdir}/ti-rtfs-tree"
>  export SYSBIOS_INSTALL_DIR_RECIPE= "${installdir}/ti-sysbios-tree"
>  export SYSLINK_INSTALL_DIR_RECIPE= "${installdir}/ti-syslink-tree"
> +export SWTOOLS_INSTALL_DIR_RECIPE= "${installdir}/ti-swtools-tree"
>  export UIA_INSTALL_DIR_RECIPE= "${installdir}/ti-uia-tree"
>  export VICPLIB_INSTALL_DIR_RECIPE= "${installdir}/ti-vicplib-tree"
>  export XDAIS_INSTALL_DIR_RECIPE  = "${installdir}/ti-xdais-tree"
> @@ -97,6 +98,7 @@ export OSAL_INSTALL_DIR   = 
> "${STAGING_DIR_TARGET}${OSAL_INSTALL_DIR_RECIPE}
>  export M4_TOOLCHAIN_INSTALL_DIR= 
> "${STAGING_DIR_NATIVE}${M4_TOOLCHAIN_INSTALL_DIR_RECIPE}"
>  export GCC_ARM_NONE_TOOLCHAIN  = 
> "${STAGING_DIR_NATIVE}${GCC_ARM_NONE_TOOLCHAIN_RECIPE}"
>  export TI_CGT_PRU_INSTALL_DIR  = 
> "${STAGING_DIR_NATIVE}${TI_CGT_PRU_INSTALL_DIR_RECIPE}"
> +export SWTOOLS_INSTALL_DIR = 
> "${STAGING_DIR_TARGET}${SWTOOLS_INSTALL_DIR_RECIPE}"
>  export DSPLIB_C66_INSTALL_DIR  = 
> "${STAGING_DIR_TARGET}${DSPLIB_C66_INSTALL_DIR_RECIPE}"
>  export MATHLIB_C66_INSTALL_DIR = 
> "${STAGING_DIR_TARGET}${MATHLIB_C66_INSTALL_DIR_RECIPE}"
>  export IMGLIB_C66_INSTALL_DIR  = 
> "${STAGING_DIR_TARGET}${IMGLIB_C66_INSTALL_DIR_RECIPE}"
> diff --git a/recipes-ti/swtools/swtools_git.bb 
> b/recipes-ti/swtools/swtools_git.bb
> new file mode 100644
> index 000..425a069
> --- /dev/null
> +++ b/recipes-ti/swtools/swtools_git.bb
> @@ -0,0 +1,44 @@
> +SUMMARY = "TI Software Tools"
> +HOMEPAGE = "https://git.ti.com/ep-processor-libraries/swtools";
> +SECTION = "devel"
> +LICENSE = "BSD"
> +LIC_FILES_CHKSUM = 
> "file://ti/mas/swtools/copyright.txt;md5=b1f52a1435051fdb18f8885b0384147d"
> +
> +require ../includes/ti-paths.inc
> +
> +DEPENDS = "ti-cgt6x-native \
> +   ti-sysbios \
> +   ti-xdctools-native"
> +
> +PV = "5_0_8"
> +PR = "r0"
> +S = "${WORKDIR}/git"
> +BRANCH = "master"
> +SRC_URI = 
> "git://git.ti.com/ep-processor-libraries/swtools.git;protocol=git;branch=${BRANCH}"
> +SRCREV = "881267836907de650edadc56b8e57ab45428021d"
> +
> +export C64PCODEGENTOOL = "${CGTOOLS_INSTALL_DIR}"
> +export C674CODEGENTOOL = "${CGTOOLS_INSTALL_DIR}"
> +export C66CODEGENTOOL  = "${CGTOOLS_INSTALL_DIR}"
> +
> +PATH_append = ":${XDC_INSTALL_DIR}"
> +
> +XDCPATH .= 
> "${XDCCGROOT}/include;${XDC_INSTALL_DIR}/packages;${SYSBIOS_INSTALL_DIR}/packages;"
> +
> +export XDCPATH
> +
> +do_compile() {
> + cd ${S}/ti/mas/swtools
> + xdc
> +}
> +
> +do_install() {
> + CP_ARGS="-Prf --preserve=mode,timestamps --no-preserve=ownership"
> + install -d ${D}${SWTOOLS_INSTALL_DIR_RECIPE}
> + cp -pPrf ${S}/* ${D}${SWTOOLS_INSTALL_DIR_RECIPE}
> +}
> +
> +FILES_${PN}-dev += "${SWTOOLS_INSTALL_DIR_RECIPE}"
> +
> +INSANE_SKIP_${PN}-dev = "arch staticdev"
> +ALLOW_EMPTY_${PN} = "1"
> -- 
> 1.9.1
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

[meta-ti] [PATCH] am335x-evm: bump leb count for UBI

[Denys Dmytriyenko]

Signed-off-by: Denys Dmytriyenko 
---
 conf/machine/am335x-evm.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/conf/machine/am335x-evm.conf b/conf/machine/am335x-evm.conf
index e54ee1de..509f2b2c 100644
--- a/conf/machine/am335x-evm.conf
+++ b/conf/machine/am335x-evm.conf
@@ -25,7 +25,7 @@ SERIAL_CONSOLES_CHECK = "${SERIAL_CONSOLES}"
 # UBI: logical eraseblock size:126976 bytes
 # from ubiattach stdout:
 # UBI device number 0, total 1988 LEBs
-MKUBIFS_ARGS = "-F -m 2048 -e 126976 -c 8000"
+MKUBIFS_ARGS = "-F -m 2048 -e 126976 -c 8200"
 
 # do ubiattach /dev/ubi_ctrl -m 7 -O 2048
 # from dmesg:
-- 
2.17.1

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

[meta-ti] [PATCH] arm-trusted-firmware: update to sync up with latest master

[Denys Dmytriyenko]

Signed-off-by: Denys Dmytriyenko 
---
 recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_1.5.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_1.5.bb 
b/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_1.5.bb
index 27b1591f..fdbf8f14 100644
--- a/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_1.5.bb
+++ b/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_1.5.bb
@@ -22,7 +22,7 @@ PV_append = "+git${SRCPV}"
 BRANCH = "ti-atf"
 SRC_URI = "git://git.ti.com/atf/arm-trusted-firmware.git;branch=${BRANCH}"
 
-SRCREV ?= "516abc5fb4826e28be0acdbe6e22fd1b1b476c59"
+SRCREV ?= "d7b4c6e1fdb4553fc23a02776bca111bdcdf6b9f"
 
 # Make ATF "aware" of OPTEE, no build dependency
 PACKAGECONFIG[optee] = "SPD=opteed"
-- 
2.17.1

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] musb_hdrc driver and "Qualcomm, Inc. Gobi Wireless Modem"

[Denys Dmytriyenko]

On Thu, Sep 13, 2018 at 01:05:17PM -0700, Leo Meza wrote:
> I'm trying to get my target to recognize a USB-connected 4G LTE modem on
> powerup
> 
> My target is a beaglebone black (AM335x) using meta-ti "rocko" branch and

What's your distro and specifically, what init system and device management? 
I.e. SysVinit, udev, systemd, etc.

-- 
Denys


> I've added a kernel config fragment with the following:
> CONFIG_USB_NET_QMI_WWAN=m
> 
> My distro.conf file removes the usbgadget and usbhost features:
> MACHINE_FEATURES_remove += " alsa usbgadget usbhost vfat"
> 
> So far, when I power up the target, it looks as though the musb-hdrc driver
> is attaching to the USB Modem:
> [   15.467735] usbcore: registered new interface driver usbfs
> [   15.475891] am335x-phy-driver 47401300.usb-phy: 47401300.usb-phy supply
> vcc not found, using dummy regulator
> [   15.483431] am335x-phy-driver 47401b00.usb-phy: 47401b00.usb-phy supply
> vcc not found, using dummy regulator
> [   15.625497] pruss 4a30.pruss: creating PRU cores and other child
> platform devices
> [   15.639846] usbcore: registered new interface driver hub
> [   15.718440] usbcore: registered new device driver usb
> [   15.831900] remoteproc remoteproc1: 4a334000.pru is available
> [   15.837767] pru-rproc 4a334000.pru: PRU rproc node
> /ocp/pruss_soc_bus@4a326004/pruss@0/pru@34000 probed successfully
> [   15.867980] musb-hdrc musb-hdrc.1: MUSB HDRC host driver
> [   15.868016] musb-hdrc musb-hdrc.1: new USB bus registered, assigned bus
> number 1
> [   15.883041] hub 1-0:1.0: USB hub found
> [   15.883105] hub 1-0:1.0: 1 port detected
> [   15.961998] remoteproc remoteproc2: 4a338000.pru is available
> [   15.967859] pru-rproc 4a338000.pru: PRU rproc node
> /ocp/pruss_soc_bus@4a326004/pruss@0/pru@38000 probed successfully
> [   16.320431] usb 1-1: new high-speed USB device number 2 using musb-hdrc
> [   53.040523] random: crng init done
> [   53.044007] random: 7 urandom warning(s) missed due to ratelimiting
> 
> When I use "lsusb" I see this, and I'm unable to use the modem:
> Bus 001 Device 002: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL
> mode)
> 
> LSMOD shows this:
> root@target:~# lsmod
> Module  Size  Used by
> pru_rproc  20480  0
> musb_dsps  20480  0
> pruss_intc 16384  1 pru_rproc
> musb_hdrc  98304  1 musb_dsps
> udc_core   28672  1 musb_hdrc
> pruss  16384  1 pru_rproc
> phy_am335x 16384  2
> usbcore   204800  1 musb_hdrc
> phy_generic16384  1 phy_am335x
> usb_common 16384  5
> phy_am335x,udc_core,musb_hdrc,musb_dsps,usbcore
> phy_am335x_control 16384  1 phy_am335x
> pm33xx 16384  0
> snd_soc_simple_card16384  0
> snd_soc_simple_card_utils16384  1 snd_soc_simple_card
> wkup_m3_rproc  16384  1
> wkup_m3_ipc16384  1 pm33xx
> remoteproc 40960  3 pru_rproc,wkup_m3_rproc,wkup_m3_ipc
> omap_aes_driver24576  0
> crypto_engine  16384  1 omap_aes_driver
> omap_crypto16384  1 omap_aes_driver
> omap_sham  28672  0
> ti_emif_sram   16384  1 pm33xx
> pruss_soc_bus  16384  0
> rtc_omap   20480  2
> musb_am335x16384  0
> omap_wdt   16384  0
> at24   16384  0
> sch_fq_codel   20480  1
> 
> However, if I don't plug in the device until AFTER the system boots and I
> login, then I see the cdc_wdm driver is gets registered and the cdc-wdm0
> device is created:
> 
> root@target:~# [   60.630559] usb 1-1: new high-speed USB device number 2
> using musb-hdrc
> [   60.993246] usbcore: registered new interface driver cdc_wdm
> [   61.013436] qmi_wwan 1-1:1.2: cdc-wdm0: USB WDM device
> [   61.038279] qmi_wwan 1-1:1.2 wwan0: register 'qmi_wwan' at
> usb-musb-hdrc.1-1, WWAN/QMI device, be:ce:e7:34:15:d8
> [   61.059967] usbcore: registered new interface driver qmi_wwan
> 
> LSUSB shows me this, and I'm able to use the modem:
> 
> root@target:~# lsusb
> Bus 001 Device 002: ID 1bc7:1040 Telit Wireless Solutions
> 
> LSMOD shows this:
> 
> root@target:~# lsmod
> Module  Size  Used by
> qmi_wwan   28672  0
> cdc_wdm20480  1 qmi_wwan
> usbnet 32768  1 qmi_wwan
> pru_rproc  20480  0
> pruss_intc 16384  1 pru_rproc
> pruss  16384  1 pru_rproc
> musb_dsps  20480  0
> musb_hdrc  98304  1 musb_dsps
> udc_core   28672  1 musb_hdrc
> usbcore   204800  4 usbnet,qmi_wwan,cdc_wdm,musb_hdrc
> phy_am335x 1[   78.790878] random: crng init done
> [   78.799335] random: 7 urandom warning(s) missed due to ratelimiting
> 6384  2
> phy_generic16384  1 phy_am335x
> usb_common 16384  5
> phy_am335x,udc_core,musb_hdrc,musb_dsps,usbcore
> phy_am335x_control 16384  1 phy_am335x
> pm3

Re: [meta-ti] [EXTERNAL] [PATCH 3/3 v2] Added DSPLIB recipe to build DSPLIB from source. Updated includes/ti-paths.inc for MATHLIB and DSPLIB.

[Denys Dmytriyenko]

https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines


On Thu, Sep 13, 2018 at 05:20:04PM -0400, Xu, Jianzhong wrote:
>Denys,
> 
>Thanks for the cleaned up patches. I applied those patches and removed
>COMPATIBLE_MACHINE and resubmitted. 
> 
>Regards,
> 
>Jianzhong
> 
>  --
> 
>From: meta-ti-boun...@yoctoproject.org 
>on behalf of Dmytriyenko, Denys
>Sent: Thursday, September 13, 2018 2:35 PM
>To: Stiffler, Jacob
>Cc: meta-ti@yoctoproject.org
>Subject: Re: [meta-ti] [EXTERNAL] [PATCH 3/3 v2] Added DSPLIB recipe to
>build DSPLIB from source. Updated includes/ti-paths.inc for MATHLIB and
>DSPLIB.
> 
>Jake, Jianzhong,
> 
>I have re-posted the cleaned up patches I had in rocko-next. Please use
>those
>for fixing the COMPATIBLE_MACHINE issue. For now I'll drop them, as I need
>rocko-next freed up.
> 
>Denys
> 
>On Thu, Sep 13, 2018 at 12:34:40PM -0400, Denys Dmytriyenko wrote:
>> On Thu, Sep 13, 2018 at 12:01:32PM -0400, Stiffler, Jacob wrote:
>> >That will work as c66x is a subset of the keystone SOC family.
>> >
>> >
>> >
>> >I just don’t think that specifying COMPATIBLE_MACHINE is necessary
>as
>> >these packages are independent of the architecture that is running
>Linux.
>>
>> Agree.
>>
>>
>> >And due to this, we should also remove the ‘PACKAGE_ARCH =
>> >${MACHINE_ARCH}”’ as there is no difference between the resulting
>packages
>> >for any machine.
>>
>> Also agree.
>>
>>
>> >IMHO, COMPATIBLE_MACHINE has been overused and it creates more
>problems
>> >that it solves.
>>
>> I've been saying this for years! Still, the response from developers was
>that
>> they only tested it on one platform, hence it's only compatible with
>this one
>> platform...
>>
>>
>> Jake,
>>
>> Please work with your team to explain this and stop abusing
>COMPATIBLE_MACHINE
>> variable. We'll also need to work with RTOS team for the same...
>>
>> --
>> Denys
>>
>>
>> >
>> >
>> >
>> >- Jake
>> >
>> >
>> >
>> >From: Xu, Jianzhong
>> >Sent: Thursday, September 13, 2018 11:45 AM
>> >To: Dmytriyenko, Denys; Stiffler, Jacob
>> >Cc: meta-ti@yoctoproject.org
>> >Subject: Re: [meta-ti] [EXTERNAL] [PATCH 3/3 v2] Added DSPLIB
>recipe to
>> >build DSPLIB from source. Updated includes/ti-paths.inc for MATHLIB
>and
>> >DSPLIB.
>> >
>> >
>> >
>> >Denys,
>> >
>> >
>> >
>> >Would the following fix the problems you've seen:
>> >
>> >
>> >
>> >COMPATIBLE_MACHINE = "omap-a15|keystone"
>> >
>> >
>> >
>> >This was in DSPLIB recipes before.
>> >
>> >
>> >
>> >Thanks,
>> >
>> >Jianzhong
>> >
>> >
>
>> >
>> >From: Dmytriyenko, Denys
>> >Sent: Thursday, September 13, 2018 11:26:45 AM
>> >To: Stiffler, Jacob
>> >Cc: Xu, Jianzhong; meta-ti@yoctoproject.org
>> >Subject: Re: [meta-ti] [EXTERNAL] [PATCH 3/3 v2] Added DSPLIB
>recipe to
>> >build DSPLIB from source. Updated includes/ti-paths.inc for MATHLIB
>and
>> >DSPLIB.
>> >
>> >
>> >
>> >On Thu, Sep 13, 2018 at 07:26:12AM -0400, Jacob Stiffler wrote:
>> >>
>> >>
>> >> On 9/12/2018 6:52 PM, Denys Dmytriyenko wrote:
>> >> >Same for dra7xx-evm...
>> >> >
>> >> >
>> >> >On Wed, Sep 12, 2018 at 04:37:48PM -0400, Dmytriyenko, Denys
>wrote:
>> >> >>And it crashed and burned right away:
>> >> >>
>

Re: [meta-ti] [EXTERNAL] [PATCH 3/3 v2] Added DSPLIB recipe to build DSPLIB from source. Updated includes/ti-paths.inc for MATHLIB and DSPLIB.

[Denys Dmytriyenko]

Jake, Jianzhong,

I have re-posted the cleaned up patches I had in rocko-next. Please use those 
for fixing the COMPATIBLE_MACHINE issue. For now I'll drop them, as I need 
rocko-next freed up.

Denys


On Thu, Sep 13, 2018 at 12:34:40PM -0400, Denys Dmytriyenko wrote:
> On Thu, Sep 13, 2018 at 12:01:32PM -0400, Stiffler, Jacob wrote:
> >That will work as c66x is a subset of the keystone SOC family.
> > 
> > 
> > 
> >I just don’t think that specifying COMPATIBLE_MACHINE is necessary as
> >these packages are independent of the architecture that is running Linux.
> 
> Agree.
> 
> 
> >And due to this, we should also remove the ‘PACKAGE_ARCH =
> >${MACHINE_ARCH}”’ as there is no difference between the resulting 
> > packages
> >for any machine.
> 
> Also agree.
> 
> 
> >IMHO, COMPATIBLE_MACHINE has been overused and it creates more problems
> >that it solves.
> 
> I've been saying this for years! Still, the response from developers was that 
> they only tested it on one platform, hence it's only compatible with this one 
> platform...
> 
> 
> Jake,
> 
> Please work with your team to explain this and stop abusing 
> COMPATIBLE_MACHINE 
> variable. We'll also need to work with RTOS team for the same...
> 
> -- 
> Denys
> 
> 
> > 
> > 
> > 
> >- Jake
> > 
> > 
> > 
> >From: Xu, Jianzhong
> >Sent: Thursday, September 13, 2018 11:45 AM
> >To: Dmytriyenko, Denys; Stiffler, Jacob
> >Cc: meta-ti@yoctoproject.org
> >Subject: Re: [meta-ti] [EXTERNAL] [PATCH 3/3 v2] Added DSPLIB recipe to
> >build DSPLIB from source. Updated includes/ti-paths.inc for MATHLIB and
> >DSPLIB.
> > 
> > 
> > 
> >Denys,
> > 
> > 
> > 
> >Would the following fix the problems you've seen:
> > 
> > 
> > 
> >COMPATIBLE_MACHINE = "omap-a15|keystone"
> > 
> > 
> > 
> >This was in DSPLIB recipes before. 
> > 
> > 
> > 
> >Thanks,
> > 
> >Jianzhong
> > 
> > 
> > 
> >From: Dmytriyenko, Denys
> >Sent: Thursday, September 13, 2018 11:26:45 AM
> >To: Stiffler, Jacob
> >Cc: Xu, Jianzhong; meta-ti@yoctoproject.org
> >Subject: Re: [meta-ti] [EXTERNAL] [PATCH 3/3 v2] Added DSPLIB recipe to
> >build DSPLIB from source. Updated includes/ti-paths.inc for MATHLIB and
> >DSPLIB.
> > 
> > 
> > 
> >On Thu, Sep 13, 2018 at 07:26:12AM -0400, Jacob Stiffler wrote:
> >>
> >>
> >> On 9/12/2018 6:52 PM, Denys Dmytriyenko wrote:
> >> >Same for dra7xx-evm...
> >> >
> >> >
> >> >On Wed, Sep 12, 2018 at 04:37:48PM -0400, Dmytriyenko, Denys wrote:
> >> >>And it crashed and burned right away:
> >> >>
> >> >>ERROR: Nothing PROVIDES 'dsplib-c66x' (but
> >
> > /OE/arago-rocko-next-build/sources/meta-arago/meta-arago-extras/recipes-apps/video-analytics-demo/qt-opencv-opencl-opengl-multithreaded_git.bb
> >DEPENDS on or otherwise requires it)
> >> >>dsplib-c66x was skipped: incompatible with machine am57xx-hs-evm (not
> >in COMPATIBLE_MACHINE)
> >> >>NOTE: Runtime target 'qt-opencv-opencl-opengl-multithreaded-src' is
> >unbuildable, removing...
> >> >>
> >> >>Jake,
> >    > >>
> >> >>Did you tested it on am57xx-hs-evm?
> >>
> >> I had only built for am57xx-evm as there are no machine overrides in
> >these
> >> recipes because they are DSP architecture-specific.
> >>
> >> Looks like we should change "COMPATIBLE_MACHINE" to, at the very least,
> >> include what was there before (omap-a15|keystone). But as these are
> >specific
> >> to the DSP architecture, should COMPATIBLE_MACHINE even be necessary?
> > 
> >Either way should be fine. Currently those patches break too many
> >platforms -
> >dra7 GP and both am5/dra7 HS.
> > 
> >> >>Denys
> >> >>
> >> >>
> >> >>>-Original Message-
> >> >>>From: Denys Dmytriyenko [mailto:de...@ti.com]
> >> >>>Sent: Wednes

[meta-ti] [PATCH 1/3] swtools: add version 5.0.8

[Denys Dmytriyenko]

From: Jianzhong Xu 

SWTOOLS package is a dependency for processor libs (DSPLIB, MATHLIB, etc)

Signed-off-by: Jianzhong Xu 
Signed-off-by: Denys Dmytriyenko 
---
 recipes-ti/swtools/swtools_git.bb | 44 +++
 1 file changed, 44 insertions(+)
 create mode 100644 recipes-ti/swtools/swtools_git.bb

diff --git a/recipes-ti/swtools/swtools_git.bb 
b/recipes-ti/swtools/swtools_git.bb
new file mode 100644
index ..425a0690
--- /dev/null
+++ b/recipes-ti/swtools/swtools_git.bb
@@ -0,0 +1,44 @@
+SUMMARY = "TI Software Tools"
+HOMEPAGE = "https://git.ti.com/ep-processor-libraries/swtools";
+SECTION = "devel"
+LICENSE = "BSD"
+LIC_FILES_CHKSUM = 
"file://ti/mas/swtools/copyright.txt;md5=b1f52a1435051fdb18f8885b0384147d"
+
+require ../includes/ti-paths.inc
+
+DEPENDS = "ti-cgt6x-native \
+   ti-sysbios \
+   ti-xdctools-native"
+
+PV = "5_0_8"
+PR = "r0"
+S = "${WORKDIR}/git"
+BRANCH = "master"
+SRC_URI = 
"git://git.ti.com/ep-processor-libraries/swtools.git;protocol=git;branch=${BRANCH}"
+SRCREV = "881267836907de650edadc56b8e57ab45428021d"
+
+export C64PCODEGENTOOL = "${CGTOOLS_INSTALL_DIR}"
+export C674CODEGENTOOL = "${CGTOOLS_INSTALL_DIR}"
+export C66CODEGENTOOL  = "${CGTOOLS_INSTALL_DIR}"
+
+PATH_append = ":${XDC_INSTALL_DIR}"
+
+XDCPATH .= 
"${XDCCGROOT}/include;${XDC_INSTALL_DIR}/packages;${SYSBIOS_INSTALL_DIR}/packages;"
+
+export XDCPATH
+
+do_compile() {
+   cd ${S}/ti/mas/swtools
+   xdc
+}
+
+do_install() {
+   CP_ARGS="-Prf --preserve=mode,timestamps --no-preserve=ownership"
+   install -d ${D}${SWTOOLS_INSTALL_DIR_RECIPE}
+   cp -pPrf ${S}/* ${D}${SWTOOLS_INSTALL_DIR_RECIPE}
+}
+
+FILES_${PN}-dev += "${SWTOOLS_INSTALL_DIR_RECIPE}"
+
+INSANE_SKIP_${PN}-dev = "arch staticdev"
+ALLOW_EMPTY_${PN} = "1"
-- 
2.17.1

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

[meta-ti] [PATCH 3/3] dsplib: add new recipe to build DSPLIB from source

[Denys Dmytriyenko]

From: Jianzhong Xu 

Updated includes/ti-paths.inc for MATHLIB and DSPLIB.

Signed-off-by: Jianzhong Xu 
Signed-off-by: Denys Dmytriyenko 
---
 recipes-ti/dsplib/dsplib-c64xp_git.bb|  9 +++
 recipes-ti/dsplib/dsplib-c66x.inc| 30 -
 recipes-ti/dsplib/dsplib-c66x_3.4.0.0.bb |  9 ---
 recipes-ti/dsplib/dsplib-c66x_git.bb | 10 +++
 recipes-ti/dsplib/dsplib-c674x_git.bb|  9 +++
 recipes-ti/dsplib/dsplib.inc | 77 
 recipes-ti/includes/ti-paths.inc |  8 ++-
 7 files changed, 112 insertions(+), 40 deletions(-)
 create mode 100644 recipes-ti/dsplib/dsplib-c64xp_git.bb
 delete mode 100644 recipes-ti/dsplib/dsplib-c66x.inc
 delete mode 100644 recipes-ti/dsplib/dsplib-c66x_3.4.0.0.bb
 create mode 100644 recipes-ti/dsplib/dsplib-c66x_git.bb
 create mode 100644 recipes-ti/dsplib/dsplib-c674x_git.bb
 create mode 100644 recipes-ti/dsplib/dsplib.inc

diff --git a/recipes-ti/dsplib/dsplib-c64xp_git.bb 
b/recipes-ti/dsplib/dsplib-c64xp_git.bb
new file mode 100644
index ..1038d44d
--- /dev/null
+++ b/recipes-ti/dsplib/dsplib-c64xp_git.bb
@@ -0,0 +1,9 @@
+MATHLIB_INSTALL_DIR = "${MATHLIB_C64P_INSTALL_DIR}/packages"
+DSPLIB_INSTALL_DIR_RECIPE = "${DSPLIB_C64P_INSTALL_DIR_RECIPE}"
+DSPLIB_INSTALL_DIR = "${DSPLIB_C64P_INSTALL_DIR}"
+DSPLIB_BUILD_TARGET = "c64Px"
+
+DEPENDS = ""
+
+include dsplib.inc
+
diff --git a/recipes-ti/dsplib/dsplib-c66x.inc 
b/recipes-ti/dsplib/dsplib-c66x.inc
deleted file mode 100644
index 7ff99c2e..
--- a/recipes-ti/dsplib/dsplib-c66x.inc
+++ /dev/null
@@ -1,30 +0,0 @@
-DESCRIPTION = "DSPLIB contains optimized general-purpose signal-processing 
routines for TI DSPs"
-HOMEPAGE = "http://www.ti.com/tool/sprc265";
-SECTION = "devel"
-LICENSE = "BSD-3-Clause"
-
-require ../includes/ti-paths.inc
-require ../includes/ti-staging.inc
-require ../includes/ti-unpack.inc
-
-COMPATIBLE_MACHINE = "omap-a15|keystone"
-
-SRC_URI = 
"http://software-dl.ti.com/sdoemb/sdoemb_public_sw/dsplib/${PV}/exports/${BINFILE};name=dsplib";
-
-BINFILE = "dsplib_c66x_${PV}_Linux.bin"
-TI_BIN_UNPK_ARGS = "--mode silent --prefix ${S}"
-TI_BIN_UNPK_CMDS = ""
-
-do_install() {
-CP_ARGS="-Prf --preserve=mode,timestamps --no-preserve=ownership"
-install -d ${D}${DSPLIB_C66_INSTALL_DIR_RECIPE}
-cp ${CP_ARGS} ${S}/* ${D}${DSPLIB_C66_INSTALL_DIR_RECIPE}
-}
-
-ALLOW_EMPTY_${PN} = "1"
-FILES_${PN}-dev += "${DSPLIB_C66_INSTALL_DIR_RECIPE}"
-
-INHIBIT_PACKAGE_STRIP = "1"
-INHIBIT_SYSROOT_STRIP = "1"
-INHIBIT_PACKAGE_DEBUG_SPLIT = "1"
-INSANE_SKIP_${PN}-dev = "arch"
diff --git a/recipes-ti/dsplib/dsplib-c66x_3.4.0.0.bb 
b/recipes-ti/dsplib/dsplib-c66x_3.4.0.0.bb
deleted file mode 100644
index f1273f3b..
--- a/recipes-ti/dsplib/dsplib-c66x_3.4.0.0.bb
+++ /dev/null
@@ -1,9 +0,0 @@
-require dsplib-c66x.inc
-
-PV = "3_4_0_0"
-PR = "r1"
-
-LIC_FILES_CHKSUM = 
"file://packages/ti/dsplib/dsplib.h;beginline=9;endline=35;md5=17733f9e1100f8a628512f47c4bf676a"
-
-SRC_URI[dsplib.md5sum] = "66785604729c153dcad5282097dee8bf"
-SRC_URI[dsplib.sha256sum] = 
"e88909b6271ce6c4c62e2ab90181b7adb36c7f28f5c52836668eb35888785ce8"
diff --git a/recipes-ti/dsplib/dsplib-c66x_git.bb 
b/recipes-ti/dsplib/dsplib-c66x_git.bb
new file mode 100644
index ..cbc25d0e
--- /dev/null
+++ b/recipes-ti/dsplib/dsplib-c66x_git.bb
@@ -0,0 +1,10 @@
+MATHLIB_INSTALL_DIR = "${MATHLIB_C66_INSTALL_DIR}/packages"
+DSPLIB_INSTALL_DIR_RECIPE = "${DSPLIB_C66_INSTALL_DIR_RECIPE}"
+DSPLIB_INSTALL_DIR = "${DSPLIB_C66_INSTALL_DIR}"
+DSPLIB_BUILD_TARGET = "c66x"
+
+DEPENDS = "mathlib-c66x"
+
+include dsplib.inc
+
+
diff --git a/recipes-ti/dsplib/dsplib-c674x_git.bb 
b/recipes-ti/dsplib/dsplib-c674x_git.bb
new file mode 100644
index ..07c68922
--- /dev/null
+++ b/recipes-ti/dsplib/dsplib-c674x_git.bb
@@ -0,0 +1,9 @@
+MATHLIB_INSTALL_DIR = "${MATHLIB_C674_INSTALL_DIR}/packages"
+DSPLIB_INSTALL_DIR_RECIPE = "${DSPLIB_C674_INSTALL_DIR_RECIPE}"
+DSPLIB_INSTALL_DIR = "${DSPLIB_C674_INSTALL_DIR}"
+DSPLIB_BUILD_TARGET = "c674x"
+
+DEPENDS = "mathlib-c674x"
+
+include dsplib.inc
+
diff --git a/recipes-ti/dsplib/dsplib.inc b/recipes-ti/dsplib/dsplib.inc
new file mode 100644
index ..fc2970c4
--- /dev/null
+++ b/recipes-ti/dsplib/dsplib.inc
@@ -0,0 +1,77 @@
+SUMMARY = "DSPLIB contains optimized signal processing functions for TI DSPs"
+HOMEPAGE = "http://git.ti.com/ep-processor-libraries/dsplib";
+LICENSE = "BSD-3-Clause"
+
+require ../includes/ti-paths.inc
+
+PV = "3_4_0_1"
+PR = "r0"
+
+COMPATIBLE_MACHINE = "am57xx-evm|keystone|c66x|omapl1"
+
+DEPEN

[meta-ti] [PATCH 2/3] mathlib: add new recipe to build MATHLIB from source

[Denys Dmytriyenko]

From: Jianzhong Xu 

Signed-off-by: Jianzhong Xu 
Signed-off-by: Denys Dmytriyenko 
---
 recipes-ti/mathlib/mathlib-c66x.inc| 29 
 recipes-ti/mathlib/mathlib-c66x_3.1.1.0.bb |  9 ---
 recipes-ti/mathlib/mathlib-c66x_git.bb |  6 ++
 recipes-ti/mathlib/mathlib-c674x_git.bb|  5 ++
 recipes-ti/mathlib/mathlib.inc | 77 ++
 5 files changed, 88 insertions(+), 38 deletions(-)
 delete mode 100644 recipes-ti/mathlib/mathlib-c66x.inc
 delete mode 100644 recipes-ti/mathlib/mathlib-c66x_3.1.1.0.bb
 create mode 100644 recipes-ti/mathlib/mathlib-c66x_git.bb
 create mode 100644 recipes-ti/mathlib/mathlib-c674x_git.bb
 create mode 100644 recipes-ti/mathlib/mathlib.inc

diff --git a/recipes-ti/mathlib/mathlib-c66x.inc 
b/recipes-ti/mathlib/mathlib-c66x.inc
deleted file mode 100644
index 7951e6ca..
--- a/recipes-ti/mathlib/mathlib-c66x.inc
+++ /dev/null
@@ -1,29 +0,0 @@
-DESCRIPTION = "MATHLIB contains optimized general-purpose signal-processing 
routines for TI DSPs"
-HOMEPAGE = "http://www.ti.com/tool/mathlib";
-SECTION = "devel"
-LICENSE = "BSD-3-Clause"
-
-require ../includes/ti-paths.inc
-require ../includes/ti-staging.inc
-require ../includes/ti-unpack.inc
-
-COMPATIBLE_MACHINE = "omap-a15|keystone"
-
-SRC_URI = 
"http://software-dl.ti.com/sdoemb/sdoemb_public_sw/mathlib/${PV}/exports/${BINFILE};name=mathlib";
-
-S = "${WORKDIR}/mathlib-c66x-${PV}"
-
-BINFILE = "mathlib_c66x_${PV}_Linux.bin"
-TI_BIN_UNPK_ARGS = "--mode silent --prefix ${S}"
-TI_BIN_UNPK_CMDS = ""
-
-do_install() {
-CP_ARGS="-Prf --preserve=mode,timestamps --no-preserve=ownership"
-install -d ${D}${MATHLIB_C66_INSTALL_DIR_RECIPE}
-cp ${CP_ARGS} ${S}/* ${D}${MATHLIB_C66_INSTALL_DIR_RECIPE}
-}
-
-ALLOW_EMPTY_${PN} = "1"
-FILES_${PN}-dev += "${MATHLIB_C66_INSTALL_DIR_RECIPE}"
-
-INSANE_SKIP_${PN}-dev = "arch"
diff --git a/recipes-ti/mathlib/mathlib-c66x_3.1.1.0.bb 
b/recipes-ti/mathlib/mathlib-c66x_3.1.1.0.bb
deleted file mode 100644
index 50746fb9..
--- a/recipes-ti/mathlib/mathlib-c66x_3.1.1.0.bb
+++ /dev/null
@@ -1,9 +0,0 @@
-require mathlib-c66x.inc
-
-PV = "3_1_1_0"
-PR = "r1"
-
-LIC_FILES_CHKSUM = 
"file://packages/ti/mathlib/mathlib.h;beginline=9;endline=35;md5=954ed7074e987be574989f985f1897db"
-
-SRC_URI[mathlib.md5sum] = "f3c9ad06dfcea780b5362c57a4bc48b8"
-SRC_URI[mathlib.sha256sum] = 
"85df897c94e8768e9a1f186c21702ed3887d39cda6dc67cb4580fa3f083e8925"
diff --git a/recipes-ti/mathlib/mathlib-c66x_git.bb 
b/recipes-ti/mathlib/mathlib-c66x_git.bb
new file mode 100644
index ..28bf8c6e
--- /dev/null
+++ b/recipes-ti/mathlib/mathlib-c66x_git.bb
@@ -0,0 +1,6 @@
+MATHLIB_BUILD_TARGET = "c66x"
+MATHLIB_INSTALL_DIR_RECIPE = "${MATHLIB_C66_INSTALL_DIR_RECIPE}"
+MATHLIB_INSTALL_DIR = "${MATHLIB_C66_INSTALL_DIR}"
+
+include mathlib.inc
+
diff --git a/recipes-ti/mathlib/mathlib-c674x_git.bb 
b/recipes-ti/mathlib/mathlib-c674x_git.bb
new file mode 100644
index ..8c042bbf
--- /dev/null
+++ b/recipes-ti/mathlib/mathlib-c674x_git.bb
@@ -0,0 +1,5 @@
+MATHLIB_BUILD_TARGET = "c674x"
+MATHLIB_INSTALL_DIR_RECIPE = "${MATHLIB_C674_INSTALL_DIR_RECIPE}"
+MATHLIB_INSTALL_DIR = "${MATHLIB_C674_INSTALL_DIR}"
+
+include mathlib.inc
diff --git a/recipes-ti/mathlib/mathlib.inc b/recipes-ti/mathlib/mathlib.inc
new file mode 100644
index ..ccb1de60
--- /dev/null
+++ b/recipes-ti/mathlib/mathlib.inc
@@ -0,0 +1,77 @@
+SUMMARY = "MATHLIB contains optimized floating-point math functions for TI 
DSPs"
+HOMEPAGE = "http://git.ti.com/ep-processor-libraries/mathlib";
+LICENSE = "BSD-3-Clause"
+
+require ../includes/ti-paths.inc
+
+PV = "3_1_2_2"
+PR = "r0"
+
+COMPATIBLE_MACHINE = "am57xx-evm|keystone|c66x|omapl1"
+
+DEPENDS = "ti-cgt6x-native \
+   ti-xdctools-native \
+   ti-sysbios \
+   doxygen-native \
+   zip-native \
+   swtools "
+
+S = "${WORKDIR}/git"
+
+SRC_URI = 
"git://git.ti.com/ep-processor-libraries/mathlib.git;protocol=git;branch=master"
+SRCREV = "195355db20f53295cfeef0bcfba0a8d8fdb0a753"
+
+LIC_FILES_CHKSUM = 
"file://ti/mathlib/src/acosdp/acosdp.h;beginline=1;endline=35;md5=c133f7e139b46385906c861dd9552250"
+
+export MATHLIB_WORK_DIR="${S}"
+export CGTOOLS_INSTALL_DIR  = "${STAGING_DIR_NATIVE}/usr/share/ti/cgt-c6x"
+export C64PCODEGENTOOL="${CGTOOLS_INSTALL_DIR}"
+export C674CODEGENTOOL="${CGTOOLS_INSTALL_DIR}"
+export C66CODEGENTOOL ="${CGTOOLS_INSTALL_DIR}"
+export SWTOOLS_PATH = "${SWTOOLS_INSTALL_DIR}/ti/mas/swtools"
+export XDCBUILDCFG="${SWTOOLS_PATH}/config.bld"
+
+PATH_append = &

Re: [meta-ti] [EXTERNAL] [PATCH 3/3 v2] Added DSPLIB recipe to build DSPLIB from source. Updated includes/ti-paths.inc for MATHLIB and DSPLIB.

[Denys Dmytriyenko]

On Thu, Sep 13, 2018 at 12:01:32PM -0400, Stiffler, Jacob wrote:
>That will work as c66x is a subset of the keystone SOC family.
> 
> 
> 
>I just don’t think that specifying COMPATIBLE_MACHINE is necessary as
>these packages are independent of the architecture that is running Linux.

Agree.


>And due to this, we should also remove the ‘PACKAGE_ARCH =
>${MACHINE_ARCH}”’ as there is no difference between the resulting packages
>for any machine.

Also agree.


>IMHO, COMPATIBLE_MACHINE has been overused and it creates more problems
>that it solves.

I've been saying this for years! Still, the response from developers was that 
they only tested it on one platform, hence it's only compatible with this one 
platform...


Jake,

Please work with your team to explain this and stop abusing COMPATIBLE_MACHINE 
variable. We'll also need to work with RTOS team for the same...

-- 
Denys


> 
> 
> 
>- Jake
> 
> 
> 
>From: Xu, Jianzhong
>Sent: Thursday, September 13, 2018 11:45 AM
>To: Dmytriyenko, Denys; Stiffler, Jacob
>Cc: meta-ti@yoctoproject.org
>Subject: Re: [meta-ti] [EXTERNAL] [PATCH 3/3 v2] Added DSPLIB recipe to
>build DSPLIB from source. Updated includes/ti-paths.inc for MATHLIB and
>DSPLIB.
> 
> 
> 
>Denys,
> 
> 
> 
>Would the following fix the problems you've seen:
> 
> 
> 
>COMPATIBLE_MACHINE = "omap-a15|keystone"
> 
> 
> 
>This was in DSPLIB recipes before. 
> 
> 
> 
>Thanks,
> 
>Jianzhong
> 
> 
> 
>From: Dmytriyenko, Denys
>Sent: Thursday, September 13, 2018 11:26:45 AM
>To: Stiffler, Jacob
>Cc: Xu, Jianzhong; meta-ti@yoctoproject.org
>Subject: Re: [meta-ti] [EXTERNAL] [PATCH 3/3 v2] Added DSPLIB recipe to
>build DSPLIB from source. Updated includes/ti-paths.inc for MATHLIB and
>DSPLIB.
> 
> 
> 
>On Thu, Sep 13, 2018 at 07:26:12AM -0400, Jacob Stiffler wrote:
>>
>>
>> On 9/12/2018 6:52 PM, Denys Dmytriyenko wrote:
>> >Same for dra7xx-evm...
>> >
>> >
>> >On Wed, Sep 12, 2018 at 04:37:48PM -0400, Dmytriyenko, Denys wrote:
>> >>And it crashed and burned right away:
>> >>
>> >>ERROR: Nothing PROVIDES 'dsplib-c66x' (but
>
> /OE/arago-rocko-next-build/sources/meta-arago/meta-arago-extras/recipes-apps/video-analytics-demo/qt-opencv-opencl-opengl-multithreaded_git.bb
>DEPENDS on or otherwise requires it)
>> >>dsplib-c66x was skipped: incompatible with machine am57xx-hs-evm (not
>in COMPATIBLE_MACHINE)
>> >>NOTE: Runtime target 'qt-opencv-opencl-opengl-multithreaded-src' is
>unbuildable, removing...
>> >>
>> >>Jake,
>> >>
>> >>Did you tested it on am57xx-hs-evm?
>>
>> I had only built for am57xx-evm as there are no machine overrides in
>these
>> recipes because they are DSP architecture-specific.
>>
>> Looks like we should change "COMPATIBLE_MACHINE" to, at the very least,
>> include what was there before (omap-a15|keystone). But as these are
>specific
>> to the DSP architecture, should COMPATIBLE_MACHINE even be necessary?
> 
>Either way should be fine. Currently those patches break too many
>platforms -
>dra7 GP and both am5/dra7 HS.
> 
>> >>Denys
>> >>
>> >>
>> >>>-Original Message-
>> >>>From: Denys Dmytriyenko [mailto:de...@ti.com]
>> >>>Sent: Wednesday, September 12, 2018 4:21 PM
>> >>>To: Xu, Jianzhong
>> >>>Cc: Stiffler, Jacob; meta-ti@yoctoproject.org
>> >>>Subject: Re: [meta-ti] [EXTERNAL] [PATCH 3/3 v2] Added DSPLIB recipe
>to build
>> >>>DSPLIB from source. Updated includes/ti-paths.inc for MATHLIB and
>DSPLIB.
>> >>>
>> >>>Thanks, merged into rocko-next for testing.
>> >>>
>> >>>There were lots of small non-critical things I had to fix, like
>whitespaces,
>> >>>indentation, etc. But the biggest one is that you have to follow
>OpenEmbedded
>> >>>Commit Message Guidelines:
>> >>>
>> >>>https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
>> >>>

Re: [meta-ti] [EXTERNAL] [PATCH 3/3 v2] Added DSPLIB recipe to build DSPLIB from source. Updated includes/ti-paths.inc for MATHLIB and DSPLIB.

[Denys Dmytriyenko]

On Thu, Sep 13, 2018 at 07:26:12AM -0400, Jacob Stiffler wrote:
> 
> 
> On 9/12/2018 6:52 PM, Denys Dmytriyenko wrote:
> >Same for dra7xx-evm...
> >
> >
> >On Wed, Sep 12, 2018 at 04:37:48PM -0400, Dmytriyenko, Denys wrote:
> >>And it crashed and burned right away:
> >>
> >>ERROR: Nothing PROVIDES 'dsplib-c66x' (but 
> >>/OE/arago-rocko-next-build/sources/meta-arago/meta-arago-extras/recipes-apps/video-analytics-demo/qt-opencv-opencl-opengl-multithreaded_git.bb
> >> DEPENDS on or otherwise requires it)
> >>dsplib-c66x was skipped: incompatible with machine am57xx-hs-evm (not in 
> >>COMPATIBLE_MACHINE)
> >>NOTE: Runtime target 'qt-opencv-opencl-opengl-multithreaded-src' is 
> >>unbuildable, removing...
> >>
> >>Jake,
> >>
> >>Did you tested it on am57xx-hs-evm?
> 
> I had only built for am57xx-evm as there are no machine overrides in these
> recipes because they are DSP architecture-specific.
> 
> Looks like we should change "COMPATIBLE_MACHINE" to, at the very least,
> include what was there before (omap-a15|keystone). But as these are specific
> to the DSP architecture, should COMPATIBLE_MACHINE even be necessary?

Either way should be fine. Currently those patches break too many platforms - 
dra7 GP and both am5/dra7 HS.


> >>Denys
> >>
> >>
> >>>-Original Message-
> >>>From: Denys Dmytriyenko [mailto:de...@ti.com]
> >>>Sent: Wednesday, September 12, 2018 4:21 PM
> >>>To: Xu, Jianzhong
> >>>Cc: Stiffler, Jacob; meta-ti@yoctoproject.org
> >>>Subject: Re: [meta-ti] [EXTERNAL] [PATCH 3/3 v2] Added DSPLIB recipe to 
> >>>build
> >>>DSPLIB from source. Updated includes/ti-paths.inc for MATHLIB and DSPLIB.
> >>>
> >>>Thanks, merged into rocko-next for testing.
> >>>
> >>>There were lots of small non-critical things I had to fix, like 
> >>>whitespaces,
> >>>indentation, etc. But the biggest one is that you have to follow 
> >>>OpenEmbedded
> >>>Commit Message Guidelines:
> >>>
> >>>https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
> >>>
> >>>
> >>>On Wed, Sep 12, 2018 at 03:40:42PM -0400, Xu, Jianzhong wrote:
> >>>>Denys,
> >>>>
> >>>>
> >>>>
> >>>>You're right. The versioning was inconsistent. Please use
> >>>>[EXTERNAL,3/3,v2] and newer versions of [EXTERNAL,2/3], 
> >>>> [EXTERNAL,1/3].
> >>>>The latter two should have had v2 in it. Please see highlights below.
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> ++
> >>>>|[EXTERNAL,3/3,v2] Added DSPLIB recipe to   |  |
> >>>> ||   |
> >>>>|build DSPLIB from source. Updated  |2018-09-06|Jianzhong 
> >>>> Xu||New|
> >>>>|includes/ti-paths.inc for MATHLIB and  |  |
> >>>> ||   |
> >>>>|DSPLIB.|  |
> >>>> ||   |
> >>>>
> >>>> |---+--+++---|
> >>>>|[EXTERNAL] Added DSPLIB recipe to build|  |
> >>>> ||   |
> >>>>|DSPLIB from source. Updated|2018-09-06|Jianzhong 
> >>>> Xu||New|
> >>>>|includes/ti-paths.inc for MATHLIB and  |  |
> >>>> ||   |
> >>>>|DSPLIB.|  |
> >>>> ||   |
> >>>>
> >>>> |---+--+++---|
> >>>>|[EXTERNAL,3/3] Added DSPLIB recipe to build|2018-09-04|Jianzhong
> >>>Xu||New|
> >>>>|DSPLIB from source.|  |
> >>>> ||   |
> >>>>
> >>>> |---+--+++---|
> >>>>|[EXTERNAL,2/3] Added MATHLIB recipe to |2018-09-04|Jianzhong
> >>>Xu||New|
> >>>>|build MATHLIB from source. |  |
> >>>> ||   |
> >>>>   

Re: [meta-ti] [EXTERNAL] [PATCH 3/3 v2] Added DSPLIB recipe to build DSPLIB from source. Updated includes/ti-paths.inc for MATHLIB and DSPLIB.

[Denys Dmytriyenko]

I don't know what you mean by "tried". Yes, am57xx-evm built fine. I don't 
build c6x platforms.


On Thu, Sep 13, 2018 at 11:24:55AM -0400, Xu, Jianzhong wrote:
> Hi Denys,
> 
> Have you tried am57xx-evm or c667x-evm? 
> 
> Thanks,
> Jianzhong
> 
> -Original Message-
> From: Stiffler, Jacob 
> Sent: Thursday, September 13, 2018 7:26 AM
> To: Dmytriyenko, Denys; Xu, Jianzhong
> Cc: meta-ti@yoctoproject.org
> Subject: Re: [meta-ti] [EXTERNAL] [PATCH 3/3 v2] Added DSPLIB recipe to build 
> DSPLIB from source. Updated includes/ti-paths.inc for MATHLIB and DSPLIB.
> 
> 
> 
> On 9/12/2018 6:52 PM, Denys Dmytriyenko wrote:
> > Same for dra7xx-evm...
> >
> >
> > On Wed, Sep 12, 2018 at 04:37:48PM -0400, Dmytriyenko, Denys wrote:
> >> And it crashed and burned right away:
> >>
> >> ERROR: Nothing PROVIDES 'dsplib-c66x' (but 
> >> /OE/arago-rocko-next-build/sources/meta-arago/meta-arago-extras/recipes-apps/video-analytics-demo/qt-opencv-opencl-opengl-multithreaded_git.bb
> >>  DEPENDS on or otherwise requires it)
> >> dsplib-c66x was skipped: incompatible with machine am57xx-hs-evm (not in 
> >> COMPATIBLE_MACHINE)
> >> NOTE: Runtime target 'qt-opencv-opencl-opengl-multithreaded-src' is 
> >> unbuildable, removing...
> >>
> >> Jake,
> >>
> >> Did you tested it on am57xx-hs-evm?
> 
> I had only built for am57xx-evm as there are no machine overrides in 
> these recipes because they are DSP architecture-specific.
> 
> Looks like we should change "COMPATIBLE_MACHINE" to, at the very least, 
> include what was there before (omap-a15|keystone). But as these are 
> specific to the DSP architecture, should COMPATIBLE_MACHINE even be 
> necessary?
> 
> >> Denys
> >>
> >>
> >>> -Original Message-
> >>> From: Denys Dmytriyenko [mailto:de...@ti.com]
> >>> Sent: Wednesday, September 12, 2018 4:21 PM
> >>> To: Xu, Jianzhong
> >>> Cc: Stiffler, Jacob; meta-ti@yoctoproject.org
> >>> Subject: Re: [meta-ti] [EXTERNAL] [PATCH 3/3 v2] Added DSPLIB recipe to 
> >>> build
> >>> DSPLIB from source. Updated includes/ti-paths.inc for MATHLIB and DSPLIB.
> >>>
> >>> Thanks, merged into rocko-next for testing.
> >>>
> >>> There were lots of small non-critical things I had to fix, like 
> >>> whitespaces,
> >>> indentation, etc. But the biggest one is that you have to follow 
> >>> OpenEmbedded
> >>> Commit Message Guidelines:
> >>>
> >>> https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
> >>>
> >>>
> >>> On Wed, Sep 12, 2018 at 03:40:42PM -0400, Xu, Jianzhong wrote:
> >>>> Denys,
> >>>>
> >>>>
> >>>>
> >>>> You're right. The versioning was inconsistent. Please use
> >>>> [EXTERNAL,3/3,v2] and newer versions of [EXTERNAL,2/3], 
> >>>> [EXTERNAL,1/3].
> >>>> The latter two should have had v2 in it. Please see highlights below.
> >>>>
> >>>>
> >>>>
> >>>> 
> >>>> ++
> >>>> |[EXTERNAL,3/3,v2] Added DSPLIB recipe to   |  |
> >>>> ||   |
> >>>> |build DSPLIB from source. Updated  |2018-09-06|Jianzhong 
> >>>> Xu||New|
> >>>> |includes/ti-paths.inc for MATHLIB and  |  |
> >>>> ||   |
> >>>> |DSPLIB.|  |
> >>>> ||   |
> >>>> 
> >>>> |---+--+++---|
> >>>> |[EXTERNAL] Added DSPLIB recipe to build|  |
> >>>> ||   |
> >>>> |DSPLIB from source. Updated|2018-09-06|Jianzhong 
> >>>> Xu||New|
> >>>> |includes/ti-paths.inc for MATHLIB and  |  |
> >>>> ||   |
> >>>> |DSPLIB.|  |
> >>>> ||   |
> >>>> 
> >>>> |---+--+++---|
> >>>> |[EXTERNAL,3/3] Added DSPLIB recipe to build|2018-09-04|Jianzhong
> >&

Re: [meta-ti] [EXTERNAL] [PATCH 3/3 v2] Added DSPLIB recipe to build DSPLIB from source. Updated includes/ti-paths.inc for MATHLIB and DSPLIB.

[Denys Dmytriyenko]

Same for dra7xx-evm...


On Wed, Sep 12, 2018 at 04:37:48PM -0400, Dmytriyenko, Denys wrote:
> And it crashed and burned right away:
> 
> ERROR: Nothing PROVIDES 'dsplib-c66x' (but 
> /OE/arago-rocko-next-build/sources/meta-arago/meta-arago-extras/recipes-apps/video-analytics-demo/qt-opencv-opencl-opengl-multithreaded_git.bb
>  DEPENDS on or otherwise requires it)
> dsplib-c66x was skipped: incompatible with machine am57xx-hs-evm (not in 
> COMPATIBLE_MACHINE)
> NOTE: Runtime target 'qt-opencv-opencl-opengl-multithreaded-src' is 
> unbuildable, removing...
> 
> Jake,
> 
> Did you tested it on am57xx-hs-evm?
> 
> Denys
> 
> 
> > -Original Message-
> > From: Denys Dmytriyenko [mailto:de...@ti.com]
> > Sent: Wednesday, September 12, 2018 4:21 PM
> > To: Xu, Jianzhong
> > Cc: Stiffler, Jacob; meta-ti@yoctoproject.org
> > Subject: Re: [meta-ti] [EXTERNAL] [PATCH 3/3 v2] Added DSPLIB recipe to 
> > build
> > DSPLIB from source. Updated includes/ti-paths.inc for MATHLIB and DSPLIB.
> > 
> > Thanks, merged into rocko-next for testing.
> > 
> > There were lots of small non-critical things I had to fix, like whitespaces,
> > indentation, etc. But the biggest one is that you have to follow 
> > OpenEmbedded
> > Commit Message Guidelines:
> > 
> > https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
> > 
> > 
> > On Wed, Sep 12, 2018 at 03:40:42PM -0400, Xu, Jianzhong wrote:
> > >Denys,
> > >
> > >
> > >
> > >You're right. The versioning was inconsistent. Please use
> > >[EXTERNAL,3/3,v2] and newer versions of [EXTERNAL,2/3], [EXTERNAL,1/3].
> > >The latter two should have had v2 in it. Please see highlights below.
> > >
> > >
> > >
> > >
> > > ++
> > >|[EXTERNAL,3/3,v2] Added DSPLIB recipe to   |  ||| 
> > >   |
> > >|build DSPLIB from source. Updated  |2018-09-06|Jianzhong 
> > > Xu||New|
> > >|includes/ti-paths.inc for MATHLIB and  |  ||| 
> > >   |
> > >|DSPLIB.|  ||| 
> > >   |
> > >
> > > |---+--+++---|
> > >|[EXTERNAL] Added DSPLIB recipe to build|  ||| 
> > >   |
> > >|DSPLIB from source. Updated|2018-09-06|Jianzhong 
> > > Xu||New|
> > >|includes/ti-paths.inc for MATHLIB and  |  ||| 
> > >   |
> > >|DSPLIB.|  ||| 
> > >   |
> > >
> > > |---+--+++---|
> > >|[EXTERNAL,3/3] Added DSPLIB recipe to build|2018-09-04|Jianzhong
> > Xu||New|
> > >|DSPLIB from source.|  ||| 
> > >   |
> > >
> > > |---+--+++---|
> > >|[EXTERNAL,2/3] Added MATHLIB recipe to |2018-09-04|Jianzhong
> > Xu||New|
> > >|build MATHLIB from source. |  ||| 
> > >   |
> > >
> > > |---+--+++---|
> > >|[EXTERNAL,1/3] Added SWTOOLS which is  |  ||| 
> > >   |
> > >|needed to build processor libs (DSPLIB,|2018-09-04|Jianzhong 
> > > Xu||New|
> > >|MATHLIB, etc) from source. |  ||| 
> > >   |
> > >
> > > ++
> > >
> > >
> > >
> > >Thanks,
> > >
> > >Jianzhong
> > >
> > >
> > >
> > >-Original Message-
> > >From: Dmytriyenko, Denys
> > >Sent: Wednesday, September 12, 2018 3:13 PM
> > >To: Stiffler, Jacob
> > >Cc: Xu, Jianzhong; meta-ti@yoctoproject.org
> > >Subject: Re: [meta-ti] [EXTERNAL] [PATCH 3/3 v2] Added DSPLIB recipe to
> > >build DSPLIB from source. Updated includes/ti-paths.inc for MATHLIB and
> > >DSPLIB.
> > >
> > >
> > >
> > >Jake,
> > >
> > >
> > 

Re: [meta-ti] [EXTERNAL] [PATCH 3/3 v2] Added DSPLIB recipe to build DSPLIB from source. Updated includes/ti-paths.inc for MATHLIB and DSPLIB.

[Denys Dmytriyenko]

Thanks, merged into rocko-next for testing.

There were lots of small non-critical things I had to fix, like whitespaces, 
indentation, etc. But the biggest one is that you have to follow OpenEmbedded 
Commit Message Guidelines:

https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines


On Wed, Sep 12, 2018 at 03:40:42PM -0400, Xu, Jianzhong wrote:
>Denys,
> 
> 
> 
>You're right. The versioning was inconsistent. Please use
>[EXTERNAL,3/3,v2] and newer versions of [EXTERNAL,2/3], [EXTERNAL,1/3].
>The latter two should have had v2 in it. Please see highlights below.
> 
> 
> 
>++
>|[EXTERNAL,3/3,v2] Added DSPLIB recipe to   |  |||   |
>|build DSPLIB from source. Updated  |2018-09-06|Jianzhong Xu||New|
>|includes/ti-paths.inc for MATHLIB and  |  |||   |
>|DSPLIB.|  |||   |
>|---+--+++---|
>|[EXTERNAL] Added DSPLIB recipe to build|  |||   |
>|DSPLIB from source. Updated|2018-09-06|Jianzhong Xu||New|
>|includes/ti-paths.inc for MATHLIB and  |  |||   |
>|DSPLIB.|  |||   |
>|---+--+++---|
>|[EXTERNAL,3/3] Added DSPLIB recipe to build|2018-09-04|Jianzhong Xu||New|
>|DSPLIB from source.|  |||   |
>|---+--+++---|
>|[EXTERNAL,2/3] Added MATHLIB recipe to |2018-09-04|Jianzhong Xu||New|
>|build MATHLIB from source. |  |||   |
>|---+--+++---|
>|[EXTERNAL,1/3] Added SWTOOLS which is  |  |||   |
>|needed to build processor libs (DSPLIB,|2018-09-04|Jianzhong Xu||New|
>|MATHLIB, etc) from source. |  |||   |
>++
> 
> 
> 
>Thanks,
> 
>Jianzhong
> 
> 
> 
>-Original Message-
>From: Dmytriyenko, Denys
>Sent: Wednesday, September 12, 2018 3:13 PM
>To: Stiffler, Jacob
>Cc: Xu, Jianzhong; meta-ti@yoctoproject.org
>Subject: Re: [meta-ti] [EXTERNAL] [PATCH 3/3 v2] Added DSPLIB recipe to
>build DSPLIB from source. Updated includes/ti-paths.inc for MATHLIB and
>DSPLIB.
> 
> 
> 
>Jake,
> 
> 
> 
>I'll give it a look - I assume you want the 3 most recent patches, I don't
> 
>think versioning was consistent...
> 
> 
> 
>Denys
> 
> 
> 
> 
> 
>On Tue, Sep 11, 2018 at 09:17:49AM -0400, Jacob Stiffler wrote:
> 
>> ACK
> 
>>
> 
>>
> 
>> Denys,
> 
>>
> 
>> Can you apply these patches to the ti2018.03 branch?
> 
>>
> 
>>
> 
>> Thank you,
> 
>>
> 
>> Jake
> 
>>
> 
>>
> 
>> On 9/6/2018 1:46 PM, Jianzhong Xu wrote:
> 
>> >Signed-off-by: Jianzhong Xu 
> 
>> >---
> 
>> >Change from previous version of patch
> 
>> >Corrected typo: MATHLIB_C674INSTALL_XXX should have been
>MATHLIB_C674_INSTALL_XXX
> 
>> >---
> 
>> >---
> 
>> >  recipes-ti/dsplib/dsplib-c64xp_git.bb|  9 
> 
>> >  recipes-ti/dsplib/dsplib-c66x.inc| 30 
> 
>> >  recipes-ti/dsplib/dsplib-c66x_3.4.0.0.bb |  9 
> 
>> >  recipes-ti/dsplib/dsplib-c66x_git.bb | 10 
> 
>> >  recipes-ti/dsplib/dsplib-c674x_git.bb|  9 
> 
>> >  recipes-ti/dsplib/dsplib.inc | 79
>
> 
>> >  recipes-ti/includes/ti-paths.inc |  8 +++-
> 
>> >  7 files changed, 114 insertions(+), 40 deletions(-)
> 
>> >  create mode 100644 recipes-ti/dsplib/dsplib-c64xp_git.bb
> 
>> >  delete mode 100644 recipes-ti/dsplib/dsplib-c66x.inc
> 
>> >  delete mode 100644 recipes-ti/dsplib/dsplib-c66x_3.4.0.0.bb
> 
>> >  create mode 100644 recipes-ti/dsplib/dsplib-c66x_git.bb
> 
>> >  create mode 100644 recipes-ti/dsplib/dsplib-c674x_git.bb
> 
>> >  create mode 100644 recipes-ti/dsplib/dsplib.inc
> 
>> >
> 
>> >diff --git a/recipes-ti/dsplib/dsplib-c64xp_git.bb
>b/recipes-ti/dsplib/dsplib-c64xp_git.bb
> 
>> >new file mode 100644
> 
>> >index 000..1038d44
> 
>> >--- /dev/null
> 
>> >+++ b/recipes-ti/dsplib/dsplib-c64xp_git.bb
> 
>> >@@ -0,0 +1,9 @@
> 
>> >+MATHLIB_INSTALL_DIR = "${MATHLIB_C64P_INSTALL_DIR}/packages"
> 
>> >+DSPLIB_INSTALL_DIR_RECIPE = "${DSPLIB_C64P_INSTALL_DIR_RECIPE}"
> 
>> >+DSPLIB_INSTALL_DIR = "${DSPLIB_C64P_INSTALL_DIR}"
> 
>> >+DSPLIB_BUILD_TARGET = "c64Px"
> 
>> >+
> 
>  

Re: [meta-ti] [EXTERNAL] [PATCH 3/3 v2] Added DSPLIB recipe to build DSPLIB from source. Updated includes/ti-paths.inc for MATHLIB and DSPLIB.

[Denys Dmytriyenko]

Jake,

I'll give it a look - I assume you want the 3 most recent patches, I don't 
think versioning was consistent...

Denys


On Tue, Sep 11, 2018 at 09:17:49AM -0400, Jacob Stiffler wrote:
> ACK
> 
> 
> Denys,
> 
> Can you apply these patches to the ti2018.03 branch?
> 
> 
> Thank you,
> 
> Jake
> 
> 
> On 9/6/2018 1:46 PM, Jianzhong Xu wrote:
> >Signed-off-by: Jianzhong Xu 
> >---
> >Change from previous version of patch
> >Corrected typo: MATHLIB_C674INSTALL_XXX should have been 
> >MATHLIB_C674_INSTALL_XXX
> >---
> >---
> >  recipes-ti/dsplib/dsplib-c64xp_git.bb|  9 
> >  recipes-ti/dsplib/dsplib-c66x.inc| 30 
> >  recipes-ti/dsplib/dsplib-c66x_3.4.0.0.bb |  9 
> >  recipes-ti/dsplib/dsplib-c66x_git.bb | 10 
> >  recipes-ti/dsplib/dsplib-c674x_git.bb|  9 
> >  recipes-ti/dsplib/dsplib.inc | 79 
> > 
> >  recipes-ti/includes/ti-paths.inc |  8 +++-
> >  7 files changed, 114 insertions(+), 40 deletions(-)
> >  create mode 100644 recipes-ti/dsplib/dsplib-c64xp_git.bb
> >  delete mode 100644 recipes-ti/dsplib/dsplib-c66x.inc
> >  delete mode 100644 recipes-ti/dsplib/dsplib-c66x_3.4.0.0.bb
> >  create mode 100644 recipes-ti/dsplib/dsplib-c66x_git.bb
> >  create mode 100644 recipes-ti/dsplib/dsplib-c674x_git.bb
> >  create mode 100644 recipes-ti/dsplib/dsplib.inc
> >
> >diff --git a/recipes-ti/dsplib/dsplib-c64xp_git.bb 
> >b/recipes-ti/dsplib/dsplib-c64xp_git.bb
> >new file mode 100644
> >index 000..1038d44
> >--- /dev/null
> >+++ b/recipes-ti/dsplib/dsplib-c64xp_git.bb
> >@@ -0,0 +1,9 @@
> >+MATHLIB_INSTALL_DIR = "${MATHLIB_C64P_INSTALL_DIR}/packages"
> >+DSPLIB_INSTALL_DIR_RECIPE = "${DSPLIB_C64P_INSTALL_DIR_RECIPE}"
> >+DSPLIB_INSTALL_DIR = "${DSPLIB_C64P_INSTALL_DIR}"
> >+DSPLIB_BUILD_TARGET = "c64Px"
> >+
> >+DEPENDS = ""
> >+
> >+include dsplib.inc
> >+
> >diff --git a/recipes-ti/dsplib/dsplib-c66x.inc 
> >b/recipes-ti/dsplib/dsplib-c66x.inc
> >deleted file mode 100644
> >index 7ff99c2..000
> >--- a/recipes-ti/dsplib/dsplib-c66x.inc
> >+++ /dev/null
> >@@ -1,30 +0,0 @@
> >-DESCRIPTION = "DSPLIB contains optimized general-purpose signal-processing 
> >routines for TI DSPs"
> >-HOMEPAGE = "http://www.ti.com/tool/sprc265";
> >-SECTION = "devel"
> >-LICENSE = "BSD-3-Clause"
> >-
> >-require ../includes/ti-paths.inc
> >-require ../includes/ti-staging.inc
> >-require ../includes/ti-unpack.inc
> >-
> >-COMPATIBLE_MACHINE = "omap-a15|keystone"
> >-
> >-SRC_URI = 
> >"http://software-dl.ti.com/sdoemb/sdoemb_public_sw/dsplib/${PV}/exports/${BINFILE};name=dsplib";
> >-
> >-BINFILE = "dsplib_c66x_${PV}_Linux.bin"
> >-TI_BIN_UNPK_ARGS = "--mode silent --prefix ${S}"
> >-TI_BIN_UNPK_CMDS = ""
> >-
> >-do_install() {
> >-CP_ARGS="-Prf --preserve=mode,timestamps --no-preserve=ownership"
> >-install -d ${D}${DSPLIB_C66_INSTALL_DIR_RECIPE}
> >-cp ${CP_ARGS} ${S}/* ${D}${DSPLIB_C66_INSTALL_DIR_RECIPE}
> >-}
> >-
> >-ALLOW_EMPTY_${PN} = "1"
> >-FILES_${PN}-dev += "${DSPLIB_C66_INSTALL_DIR_RECIPE}"
> >-
> >-INHIBIT_PACKAGE_STRIP = "1"
> >-INHIBIT_SYSROOT_STRIP = "1"
> >-INHIBIT_PACKAGE_DEBUG_SPLIT = "1"
> >-INSANE_SKIP_${PN}-dev = "arch"
> >diff --git a/recipes-ti/dsplib/dsplib-c66x_3.4.0.0.bb 
> >b/recipes-ti/dsplib/dsplib-c66x_3.4.0.0.bb
> >deleted file mode 100644
> >index f1273f3..000
> >--- a/recipes-ti/dsplib/dsplib-c66x_3.4.0.0.bb
> >+++ /dev/null
> >@@ -1,9 +0,0 @@
> >-require dsplib-c66x.inc
> >-
> >-PV = "3_4_0_0"
> >-PR = "r1"
> >-
> >-LIC_FILES_CHKSUM = 
> >"file://packages/ti/dsplib/dsplib.h;beginline=9;endline=35;md5=17733f9e1100f8a628512f47c4bf676a"
> >-
> >-SRC_URI[dsplib.md5sum] = "66785604729c153dcad5282097dee8bf"
> >-SRC_URI[dsplib.sha256sum] = 
> >"e88909b6271ce6c4c62e2ab90181b7adb36c7f28f5c52836668eb35888785ce8"
> >diff --git a/recipes-ti/dsplib/dsplib-c66x_git.bb 
> >b/recipes-ti/dsplib/dsplib-c66x_git.bb
> >new file mode 100644
> >index 000..cbc25d0
> >--- /dev/null
> >+++ b/recipes-ti/dsplib/dsplib-c66x_git.bb
> >@@ -0,0 +1,10 @@
> >+MATHLIB_INSTALL_DIR = "${MATHLIB_C66_INSTALL_DIR}/packages"
> >+DSPLIB_INSTALL_DIR_RECIPE = "${DSPLIB_C66_INSTALL_DIR_RECIPE}"
> >+DSPLIB_INSTALL_DIR = "${DSPLIB_C66_INSTALL_DIR}"
> >+DSPLIB_BUILD_TARGET = "c66x"
> >+
> >+DEPENDS = "mathlib-c66x"
> >+
> >+include dsplib.inc
> >+
> >+
> >diff --git a/recipes-ti/dsplib/dsplib-c674x_git.bb 
> >b/recipes-ti/dsplib/dsplib-c674x_git.bb
> >new file mode 100644
> >index 000..07c6892
> >--- /dev/null
> >+++ b/recipes-ti/dsplib/dsplib-c674x_git.bb
> >@@ -0,0 +1,9 @@
> >+MATHLIB_INSTALL_DIR = "${MATHLIB_C674_INSTALL_DIR}/packages"
> >+DSPLIB_INSTALL_DIR_RECIPE = "${DSPLIB_C674_INSTALL_DIR_RECIPE}"
> >+DSPLIB_INSTALL_DIR = "${DSPLIB_C674_INSTALL_DIR}"
> >+DSPLIB_BUILD_TARGET = "c674x"
> >+
> >+DEPENDS = "mathlib-c674x"
> >+
> >+include dsplib.inc
> >+
> >diff --git a/recipes-ti/dsplib/dsplib.inc b/recipes-ti/dsplib/dsplib.inc
> >new file mode 100644
> >index 000..66fe0fb
> >--- /dev/null
> >+++ b/

Re: [meta-ti] [rocko-next][PATCH v2] ti-ipc: Add systemd startup script

[Denys Dmytriyenko]

Thanks.

BTW, rocko-next is not a correct destination release/LTS for a patch.


On Mon, Sep 10, 2018 at 05:10:53PM -0400, Sam Nelson wrote:
> With systemd enabled, it is better to add the proper systemd
> script instead of legacy init.d script.
> 
> Signed-off-by: Sam Nelson 
> 
> ---
> Changes from previous version of patch
> Remove PIDFile entries
> ---
> ---
>  recipes-ti/ipc/ti-ipc/tiipclad-daemon.service |  9 +
>  recipes-ti/ipc/ti-ipc_git.bb  | 21 +
>  2 files changed, 26 insertions(+), 4 deletions(-)
>  create mode 100644 recipes-ti/ipc/ti-ipc/tiipclad-daemon.service
> 
> diff --git a/recipes-ti/ipc/ti-ipc/tiipclad-daemon.service 
> b/recipes-ti/ipc/ti-ipc/tiipclad-daemon.service
> new file mode 100644
> index 000..ea26845
> --- /dev/null
> +++ b/recipes-ti/ipc/ti-ipc/tiipclad-daemon.service
> @@ -0,0 +1,9 @@
> +[Unit]
> +Description=TI IPC Daemon
> +
> +[Service]
> +Type=forking
> +ExecStart=/usr/bin/__LAD_DAEMON__ -g -l lad.txt
> +
> +[Install]
> +WantedBy=basic.target
> diff --git a/recipes-ti/ipc/ti-ipc_git.bb b/recipes-ti/ipc/ti-ipc_git.bb
> index 23b8d94..8b3ac91 100644
> --- a/recipes-ti/ipc/ti-ipc_git.bb
> +++ b/recipes-ti/ipc/ti-ipc_git.bb
> @@ -4,12 +4,13 @@ 
> HOMEPAGE="http://processors.wiki.ti.com/index.php/Category:IPC";
>  require ti-ipc.inc
>  require ti-ipc-common.inc
>  
> -PR = "${INC_PR}.1"
> +PR = "${INC_PR}.2"
>  
>  DEPENDS += "virtual/kernel"
>  
>  SRC_URI += "file://tiipclad-daemon.sh \
>  file://omap_remoteproc.conf \
> +file://tiipclad-daemon.service \
>  file://0001-Add-kernel-build-dir.patch \
> "
>  
> @@ -23,11 +24,13 @@ DAEMON_k2g = "lad_66ak2g"
>  DAEMON_omapl138 = "lad_omapl138"
>  DAEMON_k3 = "lad_am65xx"
>  
> -inherit autotools-brokensep pkgconfig update-rc.d
> +inherit autotools-brokensep pkgconfig update-rc.d systemd
>  
>  INITSCRIPT_NAME = "tiipclad-daemon.sh"
>  INITSCRIPT_PARAMS = "defaults 10"
>  
> +SYSTEMD_SERVICE_${PN} = "tiipclad-daemon.service"
> +
>  EXTRA_OECONF += "PLATFORM=${PLATFORM} 
> KERNEL_INSTALL_DIR=${STAGING_KERNEL_DIR} 
> KERNEL_BUILD_DIR=${STAGING_KERNEL_BUILDDIR}"
>  
>  do_compile[depends] += "virtual/kernel:do_shared_workdir"
> @@ -40,10 +43,20 @@ do_configure() {
>  do_install_append() {
>  install -d ${D}${sysconfdir}/init.d/
>  
> -# Modify the tiipclad-daemon.sh script to point to the right
> +# Modify the startup scripts to point to the right
>  # lad daemon executable.
>  sed -i -e "s/__LAD_DAEMON__/${DAEMON}/" ${WORKDIR}/tiipclad-daemon.sh
> -install -c -m 755 ${WORKDIR}/tiipclad-daemon.sh 
> ${D}${sysconfdir}/init.d/${INITSCRIPT_NAME}
> +sed -i -e "s/__LAD_DAEMON__/${DAEMON}/" 
> ${WORKDIR}/tiipclad-daemon.service
> +
> +systemd_enabled=${@bb.utils.contains('DISTRO_FEATURES', 'systemd', '1', 
> '0', d)}
> +if [ ${systemd_enabled} -eq 1 ]
> +then
> +install -d ${D}${systemd_system_unitdir}
> +install -m 0644 ${WORKDIR}/tiipclad-daemon.service 
> ${D}${systemd_system_unitdir}
> +else
> +install -d ${D}${sysconfdir}/init.d/
> +install -c -m 755 ${S}/scripts/tiipclad-daemon.sh 
> ${D}${sysconfdir}/init.d/${INITSCRIPT_NAME}
> +fi
>  }
>  
>  do_install_append_dra7xx() {
> -- 
> 1.9.1
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [rocko-next][PATCH] ti-ipc: Add systemd startup script

[Denys Dmytriyenko]

Sam,

On Friday night Suman and I were debugging issues with this new systemd 
service file.

First of all, you hahve PIDFile entry twice.
Second, this entry is recommended, but not required. But if specified, systemd 
expects the daemon to create that PID file and if the file is not there after 
a minute or so, it kills the daemon.

Everything seems to work just fine w/o any PIDFile entries.

Please send v2 of the patch - I'll drop it from the next branch.


On Fri, Sep 07, 2018 at 08:05:02AM -0400, Sam Nelson wrote:
> With systemd enabled, it is better to add the proper systemd
> script instead of legacy init.d script.
> 
> Signed-off-by: Sam Nelson 
> ---
>  recipes-ti/ipc/ti-ipc/tiipclad-daemon.service | 11 +++
>  recipes-ti/ipc/ti-ipc_git.bb  | 21 +
>  2 files changed, 28 insertions(+), 4 deletions(-)
>  create mode 100644 recipes-ti/ipc/ti-ipc/tiipclad-daemon.service
> 
> diff --git a/recipes-ti/ipc/ti-ipc/tiipclad-daemon.service 
> b/recipes-ti/ipc/ti-ipc/tiipclad-daemon.service
> new file mode 100644
> index 000..7c09c7d
> --- /dev/null
> +++ b/recipes-ti/ipc/ti-ipc/tiipclad-daemon.service
> @@ -0,0 +1,11 @@
> +[Unit]
> +Description=TI IPC Daemon
> +
> +[Service]
> +Type=forking
> +PIDFile=/var/run/tiipclad.pid
> +ExecStart=/usr/bin/__LAD_DAEMON__ -g -l lad.txt
> +PIDFile=/var/run/tiipclad.pid
> +
> +[Install]
> +WantedBy=basic.target
> diff --git a/recipes-ti/ipc/ti-ipc_git.bb b/recipes-ti/ipc/ti-ipc_git.bb
> index 23b8d94..8b3ac91 100644
> --- a/recipes-ti/ipc/ti-ipc_git.bb
> +++ b/recipes-ti/ipc/ti-ipc_git.bb
> @@ -4,12 +4,13 @@ 
> HOMEPAGE="http://processors.wiki.ti.com/index.php/Category:IPC";
>  require ti-ipc.inc
>  require ti-ipc-common.inc
>  
> -PR = "${INC_PR}.1"
> +PR = "${INC_PR}.2"
>  
>  DEPENDS += "virtual/kernel"
>  
>  SRC_URI += "file://tiipclad-daemon.sh \
>  file://omap_remoteproc.conf \
> +file://tiipclad-daemon.service \
>  file://0001-Add-kernel-build-dir.patch \
> "
>  
> @@ -23,11 +24,13 @@ DAEMON_k2g = "lad_66ak2g"
>  DAEMON_omapl138 = "lad_omapl138"
>  DAEMON_k3 = "lad_am65xx"
>  
> -inherit autotools-brokensep pkgconfig update-rc.d
> +inherit autotools-brokensep pkgconfig update-rc.d systemd
>  
>  INITSCRIPT_NAME = "tiipclad-daemon.sh"
>  INITSCRIPT_PARAMS = "defaults 10"
>  
> +SYSTEMD_SERVICE_${PN} = "tiipclad-daemon.service"
> +
>  EXTRA_OECONF += "PLATFORM=${PLATFORM} 
> KERNEL_INSTALL_DIR=${STAGING_KERNEL_DIR} 
> KERNEL_BUILD_DIR=${STAGING_KERNEL_BUILDDIR}"
>  
>  do_compile[depends] += "virtual/kernel:do_shared_workdir"
> @@ -40,10 +43,20 @@ do_configure() {
>  do_install_append() {
>  install -d ${D}${sysconfdir}/init.d/
>  
> -# Modify the tiipclad-daemon.sh script to point to the right
> +# Modify the startup scripts to point to the right
>  # lad daemon executable.
>  sed -i -e "s/__LAD_DAEMON__/${DAEMON}/" ${WORKDIR}/tiipclad-daemon.sh
> -install -c -m 755 ${WORKDIR}/tiipclad-daemon.sh 
> ${D}${sysconfdir}/init.d/${INITSCRIPT_NAME}
> +sed -i -e "s/__LAD_DAEMON__/${DAEMON}/" 
> ${WORKDIR}/tiipclad-daemon.service
> +
> +systemd_enabled=${@bb.utils.contains('DISTRO_FEATURES', 'systemd', '1', 
> '0', d)}
> +if [ ${systemd_enabled} -eq 1 ]
> +then
> +install -d ${D}${systemd_system_unitdir}
> +install -m 0644 ${WORKDIR}/tiipclad-daemon.service 
> ${D}${systemd_system_unitdir}
> +else
> +install -d ${D}${sysconfdir}/init.d/
> +install -c -m 755 ${S}/scripts/tiipclad-daemon.sh 
> ${D}${sysconfdir}/init.d/${INITSCRIPT_NAME}
> +fi
>  }
>  
>  do_install_append_dra7xx() {
> -- 
> 1.9.1
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] BeagleBone Black: cannot access USB MSC devices

[Denys Dmytriyenko]

initialized
> [1.279007] IR Sharp protocol handler initialized
> [1.283737] IR MCE Keyboard/mouse protocol handler initialized
> [1.289591] IR XMP protocol handler initialized
> [1.295540] cpuidle: enable-method property 'ti,am3352' found operations
> [1.302660] sdhci: Secure Digital Host Controller Interface driver
> [1.308868] sdhci: Copyright(c) Pierre Ossman
> [1.313689] omap_hsmmc 4806.mmc: GPIO lookup for consumer cd
> [1.313698] omap_hsmmc 4806.mmc: using device tree for GPIO lookup
> [1.313728] of_get_named_gpiod_flags: parsed 'cd-gpios' property of node 
> '/ocp/mmc@4806[0]' - status (0)
> [1.313801] omap_hsmmc 4806.mmc: Got CD GPIO
> [1.318447] omap_hsmmc 4806.mmc: GPIO lookup for consumer wp
> [1.318452] omap_hsmmc 4806.mmc: using device tree for GPIO lookup
> [1.318462] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of 
> node '/ocp/mmc@4806[0]'
> [1.318470] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of 
> node '/ocp/mmc@4806[0]'
> [1.318476] omap_hsmmc 4806.mmc: using lookup tables for GPIO lookup
> [1.318484] omap_hsmmc 4806.mmc: lookup for GPIO wp failed
> [1.373035] omap_hsmmc 481d8000.mmc: GPIO lookup for consumer cd
> [1.373047] omap_hsmmc 481d8000.mmc: using device tree for GPIO lookup
> [1.373060] of_get_named_gpiod_flags: can't parse 'cd-gpios' property of 
> node '/ocp/mmc@481d8000[0]'
> [1.373068] of_get_named_gpiod_flags: can't parse 'cd-gpio' property of 
> node '/ocp/mmc@481d8000[0]'
> [1.373075] omap_hsmmc 481d8000.mmc: using lookup tables for GPIO lookup
> [1.373082] omap_hsmmc 481d8000.mmc: lookup for GPIO cd failed
> [1.373090] omap_hsmmc 481d8000.mmc: GPIO lookup for consumer wp
> [1.373095] omap_hsmmc 481d8000.mmc: using device tree for GPIO lookup
> [1.373103] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of 
> node '/ocp/mmc@481d8000[0]'
> [1.373110] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of 
> node '/ocp/mmc@481d8000[0]'
> [1.373115] omap_hsmmc 481d8000.mmc: using lookup tables for GPIO lookup
> [1.373121] omap_hsmmc 481d8000.mmc: lookup for GPIO wp failed
> [1.419813] mmc0: host does not support reading read-only switch, assuming 
> write-enable
> [1.429912] mmc0: new high speed SDHC card at address 59b4
> [1.435675] sdhci-pltfm: SDHCI platform and OF driver helper
> [1.436305] of_get_named_gpiod_flags: parsed 'gpios' property of node 
> '/leds/led2[0]' - status (0)
> [1.436317] no flags found for gpios
> [1.436453] of_get_named_gpiod_flags: parsed 'gpios' property of node 
> '/leds/led3[0]' - status (0)
> [1.436459] no flags found for gpios
> [1.436560] of_get_named_gpiod_flags: parsed 'gpios' property of node 
> '/leds/led4[0]' - status (0)
> [1.436565] no flags found for gpios
> [1.436646] of_get_named_gpiod_flags: parsed 'gpios' property of node 
> '/leds/led5[0]' - status (0)
> [1.436651] no flags found for gpios
> [1.437015] ledtrig-cpu: registered to indicate activity on CPUs
> [1.446318] NET: Registered protocol family 10
> [1.447432] Segment Routing with IPv6
> [1.447498] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
> [1.448080] NET: Registered protocol family 17
> [1.448342] Key type dns_resolver registered
> [1.448479] omap_voltage_late_init: Voltage driver support not added
> [1.489072] mmcblk0: mmc0:59b4 AF UD 7.49 GiB
> [1.495341]  mmcblk0: p1 p2
> [1.535634] random: fast init done
> [1.545382] tps65217 0-0024: TPS65217 ID 0xe version 1.2
> [1.555037] mmc1: new high speed MMC card at address 0001
> [1.560970] mmcblk1: mmc1:0001 M62704 3.56 GiB
> [1.565753] mmcblk1boot0: mmc1:0001 M62704 partition 1 2.00 MiB
> [1.571829] mmcblk1boot1: mmc1:0001 M62704 partition 2 2.00 MiB
> [1.577919] mmcblk1rpmb: mmc1:0001 M62704 partition 3 512 KiB
> [1.585135]  mmcblk1: p1
> [1.694587] tda998x 0-0070: found TDA19988
> [1.699877] tilcdc 4830e000.lcdc: bound 0-0070 (ops tda998x_ops)
> [1.705975] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
> [1.712630] [drm] No driver support for vblank timestamp query.
> [1.718986] [drm] Cannot find any crtc or sizes
> [1.724095] [drm] Initialized tilcdc 1.0.0 20121205 for 4830e000.lcdc on 
> minor 0
> [1.731638] omap_i2c 44e0b000.i2c: bus 0 rev0.11 at 400 kHz
> [1.739084] omap_i2c 4819c000.i2c: bus 2 rev0.11 

Re: [meta-ti] [rocko/master][PATCH] Updating to version 01.00.00.13

[Denys Dmytriyenko]

The patch body seems to be missing.


On Tue, Sep 04, 2018 at 03:21:24PM -0400, Tinku Mannan wrote:
> Updating to use COPYING.txt as license checksum file
> Also updating md5 checksum for COPYING.txt
> 
> Tinku Mannan (1):
>   icss-emac-lld: Updating to version 01.00.00.13
> 
>  recipes-bsp/icss-emac-lld/icss-emac-lld.inc | 8 
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> -- 
> 2.7.4
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] BeagleBone Black: cannot access USB MSC devices

[Denys Dmytriyenko]

Sorry, hit send too early.

Also try this:

# export LIBUSB_DEBUG=9
# lsusb -v

And see what the error message is.


On Fri, Aug 31, 2018 at 06:29:31PM -0400, Denys Dmytriyenko wrote:
> Do you have a complete boot log?
> 
> 
> On Fri, Aug 31, 2018 at 05:55:53PM +, Patkar, Sarvesh S. wrote:
> > Hi Denys,
> > 
> > Thank you for the quick reply.
> > 
> > I tried the core-image-base. I see the following on the console.
> > 
> > root@beaglebone:~# lsusb
> > unable to initialize libusb: -99
> > 
> > fdisk doesn't list the USB device as well. 
> > 
> > Is there anything else that I can try?
> > 
> > Thanks,
> > Sarvesh
> > 
> > -Original Message-
> > From: Denys Dmytriyenko [mailto:de...@ti.com] 
> > Sent: Thursday, August 30, 2018 7:42 PM
> > To: Patkar, Sarvesh S. 
> > Cc: meta-ti@yoctoproject.org
> > Subject: Re: [meta-ti] BeagleBone Black: cannot access USB MSC devices
> > 
> > 
> > Please don't use core-image-minimal (e.g. core-image-base is much better), 
> > if you want to get anything useful out of it, besides just booting, 
> > including such tools as fdisk, lsusb, etc. Thanks.
> > 
> > 
> > On Fri, Aug 31, 2018 at 02:16:09AM +, Patkar, Sarvesh S. wrote:
> > > Hi,
> > >
> > > I am a beginner in Yocto and still learning to configure the images 
> > > generated.
> > >
> > > I am trying to use USB devices with the BeagleBone Black (Rev C) .
> > > Specifically, I want to access a Mass Storage Class Device (a USB 
> > > Flash
> > > Drive) from the BeagleBone Black. I used the meta, meta-poky and 
> > > meta-ti layers to build a core-image-minimal image for beaglebone 
> > > machine. On booting up with the image, I do not see any obvious 
> > > errors. However, it cannot detect the presence of a USB Device 
> > > connected to it. I checked this using fdisk -l. lsusb command is not 
> > > found.
> > >
> > > I went through an old email chain
> > > https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.yoctoprojec
> > > t.org_pipermail_linux-2Dyocto_2014-2DJune_002787.html&d=DwIBAg&c=q6k2D
> > > sTcEGCcCb_WtVSz6hhIl8hvYssy7sH8ZwfbbKU&r=kLMtB9EeaG0D8_vJ7xCDnkGx5TX9d
> > > c8pLS0HaMWl2-A&m=ZnXiBdSvO_0jYV33nEuRQrF7tLzUs8TgUM7hBC6IchQ&s=nMXUhOH
> > > LBBgCs7EOynlKAfyBNTlmCSJFY8uJm1C3cAY&e=
> > > to find if there was a solution. One of the things mentioned was to 
> > > use menuconfig to configure the kernel for built-in USB support. But, 
> > > I am not sure if the .config file is being picked up by bitbake.
> > >
> > > How do I enable USB support for MSC devices on BeagleBone Black?
> > >
> > > poky branch= sumo-19.0.0
> > > meta-ti branch= ti2018.02
> > >
> > > Thanks for the help!
> > > Sarvesh
> > >
> > 
> > > --
> > > ___
> > > meta-ti mailing list
> > > meta-ti@yoctoproject.org
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] BeagleBone Black: cannot access USB MSC devices

[Denys Dmytriyenko]

Do you have a complete boot log?


On Fri, Aug 31, 2018 at 05:55:53PM +, Patkar, Sarvesh S. wrote:
> Hi Denys,
> 
> Thank you for the quick reply.
> 
> I tried the core-image-base. I see the following on the console.
> 
> root@beaglebone:~# lsusb
> unable to initialize libusb: -99
> 
> fdisk doesn't list the USB device as well. 
> 
> Is there anything else that I can try?
> 
> Thanks,
> Sarvesh
> 
> -Original Message-
> From: Denys Dmytriyenko [mailto:de...@ti.com] 
> Sent: Thursday, August 30, 2018 7:42 PM
> To: Patkar, Sarvesh S. 
> Cc: meta-ti@yoctoproject.org
> Subject: Re: [meta-ti] BeagleBone Black: cannot access USB MSC devices
> 
> 
> Please don't use core-image-minimal (e.g. core-image-base is much better), if 
> you want to get anything useful out of it, besides just booting, including 
> such tools as fdisk, lsusb, etc. Thanks.
> 
> 
> On Fri, Aug 31, 2018 at 02:16:09AM +, Patkar, Sarvesh S. wrote:
> > Hi,
> >
> > I am a beginner in Yocto and still learning to configure the images 
> > generated.
> >
> > I am trying to use USB devices with the BeagleBone Black (Rev C) .
> > Specifically, I want to access a Mass Storage Class Device (a USB 
> > Flash
> > Drive) from the BeagleBone Black. I used the meta, meta-poky and 
> > meta-ti layers to build a core-image-minimal image for beaglebone 
> > machine. On booting up with the image, I do not see any obvious 
> > errors. However, it cannot detect the presence of a USB Device 
> > connected to it. I checked this using fdisk -l. lsusb command is not found.
> >
> > I went through an old email chain
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.yoctoprojec
> > t.org_pipermail_linux-2Dyocto_2014-2DJune_002787.html&d=DwIBAg&c=q6k2D
> > sTcEGCcCb_WtVSz6hhIl8hvYssy7sH8ZwfbbKU&r=kLMtB9EeaG0D8_vJ7xCDnkGx5TX9d
> > c8pLS0HaMWl2-A&m=ZnXiBdSvO_0jYV33nEuRQrF7tLzUs8TgUM7hBC6IchQ&s=nMXUhOH
> > LBBgCs7EOynlKAfyBNTlmCSJFY8uJm1C3cAY&e=
> > to find if there was a solution. One of the things mentioned was to 
> > use menuconfig to configure the kernel for built-in USB support. But, 
> > I am not sure if the .config file is being picked up by bitbake.
> >
> > How do I enable USB support for MSC devices on BeagleBone Black?
> >
> > poky branch= sumo-19.0.0
> > meta-ti branch= ti2018.02
> >
> > Thanks for the help!
> > Sarvesh
> >
> 
> > --
> > ___
> > meta-ti mailing list
> > meta-ti@yoctoproject.org
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] BeagleBone Black: cannot access USB MSC devices

[Denys Dmytriyenko]

Please don't use core-image-minimal (e.g. core-image-base is much better), if 
you want to get anything useful out of it, besides just booting, including 
such tools as fdisk, lsusb, etc. Thanks.


On Fri, Aug 31, 2018 at 02:16:09AM +, Patkar, Sarvesh S. wrote:
> Hi,
> 
> I am a beginner in Yocto and still learning to configure the images 
> generated.
> 
> I am trying to use USB devices with the BeagleBone Black (Rev C) . 
> Specifically, I want to access a Mass Storage Class Device (a USB Flash 
> Drive) from the BeagleBone Black. I used the meta, meta-poky and meta-ti 
> layers to build a core-image-minimal image for beaglebone machine. On 
> booting up with the image, I do not see any obvious errors. However, it 
> cannot detect the presence of a USB Device connected to it. I checked this 
> using fdisk -l. lsusb command is not found.
> 
> I went through an old email chain 
> https://lists.yoctoproject.org/pipermail/linux-yocto/2014-June/002787.html 
> to find if there was a solution. One of the things mentioned was to use 
> menuconfig to configure the kernel for built-in USB support. But, I am not 
> sure if the .config file is being picked up by bitbake.
> 
> How do I enable USB support for MSC devices on BeagleBone Black?
> 
> poky branch= sumo-19.0.0
> meta-ti branch= ti2018.02
> 
> Thanks for the help!
> Sarvesh
> 

> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] omap3evm: bitbake x-load fails

[Denys Dmytriyenko]

X-load has been deprecated for over 7 years. Are you trying to build it with 
the latest toolchain with GGC 8 and glibc 2.28? Why?

U-boot provides SPL and should support OMAP3 w/o problems.

-- 
Denys


On Wed, Aug 29, 2018 at 03:12:01PM -0600, Joe Keene wrote:
> When I try the command: "bitbake x-load", it will almost finish executing
> the RunQueue tasks when it fails around 97% progress. I believe these are
> the trouble lines:
> 
> From what I understand, it means that the cross-compiler fails to find the
> gcc library. How can I help it find the gcc library? Is the sysroot
> variable hard-coded? The Log is pretty big, so I'm just going to post the
> part that I think is relevant. If you want the full log let me know!
> 
> -VirtualBox:/poky/build$ bitbake x-load
> Loading cache: 100%
> |###|
> Time: 0:00:01
> Loaded 2738 entries from dependency cache.
> NOTE: Resolving any missing task queue dependencies
> 
> Build Configuration:
> BB_VERSION   = "1.39.1"
> BUILD_SYS= "x86_64-linux"
> NATIVELSBSTRING  = "universal"
> TARGET_SYS   = "arm-poky-linux-gnueabi"
> MACHINE  = "omap3evm"
> DISTRO   = "poky"
> DISTRO_VERSION   = "2.5+snapshot-20180829"
> TUNE_FEATURES= "arm armv7a vfp thumb neon callconvention-hard"
> TARGET_FPU   = "hard"
> meta
> meta-poky
> meta-yocto-bsp   = "master:87d3a9685dd9613e4f6718031d4ebd9344b01c47"
> meta-ti  = "master:b987670824163d9aaf45af5661dc916515ec5fea"
> meta = "master:853e0499be449c71378c087e08b1926be8e2ac87"
> 
> Initialising tasks: 100%
> |##|
> Time: 0:00:00
> Sstate summary: Wanted 60 Found 0 Missed 60 Current 15 (0% match, 20%
> complete)
> NOTE: Executing SetScene Tasks
> NOTE: Executing RunQueue Tasks
> WARNING: glibc-2.28-r0 do_package: glibc-extra-nss-2.26 was registered as
> shlib provider for libnss_db.so.2, changing it to libnss-db-2.28 because it
> was built later
> ERROR: x-load-1_1.5.1-r3 do_compile: oe_runmake failed
> ERROR: x-load-1_1.5.1-r3 do_compile: Function failed: do_compile (log file
> is located at
> /poky/build/tmp/work/omap3evm-poky-linux-gnueabi/x-load/1_1.5.1-r3/temp/log.do_compile.25161)
> ERROR: Logfile of failure stored in:
> /poky/build/tmp/work/omap3evm-poky-linux-gnueabi/x-load/1_1.5.1-r3/temp/log.do_compile.25161
> Log data follows:
> | DEBUG: Executing shell function do_compile
> | NOTE: make CROSS_COMPILE=arm-poky-linux-gnueabi- CONFIG_HEADER= distclean
> | find
> /poky/build/tmp/work/omap3evm-poky-linux-gnueabi/x-load/1_1.5.1-r3/git
> -type f \
> | \( -name 'core' -o -name '*.bak' -o -name '*~' \
> | -o -name '*.o'  -o -name '*.a'  \) -print \
> | | xargs rm -f
> ...
> (removed a bunch of lines)
> ...
> | make[1]: Leaving directory
> '/poky/build/tmp/work/omap3evm-poky-linux-gnueabi/x-load/1_1.5.1-r3/git/lib'
> | UNDEF_SYM=`arm-poky-linux-gnueabi-objdump -x board/omap3evm/libomap3evm.a
> common/libcommon.a cpu/omap3/libomap3.a disk/libdisk.a drivers/libdrivers.a
> fs/fat/libfat.a lib/libarm.a |sed  -n -e
> 's/.*\(__u_boot_cmd_.*\)/-u\1/p'|sort|uniq`;\
> | cd
> /poky/build/tmp/work/omap3evm-poky-linux-gnueabi/x-load/1_1.5.1-r3/git &&
> arm-poky-linux-gnueabi-ld -Bstatic -T
> /poky/build/tmp/work/omap3evm-poky-linux-gnueabi/x-load/1_1.5.1-r3/git/board/omap3evm/x-load.lds
> -Ttext 0x40200800  $UNDEF_SYM cpu/omap3/start.o \
> | --start-group board/omap3evm/libomap3evm.a common/libcommon.a
> cpu/omap3/libomap3.a disk/libdisk.a drivers/libdrivers.a fs/fat/libfat.a
> lib/libarm.a --end-group -L . -lgcc \
> | -Map x-load.map -o x-load
> | arm-poky-linux-gnueabi-ld: cannot find -lgcc
> | ERROR: oe_runmake failed
> | Makefile:163: recipe for target 'x-load' failed
> | make: *** [x-load] Error 1
> | WARNING: exit code 1 from a shell command.
> | ERROR: Function failed: do_compile (log file is located at
> /poky/build/tmp/work/omap3evm-poky-linux-gnueabi/x-load/1_1.5.1-r3/temp/log.do_compile.25161)
> ERROR: Task (/poky/meta-ti/recipes-bsp/x-load/x-load_git.bb:do_compile)
> failed with exit code '1'
> NOTE: Tasks Summary: Attempted 431 tasks of which 125 didn't need to be
> rerun and 1 failed.
> 
> Summary: 1 task failed:
>   /poky/meta-ti/recipes-bsp/x-load/x-load_git.bb:do_compile
> Summary: There was 1 WARNING message shown.
> Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
> 
> 
> I'm fairly new to Embedded Linux and the Yocto Project, so I fear I might
> be missing something very basic. I'd be happy to provide any additional
> information.

> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/

[meta-ti] [master][PATCH 2/2] libgbm: fix undefined minor/major symbols with new glibc

[Denys Dmytriyenko]

glibc 2.28+ now requires this.
https://sourceware.org/bugzilla/show_bug.cgi?id=19239

Signed-off-by: Denys Dmytriyenko 
---
 ...de-sys-sysmacros.h-for-minor-major-in-new.patch | 28 ++
 recipes-graphics/gbm/libgbm_10.0.0.bb  |  3 ++-
 2 files changed, 30 insertions(+), 1 deletion(-)
 create mode 100644 
recipes-graphics/gbm/libgbm/0001-gbm.c-include-sys-sysmacros.h-for-minor-major-in-new.patch

diff --git 
a/recipes-graphics/gbm/libgbm/0001-gbm.c-include-sys-sysmacros.h-for-minor-major-in-new.patch
 
b/recipes-graphics/gbm/libgbm/0001-gbm.c-include-sys-sysmacros.h-for-minor-major-in-new.patch
new file mode 100644
index 000..31134ab
--- /dev/null
+++ 
b/recipes-graphics/gbm/libgbm/0001-gbm.c-include-sys-sysmacros.h-for-minor-major-in-new.patch
@@ -0,0 +1,28 @@
+From ea5fc8da36886490d0ee40d475733cd98e38c2ec Mon Sep 17 00:00:00 2001
+From: Denys Dmytriyenko 
+Date: Tue, 28 Aug 2018 18:35:55 -0400
+Subject: [PATCH] gbm.c: include  for minor/major in new glibc
+
+glibc 2.28+ now requires this.
+https://sourceware.org/bugzilla/show_bug.cgi?id=19239
+
+Signed-off-by: Denys Dmytriyenko 
+---
+ gbm.c | 1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/gbm.c b/gbm.c
+index c046b1a..9356d7b 100644
+--- a/gbm.c
 b/gbm.c
+@@ -35,6 +35,7 @@
+ #include 
+ 
+ #include 
++#include 
+ #include 
+ #include 
+ #include 
+-- 
+2.7.4
+
diff --git a/recipes-graphics/gbm/libgbm_10.0.0.bb 
b/recipes-graphics/gbm/libgbm_10.0.0.bb
index 848a5f6..38715cc 100644
--- a/recipes-graphics/gbm/libgbm_10.0.0.bb
+++ b/recipes-graphics/gbm/libgbm_10.0.0.bb
@@ -12,6 +12,7 @@ BRANCH = "next"
 
 SRCREV = "96f37555c7e82a417b02051661377b10e6b3966e"
 
-SRC_URI = "git://git.ti.com/glsdk/libgbm.git;protocol=git;branch=${BRANCH}"
+SRC_URI = "git://git.ti.com/glsdk/libgbm.git;protocol=git;branch=${BRANCH} \
+
file://0001-gbm.c-include-sys-sysmacros.h-for-minor-major-in-new.patch"
 
 S = "${WORKDIR}/git"
-- 
2.7.4

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

[meta-ti] [master][PATCH 1/2] ti-sgx-ddk-um: remove conflicting wayland-egl.pc

[Denys Dmytriyenko]

For more details see:
http://cgit.openembedded.org/openembedded-core/commit/?id=6e5952fcfc13ff4b63c9376bd41a1dbba957f425

Signed-off-by: Denys Dmytriyenko 
---
 recipes-graphics/libgles/ti-sgx-ddk-um_1.14.3699939.bb | 3 +++
 recipes-graphics/libgles/ti-sgx-ddk-um_1.17.4948957.bb | 3 +++
 2 files changed, 6 insertions(+)

diff --git a/recipes-graphics/libgles/ti-sgx-ddk-um_1.14.3699939.bb 
b/recipes-graphics/libgles/ti-sgx-ddk-um_1.14.3699939.bb
index 9896721..cc56229 100644
--- a/recipes-graphics/libgles/ti-sgx-ddk-um_1.14.3699939.bb
+++ b/recipes-graphics/libgles/ti-sgx-ddk-um_1.14.3699939.bb
@@ -60,6 +60,9 @@ do_install () {
 mkdir -p ${D}${libdir}/gbm
 ln -sf ../libpvrGBMWSEGL.so.${PV} ${D}${libdir}/gbm/gbm_pvr.so
 ln -sf libGLESv2.so.${PV} ${D}${libdir}/libGLESv2.so.1
+
+rm -f ${D}${libdir}/pkgconfig/wayland-egl.pc
+
 chown -R root:root ${D}
 }
 
diff --git a/recipes-graphics/libgles/ti-sgx-ddk-um_1.17.4948957.bb 
b/recipes-graphics/libgles/ti-sgx-ddk-um_1.17.4948957.bb
index 6a73d0f..b5bf558 100644
--- a/recipes-graphics/libgles/ti-sgx-ddk-um_1.17.4948957.bb
+++ b/recipes-graphics/libgles/ti-sgx-ddk-um_1.17.4948957.bb
@@ -47,6 +47,9 @@ do_install () {
 mkdir -p ${D}${libdir}/gbm
 ln -sf ../libpvrGBMWSEGL.so.${PV} ${D}${libdir}/gbm/gbm_pvr.so
 ln -sf libGLESv2.so.${PV} ${D}${libdir}/libGLESv2.so.1
+
+rm -f ${D}${libdir}/pkgconfig/wayland-egl.pc
+
 chown -R root:root ${D}
 }
 
-- 
2.7.4

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] amx3-cm3 build failure on master

[Denys Dmytriyenko]

On Fri, Jul 06, 2018 at 02:40:25PM -0400, Denys Dmytriyenko wrote:
> On Fri, Jul 06, 2018 at 02:20:44PM -0400, Trevor Woerner wrote:
> > Hi,
> > 
> > Has anyone else been seeing this?
> 
> Yes. This is due to gcc-8 being PITA. I haven't had time to fix it yet - need 
> to keep compatibility with older gcc too...

BTW, this is still an issue and the suggested workaround remains to use gcc-7 
for now by setting below in distro config or local.conf:

GCCVERSION = "7.%"


> > Build Configuration:
> > BB_VERSION   = "1.39.0"
> > BUILD_SYS= "x86_64-linux"
> > NATIVELSBSTRING  = "opensuseleap-15.0"
> > TARGET_SYS   = "arm-oe-linux-gnueabi"
> > MACHINE  = "beaglebone"
> > DISTRO   = "nodistro"
> > DISTRO_VERSION   = "nodistro.0"
> > TUNE_FEATURES= "arm armv7a vfp thumb neon callconvention-hard"
> > TARGET_FPU   = "hard"
> > meta-ti  = "master:63a2ec1c7f4ef0a2c355b3bc0ea1506ae3bc8534"
> > meta = "master:416a8c241aff0dca6b8b123e52cf8e2d40c74c8d"
> > 
> > Initialising tasks: 100% 
> > |##|
> >  Time: 0:00:02
> > NOTE: Executing SetScene Tasks
> > NOTE: Executing RunQueue Tasks
> > ERROR: amx3-cm3-1.9.2-r0 do_compile: Function failed: do_compile (log 
> > file is located at 
> > /z/build-master/bbb/build/tmp-glibc/work/armv7at2hf-neon-oe-linux-gnueabi/amx3-cm3/1.9.2-r0/temp/log.do_compile.21045)
> > ERROR: Logfile of failure stored in: 
> > /z/build-master/bbb/build/tmp-glibc/work/armv7at2hf-neon-oe-linux-gnueabi/amx3-cm3/1.9.2-r0/temp/log.do_compile.21045
> > Log data follows:
> > | DEBUG: Executing shell function do_compile
> > |  CC   src/pm_services/dpll_43xx.o
> > | cc1: error: -mfloat-abi=hard: selected processor lacks an FPU
> > | make: *** [Makefile:51: src/pm_services/dpll_43xx.o] Error 1
> > | WARNING: 
> > /z/build-master/bbb/build/tmp-glibc/work/armv7at2hf-neon-oe-linux-gnueabi/amx3-cm3/1.9.2-r0/temp/run.do_compile.21045:1
> >  exit 2 from 'make CROSS_COMPILE="arm-oe-linux-gnueabi-" 
> > CC="arm-oe-linux-gnueabi-gcc  
> > --sysroot=/z/build-master/bbb/build/tmp-glibc/work/armv7at2hf-neon-oe-linux-gnueabi/amx3-cm3/1.9.2-r0/recipe-sysroot
> >   -mfloat-abi=hard"'
> > | ERROR: Function failed: do_compile (log file is located at 
> > /z/build-master/bbb/build/tmp-glibc/work/armv7at2hf-neon-oe-linux-gnueabi/amx3-cm3/1.9.2-r0/temp/log.do_compile.21045)
> > ERROR: Task 
> > (/opt/oe/configs/z/build-master/bbb/layers/meta-ti/recipes-bsp/cm3-pm-firmware/amx3-cm3_git.bb:do_compile)
> >  failed with exit code '1'
> > 
> > -- 
> > ___
> > meta-ti mailing list
> > meta-ti@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/meta-ti
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [PATCH v1] pru-icss_git.bb: add am65x examples, Lab_0, 5

[Denys Dmytriyenko]

| make[1]: Entering directory 
'/OE/arago-rocko-next/build/arago-tmp-external-linaro-toolchain/work/am57xx_evm-linux-gnueabi/pru-icss/5.3.0-r1/git/labs'
| make[1]: *** lab_5/solution/PRU_RPMsg_Echo_Interrupt1: No such file or 
directory.  Stop.
| make[1]: Leaving directory 
'/OE/arago-rocko-next/build/arago-tmp-external-linaro-toolchain/work/am57xx_evm-linux-gnueabi/pru-icss/5.3.0-r1/git/labs'
| Makefile:16: recipe for target 'lab_5/solution/PRU_RPMsg_Echo_Interrupt1' 
failed
| make: *** [lab_5/solution/PRU_RPMsg_Echo_Interrupt1] Error 2


On Sun, Aug 26, 2018 at 10:19:14PM -0500, Nick Saulnier wrote:
> This updates the commit ID of the PRU Software Support Package
> which is pulled into the SDK. The updated PRU Software Support
> Package includes:
> 
> added am65x resources:
> PRU_Halt example
> PRU_MAC_Multiply_Accum example
> ICSSG header files
> 
> added Lab_0:
> this provides a "Hello World" style beginning Linux example for
> every TI processor with a supported PRU (am335x, am437x, am57x,
> k2g, am65x).
> 
> expanded Lab_5:
> expanded Lab 5 to provide a more advanced PRU Linux example for
> every TI processor with a supported PRU (am335x, am437x, am57x,
> k2g, am65x).
> 
> Kernel 4.14 new features:
> updated resource table for all examples and labs to match the
> new template introduced in kernel 4.14
> 
> Code cleanup/bug fixes:
> update RPMsg examples to provide a more elegent way to provide
> the max message length.
> updated Linker Command files to better match TRM.
> 
> Signed-off-by: Nick Saulnier 
> ---
>  recipes-bsp/pru/pru-icss_git.bb | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/recipes-bsp/pru/pru-icss_git.bb b/recipes-bsp/pru/pru-icss_git.bb
> index e150076ec0a2..ff8f4a4ab321 100644
> --- a/recipes-bsp/pru/pru-icss_git.bb
> +++ b/recipes-bsp/pru/pru-icss_git.bb
> @@ -8,10 +8,10 @@ inherit update-alternatives
>  
>  BRANCH = "master"
>  SRC_URI = 
> "git://git.ti.com/pru-software-support-package/pru-software-support-package.git;protocol=git;branch=${BRANCH}"
> -SRCREV = "1d9249c012005a669a6ffb2f76255d72ed5c0e4c"
> +SRCREV = "78bef8fcc5204129a1da6ba015563c904478f568"
>  
> -PV = "5.2.1"
> -PR = "r2"
> +PV = "5.3.0"
> +PR = "r1"
>  
>  require recipes-ti/includes/ti-paths.inc
>  
> -- 
> 1.9.1
> 
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

[meta-ti] [rocko/master][PATCH 2/2] u-boot-ti-staging: update to ti2018.03-rc4 tag

[Denys Dmytriyenko]

Signed-off-by: Denys Dmytriyenko 
---
 recipes-bsp/u-boot/u-boot-ti-staging_2018.01.bb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/recipes-bsp/u-boot/u-boot-ti-staging_2018.01.bb 
b/recipes-bsp/u-boot/u-boot-ti-staging_2018.01.bb
index 5708f94b..aed46ecd 100644
--- a/recipes-bsp/u-boot/u-boot-ti-staging_2018.01.bb
+++ b/recipes-bsp/u-boot/u-boot-ti-staging_2018.01.bb
@@ -1,7 +1,7 @@
 require u-boot-ti.inc
 
-PR = "r18"
+PR = "r19"
 
 BRANCH = "ti-u-boot-2018.01"
 
-SRCREV = "6d540394a483c2d38aec0b84d1950d1031648ccc"
+SRCREV = "8b2f1df4b55bc0797399a21d42ac191d44f99227"
-- 
2.17.1

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

[meta-ti] [rocko/master][PATCH 1/2] linux-ti-staging: update to 4.14.67 and ti2018.03-rc4 tag

[Denys Dmytriyenko]

Signed-off-by: Denys Dmytriyenko 
---
 recipes-kernel/linux/linux-ti-staging-rt_4.14.bb | 4 ++--
 recipes-kernel/linux/linux-ti-staging_4.14.bb| 6 +++---
 2 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/recipes-kernel/linux/linux-ti-staging-rt_4.14.bb 
b/recipes-kernel/linux/linux-ti-staging-rt_4.14.bb
index dc0d25a7..2edc15e6 100644
--- a/recipes-kernel/linux/linux-ti-staging-rt_4.14.bb
+++ b/recipes-kernel/linux/linux-ti-staging-rt_4.14.bb
@@ -6,5 +6,5 @@ FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-4.14:"
 
 BRANCH = "ti-rt-linux-4.14.y"
 
-SRCREV = "bf9805829c7d263775e9323ad16a4c5e3373d04e"
-PV = "4.14.61+git${SRCPV}"
+SRCREV = "89f3986aa0e6cc6a28c9f0afda67c9514d8ac40a"
+PV = "4.14.67+git${SRCPV}"
diff --git a/recipes-kernel/linux/linux-ti-staging_4.14.bb 
b/recipes-kernel/linux/linux-ti-staging_4.14.bb
index 9e092404..40f1e8df 100644
--- a/recipes-kernel/linux/linux-ti-staging_4.14.bb
+++ b/recipes-kernel/linux/linux-ti-staging_4.14.bb
@@ -55,11 +55,11 @@ S = "${WORKDIR}/git"
 
 BRANCH = "ti-lsk-linux-4.14.y"
 
-SRCREV = "3dcf448dbe396161f4633d0e38b9894fe5214786"
-PV = "4.14.62+git${SRCPV}"
+SRCREV = "c40d9fbe468d16fc3322e696336b1119028f2917"
+PV = "4.14.67+git${SRCPV}"
 
 # Append to the MACHINE_KERNEL_PR so that a new SRCREV will cause a rebuild
-MACHINE_KERNEL_PR_append = "b"
+MACHINE_KERNEL_PR_append = "a"
 PR = "${MACHINE_KERNEL_PR}"
 
 KERNEL_GIT_URI = "git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git"
-- 
2.17.1

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [rocko][PATCH] ti-pdk: Add tool chain dependencies for am65xx platform

[Denys Dmytriyenko]

On Thu, Aug 23, 2018 at 03:23:57PM -0400, Nelson, Sam wrote:
> 
> 
> > -Original Message-
> > From: Dmytriyenko, Denys
> > Sent: Thursday, August 23, 2018 12:04 PM
> > To: Nelson, Sam
> > Cc: meta-ti@yoctoproject.org; Zhang, Hao
> > Subject: Re: [meta-ti] [rocko][PATCH] ti-pdk: Add tool chain dependencies 
> > for
> > am65xx platform
> > 
> > On Wed, Aug 22, 2018 at 07:14:16PM -0400, Nelson, Sam wrote:
> > >
> > >
> > > > -Original Message-
> > > > From: Dmytriyenko, Denys
> > > > Sent: Wednesday, August 22, 2018 6:50 PM
> > > > To: Nelson, Sam
> > > > Cc: meta-ti@yoctoproject.org; Zhang, Hao
> > > > Subject: Re: [meta-ti] [rocko][PATCH] ti-pdk: Add tool chain 
> > > > dependencies
> > for
> > > > am65xx platform
> > > >
> > > > On Wed, Aug 22, 2018 at 05:18:50PM -0400, Sam Nelson wrote:
> > > > > Adds the dependency on toolchain needed for A53 and R5 cores
> > > > >
> > > > > Signed-off-by: Sam Nelson 
> > > > > ---
> > > > >  classes/ti-pdk.bbclass | 4 
> > > > >  1 file changed, 4 insertions(+)
> > > > >
> > > > > diff --git a/classes/ti-pdk.bbclass b/classes/ti-pdk.bbclass
> > > > > index 7ad6205..f0d14a7 100644
> > > > > --- a/classes/ti-pdk.bbclass
> > > > > +++ b/classes/ti-pdk.bbclass
> > > > > @@ -9,6 +9,8 @@ DEPENDS_append_omap-a15 = " ti-cgt-arm-native"
> > > > >  DEPENDS_remove_ti33x = "ti-cgt6x-native"
> > > > >  DEPENDS_remove_ti43x = "ti-cgt6x-native"
> > > > >  DEPENDS_append_omapl1 = " ti-cgt-arm-native"
> > > > > +DEPENDS_remove_am65xx-evm = "gcc-arm-none-eabi-native ti-cgt6x-
> > > > native"
> > > >
> > > > Will gcc-arm-none-eabi-native recipe be removed?
> > >
> > > My understanding is gcc-arm-none-eabi-native will still be used for A15.
> > 
> > That's strange, because both armv7 and armv8 versions of baremetal Linaro
> > gcc
> > were added by Hao recently...
> 
> Checked with Hao to confirm.
> Looks like we cannot use baremetal gcc linaro for a15 currently.  
> (we may move to use baremetal gcc linaro later)
> So this patch has to stay in the current form for now.

Ok, sounds good, thanks. Please don't forget to clean it up later.


> > > > > +DEPENDS_append_am65xx-evm = " ti-cgt-arm-native gcc-linaro-
> > baremetal-
> > > > aarch64-native"
> > > > >
> > > > >  S = "${WORKDIR}/git"
> > > > >  B = "${WORKDIR}/build"
> > > > > @@ -42,6 +44,8 @@ export TOOLCHAIN_PATH_M4 =
> > > > "${M4_TOOLCHAIN_INSTALL_DIR}"
> > > > >  export TOOLCHAIN_PATH_Arm9 = "${M4_TOOLCHAIN_INSTALL_DIR}"
> > > > >  export C6X_GEN_INSTALL_PATH =
> > > > "${STAGING_DIR_NATIVE}/usr/share/ti/cgt-c6x"
> > > > >  export CL_PRU_INSTALL_PATH = "${TI_CGT_PRU_INSTALL_DIR}"
> > > > > +export TOOLCHAIN_PATH_GCC_ARCH64 =
> > > > "${GCC_LINARO_BAREMETAL_AARCH64_TOOLCHAIN}"
> > > > > +export TOOLCHAIN_PATH_R5 = "${M4_TOOLCHAIN_INSTALL_DIR}"
> > > > >
> > > > >  export ROOTDIR = "${B}"
> > > > >  export BIOS_INSTALL_PATH = "${SYSBIOS_INSTALL_DIR}"
> > > > > --
> > > > > 1.9.1
> > > > >
> > > > > --
> > > > > ___
> > > > > meta-ti mailing list
> > > > > meta-ti@yoctoproject.org
> > > > > https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [rocko][PATCH v4 4/4] sciclient: Add recipe for SCI client driver

[Denys Dmytriyenko]

On Thu, Aug 23, 2018 at 02:28:09PM -0400, Sam Nelson wrote:
> Sci client provides API to communicate with the core running System
> firmware
> 
> Signed-off-by: Sam Nelson 
> 
> ---
> Change from previous version of patch
> - Remove redundant description
> - remove redudant defines

Sam,

Can you please make these 2 changes as a separate patch? I wanted to start 
testing all the other updates right away and didn't wait for your v4, but 
instead went with v3, as the changes are rather cosmetical. Thanks.


> ---
> ---
>  recipes-bsp/sciclient/sciclient-rtos_git.bb | 83 
> +
>  1 file changed, 83 insertions(+)
>  create mode 100644 recipes-bsp/sciclient/sciclient-rtos_git.bb
> 
> diff --git a/recipes-bsp/sciclient/sciclient-rtos_git.bb 
> b/recipes-bsp/sciclient/sciclient-rtos_git.bb
> new file mode 100644
> index 000..e059f4b
> --- /dev/null
> +++ b/recipes-bsp/sciclient/sciclient-rtos_git.bb
> @@ -0,0 +1,83 @@
> +SUMMARY = "TI RTOS low level driver for SCICLIENT"
> +
> +inherit ti-pdk
> +
> +LICENSE = "BSD-3-Clause"
> +LIC_FILES_CHKSUM = 
> "file://sciclient.h;beginline=1;endline=31;md5=7224b2eeca1444815f1737bfcdfa892a"
> +
> +COMPATIBLE_MACHINE = "k3"
> +PACKAGE_ARCH = "${MACHINE_ARCH}"
> +
> +SCICLIENT_GIT_URI = "git://git.ti.com/keystone-rtos/sciclient.git"
> +SCICLIENT_GIT_PROTOCOL = "git"
> +SCICLIENT_GIT_BRANCH = "master"
> +
> +# Below commit ID corresponds to "DEV.SCICLIENT.01.00.00.00"
> +SCICLIENT_SRCREV = "4ac052a70764c5fcf9dd18d521fe3b631bfcd875"
> +
> +BRANCH = "${SCICLIENT_GIT_BRANCH}"
> +SRC_URI = 
> "${SCICLIENT_GIT_URI};protocol=${SCICLIENT_GIT_PROTOCOL};branch=${BRANCH}"
> +
> +SRCREV = "${SCICLIENT_SRCREV}"
> +PV = "01.00.00.00"
> +PR = "r0"
> +
> +DEPENDS_append = " osal-rtos common-csl-ip-rtos"
> +
> +# Build with make instead of XDC
> +TI_PDK_XDCMAKE = "0"
> +
> +SCICLIENT_PACKAGE_BASE   = "${S}/../sciclient_base"
> +SCICLIENT_ROOTPATH = 
> "${SCICLIENT_PACKAGE_BASE}/package/all/pdk_/packages/ti/drv/sciclient"
> +
> +export PDK_INSTALL_PATH = "${PDK_INSTALL_DIR}/packages"
> +export PDK_SCICLIENT_ROOT_PATH = 
> "${SCICLIENT_PACKAGE_BASE}/package/all/pdk_/packages"
> +
> +#export PDK_SCICLIENT_ROOT_PATH ="${WORKDIR}/build"
> +#export DEST_ROOT="${S}"
> +
> +LIMSOCS_am65xx-evm = "am65xx"
> +LIMBOARDS_am65xx-evm = "am65xx_evm"
> +BOARD_PACKAGE_am65xx-evm = "am65xx_evm"
> +
> +# HTML doc link params
> +PDK_COMP_LINK_TEXT = "SCICLIENT"
> +
> +do_configure() {
> +
> +rm -rf ${SCICLIENT_PACKAGE_BASE}
> +cd ${S}
> +
> +# remove any previous package
> +rm -f ${SCICLIENT_PACKAGE_BASE}
> +
> +# make the release package before building it
> +make package BOARD=${BOARD_PACKAGE} DEST_ROOT=${SCICLIENT_PACKAGE_BASE} 
> PDK_SCICLIENT_COMP_PATH=${S}
> +
> +   # This is to ensure the make package completed successfully
> +cat  ${SCICLIENT_ROOTPATH}/makefile
> +}
> +
> +do_compile() {
> +
> +cd ${SCICLIENT_ROOTPATH}
> +
> +# Clean
> +# make clean LIMIT_SOCS="${LIMSOCS}" LIMIT_BOARDS="${LIMBOARDS}"
> +
> +# Build am65xx libraries
> +make lib xdc_meta doxygen LIMIT_SOCS="${LIMSOCS}" 
> LIMIT_BOARDS="${LIMBOARDS}"
> +
> +#archive
> +tar -cf sciclient.tar --exclude='*.tar' ./*
> +}
> +
> +do_install() {
> +cd ${SCICLIENT_ROOTPATH}
> +install -d ${D}${PDK_INSTALL_DIR_RECIPE}/packages/ti/drv/sciclient
> +find -name "*.tar" -exec tar xf {} --no-same-owner -C 
> ${D}${PDK_INSTALL_DIR_RECIPE}/packages/ti/drv/sciclient \;
> +}
> +
> +FILES_${PN} += "${PDK_INSTALL_DIR_RECIPE}/packages"
> +
> +INSANE_SKIP_${PN} = "arch ldflags file-rdeps"
> -- 
> 1.9.1
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] Getting Started with meta-ti "rocko" and beaglebone black (BBB)

[Denys Dmytriyenko]

Check if your rootfs contains zImage and DTBs in /boot as well as modules in 
/lib/modules - I don't believe "minimal" image handles those automatically.

Alternatively, don't use "minimal" image, but rather "base" or a more 
specialized image.

-- 
Denys


On Wed, Aug 22, 2018 at 11:18:49AM -0700, Leo Meza wrote:
> I'm learning yocto and was able to easily boot my BBB with a
> core-image-minimal system using the meta-yocto-bsp layer. However, when I
> removed that layer and tried with meta-ti, I just see this on the Putty
> serial console, it repeats over an over:
> 
> U-Boot SPL 2018.01-g6d540394a4 (Aug 22 2018 - 16:33:01)
> Trying to boot from MMC1
> *** Warning - bad CRC, using default environment
> 
> I'm copying MLO, zImage, u-boot.img, and am335x-boneblack.dtb to the BOOT
> (1st) partition of my uSD card. Then extracting
> core-image-minimal-beaglebone.tar.xz -C to the ROOT (2nd) partition of my
> uSD card. This works fine when using meta-yocto-bsp, but not with meta-ti.
> So, if anyone can help me understand what the different steps are between
> using the two different layers, I'd greatly appreciate it. Spent several
> days trying to figure this out so far.
> 
> Thanks in advance,
> Leo

> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] FW: Problem with TI SDK Build 05.

[Denys Dmytriyenko]

You have some setup issues. From config.log your Linaro GCC seems broken:

configure:3815: checking whether the C compiler works
configure:3837: arm-linux-gnueabihf-gcc  -march=armv7-a -marm -mfpu=neon 
-mfloat-abi=hard 
--sysroot=/home/dcastelow/sdk5/arago/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/libtool-cross/2.4.6-r0/recipe-sysroot
  
-isystem/home/dcastelow/gcc-linaro-7.2.1-2017.11-x86_64_arm-linux-gnueabihf/arm-linux-gnueabihf/include
  -O2 -pipe -g -feliminate-unused-debug-types 
-fdebug-prefix-map=/home/dcastelow/sdk5/arago/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/libtool-cross/2.4.6-r0=/usr/src/debug/libtool-cross/2.4.6-r0
 
-fdebug-prefix-map=/home/dcastelow/sdk5/arago/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/libtool-cross/2.4.6-r0/recipe-sysroot-native=
 
-fdebug-prefix-map=/home/dcastelow/sdk5/arago/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/libtool-cross/2.4.6-r0/recipe-sysroot=
   -isystem/home/dcastelow/gcc-linaro-7.2.1-2017.11-x86_64_arm-linux
 -gnueabihf/arm-linux-gnueabihf/include   
-L/home/dcastelow/gcc-linaro-7.2.1-2017.11-x86_64_arm-linux-gnueabihf/arm-linux-gnueabihf/lib
 
-Wl,-rpath-link,/home/dcastelow/gcc-linaro-7.2.1-2017.11-x86_64_arm-linux-gnueabihf/arm-linux-gnueabihf/lib
 -Wl,-O1 -Wl,--hash-style=gnu conftest.c  >&5
/media/disk/users/dcastelow/gcc-linaro-7.2.1-2017.11-x86_64_arm-linux-gnueabihf/bin/../lib/gcc/arm-linux-gnueabihf/7.2.1/../../../../arm-linux-gnueabihf/bin/ld:
 cannot find ../../lib/libc.so.6
collect2: error: ld returned 1 exit status
[...]
configure:3884: error: in 
`/home/dcastelow/sdk5/arago/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/libtool-cross/2.4.6-r0/build':
configure:3886: error: C compiler cannot create executables

So, since your Linaro GCC cannot cross-compile a simple program, it fails at 
the first dependency that uses it, which happens to be libtool-cross.

Please resolve your setup problems and everything will work w/o any 
modifications to recipes. Thanks.

-- 
Denys


On Wed, Aug 22, 2018 at 03:33:57PM +, David Castelow wrote:
> Hi,
> 
> I had an issue building the latest TI SDK for Sitara processors 
> (05_00_00_15), and Kemal from TI suggested I post my findings here for 
> comment.
> 
> So the build I attempted was for
> 
> $ MACHINE=am335x-evm bitbake arago-base-tisdk-image
> 
> following instructions from
> 
> http 
> //software-dl.ti.com/processor-sdk-linux/esd/docs/latest/linux/Overview.html 
> 
> 
> and using both Linux Mint 17.3 (trusty based) and Ubuntu Xenial (16.04) as 
> host machines, giving essentially the same error.
> 
> The problem appears in failure to build libtool-cross successfully.
> 
> I have traced this back to something in the bitbake recipes/patches that 
> modify the libtool configure script:
> See http://e2e.ti.com/support/arm/sitara_arm/f/791/p/718479/2660196#2660196 
> for the history.
> 
> The build does succeed if I ensure HOST_SYS is defined:
> As I said in my last post to that thread,
> Compilation/build is successful if I edit
> 
> arago/tisdk/sources/oe-core/meta/classes/nativesdk.bbclass
> 
> -#HOST_SYS = "${HOST_ARCH}${TARGET_VENDOR}-${HOST_OS}"
> +HOST_SYS = "${HOST_ARCH}${TARGET_VENDOR}-${HOST_OS}"
> 
> I think this is because there are libtool related .bb files and .patch files 
> that reference either ${host_alias}-libtool or ${HOST_SYS}-libtool.
> 
> If HOST_SYS is empty, then the executable would be called -libtool, and then 
> the configure script fails to clean up as it attempts to execute
> 
> rm -libtool
> 
> which won't work as the file name starts with a - (were this to work, it 
> would need to do the mv/rm of ./${file} rather than just of ${file}).
> 
> I'm not sure if this is the correct solution to the problem, but it suggests 
> the need to set HOST_SYS as part of the build instructions.
> 
> Can you advise if this is correct?
> 
> [cid:GLOMO2018_e6c86ab3-4fac-42ae-88d7-eab266a26da8.png] tfx



> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [rocko][PATCH v3 4/4] sciclient: Add recipe for SCI client driver

[Denys Dmytriyenko]

On Wed, Aug 22, 2018 at 08:25:04PM -0400, Sam Nelson wrote:
> Sci client provides API to communicate with the core running System
> firmware
> 
> Signed-off-by: Sam Nelson 
> 
> ---
> Change from previous version of patch
> - Update compatibility to k3
> ---
> ---
>  recipes-bsp/sciclient/sciclient-rtos_git.bb | 89 
> +
>  1 file changed, 89 insertions(+)
>  create mode 100644 recipes-bsp/sciclient/sciclient-rtos_git.bb
> 
> diff --git a/recipes-bsp/sciclient/sciclient-rtos_git.bb 
> b/recipes-bsp/sciclient/sciclient-rtos_git.bb
> new file mode 100644
> index 000..e899b66
> --- /dev/null
> +++ b/recipes-bsp/sciclient/sciclient-rtos_git.bb
> @@ -0,0 +1,89 @@
> +SUMMARY = "TI RTOS low level driver for SCICLIENT"
> +DESCRIPTION = "TI RTOS low level driver for SCICLIENT "

By default, DESCRIPTION = "${SUMMARY}." so no need to duplicate it, unless you 
provide a more detailed description.


> +inherit ti-pdk
> +
> +LICENSE = "BSD-3-Clause"
> +LIC_FILES_CHKSUM = 
> "file://sciclient.h;beginline=1;endline=31;md5=7224b2eeca1444815f1737bfcdfa892a"
> +
> +COMPATIBLE_MACHINE = "k3"
> +PACKAGE_ARCH = "${MACHINE_ARCH}"
> +
> +SCICLIENT_GIT_URI = "git://git.ti.com/keystone-rtos/sciclient.git"
> +SCICLIENT_GIT_PROTOCOL = "git"
> +SCICLIENT_GIT_BRANCH = "master"
> +
> +# Below commit ID corresponds to "DEV.SCICLIENT.01.00.00.00"
> +SCICLIENT_SRCREV = "4ac052a70764c5fcf9dd18d521fe3b631bfcd875"
> +
> +BRANCH = "${SCICLIENT_GIT_BRANCH}"
> +SRC_URI = 
> "${SCICLIENT_GIT_URI};protocol=${SCICLIENT_GIT_PROTOCOL};branch=${BRANCH}"
> +
> +SRCREV = "${SCICLIENT_SRCREV}"
> +PV = "01.00.00.00"
> +PR = "r0"
> +
> +DEPENDS_append = " osal-rtos common-csl-ip-rtos"
> +
> +# Build with make instead of XDC
> +TI_PDK_XDCMAKE = "0"
> +
> +SCICLIENT_PACKAGE_BASE   = "${S}/../sciclient_base"
> +SCICLIENT_ROOTPATH = 
> "${SCICLIENT_PACKAGE_BASE}/package/all/pdk_/packages/ti/drv/sciclient"
> +
> +export PDK_INSTALL_PATH = "${PDK_INSTALL_DIR}/packages"
> +export PDK_SCICLIENT_ROOT_PATH = 
> "${SCICLIENT_PACKAGE_BASE}/package/all/pdk_/packages"
> +
> +#export PDK_SCICLIENT_ROOT_PATH ="${WORKDIR}/build"
> +#export DEST_ROOT="${S}"
> +
> +LIMSOCS = "am65xx"
> +LIMSOCS_am65xx-evm = "am65xx"
> +
> +LIMBOARDS = "am65xx_evm"
> +LIMBOARDS_am65xx-evm = "am65xx_evm"

The above 4 lines look strange right now - the second line in each pair is 
redundant at the moment.


> +BOARD_PACKAGE = ""
> +BOARD_PACKAGE_am65xx-evm = "am65xx_evm"
> +
> +# HTML doc link params
> +PDK_COMP_LINK_TEXT = "SCICLIENT"
> +
> +do_configure() {
> +
> +rm -rf ${SCICLIENT_PACKAGE_BASE}
> +cd ${S}
> +
> +# remove any previous package
> +rm -f ${SCICLIENT_PACKAGE_BASE}
> +
> +# make the release package before building it
> +make package BOARD=${BOARD_PACKAGE} DEST_ROOT=${SCICLIENT_PACKAGE_BASE} 
> PDK_SCICLIENT_COMP_PATH=${S}
> +
> +   # This is to ensure the make package completed successfully
> +cat  ${SCICLIENT_ROOTPATH}/makefile
> +}
> +
> +do_compile() {
> +
> +cd ${SCICLIENT_ROOTPATH}
> +
> +# Clean
> +# make clean LIMIT_SOCS="${LIMSOCS}" LIMIT_BOARDS="${LIMBOARDS}"
> +
> +# Build am65xx libraries
> +make lib xdc_meta doxygen LIMIT_SOCS="${LIMSOCS}" 
> LIMIT_BOARDS="${LIMBOARDS}"
> +
> +#archive
> +tar -cf sciclient.tar --exclude='*.tar' ./*
> +}
> +
> +do_install() {
> +cd ${SCICLIENT_ROOTPATH}
> +install -d ${D}${PDK_INSTALL_DIR_RECIPE}/packages/ti/drv/sciclient
> +find -name "*.tar" -exec tar xf {} --no-same-owner -C 
> ${D}${PDK_INSTALL_DIR_RECIPE}/packages/ti/drv/sciclient \;
> +}
> +
> +FILES_${PN} += "${PDK_INSTALL_DIR_RECIPE}/packages"
> +
> +INSANE_SKIP_${PN} = "arch ldflags file-rdeps"
> -- 
> 1.9.1
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [rocko][PATCH] ti-pdk: Add tool chain dependencies for am65xx platform

[Denys Dmytriyenko]

On Wed, Aug 22, 2018 at 07:14:16PM -0400, Nelson, Sam wrote:
> 
> 
> > -Original Message-
> > From: Dmytriyenko, Denys
> > Sent: Wednesday, August 22, 2018 6:50 PM
> > To: Nelson, Sam
> > Cc: meta-ti@yoctoproject.org; Zhang, Hao
> > Subject: Re: [meta-ti] [rocko][PATCH] ti-pdk: Add tool chain dependencies 
> > for
> > am65xx platform
> > 
> > On Wed, Aug 22, 2018 at 05:18:50PM -0400, Sam Nelson wrote:
> > > Adds the dependency on toolchain needed for A53 and R5 cores
> > >
> > > Signed-off-by: Sam Nelson 
> > > ---
> > >  classes/ti-pdk.bbclass | 4 
> > >  1 file changed, 4 insertions(+)
> > >
> > > diff --git a/classes/ti-pdk.bbclass b/classes/ti-pdk.bbclass
> > > index 7ad6205..f0d14a7 100644
> > > --- a/classes/ti-pdk.bbclass
> > > +++ b/classes/ti-pdk.bbclass
> > > @@ -9,6 +9,8 @@ DEPENDS_append_omap-a15 = " ti-cgt-arm-native"
> > >  DEPENDS_remove_ti33x = "ti-cgt6x-native"
> > >  DEPENDS_remove_ti43x = "ti-cgt6x-native"
> > >  DEPENDS_append_omapl1 = " ti-cgt-arm-native"
> > > +DEPENDS_remove_am65xx-evm = "gcc-arm-none-eabi-native ti-cgt6x-
> > native"
> > 
> > Will gcc-arm-none-eabi-native recipe be removed?
> 
> My understanding is gcc-arm-none-eabi-native will still be used for A15.

That's strange, because both armv7 and armv8 versions of baremetal Linaro gcc 
were added by Hao recently...


> > > +DEPENDS_append_am65xx-evm = " ti-cgt-arm-native gcc-linaro-baremetal-
> > aarch64-native"
> > >
> > >  S = "${WORKDIR}/git"
> > >  B = "${WORKDIR}/build"
> > > @@ -42,6 +44,8 @@ export TOOLCHAIN_PATH_M4 =
> > "${M4_TOOLCHAIN_INSTALL_DIR}"
> > >  export TOOLCHAIN_PATH_Arm9 = "${M4_TOOLCHAIN_INSTALL_DIR}"
> > >  export C6X_GEN_INSTALL_PATH =
> > "${STAGING_DIR_NATIVE}/usr/share/ti/cgt-c6x"
> > >  export CL_PRU_INSTALL_PATH = "${TI_CGT_PRU_INSTALL_DIR}"
> > > +export TOOLCHAIN_PATH_GCC_ARCH64 =
> > "${GCC_LINARO_BAREMETAL_AARCH64_TOOLCHAIN}"
> > > +export TOOLCHAIN_PATH_R5 = "${M4_TOOLCHAIN_INSTALL_DIR}"
> > >
> > >  export ROOTDIR = "${B}"
> > >  export BIOS_INSTALL_PATH = "${SYSBIOS_INSTALL_DIR}"
> > > --
> > > 1.9.1
> > >
> > > --
> > > ___
> > > meta-ti mailing list
> > > meta-ti@yoctoproject.org
> > > https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [rocko][PATCH 1/4] ti-pdk-build-rtos: Update to new version 1.0.0.10

[Denys Dmytriyenko]

On Wed, Aug 22, 2018 at 07:28:53PM -0400, Nelson, Sam wrote:
> 
> 
> > -Original Message-
> > From: Dmytriyenko, Denys
> > Sent: Wednesday, August 22, 2018 6:47 PM
> > To: Nelson, Sam
> > Cc: meta-ti@yoctoproject.org
> > Subject: Re: [meta-ti] [rocko][PATCH 1/4] ti-pdk-build-rtos: Update to new
> > version 1.0.0.10
> > 
> > On Wed, Aug 22, 2018 at 05:50:49PM -0400, Sam Nelson wrote:
> > > Add support for am65xx-evm
> > >
> > > Signed-off-by: Sam Nelson 
> > > ---
> > >  recipes-ti/ti-pdk-build/ti-pdk-build-rtos_git.bb | 9 -
> > >  1 file changed, 4 insertions(+), 5 deletions(-)
> > >
> > > diff --git a/recipes-ti/ti-pdk-build/ti-pdk-build-rtos_git.bb 
> > > b/recipes-ti/ti-
> > pdk-build/ti-pdk-build-rtos_git.bb
> > > index c838d71..fd716d7 100644
> > > --- a/recipes-ti/ti-pdk-build/ti-pdk-build-rtos_git.bb
> > > +++ b/recipes-ti/ti-pdk-build/ti-pdk-build-rtos_git.bb
> > > @@ -4,25 +4,24 @@ LIC_FILES_CHKSUM =
> > "file://makerules/env.mk;beginline=1;endline=31;md5=10503e8de
> > >
> > >  require recipes-ti/includes/ti-paths.inc
> > >
> > > -PV = "01.00.00.09A"
> > > +PV = "01.00.00.10"
> > >  PR = "r0"
> > >
> > >  PDK_BUILD_GIT_URI = "git://git.ti.com/keystone-rtos/processor-pdk-
> > build.git"
> > >  PDK_BUILD_GIT_PROTOCOL = "git"
> > >  PDK_BUILD_GIT_BRANCH = "master"
> > >
> > > -# Below Commit ID corresponds to "DEV.PDK_BUILD.01.00.00.09A"
> > > -PDK_BUILD_SRCREV = "4870d6cfcab92dfedae8ed28054fdc61169e28b1"
> > > +# Below Commit ID corresponds to "DEV.PDK_BUILD.01.00.00.10"
> > > +PDK_BUILD_SRCREV = "f06835474e51a5fd63cf23bab0d2f42b0f73f19d"
> > >
> > >  BRANCH = "${PDK_BUILD_GIT_BRANCH}"
> > >  SRC_URI = "\
> > >
> > ${PDK_BUILD_GIT_URI};protocol=${PDK_BUILD_GIT_PROTOCOL};branch=${BR
> > ANCH} \
> > > -file://0001-comp_mk-Allow-doxygen-support-to-be-overridden.patch \
> > 
> > ???
> 
> This patch is already part of the new baseline. So can be removed..

Then you'd want to remove corresponding file.


> > >  "
> > >
> > >  SRCREV = "${PDK_BUILD_SRCREV}"
> > >
> > > -COMPATIBLE_MACHINE = "ti33x|ti43x|omap-a15|keystone|omapl1|c66x"
> > > +COMPATIBLE_MACHINE = "ti33x|ti43x|omap-
> > a15|keystone|omapl1|c66x|am65xx-evm"
> > 
> > k3?
> 
> Yes k3.

I meant maybe you want to use "k3" isntead of "am65xx-evm" here?


> > >  PACKAGE_ARCH = "${MACHINE_ARCH}"
> > >
> > >  S = "${WORKDIR}/git/"
> > > --
> > > 1.9.1
> > >
> > > --
> > > ___
> > > meta-ti mailing list
> > > meta-ti@yoctoproject.org
> > > https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [rocko][PATCH] ti-pdk: Add tool chain dependencies for am65xx platform

[Denys Dmytriyenko]

On Wed, Aug 22, 2018 at 05:18:50PM -0400, Sam Nelson wrote:
> Adds the dependency on toolchain needed for A53 and R5 cores
> 
> Signed-off-by: Sam Nelson 
> ---
>  classes/ti-pdk.bbclass | 4 
>  1 file changed, 4 insertions(+)
> 
> diff --git a/classes/ti-pdk.bbclass b/classes/ti-pdk.bbclass
> index 7ad6205..f0d14a7 100644
> --- a/classes/ti-pdk.bbclass
> +++ b/classes/ti-pdk.bbclass
> @@ -9,6 +9,8 @@ DEPENDS_append_omap-a15 = " ti-cgt-arm-native"
>  DEPENDS_remove_ti33x = "ti-cgt6x-native"
>  DEPENDS_remove_ti43x = "ti-cgt6x-native"
>  DEPENDS_append_omapl1 = " ti-cgt-arm-native"
> +DEPENDS_remove_am65xx-evm = "gcc-arm-none-eabi-native ti-cgt6x-native"

Will gcc-arm-none-eabi-native recipe be removed?


> +DEPENDS_append_am65xx-evm = " ti-cgt-arm-native 
> gcc-linaro-baremetal-aarch64-native"
>  
>  S = "${WORKDIR}/git"
>  B = "${WORKDIR}/build"
> @@ -42,6 +44,8 @@ export TOOLCHAIN_PATH_M4 = "${M4_TOOLCHAIN_INSTALL_DIR}"
>  export TOOLCHAIN_PATH_Arm9 = "${M4_TOOLCHAIN_INSTALL_DIR}"
>  export C6X_GEN_INSTALL_PATH = "${STAGING_DIR_NATIVE}/usr/share/ti/cgt-c6x"
>  export CL_PRU_INSTALL_PATH = "${TI_CGT_PRU_INSTALL_DIR}"
> +export TOOLCHAIN_PATH_GCC_ARCH64 = 
> "${GCC_LINARO_BAREMETAL_AARCH64_TOOLCHAIN}"
> +export TOOLCHAIN_PATH_R5 = "${M4_TOOLCHAIN_INSTALL_DIR}"
>  
>  export ROOTDIR = "${B}"
>  export BIOS_INSTALL_PATH = "${SYSBIOS_INSTALL_DIR}"
> -- 
> 1.9.1
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [rocko][PATCH 2/4] common-csl-ip: Update to new version 05.01.00.00

[Denys Dmytriyenko]

On Wed, Aug 22, 2018 at 05:50:50PM -0400, Sam Nelson wrote:
> Adds support for am65xx
> 
> Signed-off-by: Sam Nelson 
> ---
>  recipes-bsp/common-csl-ip/common-csl-ip-rtos_git.bb | 2 +-
>  recipes-bsp/common-csl-ip/common-csl-ip.inc | 6 +++---
>  2 files changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/recipes-bsp/common-csl-ip/common-csl-ip-rtos_git.bb 
> b/recipes-bsp/common-csl-ip/common-csl-ip-rtos_git.bb
> index 5f2dbd5..7da02a3 100644
> --- a/recipes-bsp/common-csl-ip/common-csl-ip-rtos_git.bb
> +++ b/recipes-bsp/common-csl-ip/common-csl-ip-rtos_git.bb
> @@ -2,7 +2,7 @@ require common-csl-ip.inc
>  PR = "${INC_PR}.6"
>  
>  PACKAGE_ARCH = "${MACHINE_ARCH}"
> -COMPATIBLE_MACHINE_append = "|c66x"
> +COMPATIBLE_MACHINE_append = "|c66x|am65xx-evm"

k3?


>  inherit ti-pdk
>  
> diff --git a/recipes-bsp/common-csl-ip/common-csl-ip.inc 
> b/recipes-bsp/common-csl-ip/common-csl-ip.inc
> index 8387095..ed8078d 100644
> --- a/recipes-bsp/common-csl-ip/common-csl-ip.inc
> +++ b/recipes-bsp/common-csl-ip/common-csl-ip.inc
> @@ -4,7 +4,7 @@ LIC_FILES_CHKSUM = 
> "file://COPYING.txt;md5=5857833e20836213677fac33f9aded21"
>  
>  COMPATIBLE_MACHINE = "keystone|dra7xx|ti33x|ti43x|omapl1"
>  
> -PV = "03.03.00.11A"
> +PV = "05.01.00.00"
>  INC_PR = "r0"
>  
>  CSL_GIT_URI = "git://git.ti.com/keystone-rtos/common-csl-ip.git"
> @@ -12,8 +12,8 @@ CSL_GIT_PROTOCOL ="git"
>  CSL_GIT_BRANCH = "master"
>  CSL_GIT_DESTSUFFIX = "git"
>  
> -# Below commit ID corresponding to "DEV.CSL_PROCESSOR-SDK.03.03.00.11A"
> -CSL_SRCREV = "c7b021fd5e7efa2feb8f558b3a3fd63d5dee266f"
> +# Below commit ID corresponding to "DEV.CSL_PROCESSOR-SDK.05.01.00.00"
> +CSL_SRCREV = "8db3d673101a504fd7fb36d6c9c4981e1e15ff50"
>  
>  BRANCH="${CSL_GIT_BRANCH}"
>  SRC_URI = 
> "${CSL_GIT_URI};protocol=${CSL_GIT_PROTOCOL};branch=${BRANCH};destsuffix=${CSL_GIT_DESTSUFFIX}"
> -- 
> 1.9.1
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [rocko][PATCH 3/4] osal: Update to new version 1.0.0.12

[Denys Dmytriyenko]

On Wed, Aug 22, 2018 at 05:50:51PM -0400, Sam Nelson wrote:
> Adds support for AM65XX platform
> 
> NOTE:
> License checksum change is just due to addition of current year
> 2018 to copyright
> 
> Signed-off-by: Sam Nelson 
> ---
>  recipes-bsp/osal/osal-rtos_git.bb | 2 +-
>  recipes-bsp/osal/osal.inc | 8 
>  2 files changed, 5 insertions(+), 5 deletions(-)
> 
> diff --git a/recipes-bsp/osal/osal-rtos_git.bb 
> b/recipes-bsp/osal/osal-rtos_git.bb
> index b150760..8ba7862 100644
> --- a/recipes-bsp/osal/osal-rtos_git.bb
> +++ b/recipes-bsp/osal/osal-rtos_git.bb
> @@ -3,7 +3,7 @@ require recipes-bsp/osal/osal.inc
>  
>  PR = "${INC_PR}.0"
>  
> -COMPATIBLE_MACHINE_append = "|c66x"
> +COMPATIBLE_MACHINE_append = "|c66x|am65xx-evm"

k3?


>  S = "${WORKDIR}/${OSAL_GIT_DESTSUFFIX}"
>  
> diff --git a/recipes-bsp/osal/osal.inc b/recipes-bsp/osal/osal.inc
> index 16cf1fa..f360244 100644
> --- a/recipes-bsp/osal/osal.inc
> +++ b/recipes-bsp/osal/osal.inc
> @@ -1,5 +1,5 @@
>  LICENSE = "BSD-3-Clause"
> -LIC_FILES_CHKSUM = 
> "file://osal.h;beginline=1;endline=31;md5=ae7b9f0410f26c80dcf790ef3f622fad"
> +LIC_FILES_CHKSUM = 
> "file://osal.h;beginline=1;endline=31;md5=6fbde6922f8bca1e6cd371d3c2faa4f9"
>  
>  COMPATIBLE_MACHINE = "ti33x|ti43x|omap-a15|keystone|omapl1"
>  PACKAGE_ARCH = "${MACHINE_ARCH}"
> @@ -9,12 +9,12 @@ OSAL_GIT_PROTOCOL = "git"
>  OSAL_GIT_BRANCH = "master"
>  OSAL_GIT_DESTSUFFIX = "git/ti/osal"
>  
> -# Below commit ID corresponding to "DEV.OSAL.01.00.00.11"
> -OSAL_SRCREV = "6113a74a2aded1aa1c339708d39b2e47e74263e9"
> +# Below commit ID corresponding to "DEV.OSAL.01.00.00.12"
> +OSAL_SRCREV = "d93d8833e5e0bbd3e76f8618a4f717e3539a8d11"
>  
>  BRANCH = "${OSAL_GIT_BRANCH}"
>  SRC_URI = 
> "${OSAL_GIT_URI};destsuffix=${OSAL_GIT_DESTSUFFIX};protocol=${OSAL_GIT_PROTOCOL};branch=${BRANCH}"
>  
>  SRCREV = "${OSAL_SRCREV}"
> -PV = "01.00.00.11"
> +PV = "01.00.00.12"
>  INC_PR = "r0"
> -- 
> 1.9.1
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [rocko][PATCH 1/4] ti-pdk-build-rtos: Update to new version 1.0.0.10

[Denys Dmytriyenko]

On Wed, Aug 22, 2018 at 05:50:49PM -0400, Sam Nelson wrote:
> Add support for am65xx-evm
> 
> Signed-off-by: Sam Nelson 
> ---
>  recipes-ti/ti-pdk-build/ti-pdk-build-rtos_git.bb | 9 -
>  1 file changed, 4 insertions(+), 5 deletions(-)
> 
> diff --git a/recipes-ti/ti-pdk-build/ti-pdk-build-rtos_git.bb 
> b/recipes-ti/ti-pdk-build/ti-pdk-build-rtos_git.bb
> index c838d71..fd716d7 100644
> --- a/recipes-ti/ti-pdk-build/ti-pdk-build-rtos_git.bb
> +++ b/recipes-ti/ti-pdk-build/ti-pdk-build-rtos_git.bb
> @@ -4,25 +4,24 @@ LIC_FILES_CHKSUM = 
> "file://makerules/env.mk;beginline=1;endline=31;md5=10503e8de
>  
>  require recipes-ti/includes/ti-paths.inc
>  
> -PV = "01.00.00.09A"
> +PV = "01.00.00.10"
>  PR = "r0"
>  
>  PDK_BUILD_GIT_URI = "git://git.ti.com/keystone-rtos/processor-pdk-build.git"
>  PDK_BUILD_GIT_PROTOCOL = "git"
>  PDK_BUILD_GIT_BRANCH = "master"
>  
> -# Below Commit ID corresponds to "DEV.PDK_BUILD.01.00.00.09A"
> -PDK_BUILD_SRCREV = "4870d6cfcab92dfedae8ed28054fdc61169e28b1"
> +# Below Commit ID corresponds to "DEV.PDK_BUILD.01.00.00.10"
> +PDK_BUILD_SRCREV = "f06835474e51a5fd63cf23bab0d2f42b0f73f19d"
>  
>  BRANCH = "${PDK_BUILD_GIT_BRANCH}"
>  SRC_URI = "\
>  ${PDK_BUILD_GIT_URI};protocol=${PDK_BUILD_GIT_PROTOCOL};branch=${BRANCH} 
> \
> -file://0001-comp_mk-Allow-doxygen-support-to-be-overridden.patch \

???


>  "
>  
>  SRCREV = "${PDK_BUILD_SRCREV}"
>  
> -COMPATIBLE_MACHINE = "ti33x|ti43x|omap-a15|keystone|omapl1|c66x"
> +COMPATIBLE_MACHINE = "ti33x|ti43x|omap-a15|keystone|omapl1|c66x|am65xx-evm"

k3?


>  PACKAGE_ARCH = "${MACHINE_ARCH}"
>  
>  S = "${WORKDIR}/git/"
> -- 
> 1.9.1
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [rocko][PATCH 4/4] sciclient: Add recipe for SCI client driver

[Denys Dmytriyenko]

On Wed, Aug 22, 2018 at 05:50:52PM -0400, Sam Nelson wrote:
> Sci client provides API to communicate with the core running System
> firmware
> 
> Signed-off-by: Sam Nelson 
> ---
>  recipes-bsp/sciclient/sciclient-rtos_git.bb | 89 
> +
>  1 file changed, 89 insertions(+)
>  create mode 100644 recipes-bsp/sciclient/sciclient-rtos_git.bb
> 
> diff --git a/recipes-bsp/sciclient/sciclient-rtos_git.bb 
> b/recipes-bsp/sciclient/sciclient-rtos_git.bb
> new file mode 100644
> index 000..6a6de40
> --- /dev/null
> +++ b/recipes-bsp/sciclient/sciclient-rtos_git.bb
> @@ -0,0 +1,89 @@
> +SUMMARY = "TI RTOS low level driver for SCICLIENT"
> +DESCRIPTION = "TI RTOS low level driver for SCICLIENT "
> +
> +inherit ti-pdk
> +
> +LICENSE = "BSD-3-Clause"
> +LIC_FILES_CHKSUM = 
> "file://sciclient.h;beginline=1;endline=31;md5=7224b2eeca1444815f1737bfcdfa892a"
> +
> +COMPATIBLE_MACHINE = "am65xx-evm"
> +PACKAGE_ARCH = "${MACHINE_ARCH}"
> +
> +SCICLIENT_GIT_URI = 
> "git://g...@bitbucket.itg.ti.com/processor-sdk/sciclient.git"

NAK!


> +SCICLIENT_GIT_PROTOCOL = "ssh"
> +SCICLIENT_GIT_BRANCH = "master"
> +
> +# Below commit ID corresponds to "DEV.SCICLIENT.01.00.00.00"
> +SCICLIENT_SRCREV = "4ac052a70764c5fcf9dd18d521fe3b631bfcd875"
> +
> +BRANCH = "${SCICLIENT_GIT_BRANCH}"
> +SRC_URI = 
> "${SCICLIENT_GIT_URI};protocol=${SCICLIENT_GIT_PROTOCOL};branch=${BRANCH}"
> +
> +SRCREV = "${SCICLIENT_SRCREV}"
> +PV = "01.00.00.00"
> +PR = "r0"
> +
> +DEPENDS_append = " osal-rtos common-csl-ip-rtos"
> +
> +# Build with make instead of XDC
> +TI_PDK_XDCMAKE = "0"
> +
> +SCICLIENT_PACKAGE_BASE   = "${S}/../sciclient_base"
> +SCICLIENT_ROOTPATH = 
> "${SCICLIENT_PACKAGE_BASE}/package/all/pdk_/packages/ti/drv/sciclient"
> +
> +export PDK_INSTALL_PATH = "${PDK_INSTALL_DIR}/packages"
> +export PDK_SCICLIENT_ROOT_PATH = 
> "${SCICLIENT_PACKAGE_BASE}/package/all/pdk_/packages"
> +
> +#export PDK_SCICLIENT_ROOT_PATH ="${WORKDIR}/build"
> +#export DEST_ROOT="${S}"
> +
> +LIMSOCS = "am65xx"
> +LIMSOCS_am65xx-evm = "am65xx"
> +
> +LIMBOARDS = "am65xx_evm"
> +LIMBOARDS_am65xx-evm = "am65xx_evm"
> +
> +BOARD_PACKAGE = ""
> +BOARD_PACKAGE_am65xx-evm = "am65xx_evm"
> +
> +# HTML doc link params
> +PDK_COMP_LINK_TEXT = "SCICLIENT"
> +
> +do_configure() {
> +
> +rm -rf ${SCICLIENT_PACKAGE_BASE}
> +cd ${S}
> +
> +# remove any previous package
> +rm -f ${SCICLIENT_PACKAGE_BASE}
> +
> +# make the release package before building it
> +make package BOARD=${BOARD_PACKAGE} DEST_ROOT=${SCICLIENT_PACKAGE_BASE} 
> PDK_SCICLIENT_COMP_PATH=${S}
> +
> +   # This is to ensure the make package completed successfully
> +cat  ${SCICLIENT_ROOTPATH}/makefile
> +}
> +
> +do_compile() {
> +
> +cd ${SCICLIENT_ROOTPATH}
> +
> +# Clean
> +# make clean LIMIT_SOCS="${LIMSOCS}" LIMIT_BOARDS="${LIMBOARDS}"
> +
> +# Build am65xx libraries
> +make lib xdc_meta doxygen LIMIT_SOCS="${LIMSOCS}" 
> LIMIT_BOARDS="${LIMBOARDS}"
> +
> +#archive
> +tar -cf sciclient.tar --exclude='*.tar' ./*
> +}
> +
> +do_install() {
> +cd ${SCICLIENT_ROOTPATH}
> +install -d ${D}${PDK_INSTALL_DIR_RECIPE}/packages/ti/drv/sciclient
> +find -name "*.tar" -exec tar xf {} --no-same-owner -C 
> ${D}${PDK_INSTALL_DIR_RECIPE}/packages/ti/drv/sciclient \;
> +}
> +
> +FILES_${PN} += "${PDK_INSTALL_DIR_RECIPE}/packages"
> +
> +INSANE_SKIP_${PN} = "arch ldflags file-rdeps"
> -- 
> 1.9.1
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [rocko][PATCH v2] am65xx-evm: Add PDK specific soc, boards and cores configuration for AM65xx

[Denys Dmytriyenko]

Well, it already says am65xx in the beginning, why do you need to repeat it at 
the end? :)

But fine, I'll take it.


On Wed, Aug 22, 2018 at 04:13:40PM -0400, Sam Nelson wrote:
> Signed-off-by: Sam Nelson 
> 
> ---
> Change from previous version
> Updated title and comments
> ---
> ---
>  conf/machine/am65xx-evm.conf | 5 +
>  1 file changed, 5 insertions(+)
> 
> diff --git a/conf/machine/am65xx-evm.conf b/conf/machine/am65xx-evm.conf
> index 08dbc9e..82ee02c 100644
> --- a/conf/machine/am65xx-evm.conf
> +++ b/conf/machine/am65xx-evm.conf
> @@ -25,3 +25,8 @@ WKS_FILE = "sdimage-bootpart.wks"
>  IMAGE_BOOT_FILES = "u-boot.img"
>  
>  do_image_wic[depends] += "mtools-native:do_populate_sysroot 
> dosfstools-native:do_populate_sysroot"
> +
> +# Set the list of device targets for ti-pdk class recipes
> +TI_PDK_LIMIT_SOCS = "am65xx"
> +TI_PDK_LIMIT_BOARDS = "am65xx_evm am65xx_idk"
> +TI_PDK_LIMIT_CORES = "mcu1_0 mpu1_0"
> -- 
> 1.9.1
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [rocko][PATCH] am65xx-evm: Add am65xx specific soc, boards and cores configuration

[Denys Dmytriyenko]

I believe the commit message should be:

am65xx-evm: Add PDK specific soc, boards and cores configuration

Otherwise it's kind of circular and confusing.


On Wed, Aug 22, 2018 at 04:05:51PM -0400, Sam Nelson wrote:
> Specifies the pdk soc names, board names and core names supported
> 
> Signed-off-by: Sam Nelson 
> ---
>  conf/machine/am65xx-evm.conf | 5 +
>  1 file changed, 5 insertions(+)
> 
> diff --git a/conf/machine/am65xx-evm.conf b/conf/machine/am65xx-evm.conf
> index 08dbc9e..82ee02c 100644
> --- a/conf/machine/am65xx-evm.conf
> +++ b/conf/machine/am65xx-evm.conf
> @@ -25,3 +25,8 @@ WKS_FILE = "sdimage-bootpart.wks"
>  IMAGE_BOOT_FILES = "u-boot.img"
>  
>  do_image_wic[depends] += "mtools-native:do_populate_sysroot 
> dosfstools-native:do_populate_sysroot"
> +
> +# Set the list of device targets for ti-pdk class recipes
> +TI_PDK_LIMIT_SOCS = "am65xx"
> +TI_PDK_LIMIT_BOARDS = "am65xx_evm am65xx_idk"
> +TI_PDK_LIMIT_CORES = "mcu1_0 mpu1_0"
> -- 
> 1.9.1
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [rocko][PATCH V3 2/2] recipes-ti: bios: add TI SYSBIOS 6.73.00.12

[Denys Dmytriyenko]

Karthik,

Would you be able to send a revised patch for ipumm recipe? Thanks.

-- 
Denys


On Fri, Aug 17, 2018 at 09:54:21AM -0500, Suman Anna wrote:
> All,
> My earlier statements on POSIX in SYS/BIOS need to be revised.
> I have got confirmation that POSIX support is still very much a part of
> the released SYS/BIOSes. There is a change in the directory structure
> where the POSIX related modules and headers are maintained. So, we don't
> have any external dependencies. All software would need to adjust for
> the new locations when moving to the newer SYS/BIOS if using the POSIX.
> 
> Karthik,
> You might want to updated the .cfg file as well. Current SYS/BIOS does
> find the new module location when using the older module. Please see the
> compatibility notes in one of the SYS/BIOS releases prior to 6.70 and
> after 6.52.
> 
> regards
> Suman
> 
> On 08/17/2018 07:27 AM, Karthik Ramanan wrote:
> > Denys, Suman,
> > 
> > We looked into this further and the below patch seems to resolve the
> > build issue.
> > 
> > The generated binary hasn't been validated yet, but we can give you
> > feedback on Monday when we get some time to test this ipumm-fw.
> > 
> > Regards
> > 
> > Karthik
> > 
> > 
> > +diff --git a/src/ti/framework/dce/dce.c b/src/ti/framework/dce/dce.c
> > +index 62bea8c..01dbcce 100644
> > +--- a/src/ti/framework/dce/dce.c
> >  b/src/ti/framework/dce/dce.c
> > +@@ -50,7 +50,7 @@
> > + #include 
> > + #include 
> > + #include 
> > +-#include 
> > ++#include 
> > + #include 
> > + #include 
> > + #include 
> > +--
> > 
> > 
> > On 16-Aug-18 6:33 PM, Suman Anna wrote:
> >> Hi Denys,
> >>
> >> I have taken a quick look at this, and looks like the POSIX support in
> >> SYS/BIOS is moved out into its own project. However, I couldn't find a
> >> GA version of that tool released. All users will have to move to the
> >> newer ti.posix.tirtos package. So, this might be a bigger blocker.
> >>
> >> regards
> >> Suman
> >>
> >> On 08/16/2018 06:50 AM, Anna, Suman wrote:
> >>> + Sunita as well.
> >>>
>  Ok, this breaks ipumm-fw build:
> 
>  | NOTE: make -j 56 XDCDIST_TREE=/OE/arago-rocko-next/build/arago-tmp-
>  external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/ipumm-
>  fw/3.00.15.00-r1/recipe-sysroot-native/usr/share/ti/ti-xdctools-tree
>  | export XDCARGS="profile=release trace_level=0 hw_type=VAYU
>  hw_version=ES10 BIOS_type=SMP prof_type=DISABLE"; \
>  | /OE/arago-rocko-next/build/arago-tmp-external-linaro-
>  toolchain/work/armv7ahf-neon-linux-gnueabi/ipumm-fw/3.00.15.00-r1/recipe-
> 
>  sysroot-native/usr/share/ti/ti-xdctools-tree/xdc --jobs=1 -PD
>  /OE/arago-rocko-
>  next/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-
> 
>  gnueabi/ipumm-fw/3.00.15.00-r1/git/platform/ti/dce/baselib/.; \
>  | /OE/arago-rocko-next/build/arago-tmp-external-linaro-
>  toolchain/work/armv7ahf-neon-linux-gnueabi/ipumm-fw/3.00.15.00-r1/recipe-
> 
>  sysroot-native/usr/share/ti/ti-xdctools-tree/xdc --jobs=1 -PD
>  /OE/arago-rocko-
>  next/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-
> 
>  gnueabi/ipumm-fw/3.00.15.00-r1/git/platform/ti/dce/baseimage/.
>  | making all: Thu Aug 16 02:48:21 UTC 2018 ...
>  |  .interfaces
>  [/OE/arago-rocko-next/build/arago-tmp-external-linaro-
>  toolchain/work/armv7ahf-neon-linux-gnueabi/ipumm-fw/3.00.15.00-
>  r1/git/src/ti/framework/dce] 
>  | making package.mak (because of package.bld) ...
>  | Selected Vayu for ES10
>  | generating interfaces for package ti.framework.dce (because
>  package/package.xdc.inc is older than package.xdc) ...
>  |  .interfaces
>  [/OE/arago-rocko-next/build/arago-tmp-external-linaro-
>  toolchain/work/armv7ahf-neon-linux-gnueabi/ipumm-fw/3.00.15.00-
>  r1/git/src/ti/utils] 
>  | making package.mak (because of package.bld) ...
>  | Selected Vayu for ES10
>  | generating interfaces for package src.ti.utils (because
>  package/package.xdc.inc
>  is older than package.xdc) ...
>  |  .interfaces
>  [/OE/arago-rocko-next/build/arago-tmp-external-linaro-
>  toolchain/work/armv7ahf-neon-linux-gnueabi/ipumm-fw/3.00.15.00-
>  r1/git/platform/ti/dce/baselib] 
>  | making package.mak (because of package.bld) ...
>  | Selected Vayu for ES10
>  | config file: dce_ipu.cfg
>  |
>  | profile: release
>  |
>  |  -D_DM270  -D_DM290_IMX_MCFIX_   -DDRIVERCOMPONENTS=1 -
>  DISSCOMPONENTS=1 -DVIDEOCOMPONENTS=1 -DTESTCOMPONENTS=1
>  |
>  | HwType = 2
>  | HwVer = 1
>  | generating interfaces for package platform.ti.dce.baselib (because
>  package/package.xdc.inc is older than package.xdc) ...
>  | translating BASELIB
>  | .interfaces files complete: Thu Aug 16 02:48:34 UTC 2018.
>  |  .libraries
>  [/OE/arago-rocko-next/b

[meta-ti] [rocko/master][PATCH] gdbc6x: gcc7 related fixes got accepted upstream, remove

[Denys Dmytriyenko]

Signed-off-by: Denys Dmytriyenko 
---
 recipes-devtools/gdbc6x/gdbc6x.inc|  4 +-
 ...-fall-through-comment-to-work-with-g.patch | 35 
 ...llthrough-comment-to-recognize-by-gc.patch | 26 
 ...x-implicit-fallthrough-error-in-gcc7.patch | 26 
 ...x-implicit-fallthrough-error-in-gcc7.patch | 25 
 c-fix-format-overflow-error-in-gcc7.patch | 26 
 ...ents-for-implicit-fallthrough-error-.patch | 38 --
 ...cit-fallthrough-and-format-overflow-.patch | 40 ---
 ...format-truncation-and-implicit-fallt.patch | 35 
 recipes-devtools/gdbc6x/gdbc6x_git.bb |  8 
 10 files changed, 2 insertions(+), 261 deletions(-)
 delete mode 100644 
recipes-devtools/gdbc6x/gdbc6x/0001-coffgen.c-adjust-fall-through-comment-to-work-with-g.patch
 delete mode 100644 
recipes-devtools/gdbc6x/gdbc6x/0001-elf.c-correct-fallthrough-comment-to-recognize-by-gc.patch
 delete mode 100644 
recipes-devtools/gdbc6x/gdbc6x/0001-elf32-tic6x.c-fix-implicit-fallthrough-error-in-gcc7.patch
 delete mode 100644 
recipes-devtools/gdbc6x/gdbc6x/0001-elflink.c-fix-implicit-fallthrough-error-in-gcc7.patch
 delete mode 100644 
recipes-devtools/gdbc6x/gdbc6x/0001-ihex.c-fix-format-overflow-error-in-gcc7.patch
 delete mode 100644 
recipes-devtools/gdbc6x/gdbc6x/0001-reloc.c-add-comments-for-implicit-fallthrough-error-.patch
 delete mode 100644 
recipes-devtools/gdbc6x/gdbc6x/0001-srec.c-fix-implicit-fallthrough-and-format-overflow-.patch
 delete mode 100644 
recipes-devtools/gdbc6x/gdbc6x/0001-tic6x-dis.c-fix-format-truncation-and-implicit-fallt.patch

diff --git a/recipes-devtools/gdbc6x/gdbc6x.inc 
b/recipes-devtools/gdbc6x/gdbc6x.inc
index df08ee5c..9fc2f1dd 100644
--- a/recipes-devtools/gdbc6x/gdbc6x.inc
+++ b/recipes-devtools/gdbc6x/gdbc6x.inc
@@ -1,8 +1,8 @@
 # This corresponds to version 1.1.0
-SRCREV = "df0b8f6f4e9ba5b9c94ea8c17c6dfeae37c1c9d1"
+SRCREV = "d136542bbcad9489b8391550d8a8bee41076f080"
 
 PV = "1.1.0"
-INC_PR = "r3"
+INC_PR = "r4"
 
 SRC_URI = "git://git.ti.com/sdo-emu/gdbc6x.git;protocol=git;branch=${BRANCH}"
 
diff --git 
a/recipes-devtools/gdbc6x/gdbc6x/0001-coffgen.c-adjust-fall-through-comment-to-work-with-g.patch
 
b/recipes-devtools/gdbc6x/gdbc6x/0001-coffgen.c-adjust-fall-through-comment-to-work-with-g.patch
deleted file mode 100644
index eb72db9e..
--- 
a/recipes-devtools/gdbc6x/gdbc6x/0001-coffgen.c-adjust-fall-through-comment-to-work-with-g.patch
+++ /dev/null
@@ -1,35 +0,0 @@
-From 043a40fdc396118e099180b0ce0578ead24cf312 Mon Sep 17 00:00:00 2001
-From: Denys Dmytriyenko 
-Date: Fri, 10 Nov 2017 19:12:28 -0500
-Subject: [PATCH] coffgen.c: adjust fall through comment to work with gcc7
-
-Signed-off-by: Denys Dmytriyenko 

- gdbc6x/bfd/coffgen.c | 4 ++--
- 1 file changed, 2 insertions(+), 2 deletions(-)
-
-diff --git a/gdbc6x/bfd/coffgen.c b/gdbc6x/bfd/coffgen.c
-index 07a527d..665df95 100644
 a/gdbc6x/bfd/coffgen.c
-+++ b/gdbc6x/bfd/coffgen.c
-@@ -2116,7 +2116,7 @@ coff_print_symbol (bfd *abfd,
-auxp->u.auxent.x_scn.x_comdat);
- break;
-   }
--  /* Otherwise fall through.  */
-+  /* Else fall through.  */
-   case C_EXT:
-   case C_AIX_WEAKEXT:
- if (ISFCN (combined->u.syment.n_type))
-@@ -2136,7 +2136,7 @@ coff_print_symbol (bfd *abfd,
-  llnos, next);
- break;
-   }
--/* Otherwise fall through.  */
-+/* Else fall through.  */
-   default:
- fprintf (file, "AUX lnno %d size 0x%x tagndx %ld",
-  auxp->u.auxent.x_sym.x_misc.x_lnsz.x_lnno,
--- 
-2.7.4
-
diff --git 
a/recipes-devtools/gdbc6x/gdbc6x/0001-elf.c-correct-fallthrough-comment-to-recognize-by-gc.patch
 
b/recipes-devtools/gdbc6x/gdbc6x/0001-elf.c-correct-fallthrough-comment-to-recognize-by-gc.patch
deleted file mode 100644
index de5f1ca1..
--- 
a/recipes-devtools/gdbc6x/gdbc6x/0001-elf.c-correct-fallthrough-comment-to-recognize-by-gc.patch
+++ /dev/null
@@ -1,26 +0,0 @@
-From b77515953ba72728a10a46381d8b1dd73b89825d Mon Sep 17 00:00:00 2001
-From: Denys Dmytriyenko 
-Date: Fri, 10 Nov 2017 20:19:51 -0500
-Subject: [PATCH] elf.c: correct fallthrough comment to recognize by gcc7
-
-Signed-off-by: Denys Dmytriyenko 

- gdbc6x/bfd/elf.c | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/gdbc6x/bfd/elf.c b/gdbc6x/bfd/elf.c
-index ede51e9..80bac08 100644
 a/gdbc6x/bfd/elf.c
-+++ b/gdbc6x/bfd/elf.c
-@@ -1595,7 +1595,7 @@ bfd_section_from_shdr (bfd *abfd, unsigned int shindex)
- if (hdr->sh_link == (SHN_LORESERVE & 0x) /* SHN_BEFORE */
- || hdr->sh_link == ((SHN_LORESERVE + 1) &

Re: [meta-ti] [rocko][sumo][master][PATCH] u-boot-ti: add UBOOT_GIT_URI, UBOOT_GIT_PROTOCOL variable

[Denys Dmytriyenko]

Thanks, I can take this.


On Sat, Aug 18, 2018 at 01:02:23PM +1200, Ankur Tyagi wrote:
> This is to allow user to override git repository and git protocol.
> 
> Signed-off-by: Ankur Tyagi 
> ---
>  recipes-bsp/u-boot/u-boot-ti.inc | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/recipes-bsp/u-boot/u-boot-ti.inc 
> b/recipes-bsp/u-boot/u-boot-ti.inc
> index 61bf990..f22fcb4 100644
> --- a/recipes-bsp/u-boot/u-boot-ti.inc
> +++ b/recipes-bsp/u-boot/u-boot-ti.inc
> @@ -22,7 +22,9 @@ LICENSE = "GPLv2+"
>  LIC_FILES_CHKSUM = 
> "file://Licenses/README;md5=a2c678cfd4a4d97135585cad908541c6"
>  
>  BRANCH ?= "master"
> -SRC_URI = 
> "git://git.ti.com/ti-u-boot/ti-u-boot.git;protocol=git;branch=${BRANCH}"
> +UBOOT_GIT_URI = "git://git.ti.com/ti-u-boot/ti-u-boot.git"
> +UBOOT_GIT_PROTOCOL = "git"
> +SRC_URI = "${UBOOT_GIT_URI};protocol=${UBOOT_GIT_PROTOCOL};branch=${BRANCH}"
>  
>  PV_append = "+git${SRCPV}"
>  
> -- 
> 2.7.4
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [rocko][PATCH v2] ti-ipc: Update to new version 3.50

[Denys Dmytriyenko]

On Thu, Aug 16, 2018 at 02:03:08PM -0400, Nelson, Sam wrote:
> 
> 
> > -Original Message-
> > From: Anna, Suman
> > Sent: Thursday, August 16, 2018 12:40 PM
> > To: Dmytriyenko, Denys; Nelson, Sam
> > Cc: meta-ti@yoctoproject.org
> > Subject: Re: [meta-ti] [rocko][PATCH v2] ti-ipc: Update to new version 3.50
> > 
> > Hi Sam,
> > 
> > On 08/16/2018 10:47 AM, Denys Dmytriyenko wrote:
> > > +Suman,
> > >
> > > On Tue, Aug 14, 2018 at 02:59:28PM -0400, Sam Nelson wrote:
> > >> Add AM65XX platform support
> > >>
> > >> Signed-off-by: Sam Nelson 
> > >>
> > >> ---
> > >> Change from previous version of patch
> > >> - Update gcc toolchain to gcc-linaro-baremetal-aarch64
> > >> NOTE: This patch depends on gcc-linaro-baremetal-aarch64-native patch to
> > be checked in
> > >> ---
> > >> ---
> > >>  recipes-ti/ipc/ti-ipc-common.inc   |  3 ++-
> > >>  recipes-ti/ipc/ti-ipc-examples.inc |  2 +-
> > >>  recipes-ti/ipc/ti-ipc-rtos.inc | 16 
> > >>  recipes-ti/ipc/ti-ipc-rtos_git.bb  |  8 
> > >>  recipes-ti/ipc/ti-ipc.inc  |  6 +++---
> > >>  5 files changed, 26 insertions(+), 9 deletions(-)
> > >>
> > >> diff --git a/recipes-ti/ipc/ti-ipc-common.inc b/recipes-ti/ipc/ti-ipc-
> > common.inc
> > >> index 7f93842..6aea8e6 100644
> > >> --- a/recipes-ti/ipc/ti-ipc-common.inc
> > >> +++ b/recipes-ti/ipc/ti-ipc-common.inc
> > >> @@ -1,4 +1,4 @@
> > >> -PV = "3.47.02.00"
> > >> +PV = "3.50.01.00"
> > >>  INC_PR = "r0"
> > >>
> > >>  PACKAGE_ARCH = "${MACHINE_ARCH}"
> > >> @@ -13,6 +13,7 @@ PLATFORM_k2g = "66AK2G"
> > >>  PLATFORM_omapl138 = "OMAPL138"
> > >>  PLATFORM_c667x-evm = "C6678"
> > >>  PLATFORM_c665x-evm = "C6678"
> > >> +PLATFORM_am65xx-evm = "AM65XX"
> > >>
> > >>  ALT_PLATFORM_k2hk = "TCI6636"
> > >>  ALT_PLATFORM_am57xx-evm = "AM572X AM571X"
> > >> diff --git a/recipes-ti/ipc/ti-ipc-examples.inc b/recipes-ti/ipc/ti-ipc-
> > examples.inc
> > >> index cd2240c..022b13f 100644
> > >> --- a/recipes-ti/ipc/ti-ipc-examples.inc
> > >> +++ b/recipes-ti/ipc/ti-ipc-examples.inc
> > >> @@ -3,7 +3,7 @@ require ti-ipc-common.inc
> > >>  require ti-ipc-rtos.inc
> > >>
> > >>  LICENSE = "BSD"
> > >> -LIC_FILES_CHKSUM = "file://${S_ipc-
> > examples}/src/makefile;beginline=1;endline=30;md5=fb83580b16bce88e8ed
> > 568a6005c8f02"
> > >> +LIC_FILES_CHKSUM = "file://${S_ipc-
> > examples}/src/makefile;beginline=1;endline=30;md5=a52324bd5033bb49ea0
> > 7bade1244ac9a"
> > >>
> > >>  INSANE_SKIP_${PN} += "arch"
> > >>
> > >> diff --git a/recipes-ti/ipc/ti-ipc-rtos.inc 
> > >> b/recipes-ti/ipc/ti-ipc-rtos.inc
> > >> index 868743e..13b1914 100644
> > >> --- a/recipes-ti/ipc/ti-ipc-rtos.inc
> > >> +++ b/recipes-ti/ipc/ti-ipc-rtos.inc
> > >> @@ -24,11 +24,11 @@ protocol=${TI_IPC_METADATA_GIT_PROTOCOL};\
> > >>  branch=${TI_IPC_METADATA_GIT_BRANCH};\
> > >>  name=${TI_IPC_METADATA_NAME}"
> > >>
> > >> -# Corresponds to tag: 3.47.02.00
> > >> -SRCREV_ipc-metadata =
> > "e8aff83111b8a0d64d7a77413b6f66d3106084d8"
> > >> +# Corresponds to tag: 3.50.01.00
> > >> +SRCREV_ipc-metadata =
> > "19a8e70cf6ca4fe0984987e25d937c61a62c7658"
> > >>
> > >> -# Corresponds to tag: 3.47.02.00
> > >> -SRCREV_ipc-examples =
> > "351e9a6d94c68f7ff64b2c002ee6750242ece6d9"
> > >> +# Corresponds to tag: 3.50.01.00
> > >> +SRCREV_ipc-examples =
> > "1975687076426b587be8d2530df56c24425ca53a"
> > >>
> > >>  S_ipc-examples = "${WORKDIR}/git/ipc-examples"
> > >>  S_ipc-metadata = "${WORKDIR}/git/ipc-metadata"
> > >> @@ -50,6 +50,9 @@ DEPENDS_append_omapl138 = " ti-cgt6x-native \
> > >>  DEPENDS_append_c66x = " ti-cgt6x-native \
> > >>  "
> > >>
> > >> +DEPENDS_append_am65xx-evm = " ti-cgt-arm-native \
> > >> +  gcc-linaro-baremetal-

Re: [meta-ti] [rocko][PATCH v2] ti-ipc: Update to new version 3.50

[Denys Dmytriyenko]

+Suman,


On Tue, Aug 14, 2018 at 02:59:28PM -0400, Sam Nelson wrote:
> Add AM65XX platform support
> 
> Signed-off-by: Sam Nelson 
> 
> ---
> Change from previous version of patch
> - Update gcc toolchain to gcc-linaro-baremetal-aarch64
> NOTE: This patch depends on gcc-linaro-baremetal-aarch64-native patch to be 
> checked in
> ---
> ---
>  recipes-ti/ipc/ti-ipc-common.inc   |  3 ++-
>  recipes-ti/ipc/ti-ipc-examples.inc |  2 +-
>  recipes-ti/ipc/ti-ipc-rtos.inc | 16 
>  recipes-ti/ipc/ti-ipc-rtos_git.bb  |  8 
>  recipes-ti/ipc/ti-ipc.inc  |  6 +++---
>  5 files changed, 26 insertions(+), 9 deletions(-)
> 
> diff --git a/recipes-ti/ipc/ti-ipc-common.inc 
> b/recipes-ti/ipc/ti-ipc-common.inc
> index 7f93842..6aea8e6 100644
> --- a/recipes-ti/ipc/ti-ipc-common.inc
> +++ b/recipes-ti/ipc/ti-ipc-common.inc
> @@ -1,4 +1,4 @@
> -PV = "3.47.02.00"
> +PV = "3.50.01.00"
>  INC_PR = "r0"
>  
>  PACKAGE_ARCH = "${MACHINE_ARCH}"
> @@ -13,6 +13,7 @@ PLATFORM_k2g = "66AK2G"
>  PLATFORM_omapl138 = "OMAPL138"
>  PLATFORM_c667x-evm = "C6678"
>  PLATFORM_c665x-evm = "C6678"
> +PLATFORM_am65xx-evm = "AM65XX"
>  
>  ALT_PLATFORM_k2hk = "TCI6636"
>  ALT_PLATFORM_am57xx-evm = "AM572X AM571X"
> diff --git a/recipes-ti/ipc/ti-ipc-examples.inc 
> b/recipes-ti/ipc/ti-ipc-examples.inc
> index cd2240c..022b13f 100644
> --- a/recipes-ti/ipc/ti-ipc-examples.inc
> +++ b/recipes-ti/ipc/ti-ipc-examples.inc
> @@ -3,7 +3,7 @@ require ti-ipc-common.inc
>  require ti-ipc-rtos.inc
>  
>  LICENSE = "BSD"
> -LIC_FILES_CHKSUM = 
> "file://${S_ipc-examples}/src/makefile;beginline=1;endline=30;md5=fb83580b16bce88e8ed568a6005c8f02"
> +LIC_FILES_CHKSUM = 
> "file://${S_ipc-examples}/src/makefile;beginline=1;endline=30;md5=a52324bd5033bb49ea07bade1244ac9a"
>  
>  INSANE_SKIP_${PN} += "arch"
>  
> diff --git a/recipes-ti/ipc/ti-ipc-rtos.inc b/recipes-ti/ipc/ti-ipc-rtos.inc
> index 868743e..13b1914 100644
> --- a/recipes-ti/ipc/ti-ipc-rtos.inc
> +++ b/recipes-ti/ipc/ti-ipc-rtos.inc
> @@ -24,11 +24,11 @@ protocol=${TI_IPC_METADATA_GIT_PROTOCOL};\
>  branch=${TI_IPC_METADATA_GIT_BRANCH};\
>  name=${TI_IPC_METADATA_NAME}"
>  
> -# Corresponds to tag: 3.47.02.00
> -SRCREV_ipc-metadata = "e8aff83111b8a0d64d7a77413b6f66d3106084d8"
> +# Corresponds to tag: 3.50.01.00
> +SRCREV_ipc-metadata = "19a8e70cf6ca4fe0984987e25d937c61a62c7658"
>  
> -# Corresponds to tag: 3.47.02.00
> -SRCREV_ipc-examples = "351e9a6d94c68f7ff64b2c002ee6750242ece6d9"
> +# Corresponds to tag: 3.50.01.00
> +SRCREV_ipc-examples = "1975687076426b587be8d2530df56c24425ca53a"
>  
>  S_ipc-examples = "${WORKDIR}/git/ipc-examples"
>  S_ipc-metadata = "${WORKDIR}/git/ipc-metadata"
> @@ -50,6 +50,9 @@ DEPENDS_append_omapl138 = " ti-cgt6x-native \
>  DEPENDS_append_c66x = " ti-cgt6x-native \
>  "
>  
> +DEPENDS_append_am65xx-evm = " ti-cgt-arm-native \
> +  gcc-linaro-baremetal-aarch64-native"
> +
>  IPC_TARGETS = ""
>  
>  IPC_TARGETS_omap-a15 = "\
> @@ -73,6 +76,11 @@ IPC_TARGETS_c66x = " \
>  
> ti.targets.elf.C66_big_endian="${STAGING_DIR_NATIVE}/usr/share/ti/cgt-c6x" \
>  "
>  
> +IPC_TARGETS_am65xx-evm = "\
> +gnu.targets.arm.A53F="${GCC_LINARO_BAREMETAL_AARCH64_TOOLCHAIN}" \
> +ti.targets.arm.elf.R5F="${M4_TOOLCHAIN_INSTALL_DIR}" \
> +"
> +
>  EXTRA_OEMAKE = "\
>  PLATFORM=${PLATFORM} \
>  XDC_INSTALL_DIR="${XDC_INSTALL_DIR}" \
> diff --git a/recipes-ti/ipc/ti-ipc-rtos_git.bb 
> b/recipes-ti/ipc/ti-ipc-rtos_git.bb
> index b292d67..b70935a 100644
> --- a/recipes-ti/ipc/ti-ipc-rtos_git.bb
> +++ b/recipes-ti/ipc/ti-ipc-rtos_git.bb
> @@ -122,3 +122,11 @@ pkg_postinst_${PN}-fw_omapl138 () {
>  pkg_postrm_${PN}-fw_omapl138 () {
>update-alternatives --remove rproc-dsp-fw 
> ipc/ti_platforms_evmOMAPL138_DSP/messageq_single.xe674
>  }
> +
> +pkg_postinst_${PN}-fw_am65xx-evm () {
> +  update-alternatives --install /lib/firmware/rproc-r5f-fw rproc-r5f-fw 
> ipc/ti_platforms_cortexR_AM65X/messageq_single.xer5f ${ALTERNATIVE_PRIORITY}
> +}
> +
> +pkg_postrm_${PN}-fw_am65xx-evm () {
> +  update-alternatives --remove rproc-r5f-fw 
> ipc/ti_platforms_cortexR_AM65X/messageq_single.xe674
> +}
> diff --git a/recipes-ti/ipc/ti-ipc.inc b/recipes-ti/ipc/ti-ipc.inc
> index e8038a5..07321cb 100644
> --- a/recipes-ti/ipc/ti-ipc.inc
> +++ b/recipes-ti/ipc/ti-ipc.inc
> @@ -6,10 +6,10 @@ LIC_FILES_CHKSUM = 
> "file://${S}/ipc-linux.mak;beginline=1;endline=30;md5=7b327f9
>  
>  TI_IPC_GIT_URI = "git://git.ti.com/ipc/ipcdev.git"
>  TI_IPC_GIT_PROTOCOL = "git"
> -TI_IPC_GIT_BRANCH = "3.47"
> +TI_IPC_GIT_BRANCH = "3.50"
>  
> -#Corresponds to 3.47.02.00
> -TI_IPC_SRCREV = "24c36385d096613af123d1e1696fb2fee652ef36"
> +#Corresponds to 3.50.01.00
> +TI_IPC_SRCREV = "f0d0edaf3ce7ed8d81d8969eaaa98cec8b662424"
>  
>  BRANCH = "${TI_IPC_GIT_BRANCH}"
>  SRC_URI = 
> "${TI_IPC_GIT_URI};protocol=${TI_IPC_GIT_PROTOCOL};branch=${BRANCH};name=ipcdev"
> -- 
> 1.9.1
> 
> -- 
> ___
> meta-ti mailing list
> 

Re: [meta-ti] [rocko][PATCH V3 2/2] recipes-ti: bios: add TI SYSBIOS 6.73.00.12

[Denys Dmytriyenko]

Ok, this breaks ipumm-fw build:

| NOTE: make -j 56 
XDCDIST_TREE=/OE/arago-rocko-next/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/ipumm-fw/3.00.15.00-r1/recipe-sysroot-native/usr/share/ti/ti-xdctools-tree
| export XDCARGS="profile=release trace_level=0 hw_type=VAYU hw_version=ES10 
BIOS_type=SMP prof_type=DISABLE"; \
| 
/OE/arago-rocko-next/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/ipumm-fw/3.00.15.00-r1/recipe-sysroot-native/usr/share/ti/ti-xdctools-tree/xdc
 --jobs=1 -PD 
/OE/arago-rocko-next/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/ipumm-fw/3.00.15.00-r1/git/platform/ti/dce/baselib/.;
 \
| 
/OE/arago-rocko-next/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/ipumm-fw/3.00.15.00-r1/recipe-sysroot-native/usr/share/ti/ti-xdctools-tree/xdc
 --jobs=1 -PD 
/OE/arago-rocko-next/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/ipumm-fw/3.00.15.00-r1/git/platform/ti/dce/baseimage/.
| making all: Thu Aug 16 02:48:21 UTC 2018 ...
|  .interfaces 
[/OE/arago-rocko-next/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/ipumm-fw/3.00.15.00-r1/git/src/ti/framework/dce]
 
| making package.mak (because of package.bld) ...
| Selected Vayu for ES10
| generating interfaces for package ti.framework.dce (because 
package/package.xdc.inc is older than package.xdc) ...
|  .interfaces 
[/OE/arago-rocko-next/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/ipumm-fw/3.00.15.00-r1/git/src/ti/utils]
 
| making package.mak (because of package.bld) ...
| Selected Vayu for ES10
| generating interfaces for package src.ti.utils (because 
package/package.xdc.inc is older than package.xdc) ...
|  .interfaces 
[/OE/arago-rocko-next/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/ipumm-fw/3.00.15.00-r1/git/platform/ti/dce/baselib]
 
| making package.mak (because of package.bld) ...
| Selected Vayu for ES10
| config file: dce_ipu.cfg
| 
| profile: release
| 
|  -D_DM270  -D_DM290_IMX_MCFIX_   -DDRIVERCOMPONENTS=1 -DISSCOMPONENTS=1 
-DVIDEOCOMPONENTS=1 -DTESTCOMPONENTS=1
| 
| HwType = 2
| HwVer = 1
| generating interfaces for package platform.ti.dce.baselib (because 
package/package.xdc.inc is older than package.xdc) ...
| translating BASELIB
| .interfaces files complete: Thu Aug 16 02:48:34 UTC 2018.
|  .libraries 
[/OE/arago-rocko-next/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/ipumm-fw/3.00.15.00-r1/git/src/ti/framework/dce]
 
| clem4 package/package_ti.framework.dce.c ...
| clem4 dce.c ...
| "dce.c", line 53: fatal error #1965: cannot open source file 
"ti/sysbios/posix/pthread.h"
| 1 catastrophic error detected in the compilation of "dce.c".
| Compilation terminated.
| 
| >> Compilation failure
| lib/ipu/release/ti.framework.dce.aem4.mak:44: recipe for target 
'package/lib/lib/ipu/release/ti.framework.dce/dce.oem4' failed
| make[1]: *** [package/lib/lib/ipu/release/ti.framework.dce/dce.oem4] Error 1
| gmake: *** 
[/OE/arago-rocko-next/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/ipumm-fw/3.00.15.00-r1/git/src/ti/framework/dce,.libraries]
 Error 2
| making all: Thu Aug 16 02:48:35 UTC 2018 ...
|  .interfaces 
[/OE/arago-rocko-next/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/ipumm-fw/3.00.15.00-r1/git/platform/ti/dce/baseimage]
 
| making package.mak (because of package.bld) ...
| Selected Vayu for ES10
| config file: dce_ipu.cfg
| 
| profile: release
| 
|  -D_DM270  -D_DM290_IMX_MCFIX_   -DDRIVERCOMPONENTS=1 -DISSCOMPONENTS=1 
-DVIDEOCOMPONENTS=1 -DTESTCOMPONENTS=1
| 
| HwType = 2
| HwVer = 1
| generating interfaces for package platform.ti.dce.baseimage (because 
package/package.xdc.inc is older than package.xdc) ...
| .interfaces files complete: Thu Aug 16 02:48:39 UTC 2018.
|  .libraries 
[/OE/arago-rocko-next/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/ipumm-fw/3.00.15.00-r1/git/platform/ti/dce/baseimage]
 
| .libraries files complete: Thu Aug 16 02:48:39 UTC 2018.
|  .dlls 
[/OE/arago-rocko-next/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/ipumm-fw/3.00.15.00-r1/git/platform/ti/dce/baseimage]
 
| configuring out/ipu/release/ipu.xem4 from 
package/cfg/out/ipu/release/ipu_pem4.cfg ...
| HwType = 2
| HwVer = 1
| IPUMM commit 035ba25 version MMIP 3_00_15_00  IPC 3_47_01_00
| Benelli Vayu: Setting PRCM Addresses ES1.0
| loading: ivahd_mpeg4dec
| loading: ivahd_h264dec
| loading: ivahd_jpegvdec
| loading: ivahd_jpegvenc
| loading: ivahd_vc1vdec
| loading: ivahd_mpeg2vdec
| loading: ivahd_h264enc
| loading: ivahd_mpeg4enc
| SMP Enabled BIOS
| warning: ti.sysbios.posix.Settings: 
"/OE/arago-rocko-next/build/arago-tmp-external-linaro-toolchain/work/armv7

Re: [meta-ti] [rocko][PATCH v2] ti-ipc: Update to new version 3.50

[Denys Dmytriyenko]

On Tue, Aug 14, 2018 at 02:59:28PM -0400, Sam Nelson wrote:
> Add AM65XX platform support
> 
> Signed-off-by: Sam Nelson 
> 
> ---
> Change from previous version of patch
> - Update gcc toolchain to gcc-linaro-baremetal-aarch64
> NOTE: This patch depends on gcc-linaro-baremetal-aarch64-native patch to be 
> checked in
> ---
> ---
>  recipes-ti/ipc/ti-ipc-common.inc   |  3 ++-
>  recipes-ti/ipc/ti-ipc-examples.inc |  2 +-
>  recipes-ti/ipc/ti-ipc-rtos.inc | 16 
>  recipes-ti/ipc/ti-ipc-rtos_git.bb  |  8 
>  recipes-ti/ipc/ti-ipc.inc  |  6 +++---
>  5 files changed, 26 insertions(+), 9 deletions(-)
> 
> diff --git a/recipes-ti/ipc/ti-ipc-common.inc 
> b/recipes-ti/ipc/ti-ipc-common.inc
> index 7f93842..6aea8e6 100644
> --- a/recipes-ti/ipc/ti-ipc-common.inc
> +++ b/recipes-ti/ipc/ti-ipc-common.inc
> @@ -1,4 +1,4 @@
> -PV = "3.47.02.00"
> +PV = "3.50.01.00"
>  INC_PR = "r0"
>  
>  PACKAGE_ARCH = "${MACHINE_ARCH}"
> @@ -13,6 +13,7 @@ PLATFORM_k2g = "66AK2G"
>  PLATFORM_omapl138 = "OMAPL138"
>  PLATFORM_c667x-evm = "C6678"
>  PLATFORM_c665x-evm = "C6678"
> +PLATFORM_am65xx-evm = "AM65XX"
>  
>  ALT_PLATFORM_k2hk = "TCI6636"
>  ALT_PLATFORM_am57xx-evm = "AM572X AM571X"
> diff --git a/recipes-ti/ipc/ti-ipc-examples.inc 
> b/recipes-ti/ipc/ti-ipc-examples.inc
> index cd2240c..022b13f 100644
> --- a/recipes-ti/ipc/ti-ipc-examples.inc
> +++ b/recipes-ti/ipc/ti-ipc-examples.inc
> @@ -3,7 +3,7 @@ require ti-ipc-common.inc
>  require ti-ipc-rtos.inc
>  
>  LICENSE = "BSD"
> -LIC_FILES_CHKSUM = 
> "file://${S_ipc-examples}/src/makefile;beginline=1;endline=30;md5=fb83580b16bce88e8ed568a6005c8f02"
> +LIC_FILES_CHKSUM = 
> "file://${S_ipc-examples}/src/makefile;beginline=1;endline=30;md5=a52324bd5033bb49ea07bade1244ac9a"

What is the change in the license?


>  INSANE_SKIP_${PN} += "arch"
>  
> diff --git a/recipes-ti/ipc/ti-ipc-rtos.inc b/recipes-ti/ipc/ti-ipc-rtos.inc
> index 868743e..13b1914 100644
> --- a/recipes-ti/ipc/ti-ipc-rtos.inc
> +++ b/recipes-ti/ipc/ti-ipc-rtos.inc
> @@ -24,11 +24,11 @@ protocol=${TI_IPC_METADATA_GIT_PROTOCOL};\
>  branch=${TI_IPC_METADATA_GIT_BRANCH};\
>  name=${TI_IPC_METADATA_NAME}"
>  
> -# Corresponds to tag: 3.47.02.00
> -SRCREV_ipc-metadata = "e8aff83111b8a0d64d7a77413b6f66d3106084d8"
> +# Corresponds to tag: 3.50.01.00
> +SRCREV_ipc-metadata = "19a8e70cf6ca4fe0984987e25d937c61a62c7658"
>  
> -# Corresponds to tag: 3.47.02.00
> -SRCREV_ipc-examples = "351e9a6d94c68f7ff64b2c002ee6750242ece6d9"
> +# Corresponds to tag: 3.50.01.00
> +SRCREV_ipc-examples = "1975687076426b587be8d2530df56c24425ca53a"
>  
>  S_ipc-examples = "${WORKDIR}/git/ipc-examples"
>  S_ipc-metadata = "${WORKDIR}/git/ipc-metadata"
> @@ -50,6 +50,9 @@ DEPENDS_append_omapl138 = " ti-cgt6x-native \
>  DEPENDS_append_c66x = " ti-cgt6x-native \
>  "
>  
> +DEPENDS_append_am65xx-evm = " ti-cgt-arm-native \
> +  gcc-linaro-baremetal-aarch64-native"
> +
>  IPC_TARGETS = ""
>  
>  IPC_TARGETS_omap-a15 = "\
> @@ -73,6 +76,11 @@ IPC_TARGETS_c66x = " \
>  
> ti.targets.elf.C66_big_endian="${STAGING_DIR_NATIVE}/usr/share/ti/cgt-c6x" \
>  "
>  
> +IPC_TARGETS_am65xx-evm = "\
> +gnu.targets.arm.A53F="${GCC_LINARO_BAREMETAL_AARCH64_TOOLCHAIN}" \
> +ti.targets.arm.elf.R5F="${M4_TOOLCHAIN_INSTALL_DIR}" \
> +"
> +
>  EXTRA_OEMAKE = "\
>  PLATFORM=${PLATFORM} \
>  XDC_INSTALL_DIR="${XDC_INSTALL_DIR}" \
> diff --git a/recipes-ti/ipc/ti-ipc-rtos_git.bb 
> b/recipes-ti/ipc/ti-ipc-rtos_git.bb
> index b292d67..b70935a 100644
> --- a/recipes-ti/ipc/ti-ipc-rtos_git.bb
> +++ b/recipes-ti/ipc/ti-ipc-rtos_git.bb
> @@ -122,3 +122,11 @@ pkg_postinst_${PN}-fw_omapl138 () {
>  pkg_postrm_${PN}-fw_omapl138 () {
>update-alternatives --remove rproc-dsp-fw 
> ipc/ti_platforms_evmOMAPL138_DSP/messageq_single.xe674
>  }
> +
> +pkg_postinst_${PN}-fw_am65xx-evm () {
> +  update-alternatives --install /lib/firmware/rproc-r5f-fw rproc-r5f-fw 
> ipc/ti_platforms_cortexR_AM65X/messageq_single.xer5f ${ALTERNATIVE_PRIORITY}
> +}
> +
> +pkg_postrm_${PN}-fw_am65xx-evm () {
> +  update-alternatives --remove rproc-r5f-fw 
> ipc/ti_platforms_cortexR_AM65X/messageq_single.xe674
> +}
> diff --git a/recipes-ti/ipc/ti-ipc.inc b/recipes-ti/ipc/ti-ipc.inc
> index e8038a5..07321cb 100644
> --- a/recipes-ti/ipc/ti-ipc.inc
> +++ b/recipes-ti/ipc/ti-ipc.inc
> @@ -6,10 +6,10 @@ LIC_FILES_CHKSUM = 
> "file://${S}/ipc-linux.mak;beginline=1;endline=30;md5=7b327f9
>  
>  TI_IPC_GIT_URI = "git://git.ti.com/ipc/ipcdev.git"
>  TI_IPC_GIT_PROTOCOL = "git"
> -TI_IPC_GIT_BRANCH = "3.47"
> +TI_IPC_GIT_BRANCH = "3.50"
>  
> -#Corresponds to 3.47.02.00
> -TI_IPC_SRCREV = "24c36385d096613af123d1e1696fb2fee652ef36"
> +#Corresponds to 3.50.01.00
> +TI_IPC_SRCREV = "f0d0edaf3ce7ed8d81d8969eaaa98cec8b662424"
>  
>  BRANCH = "${TI_IPC_GIT_BRANCH}"
>  SRC_URI = 
> "${TI_IPC_GIT_URI};protocol=${TI_IPC_GIT_PROTOCOL};branch=${BRANCH};name=ipcdev"
> -- 
> 1.9.1
> 
> -- 
> ___
>

Re: [meta-ti] [PATCH 1/2] linux-ti-staging: update ti2018.03-rc3 tag

[Denys Dmytriyenko]

No RT bump?


On Wed, Aug 15, 2018 at 01:21:40PM -0500, Dan Murphy wrote:
> Signed-off-by: Dan Murphy 
> ---
>  recipes-kernel/linux/linux-ti-staging_4.14.bb | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/recipes-kernel/linux/linux-ti-staging_4.14.bb 
> b/recipes-kernel/linux/linux-ti-staging_4.14.bb
> index 6bb5c33b..9e092404 100644
> --- a/recipes-kernel/linux/linux-ti-staging_4.14.bb
> +++ b/recipes-kernel/linux/linux-ti-staging_4.14.bb
> @@ -55,8 +55,8 @@ S = "${WORKDIR}/git"
>  
>  BRANCH = "ti-lsk-linux-4.14.y"
>  
> -SRCREV = "7364914505da7bc264d2f8a38c4ff4f865fcba03"
> -PV = "4.14.61+git${SRCPV}"
> +SRCREV = "3dcf448dbe396161f4633d0e38b9894fe5214786"
> +PV = "4.14.62+git${SRCPV}"
>  
>  # Append to the MACHINE_KERNEL_PR so that a new SRCREV will cause a rebuild
>  MACHINE_KERNEL_PR_append = "b"
> -- 
> 2.17.0.582.gccdcbd54c
> 
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [rocko][PATCH V4] recipes-ti: devtools: add GCC Linaro baremetal toolchain 2017.11 v7.2.1

[Denys Dmytriyenko]

Thanks, I'll take it. Please fix the host contamination warnings from "cp" in 
the followup patch.


On Tue, Aug 14, 2018 at 10:32:19AM -0400, hzh...@ti.com wrote:
> From: Hao Zhang 
> 
> Signed-off-by: Hao Zhang 
> 
> ---
> Changes from previous version of patch
> Remove white space
> ---
> ---
>  .../gcc-linaro-baremetal-aarch64-native.bb | 23 
> ++
>  recipes-ti/devtools/gcc-linaro-baremetal-native.bb | 23 
> ++
>  recipes-ti/devtools/gcc-linaro.inc | 10 ++
>  recipes-ti/includes/ti-paths.inc   |  5 +
>  4 files changed, 61 insertions(+)
>  create mode 100644 recipes-ti/devtools/gcc-linaro-baremetal-aarch64-native.bb
>  create mode 100644 recipes-ti/devtools/gcc-linaro-baremetal-native.bb
>  create mode 100644 recipes-ti/devtools/gcc-linaro.inc
> 
> diff --git a/recipes-ti/devtools/gcc-linaro-baremetal-aarch64-native.bb 
> b/recipes-ti/devtools/gcc-linaro-baremetal-aarch64-native.bb
> new file mode 100644
> index 000..97344f9
> --- /dev/null
> +++ b/recipes-ti/devtools/gcc-linaro-baremetal-aarch64-native.bb
> @@ -0,0 +1,23 @@
> +include recipes-ti/devtools/gcc-linaro.inc
> +
> +PACKAGE_DIR = "gcc-linaro-${PV}-${GCC_ARM_YEAR}-x86_64_aarch64-elf"
> +S = "${WORKDIR}/${PACKAGE_DIR}"
> +
> +LIC_CHKSUM = "bc7fad4bba98e7a4cd5ab3042506493c"
> +
> +inherit native
> +require recipes-ti/includes/ti-paths.inc
> +
> +SRC_URI = 
> "https://releases.linaro.org/components/toolchain/binaries/7.2-${GCC_ARM_YEAR}/aarch64-elf/gcc-linaro-${PV}-${GCC_ARM_YEAR}-x86_64_aarch64-elf.tar.xz;name=gcc-linaro-aarch64";
> +
> +SRC_URI[gcc-linaro-aarch64.md5sum] = "4972f8943820bdd2f577f498de78964b"
> +SRC_URI[gcc-linaro-aarch64.sha256sum] = 
> "30fb7d876bcb982c502057c593d9c1f11b35d5158a26d986718e2b998388c4c8"
> +
> +do_install() {
> +install -d ${D}${GCC_LINARO_BAREMETAL_AARCH64_TOOLCHAIN_RECIPE}
> +cp -r ${S}/. ${D}${GCC_LINARO_BAREMETAL_AARCH64_TOOLCHAIN_RECIPE}
> +}
> +
> +FILES_${PN} = "${GCC_LINARO_BAREMETAL_AARCH64_TOOLCHAIN_RECIPE}/*"
> +
> +INSANE_SKIP_${PN} = "already-stripped"
> diff --git a/recipes-ti/devtools/gcc-linaro-baremetal-native.bb 
> b/recipes-ti/devtools/gcc-linaro-baremetal-native.bb
> new file mode 100644
> index 000..0268ae3
> --- /dev/null
> +++ b/recipes-ti/devtools/gcc-linaro-baremetal-native.bb
> @@ -0,0 +1,23 @@
> +include recipes-ti/devtools/gcc-linaro.inc
> +
> +PACKAGE_DIR = "gcc-linaro-${PV}-${GCC_ARM_YEAR}-x86_64_arm-eabi"
> +S = "${WORKDIR}/${PACKAGE_DIR}"
> +
> +LIC_CHKSUM = "bc7fad4bba98e7a4cd5ab3042506493c"
> +
> +inherit native
> +require recipes-ti/includes/ti-paths.inc
> +
> +SRC_URI = 
> "https://releases.linaro.org/components/toolchain/binaries/7.2-${GCC_ARM_YEAR}/arm-eabi/gcc-linaro-${PV}-${GCC_ARM_YEAR}-x86_64_arm-eabi.tar.xz;name=gcc-linaro";
> +
> +SRC_URI[gcc-linaro.md5sum] = "9a4a39cfc78c84375b1160aa93587aed"
> +SRC_URI[gcc-linaro.sha256sum] = 
> "45fc4f90af2e2e9c3197a275f6005ef5639f7a1889fa3eb24c3125ccd70fcd3d"
> +
> +do_install() {
> +install -d ${D}${GCC_LINARO_BAREMETAL_TOOLCHAIN_RECIPE}
> +cp -r ${S}/. ${D}${GCC_LINARO_BAREMETAL_TOOLCHAIN_RECIPE}
> +}
> +
> +FILES_${PN} = "${GCC_LINARO_BAREMETAL_TOOLCHAIN_RECIPE}/*"
> +
> +INSANE_SKIP_${PN} = "already-stripped"
> diff --git a/recipes-ti/devtools/gcc-linaro.inc 
> b/recipes-ti/devtools/gcc-linaro.inc
> new file mode 100644
> index 000..19f5a2c
> --- /dev/null
> +++ b/recipes-ti/devtools/gcc-linaro.inc
> @@ -0,0 +1,10 @@
> +DESCRIPTION = "Linaro GCC for ARM"
> +HOMEPAGE = "https://launchpad.net/gcc-arm-embedded";
> +SECTION = "devel"
> +LICENSE = "GPL-3.0-with-GCC-exception & GPLv3"
> +LIC_FILES_CHKSUM = 
> "file://share/doc/gcc/GNU-Free-Documentation-License.html;md5=${LIC_CHKSUM}"
> +
> +PV = "7.2.1"
> +PR = "r0"
> +
> +GCC_ARM_YEAR = "2017.11"
> diff --git a/recipes-ti/includes/ti-paths.inc 
> b/recipes-ti/includes/ti-paths.inc
> index 4f99d5e..a401264 100644
> --- a/recipes-ti/includes/ti-paths.inc
> +++ b/recipes-ti/includes/ti-paths.inc
> @@ -56,6 +56,8 @@ export CG_XML_INSTALL_DIR_RECIPE = 
> "${installdir}/ti-cg-xml-tree"
>  export OMP_INSTALL_DIR_RECIPE= "${installdir}/ti-omp-tree"
>  export MPM_INSTALL_DIR_RECIPE= "${installdir}/ti-mpm-tree"
>  export TI_CGT6X_7_INSTALL_DIR_RECIPE   = "${installdir}/cgt6x-7"
> +export GCC_LINARO_BAREMETAL_TOOLCHAIN_RECIPE  = 
> "${installdir}/gcc-linaro-baremetal"
> +export GCC_LINARO_BAREMETAL_AARCH64_TOOLCHAIN_RECIPE  = 
> "${installdir}/gcc-linaro-baremetal-aarch64"
>  
>  # This is where the tools will end up in sysroot
>  export BIOS_INSTALL_DIR   = 
> "${STAGING_DIR_TARGET}${BIOS_INSTALL_DIR_RECIPE}"
> @@ -103,6 +105,9 @@ export CG_XML_INSTALL_DIR = 
> "${STAGING_DIR_NATIVE}${CG_XML_INSTALL_DIR_RECIP
>  export OMP_INSTALL_DIR= 
> "${STAGING_DIR_TARGET}${OMP_INSTALL_DIR_RECIPE}"
>  export MPM_INSTALL_DIR= 
> "${STAGING_DIR_TARGET}${MPM_INSTALL_DIR_RECIPE}"
>  export TI_CGT6X_7_INSTALL_DIR   = 
> "${STAGING_DIR_NATIV

Re: [meta-ti] [rocko][PATCH V3] recipes-ti: devtools: add GCC Linaro baremetal toolchain 2017.11 v7.2.1

[Denys Dmytriyenko]

On Tue, Aug 14, 2018 at 09:47:22AM -0400, hzh...@ti.com wrote:
> From: Hao Zhang 
> 
> Signed-off-by: Hao Zhang 
> 
> ---
> Changes from previous version of patch
> Remote white spaces end of file
> ---
> ---
>  .../gcc-linaro-baremetal-aarch64-native.bb | 23 
> ++
>  recipes-ti/devtools/gcc-linaro-baremetal-native.bb | 23 
> ++
>  recipes-ti/devtools/gcc-linaro.inc | 10 ++
>  recipes-ti/includes/ti-paths.inc   |  5 +
>  4 files changed, 61 insertions(+)
>  create mode 100644 recipes-ti/devtools/gcc-linaro-baremetal-aarch64-native.bb
>  create mode 100644 recipes-ti/devtools/gcc-linaro-baremetal-native.bb
>  create mode 100644 recipes-ti/devtools/gcc-linaro.inc
> 
> diff --git a/recipes-ti/devtools/gcc-linaro-baremetal-aarch64-native.bb 
> b/recipes-ti/devtools/gcc-linaro-baremetal-aarch64-native.bb
> new file mode 100644
> index 000..97344f9
> --- /dev/null
> +++ b/recipes-ti/devtools/gcc-linaro-baremetal-aarch64-native.bb
> @@ -0,0 +1,23 @@
> +include recipes-ti/devtools/gcc-linaro.inc
> +
> +PACKAGE_DIR = "gcc-linaro-${PV}-${GCC_ARM_YEAR}-x86_64_aarch64-elf"
> +S = "${WORKDIR}/${PACKAGE_DIR}"
> +
> +LIC_CHKSUM = "bc7fad4bba98e7a4cd5ab3042506493c"
> +
> +inherit native
> +require recipes-ti/includes/ti-paths.inc
> +
> +SRC_URI = 
> "https://releases.linaro.org/components/toolchain/binaries/7.2-${GCC_ARM_YEAR}/aarch64-elf/gcc-linaro-${PV}-${GCC_ARM_YEAR}-x86_64_aarch64-elf.tar.xz;name=gcc-linaro-aarch64";
> +
> +SRC_URI[gcc-linaro-aarch64.md5sum] = "4972f8943820bdd2f577f498de78964b"
> +SRC_URI[gcc-linaro-aarch64.sha256sum] = 
> "30fb7d876bcb982c502057c593d9c1f11b35d5158a26d986718e2b998388c4c8"
> +
> +do_install() {
> +install -d ${D}${GCC_LINARO_BAREMETAL_AARCH64_TOOLCHAIN_RECIPE}
> +cp -r ${S}/. ${D}${GCC_LINARO_BAREMETAL_AARCH64_TOOLCHAIN_RECIPE}
> +}
> +
> +FILES_${PN} = "${GCC_LINARO_BAREMETAL_AARCH64_TOOLCHAIN_RECIPE}/*"
> +
> +INSANE_SKIP_${PN} = "already-stripped"
> diff --git a/recipes-ti/devtools/gcc-linaro-baremetal-native.bb 
> b/recipes-ti/devtools/gcc-linaro-baremetal-native.bb
> new file mode 100644
> index 000..0268ae3
> --- /dev/null
> +++ b/recipes-ti/devtools/gcc-linaro-baremetal-native.bb
> @@ -0,0 +1,23 @@
> +include recipes-ti/devtools/gcc-linaro.inc
> +
> +PACKAGE_DIR = "gcc-linaro-${PV}-${GCC_ARM_YEAR}-x86_64_arm-eabi"
> +S = "${WORKDIR}/${PACKAGE_DIR}"
> +
> +LIC_CHKSUM = "bc7fad4bba98e7a4cd5ab3042506493c"
> +
> +inherit native
> +require recipes-ti/includes/ti-paths.inc
> +
> +SRC_URI = 
> "https://releases.linaro.org/components/toolchain/binaries/7.2-${GCC_ARM_YEAR}/arm-eabi/gcc-linaro-${PV}-${GCC_ARM_YEAR}-x86_64_arm-eabi.tar.xz;name=gcc-linaro";
> +
> +SRC_URI[gcc-linaro.md5sum] = "9a4a39cfc78c84375b1160aa93587aed"
> +SRC_URI[gcc-linaro.sha256sum] = 
> "45fc4f90af2e2e9c3197a275f6005ef5639f7a1889fa3eb24c3125ccd70fcd3d"
> +
> +do_install() {
> +install -d ${D}${GCC_LINARO_BAREMETAL_TOOLCHAIN_RECIPE}
> +cp -r ${S}/. ${D}${GCC_LINARO_BAREMETAL_TOOLCHAIN_RECIPE}
> +}
> +
> +FILES_${PN} = "${GCC_LINARO_BAREMETAL_TOOLCHAIN_RECIPE}/*"
> +
> +INSANE_SKIP_${PN} = "already-stripped"
> diff --git a/recipes-ti/devtools/gcc-linaro.inc 
> b/recipes-ti/devtools/gcc-linaro.inc
> new file mode 100644
> index 000..19f5a2c
> --- /dev/null
> +++ b/recipes-ti/devtools/gcc-linaro.inc
> @@ -0,0 +1,10 @@
> +DESCRIPTION = "Linaro GCC for ARM"
> +HOMEPAGE = "https://launchpad.net/gcc-arm-embedded";
> +SECTION = "devel"
> +LICENSE = "GPL-3.0-with-GCC-exception & GPLv3"
> +LIC_FILES_CHKSUM = 
> "file://share/doc/gcc/GNU-Free-Documentation-License.html;md5=${LIC_CHKSUM}"
> +
> +PV = "7.2.1"
> +PR = "r0"
> +
> +GCC_ARM_YEAR = "2017.11"
> diff --git a/recipes-ti/includes/ti-paths.inc 
> b/recipes-ti/includes/ti-paths.inc
> index 4f99d5e..ddfb8aa 100644
> --- a/recipes-ti/includes/ti-paths.inc
> +++ b/recipes-ti/includes/ti-paths.inc
> @@ -56,6 +56,8 @@ export CG_XML_INSTALL_DIR_RECIPE = 
> "${installdir}/ti-cg-xml-tree"
>  export OMP_INSTALL_DIR_RECIPE= "${installdir}/ti-omp-tree"
>  export MPM_INSTALL_DIR_RECIPE= "${installdir}/ti-mpm-tree"
>  export TI_CGT6X_7_INSTALL_DIR_RECIPE   = "${installdir}/cgt6x-7"
> +export GCC_LINARO_BAREMETAL_TOOLCHAIN_RECIPE  = 
> "${installdir}/gcc-linaro-baremetal"
> +export GCC_LINARO_BAREMETAL_AARCH64_TOOLCHAIN_RECIPE  = 
> "${installdir}/gcc-linaro-baremetal-aarch64"
>  
>  # This is where the tools will end up in sysroot
>  export BIOS_INSTALL_DIR   = 
> "${STAGING_DIR_TARGET}${BIOS_INSTALL_DIR_RECIPE}"
> @@ -103,6 +105,9 @@ export CG_XML_INSTALL_DIR = 
> "${STAGING_DIR_NATIVE}${CG_XML_INSTALL_DIR_RECIP
>  export OMP_INSTALL_DIR= 
> "${STAGING_DIR_TARGET}${OMP_INSTALL_DIR_RECIPE}"
>  export MPM_INSTALL_DIR= 
> "${STAGING_DIR_TARGET}${MPM_INSTALL_DIR_RECIPE}"
>  export TI_CGT6X_7_INSTALL_DIR   = 
> "${STAGING_DIR_NATIVE}${TI_CGT6X_7_INSTALL_DIR_RECIPE}"
> +export GCC_LINARO_BAREMETAL_TOOLCHAIN =  

Re: [meta-ti] [PATCH 1/2] recipes-ti: devtools: add TI XDC tools 3.50.07.20

[Denys Dmytriyenko]

On Tue, Aug 14, 2018 at 02:39:45PM -0400, Denys Dmytriyenko wrote:
> On Tue, Aug 14, 2018 at 10:58:21AM -0400, Zhang, Hao wrote:
> > 
> > 
> > > -Original Message-
> > > From: Dmytriyenko, Denys
> > > Sent: Monday, August 13, 2018 8:56 PM
> > > To: Zhang, Hao
> > > Cc: meta-ti@yoctoproject.org
> > > Subject: Re: [meta-ti] [PATCH 1/2] recipes-ti: devtools: add TI XDC tools
> > > 3.50.07.20
> > > 
> > > On Fri, Aug 10, 2018 at 05:54:27AM -0400, hzh...@ti.com wrote:
> > > > From: Hao Zhang 
> > > >
> > > > Signed-off-by: Hao Zhang 
> > > > ---
> > > >  recipes-ti/devtools/ti-xdctools_3.50.07.20.bb | 9 +
> > > >  1 file changed, 9 insertions(+)
> > > >  create mode 100644 recipes-ti/devtools/ti-xdctools_3.50.07.20.bb
> > > 
> > > Why is 3.50.03 being left around?
> > > 
> > Please keep the old version for now, we will remove it later if it is not 
> > needed.
> 
> The general OE convention is to keep only the latest version, unless there 
> are 
> clear uses for older version as well.
> 
> That said, we keep on adding new versions and never remove old ones - 3.23, 
> 3.30, 3.50 and now another minor version of 3.50.
> 
> I'd understand the need for 3.23 and 3.30 if they are API/ABI incompatible 
> with 3.50, but two minor versions of 3.50?
> 
> Please start cleaning those up. Thanks.

And also please make patches as diffs against old versions - use -C/-M flags.


> > > > diff --git a/recipes-ti/devtools/ti-xdctools_3.50.07.20.bb b/recipes-
> > > ti/devtools/ti-xdctools_3.50.07.20.bb
> > > > new file mode 100644
> > > > index 000..d45f373
> > > > --- /dev/null
> > > > +++ b/recipes-ti/devtools/ti-xdctools_3.50.07.20.bb
> > > > @@ -0,0 +1,9 @@
> > > > +require recipes-ti/devtools/ti-xdctools-core.inc
> > > > +
> > > > +PV = "3_50_07_20"
> > > > +PR = "r0"
> > > > +
> > > > +LIC_FILES_CHKSUM =
> > > "file://docs/license/xdc/shelf/package.html;beginline=1;endline=140;md5=1
> > > 796f68c3d32d408415f5612f1f60652"
> > > > +
> > > > +SRC_URI[xdczip.md5sum] = "52e4b5ddf2e004c6acff52104840724e"
> > > > +SRC_URI[xdczip.sha256sum] =
> > > "bef631c110ca9243790de06cd51839170d7979b92e01396e4265009776ff7a07
> > > "
> > > > --
> > > > 2.7.4
> > > >
> > > > --
> > > > ___
> > > > meta-ti mailing list
> > > > meta-ti@yoctoproject.org
> > > > https://lists.yoctoproject.org/listinfo/meta-ti
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [PATCH 1/2] recipes-ti: devtools: add TI XDC tools 3.50.07.20

[Denys Dmytriyenko]

On Tue, Aug 14, 2018 at 10:58:21AM -0400, Zhang, Hao wrote:
> 
> 
> > -Original Message-
> > From: Dmytriyenko, Denys
> > Sent: Monday, August 13, 2018 8:56 PM
> > To: Zhang, Hao
> > Cc: meta-ti@yoctoproject.org
> > Subject: Re: [meta-ti] [PATCH 1/2] recipes-ti: devtools: add TI XDC tools
> > 3.50.07.20
> > 
> > On Fri, Aug 10, 2018 at 05:54:27AM -0400, hzh...@ti.com wrote:
> > > From: Hao Zhang 
> > >
> > > Signed-off-by: Hao Zhang 
> > > ---
> > >  recipes-ti/devtools/ti-xdctools_3.50.07.20.bb | 9 +
> > >  1 file changed, 9 insertions(+)
> > >  create mode 100644 recipes-ti/devtools/ti-xdctools_3.50.07.20.bb
> > 
> > Why is 3.50.03 being left around?
> > 
> Please keep the old version for now, we will remove it later if it is not 
> needed.

The general OE convention is to keep only the latest version, unless there are 
clear uses for older version as well.

That said, we keep on adding new versions and never remove old ones - 3.23, 
3.30, 3.50 and now another minor version of 3.50.

I'd understand the need for 3.23 and 3.30 if they are API/ABI incompatible 
with 3.50, but two minor versions of 3.50?

Please start cleaning those up. Thanks.


> > > diff --git a/recipes-ti/devtools/ti-xdctools_3.50.07.20.bb b/recipes-
> > ti/devtools/ti-xdctools_3.50.07.20.bb
> > > new file mode 100644
> > > index 000..d45f373
> > > --- /dev/null
> > > +++ b/recipes-ti/devtools/ti-xdctools_3.50.07.20.bb
> > > @@ -0,0 +1,9 @@
> > > +require recipes-ti/devtools/ti-xdctools-core.inc
> > > +
> > > +PV = "3_50_07_20"
> > > +PR = "r0"
> > > +
> > > +LIC_FILES_CHKSUM =
> > "file://docs/license/xdc/shelf/package.html;beginline=1;endline=140;md5=1
> > 796f68c3d32d408415f5612f1f60652"
> > > +
> > > +SRC_URI[xdczip.md5sum] = "52e4b5ddf2e004c6acff52104840724e"
> > > +SRC_URI[xdczip.sha256sum] =
> > "bef631c110ca9243790de06cd51839170d7979b92e01396e4265009776ff7a07
> > "
> > > --
> > > 2.7.4
> > >
> > > --
> > > ___
> > > meta-ti mailing list
> > > meta-ti@yoctoproject.org
> > > https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [PATCH v2] pru-icss_git.bb: Add am65x PRU_Halt

[Denys Dmytriyenko]

On Tue, Aug 14, 2018 at 10:50:21AM -0500, Nick Saulnier wrote:
> Updated SRCREV to point to an updated version of the PRU Software Support
> Package which includes PRU_Halt and RTU_Halt examples for am65x. PV will
> get updated in the next patch.

Not that it's critical, but I thought you were going to update PV here as 
well...


> Added PRU_Halt and RTU_Halt to do_install_append_am65xx-evm(). Decided to 
> leave
> the installation of PRU_Halt examples in each processor's do_install_append
> function for now since PRU_Halt and RTU_Halt for am65x have different output
> file names than the previous ICSS processors. Those different output names can
> be seen in the lines ALTERNATIVE_TARGET_pru-icss-halt[am65x].
> 
> The previous commit made several changes to account for the fact that am65x 
> Halt
> examples had not yet been added to the PRU Software Support Package. Those
> changes were removed in this commit.
> 
> Signed-off-by: Nick Saulnier 
> ---
>  recipes-bsp/pru/pru-icss_git.bb | 32 +++-
>  1 file changed, 23 insertions(+), 9 deletions(-)
> 
> diff --git a/recipes-bsp/pru/pru-icss_git.bb b/recipes-bsp/pru/pru-icss_git.bb
> index 3c871b70e3f0..e150076ec0a2 100644
> --- a/recipes-bsp/pru/pru-icss_git.bb
> +++ b/recipes-bsp/pru/pru-icss_git.bb
> @@ -8,10 +8,10 @@ inherit update-alternatives
>  
>  BRANCH = "master"
>  SRC_URI = 
> "git://git.ti.com/pru-software-support-package/pru-software-support-package.git;protocol=git;branch=${BRANCH}"
> -SRCREV = "81b568741b8b98e6f590271a9aea5956d2b2d9ce"
> +SRCREV = "1d9249c012005a669a6ffb2f76255d72ed5c0e4c"
>  
>  PV = "5.2.1"
> -PR = "r1"
> +PR = "r2"
>  
>  require recipes-ti/includes/ti-paths.inc
>  
> @@ -103,6 +103,13 @@ do_install_append_k2g() {
>  }
>  
>  do_install_append_am65xx-evm() {
> +for i in 0 1 
> +do
> +install -m 644 
> ${S}/examples/${PLATFORM}/PRU_Halt/gen/PRU${i}/PRU_Halt_${i}.out \
> +   ${D}/lib/firmware/pru
> +install -m 644 
> ${S}/examples/${PLATFORM}/RTU_Halt/gen/RTU${i}/RTU_Halt_${i}.out \
> +   ${D}/lib/firmware/pru
> +done
>  for i in 0 1 2
>  do
>  for j in 0 1
> @@ -116,7 +123,7 @@ do_install_append_am65xx-evm() {
>  done
>  }
>  
> -FILES_${PN}-halt = "/lib/firmware/pru/PRU_Halt.out"
> +FILES_${PN}-halt = "/lib/firmware/pru/PRU_Halt* /lib/firmware/pru/RTU_Halt*"
>  FILES_${PN}-rpmsg-echo = "/lib/firmware/pru/PRU_RPMsg_Echo_Interrupt* 
> /lib/firmware/pru/RTU_RPMsg_Echo_Interrupt*"
>  
>  # Set up names for the firmwares
> @@ -161,9 +168,6 @@ ALTERNATIVE_LINK_NAME[am65x-rtu2_1-fw] = 
> "/lib/firmware/am65x-rtu2_1-fw"
>  # Create the pru-icss-halt firmware alternatives
>  ALTERNATIVE_pru-icss-halt = "${PRU_ICSS_ALTERNATIVES}"
>  
> -# am65xx doesn't have halt FW for now
> -ALTERNATIVE_pru-icss-halt_am65xx-evm = ""
> -
>  ALTERNATIVE_TARGET_pru-icss-halt[am335x-pru0-fw] = 
> "/lib/firmware/pru/PRU_Halt.out"
>  ALTERNATIVE_TARGET_pru-icss-halt[am335x-pru1-fw] = 
> "/lib/firmware/pru/PRU_Halt.out"
>  
> @@ -182,6 +186,19 @@ ALTERNATIVE_TARGET_pru-icss-halt[k2g-pru0_1-fw] = 
> "/lib/firmware/pru/PRU_Halt.ou
>  ALTERNATIVE_TARGET_pru-icss-halt[k2g-pru1_0-fw] = 
> "/lib/firmware/pru/PRU_Halt.out"
>  ALTERNATIVE_TARGET_pru-icss-halt[k2g-pru1_1-fw] = 
> "/lib/firmware/pru/PRU_Halt.out"
>  
> +ALTERNATIVE_TARGET_pru-icss-halt[am65x-pru0_0-fw] = 
> "/lib/firmware/pru/PRU_Halt_0.out"
> +ALTERNATIVE_TARGET_pru-icss-halt[am65x-pru0_1-fw] = 
> "/lib/firmware/pru/PRU_Halt_1.out"
> +ALTERNATIVE_TARGET_pru-icss-halt[am65x-pru1_0-fw] = 
> "/lib/firmware/pru/PRU_Halt_0.out"
> +ALTERNATIVE_TARGET_pru-icss-halt[am65x-pru1_1-fw] = 
> "/lib/firmware/pru/PRU_Halt_1.out"
> +ALTERNATIVE_TARGET_pru-icss-halt[am65x-pru2_0-fw] = 
> "/lib/firmware/pru/PRU_Halt_0.out"
> +ALTERNATIVE_TARGET_pru-icss-halt[am65x-pru2_1-fw] = 
> "/lib/firmware/pru/PRU_Halt_1.out"
> +ALTERNATIVE_TARGET_pru-icss-halt[am65x-rtu0_0-fw] = 
> "/lib/firmware/pru/RTU_Halt_0.out"
> +ALTERNATIVE_TARGET_pru-icss-halt[am65x-rtu0_1-fw] = 
> "/lib/firmware/pru/RTU_Halt_1.out"
> +ALTERNATIVE_TARGET_pru-icss-halt[am65x-rtu1_0-fw] = 
> "/lib/firmware/pru/RTU_Halt_0.out"
> +ALTERNATIVE_TARGET_pru-icss-halt[am65x-rtu1_1-fw] = 
> "/lib/firmware/pru/RTU_Halt_1.out"
> +ALTERNATIVE_TARGET_pru-icss-halt[am65x-rtu2_0-fw] = 
> "/lib/firmware/pru/RTU_Halt_0.out"
> +ALTERNATIVE_TARGET_pru-icss-halt[am65x-rtu2_1-fw] = 
> "/lib/firmware/pru/RTU_Halt_1.out"
> +
>  ALTERNATIVE_PRIORITY_pru-icss-halt = "50"
>  
>  # Create the pru-icss-rpmsg-echo firmware alternatives
> @@ -220,9 +237,6 @@ ALTERNATIVE_TARGET_pru-icss-rpmsg-echo[am65x-rtu2_1-fw] = 
> "/lib/firmware/pru/RTU
>  
>  ALTERNATIVE_PRIORITY_pru-icss-rpmsg-echo = "100"
>  
> -# am65xx doesn't have halt FW for now
> -ALLOW_EMPTY_${PN}-halt = "1"
> -
>  ALLOW_EMPTY_${PN} = "1"
>  
>  # This installs PRU firmware, so skip "arch" QA check
> -- 
> 1.9.1
> 
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.o

Re: [meta-ti] [PATCH] recipes-ti: devtools: add GCC Linaro baremetal toolchain 2017.11 v7.2.1

[Denys Dmytriyenko]

What is the revision number of this patch? Please specify PATCH v# in the 
subject to ensure the correct one gets merged.

Also, see below.


On Tue, Aug 14, 2018 at 08:47:06AM -0400, hzh...@ti.com wrote:
> From: Hao Zhang 
> 
> Signed-off-by: Hao Zhang 
> ---
>  .../gcc-linaro-baremetal-aarch64-native.bb | 24 
> ++
>  recipes-ti/devtools/gcc-linaro-baremetal-native.bb | 24 
> ++
>  recipes-ti/devtools/gcc-linaro.inc | 12 +++
>  recipes-ti/includes/ti-paths.inc   |  5 +
>  4 files changed, 65 insertions(+)
>  create mode 100644 recipes-ti/devtools/gcc-linaro-baremetal-aarch64-native.bb
>  create mode 100644 recipes-ti/devtools/gcc-linaro-baremetal-native.bb
>  create mode 100644 recipes-ti/devtools/gcc-linaro.inc
> 
> diff --git a/recipes-ti/devtools/gcc-linaro-baremetal-aarch64-native.bb 
> b/recipes-ti/devtools/gcc-linaro-baremetal-aarch64-native.bb
> new file mode 100644
> index 000..5e3e3b6
> --- /dev/null
> +++ b/recipes-ti/devtools/gcc-linaro-baremetal-aarch64-native.bb
> @@ -0,0 +1,24 @@
> +include recipes-ti/devtools/gcc-linaro.inc
> +
> +PACKAGE_DIR = "gcc-linaro-${PV}-${GCC_ARM_YEAR}-x86_64_aarch64-elf"
> +S = "${WORKDIR}/${PACKAGE_DIR}"
> +
> +LIC_CHKSUM = "bc7fad4bba98e7a4cd5ab3042506493c"
> +
> +inherit native
> +require recipes-ti/includes/ti-paths.inc
> +
> +SRC_URI = 
> "https://releases.linaro.org/components/toolchain/binaries/7.2-${GCC_ARM_YEAR}/aarch64-elf/gcc-linaro-${PV}-${GCC_ARM_YEAR}-x86_64_aarch64-elf.tar.xz;name=gcc-linaro-aarch64";
> +
> +SRC_URI[gcc-linaro-aarch64.md5sum] = "4972f8943820bdd2f577f498de78964b"
> +SRC_URI[gcc-linaro-aarch64.sha256sum] = 
> "30fb7d876bcb982c502057c593d9c1f11b35d5158a26d986718e2b998388c4c8"
> +
> +do_install() {
> +install -d ${D}${GCC_LINARO_BAREMETAL_AARCH64_TOOLCHAIN_RECIPE}
> +cp -r ${S}/. ${D}${GCC_LINARO_BAREMETAL_AARCH64_TOOLCHAIN_RECIPE}
> +}
> +
> +FILES_${PN} = "${GCC_LINARO_BAREMETAL_AARCH64_TOOLCHAIN_RECIPE}/*"
> +
> +INSANE_SKIP_${PN} = "already-stripped"
> +
> diff --git a/recipes-ti/devtools/gcc-linaro-baremetal-native.bb 
> b/recipes-ti/devtools/gcc-linaro-baremetal-native.bb
> new file mode 100644
> index 000..07a6f49
> --- /dev/null
> +++ b/recipes-ti/devtools/gcc-linaro-baremetal-native.bb
> @@ -0,0 +1,24 @@
> +include recipes-ti/devtools/gcc-linaro.inc
> +
> +PACKAGE_DIR = "gcc-linaro-${PV}-${GCC_ARM_YEAR}-x86_64_arm-eabi"
> +S = "${WORKDIR}/${PACKAGE_DIR}"
> +
> +LIC_CHKSUM = "bc7fad4bba98e7a4cd5ab3042506493c"
> +
> +inherit native
> +require recipes-ti/includes/ti-paths.inc
> +
> +SRC_URI = 
> "https://releases.linaro.org/components/toolchain/binaries/7.2-${GCC_ARM_YEAR}/arm-eabi/gcc-linaro-${PV}-${GCC_ARM_YEAR}-x86_64_arm-eabi.tar.xz;name=gcc-linaro";
> +
> +SRC_URI[gcc-linaro.md5sum] = "9a4a39cfc78c84375b1160aa93587aed"
> +SRC_URI[gcc-linaro.sha256sum] = 
> "45fc4f90af2e2e9c3197a275f6005ef5639f7a1889fa3eb24c3125ccd70fcd3d"
> +
> +do_install() {
> +install -d ${D}${GCC_LINARO_BAREMETAL_TOOLCHAIN_RECIPE}
> +cp -r ${S}/. ${D}${GCC_LINARO_BAREMETAL_TOOLCHAIN_RECIPE}
> +}
> +
> +FILES_${PN} = "${GCC_LINARO_BAREMETAL_TOOLCHAIN_RECIPE}/*"
> +
> +INSANE_SKIP_${PN} = "already-stripped"
> +
> diff --git a/recipes-ti/devtools/gcc-linaro.inc 
> b/recipes-ti/devtools/gcc-linaro.inc
> new file mode 100644
> index 000..6575fc5
> --- /dev/null
> +++ b/recipes-ti/devtools/gcc-linaro.inc
> @@ -0,0 +1,12 @@
> +DESCRIPTION = "Linaro GCC for ARM"
> +HOMEPAGE = "https://launchpad.net/gcc-arm-embedded";
> +SECTION = "devel"
> +LICENSE = "GPL-3.0-with-GCC-exception & GPLv3"
> +LIC_FILES_CHKSUM = 
> "file://share/doc/gcc/GNU-Free-Documentation-License.html;md5=${LIC_CHKSUM}"
> +
> +PV = "7.2.1"
> +PR = "r0"
> +
> +GCC_ARM_YEAR = "2017.11"
> +
> +
> diff --git a/recipes-ti/includes/ti-paths.inc 
> b/recipes-ti/includes/ti-paths.inc
> index 4f99d5e..ddfb8aa 100644
> --- a/recipes-ti/includes/ti-paths.inc
> +++ b/recipes-ti/includes/ti-paths.inc
> @@ -56,6 +56,8 @@ export CG_XML_INSTALL_DIR_RECIPE = 
> "${installdir}/ti-cg-xml-tree"
>  export OMP_INSTALL_DIR_RECIPE= "${installdir}/ti-omp-tree"
>  export MPM_INSTALL_DIR_RECIPE= "${installdir}/ti-mpm-tree"
>  export TI_CGT6X_7_INSTALL_DIR_RECIPE   = "${installdir}/cgt6x-7"
> +export GCC_LINARO_BAREMETAL_TOOLCHAIN_RECIPE  = 
> "${installdir}/gcc-linaro-baremetal"
> +export GCC_LINARO_BAREMETAL_AARCH64_TOOLCHAIN_RECIPE  = 
> "${installdir}/gcc-linaro-baremetal-aarch64"
>  
>  # This is where the tools will end up in sysroot
>  export BIOS_INSTALL_DIR   = 
> "${STAGING_DIR_TARGET}${BIOS_INSTALL_DIR_RECIPE}"
> @@ -103,6 +105,9 @@ export CG_XML_INSTALL_DIR = 
> "${STAGING_DIR_NATIVE}${CG_XML_INSTALL_DIR_RECIP
>  export OMP_INSTALL_DIR= 
> "${STAGING_DIR_TARGET}${OMP_INSTALL_DIR_RECIPE}"
>  export MPM_INSTALL_DIR= 
> "${STAGING_DIR_TARGET}${MPM_INSTALL_DIR_RECIPE}"
>  export TI_CGT6X_7_INSTALL_DIR   = 
> "${STAGING_DIR_NATIVE}${TI_CGT6X_7_INST

Re: [meta-ti] [PATCH v1] pru-icss_git.bb: Add am65x PRU_Halt

[Denys Dmytriyenko]

On Mon, Aug 13, 2018 at 02:34:23PM -0500, Nick Saulnier wrote:
> Updated SRCREV to point to an updated version of the PRU Software Support
> Package which includes PRU_Halt and RTU_Halt examples for am65x. PV will
> get updated in the next patch.
> 
> Added PRU_Halt and RTU_Halt to do_install_append_am65xx-evm(). Decided to 
> leave
> the installation of PRU_Halt examples in each processor's do_install_append
> function for now since PRU_Halt and RTU_Halt for am65x have different output
> file names than the previous ICSS processors. Those different output names can
> be seen in the lines ALTERNATIVE_TARGET_pru-icss-halt[am65x].
> 
> The previous commit made several changes to account for the fact that am65x 
> Halt
> examples had not yet been added to the PRU Software Support Package. I tried 
> to
> comment out those temporary changes from the previous commit. The commented
> lines will be removed in a future patch once we verify that I commented the
> correct lines of code.

Thanks, looks good. Do you expect more functional changes in the next patch? 
If not, I'd suggest cleaning commented out lines in v2.


> Signed-off-by: Nick Saulnier 
> ---
>  recipes-bsp/pru/pru-icss_git.bb | 35 ---
>  1 file changed, 28 insertions(+), 7 deletions(-)
> 
> diff --git a/recipes-bsp/pru/pru-icss_git.bb b/recipes-bsp/pru/pru-icss_git.bb
> index 3c871b70e3f0..7d23b3d066f8 100644
> --- a/recipes-bsp/pru/pru-icss_git.bb
> +++ b/recipes-bsp/pru/pru-icss_git.bb
> @@ -8,10 +8,10 @@ inherit update-alternatives
>  
>  BRANCH = "master"
>  SRC_URI = 
> "git://git.ti.com/pru-software-support-package/pru-software-support-package.git;protocol=git;branch=${BRANCH}"
> -SRCREV = "81b568741b8b98e6f590271a9aea5956d2b2d9ce"
> +SRCREV = "1d9249c012005a669a6ffb2f76255d72ed5c0e4c"
>  
>  PV = "5.2.1"
> -PR = "r1"
> +PR = "r2"
>  
>  require recipes-ti/includes/ti-paths.inc
>  
> @@ -103,6 +103,13 @@ do_install_append_k2g() {
>  }
>  
>  do_install_append_am65xx-evm() {
> +for i in 0 1 
> +do
> +install -m 644 
> ${S}/examples/${PLATFORM}/PRU_Halt/gen/PRU${i}/PRU_Halt_${i}.out \
> +   ${D}/lib/firmware/pru
> +install -m 644 
> ${S}/examples/${PLATFORM}/RTU_Halt/gen/RTU${i}/RTU_Halt_${i}.out \
> +   ${D}/lib/firmware/pru
> +done
>  for i in 0 1 2
>  do
>  for j in 0 1
> @@ -116,7 +123,7 @@ do_install_append_am65xx-evm() {
>  done
>  }
>  
> -FILES_${PN}-halt = "/lib/firmware/pru/PRU_Halt.out"
> +FILES_${PN}-halt = "/lib/firmware/pru/PRU_Halt* /lib/firmware/pru/RTU_Halt*"
>  FILES_${PN}-rpmsg-echo = "/lib/firmware/pru/PRU_RPMsg_Echo_Interrupt* 
> /lib/firmware/pru/RTU_RPMsg_Echo_Interrupt*"
>  
>  # Set up names for the firmwares
> @@ -161,8 +168,8 @@ ALTERNATIVE_LINK_NAME[am65x-rtu2_1-fw] = 
> "/lib/firmware/am65x-rtu2_1-fw"
>  # Create the pru-icss-halt firmware alternatives
>  ALTERNATIVE_pru-icss-halt = "${PRU_ICSS_ALTERNATIVES}"
>  
> -# am65xx doesn't have halt FW for now
> -ALTERNATIVE_pru-icss-halt_am65xx-evm = ""
> +# since am65xx now has halt, we can comment out the line below right?
> +#ALTERNATIVE_pru-icss-halt_am65xx-evm = ""
>  
>  ALTERNATIVE_TARGET_pru-icss-halt[am335x-pru0-fw] = 
> "/lib/firmware/pru/PRU_Halt.out"
>  ALTERNATIVE_TARGET_pru-icss-halt[am335x-pru1-fw] = 
> "/lib/firmware/pru/PRU_Halt.out"
> @@ -182,6 +189,19 @@ ALTERNATIVE_TARGET_pru-icss-halt[k2g-pru0_1-fw] = 
> "/lib/firmware/pru/PRU_Halt.ou
>  ALTERNATIVE_TARGET_pru-icss-halt[k2g-pru1_0-fw] = 
> "/lib/firmware/pru/PRU_Halt.out"
>  ALTERNATIVE_TARGET_pru-icss-halt[k2g-pru1_1-fw] = 
> "/lib/firmware/pru/PRU_Halt.out"
>  
> +ALTERNATIVE_TARGET_pru-icss-halt[am65x-pru0_0-fw] = 
> "/lib/firmware/pru/PRU_Halt_0.out"
> +ALTERNATIVE_TARGET_pru-icss-halt[am65x-pru0_1-fw] = 
> "/lib/firmware/pru/PRU_Halt_1.out"
> +ALTERNATIVE_TARGET_pru-icss-halt[am65x-pru1_0-fw] = 
> "/lib/firmware/pru/PRU_Halt_0.out"
> +ALTERNATIVE_TARGET_pru-icss-halt[am65x-pru1_1-fw] = 
> "/lib/firmware/pru/PRU_Halt_1.out"
> +ALTERNATIVE_TARGET_pru-icss-halt[am65x-pru2_0-fw] = 
> "/lib/firmware/pru/PRU_Halt_0.out"
> +ALTERNATIVE_TARGET_pru-icss-halt[am65x-pru2_1-fw] = 
> "/lib/firmware/pru/PRU_Halt_1.out"
> +ALTERNATIVE_TARGET_pru-icss-halt[am65x-rtu0_0-fw] = 
> "/lib/firmware/pru/RTU_Halt_0.out"
> +ALTERNATIVE_TARGET_pru-icss-halt[am65x-rtu0_1-fw] = 
> "/lib/firmware/pru/RTU_Halt_1.out"
> +ALTERNATIVE_TARGET_pru-icss-halt[am65x-rtu1_0-fw] = 
> "/lib/firmware/pru/RTU_Halt_0.out"
> +ALTERNATIVE_TARGET_pru-icss-halt[am65x-rtu1_1-fw] = 
> "/lib/firmware/pru/RTU_Halt_1.out"
> +ALTERNATIVE_TARGET_pru-icss-halt[am65x-rtu2_0-fw] = 
> "/lib/firmware/pru/RTU_Halt_0.out"
> +ALTERNATIVE_TARGET_pru-icss-halt[am65x-rtu2_1-fw] = 
> "/lib/firmware/pru/RTU_Halt_1.out"
> +
>  ALTERNATIVE_PRIORITY_pru-icss-halt = "50"
>  
>  # Create the pru-icss-rpmsg-echo firmware alternatives
> @@ -220,8 +240,9 @@ ALTERNATIVE_TARGET_pru-icss-rpmsg-echo[am65x-rtu2_1-fw] = 
> "/lib/firmware/pru/RTU
>  
>  ALTERNATIVE

Re: [meta-ti] [PATCH 2/2] recipes-ti: bios: add TI SYSBIOS 6.73.00.12

[Denys Dmytriyenko]

On Fri, Aug 10, 2018 at 05:54:49AM -0400, hzh...@ti.com wrote:
> From: Hao Zhang 
> 
> Signed-off-by: Hao Zhang 
> ---
>  recipes-ti/bios/ti-sysbios_6.73.00.12.bb | 15 +++
>  1 file changed, 15 insertions(+)
>  create mode 100644 recipes-ti/bios/ti-sysbios_6.73.00.12.bb

Same question - do we need to keep around 6.52, 6.46 and 6.33 versions?


> diff --git a/recipes-ti/bios/ti-sysbios_6.73.00.12.bb 
> b/recipes-ti/bios/ti-sysbios_6.73.00.12.bb
> new file mode 100644
> index 000..b727673
> --- /dev/null
> +++ b/recipes-ti/bios/ti-sysbios_6.73.00.12.bb
> @@ -0,0 +1,15 @@
> +require recipes-ti/bios/ti-sysbios.inc
> +
> +PV = "6_73_00_12"
> +PR = "r0"
> +
> +LIC_FILES_CHKSUM = 
> "file://manifest_bios_${PV}.html;md5=99771475f3621a6bf690df10327eaaa9"
> +
> +SRC_URI[sysbiosbin.md5sum] = "f8ff74bf0cfebdd5689fba843272ac61"
> +SRC_URI[sysbiosbin.sha256sum] = 
> "4fdf76696fb43984a9cae739fd2ee091ca9d031ad0277d2bb94dbb26eae63f43"
> +
> +TI_BIN_UNPK_CMDS = ""
> +TI_BIN_UNPK_ARGS = "--mode unattended --prefix ${WORKDIR}"
> +
> +BINFILE = "bios_${PV}.run"
> +SRC_URI = 
> "http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/bios/sysbios/${PV}/exports/${BINFILE};name=sysbiosbin";
> -- 
> 2.7.4
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [PATCH 1/2] recipes-ti: devtools: add TI XDC tools 3.50.07.20

[Denys Dmytriyenko]

On Fri, Aug 10, 2018 at 05:54:27AM -0400, hzh...@ti.com wrote:
> From: Hao Zhang 
> 
> Signed-off-by: Hao Zhang 
> ---
>  recipes-ti/devtools/ti-xdctools_3.50.07.20.bb | 9 +
>  1 file changed, 9 insertions(+)
>  create mode 100644 recipes-ti/devtools/ti-xdctools_3.50.07.20.bb

Why is 3.50.03 being left around?


> diff --git a/recipes-ti/devtools/ti-xdctools_3.50.07.20.bb 
> b/recipes-ti/devtools/ti-xdctools_3.50.07.20.bb
> new file mode 100644
> index 000..d45f373
> --- /dev/null
> +++ b/recipes-ti/devtools/ti-xdctools_3.50.07.20.bb
> @@ -0,0 +1,9 @@
> +require recipes-ti/devtools/ti-xdctools-core.inc
> +
> +PV = "3_50_07_20"
> +PR = "r0"
> +
> +LIC_FILES_CHKSUM = 
> "file://docs/license/xdc/shelf/package.html;beginline=1;endline=140;md5=1796f68c3d32d408415f5612f1f60652"
> +
> +SRC_URI[xdczip.md5sum] = "52e4b5ddf2e004c6acff52104840724e"
> +SRC_URI[xdczip.sha256sum] = 
> "bef631c110ca9243790de06cd51839170d7979b92e01396e4265009776ff7a07"
> -- 
> 2.7.4
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti