It was building default arago-core-tisdk-bundle.

On Mon, Aug 19, 2019 at 11:47:52AM -0400, Xu, Jianzhong wrote:
> Denys,
> 
> I tried "MACHINE=am65xx-evm bitbake nativesdk-tidl-utils" in my local Yocto 
> and it builds fine.
> 
> Did you try to do "MACHINE=am65xx-evm bitbake tidl-utils" when you saw the 
> failure? It wouldn't build because am65xx-evm is not in the 
> COMPATIBLE_MACHINES of tidl-utils.
> 
> Thanks,
> Jianzhong
> 
> -----Original Message-----
> From: Dmytriyenko, Denys 
> Sent: Tuesday, August 13, 2019 7:51 PM
> To: Xu, Jianzhong
> Cc: [email protected]
> Subject: Re: [meta-arago] [thud/master] [PATCH] tidl-utils: bump SRCREV
> 
> This update fails on am65x. Does it require armnn changes? If so, should be 
> in 
> the series, not 2 separate patches.
> 
> 
> On Fri, Aug 09, 2019 at 03:40:48PM -0400, Jianzhong Xu wrote:
> > * tidl import tool fixes for non-square padding and Caffe data layer format
> > 
> > Signed-off-by: Jianzhong Xu <[email protected]>
> > ---
> >  meta-arago-extras/recipes-ti/tidl-utils/tidl-utils.inc | 4 ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
> > 
> > diff --git a/meta-arago-extras/recipes-ti/tidl-utils/tidl-utils.inc 
> > b/meta-arago-extras/recipes-ti/tidl-utils/tidl-utils.inc
> > index 2c29fc27..6fdeec48 100644
> > --- a/meta-arago-extras/recipes-ti/tidl-utils/tidl-utils.inc
> > +++ b/meta-arago-extras/recipes-ti/tidl-utils/tidl-utils.inc
> > @@ -1,6 +1,6 @@
> >  SRC_URI = "git://git.ti.com/tidl/tidl-utils.git;protocol=git;branch=master"
> > -SRCREV = "0c52c82a2aed1a27ca2a9b4b11effb426842b6ab"
> > +SRCREV = "b2466e02f99d85d8afcbc93edc612da5cc9345de"
> >  
> > -PV = "01.01.01.00"
> > +PV = "01.01.02.00"
> >  PR = "r0"
> >  
> > -- 
> > 2.17.1
> > 
> > _______________________________________________
> > meta-arago mailing list
> > [email protected]
> > http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
_______________________________________________
meta-arago mailing list
[email protected]
http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago

Reply via email to