Re: [PATCH 2/2] pru-icss: Add PRU software package version 4.0.0.0

[Jacob Stiffler <j-stiffler@ti.com>]

On 10/29/2015 10:46 AM, Denys Dmytriyenko wrote:
> On Thu, Oct 29, 2015 at 08:27:13AM -0400, Jacob Stiffler wrote:
>> Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
>> ---
>>   recipes-bsp/pru/pru-icss_git.bb | 69 +++++++++++++++++++++++++++++++++++++++++
>>   1 file changed, 69 insertions(+)
>>   create mode 100644 recipes-bsp/pru/pru-icss_git.bb
>>
>> diff --git a/recipes-bsp/pru/pru-icss_git.bb b/recipes-bsp/pru/pru-icss_git.bb
>> new file mode 100644
>> index 0000000..2e90b65
>> --- /dev/null
>> +++ b/recipes-bsp/pru/pru-icss_git.bb
>> @@ -0,0 +1,69 @@
>> +DESCRIPTION = "Programmable Real-time Unit Software Package"
>> +HOMEPAGE = "http://processors.wiki.ti.com/index.php/PRU-ICSS"
>> +LICENSE = "BSD-3-Clause & GPL-2.0 & PD"
>> +
>> +LIC_FILES_CHKSUM = "file://PRU-Package-v4.0-Manifest.html;md5=5ea937e4ff2c924a735d42e61ad8cbe3"
>> +
>> +BRANCH = "master"
>> +SRC_URI = "git://git.ti.com/pru-software-support-package/pru-software-support-package.git;protocol=git;branch=${BRANCH}"
>> +SRCREV = "476289eb7c3a91977bae84aea55c56f3120b48ea"
>> +
>> +BASE_PV = "4.0.0.0"
> Do you need this defined? I don't see it being used.

I was going to use this when creating the sourceipk. It is desired to 
not have the commit id fragment in the destination sourceipk location. I 
suppose I could just drop the SRCPV from the PV.

>
>> +PV = "${BASE_PV}+git${SRCPV}"
>> +PR = "r0"
>> +
>> +PACKAGE_ARCH = "${MACHINE_ARCH}"
>> +
>> +DEPENDS = "ti-cgt-pru-native"
>> +
>> +S = "${WORKDIR}/git"
>> +
>> +export PRU_CGT = "${STAGING_DIR_NATIVE}/usr/share/ti/cgt-pru"
> require ti-paths.inc
> export PRU_CGT = "${TI_CGT_PRU_INSTALL_DIR}"

Thanks for pointing this out. I missed this when bringing the recipe 
over from meta-processor-sdk.

>
>> +
>> +SUBDIRS = "examples pru_cape/pru_fw lib/src labs"
>> +
>> +do_compile() {
>> +    for dir in ${SUBDIRS}
>> +    do
>> +        make -C ${S}/$dir
>> +    done
>> +}
> Does it build all the example FW images for all platforms, or are those
> already prebuilt?

This rebuilds all of the example firmware for all platforms.

>
>> +# By default, do not install anything
>> +do_install() {
>> +    :
>> +}
>> +
>> +do_install_am335x-evm() {
>> +    install -d ${D}/lib/firmware
>> +    for i in 0 1
>> +    do
>> +        install -m 0644 ${S}/examples/am335x/PRU_RPMsg_Echo_Interrupt${i}/gen/PRU_RPMsg_Echo_Interrupt${i}.out \
>> +                        ${D}/lib/firmware/am335x-pru${i}-fw
>> +    done
>> +}
>> +
>> +do_install_am437x-evm() {
>> +    install -d ${D}/lib/firmware
>> +    for i in 0 1
>> +    do
>> +        install -m 0644 ${S}/examples/am437x/PRU_RPMsg_Echo_Interrupt${i}/gen/PRU_RPMsg_Echo_Interrupt${i}.out \
>> +                        ${D}/lib/firmware/am437x-pru1_${i}-fw
>> +    done
>> +}
>> +
>> +do_install_am57xx-evm() {
>> +    install -d ${D}/lib/firmware
>> +    for i in 1 2
>> +    do
>> +        for j in 0 1
>> +        do
>> +            install -m 0644 ${S}/examples/am572x/PRU_RPMsg_Echo_Interrupt${i}_${j}/gen/PRU_RPMsg_Echo_Interrupt${i}_${j}.out \
>> +                            ${D}/lib/firmware/am57xx-pru${i}_${j}-fw
>> +        done
>> +    done
>> +}
> What about PRU-less platforms? You don't set COMPATIBLE_MACHINE, so for
> example KS2 will try to build something, but won't install anything. Do we
> want to prevent that?

That makes sense. I will add this.

>
>> +FILES_${PN} += "/lib/firmware"
>> +
>> +INSANE_SKIP_${PN} = "arch"
>> -- 
>> 1.9.1
>>
>> -- 
>> _______________________________________________
>> meta-ti mailing list
>> meta-ti@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/meta-ti