Building meta-arago daisy

Building meta-arago daisy

[Devin Hughes]

[-- Attachment #1: Type: text/plain, Size: 1545 bytes --]

Hello Everyone

 

I am trying to build the daisy branch for my 335x-EVMSK. The build is setup
using arago-daisy-config.txt, and I am using the internal linaro compiler. I
get the same results described using the external linaro gcc4.7 toolchain
mentioned on the wiki page. I have run into a couple of problems:

1.      The arago-base-tisdk-image builds successfully and boots on the SK,
but the splash screen fails to show with failure to find /dev/fb0 in dmesg.
After the boot is complete, I can manually display the splash properly. This
makes me think psplash is running before the lcd modules are loaded, and I
was curious if any of you have seen this behavior.

2.  Building arago-core-tisdk-image fails when building qt 5.2.1 with (from
log.do_compile):


/home/devin/yocto/build/arago-tmp-eglibc/work/cortexa8t2hf-vfp-neon-oe-linux
-gnueabi/qtbase/5.2.1-r0-arago2/qtbase-opensource-src-5.2.1/src/tools/qdoc/q
uoter.cpp: In constructor 'Quoter::Quoter()':

/home/devin/yocto/build/arago-tmp-eglibc/work/cortexa8t2hf-vfp-neon-oe-linux
-gnueabi/qtbase/5.2.1-r0-arago2/qtbase-opensource-src-5.2.1/src/tools/qdoc/q
uoter.cpp:139:1: internal compiler error: in add_stores, at
var-tracking.c:5918

}

^

Please submit a full bug report,

with preprocessed source if appropriate.

See <http://gcc.gnu.org/bugs.html> for instructions.

make[2]: *** [.obj/quoter.o] Error 1

make[2]: *** Waiting for unfinished jobs....

 

Any guidance is greatly appreciated.

 

Regards,

Devin Hughes

 


[-- Attachment #2: Type: text/html, Size: 6375 bytes --]

Re: Building meta-arago daisy

[Denys Dmytriyenko]

Hi, Devin,

On Tue, Aug 26, 2014 at 09:37:11AM -0400, Devin Hughes wrote:
> I am trying to build the daisy branch for my 335x-EVMSK. The build is setup
> using arago-daisy-config.txt, and I am using the internal linaro compiler. I
> get the same results described using the external linaro gcc4.7 toolchain
> mentioned on the wiki page. I have run into a couple of problems:
> 
> 1.      The arago-base-tisdk-image builds successfully and boots on the SK,
> but the splash screen fails to show with failure to find /dev/fb0 in dmesg.
> After the boot is complete, I can manually display the splash properly. This
> makes me think psplash is running before the lcd modules are loaded, and I
> was curious if any of you have seen this behavior.

Yes, it's a known issue, but not a critical one, so not yet being addressed.


> 2.  Building arago-core-tisdk-image fails when building qt 5.2.1 with (from
> log.do_compile):
> 
> 
> /home/devin/yocto/build/arago-tmp-eglibc/work/cortexa8t2hf-vfp-neon-oe-linux
> -gnueabi/qtbase/5.2.1-r0-arago2/qtbase-opensource-src-5.2.1/src/tools/qdoc/q
> uoter.cpp: In constructor 'Quoter::Quoter()':
> 
> /home/devin/yocto/build/arago-tmp-eglibc/work/cortexa8t2hf-vfp-neon-oe-linux
> -gnueabi/qtbase/5.2.1-r0-arago2/qtbase-opensource-src-5.2.1/src/tools/qdoc/q
> uoter.cpp:139:1: internal compiler error: in add_stores, at
> var-tracking.c:5918

Internal compiler error in qtbase is also a known issue with Linaro toolchain 
gcc-4.8 and Linaro developers are looking into it already. Right now we are 
using gcc-4.7 (2013.03) and evaluating gcc-4.9...

-- 
Denys


> }
> 
> ^
> 
> Please submit a full bug report,
> 
> with preprocessed source if appropriate.
> 
> See <http://gcc.gnu.org/bugs.html> for instructions.
> 
> make[2]: *** [.obj/quoter.o] Error 1
> 
> make[2]: *** Waiting for unfinished jobs....
> 
>  
> 
> Any guidance is greatly appreciated.
> 
>  
> 
> Regards,
> 
> Devin Hughes
> 
>  
> 

> _______________________________________________
> meta-arago mailing list
> meta-arago@arago-project.org
> http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago

Re: Building meta-arago daisy

[Devin Hughes]

Hi Denys,

> -----Original Message-----
> From: Denys Dmytriyenko [mailto:denys@ti.com]
> Sent: Tuesday, August 26, 2014 10:21 AM
> To: Devin Hughes
> Cc: meta-arago@arago-project.org
> Subject: Re: [meta-arago] Building meta-arago daisy
> 
> Hi, Devin,
> 
> On Tue, Aug 26, 2014 at 09:37:11AM -0400, Devin Hughes wrote:
> > I am trying to build the daisy branch for my 335x-EVMSK. The build is
> setup
> > using arago-daisy-config.txt, and I am using the internal linaro
> compiler. I
> > get the same results described using the external linaro gcc4.7
> toolchain
> > mentioned on the wiki page. I have run into a couple of problems:
> >
> > 1.      The arago-base-tisdk-image builds successfully and boots on the
> SK,
> > but the splash screen fails to show with failure to find /dev/fb0 in
> dmesg.
> > After the boot is complete, I can manually display the splash properly.
> This
> > makes me think psplash is running before the lcd modules are loaded,
> > and
> I
> > was curious if any of you have seen this behavior.
> 
> Yes, it's a known issue, but not a critical one, so not yet being
addressed.
[Devin Hughes] No problem, I think I will use the kernel splash as a
substitute.

> 
> 
> > 2.  Building arago-core-tisdk-image fails when building qt 5.2.1 with
> (from
> > log.do_compile):
> >
> >
> >
> /home/devin/yocto/build/arago-tmp-eglibc/work/cortexa8t2hf-vfp-neon-oe-lin
> ux
> >
> -gnueabi/qtbase/5.2.1-r0-arago2/qtbase-opensource-src-5.2.1/src/tools/qdoc
> /q
> > uoter.cpp: In constructor 'Quoter::Quoter()':
> >
> >
> /home/devin/yocto/build/arago-tmp-eglibc/work/cortexa8t2hf-vfp-neon-oe-lin
> ux
> >
> -gnueabi/qtbase/5.2.1-r0-arago2/qtbase-opensource-src-5.2.1/src/tools/qdoc
> /q
> > uoter.cpp:139:1: internal compiler error: in add_stores, at
> > var-tracking.c:5918
> 
> Internal compiler error in qtbase is also a known issue with Linaro
toolchain
> gcc-4.8 and Linaro developers are looking into it already. Right now we
are
> using gcc-4.7 (2013.03) and evaluating gcc-4.9...
[Devin Hughes] Is the daisy configured build stable? I rebuilt the image
yesterday 
after the servers returned and it seems to run unexpectedly. No boot errors,
but the
touchscreen and application performance seem worse than the SDK release. I
am 
going to build a customized image as a test next, and I was thinking
arago-base from
daisy would be a good starting point since I would like qt 5.2 or greater.
> 
> --
> Denys
> 
> 
> > }
> >
> > ^
> >
> > Please submit a full bug report,
> >
> > with preprocessed source if appropriate.
> >
> > See <http://gcc.gnu.org/bugs.html> for instructions.
> >
> > make[2]: *** [.obj/quoter.o] Error 1
> >
> > make[2]: *** Waiting for unfinished jobs....
> >
> >
> >
> > Any guidance is greatly appreciated.
> >
> >
> >
> > Regards,
> >
> > Devin Hughes
> >
> >
> >
> 
> > _______________________________________________
> > meta-arago mailing list
> > meta-arago@arago-project.org
> > http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago

Re: Building meta-arago daisy

[Cooper Jr., Franklin]

> -----Original Message-----
> From: meta-arago-bounces@arago-project.org [mailto:meta-arago-
> bounces@arago-project.org] On Behalf Of Devin Hughes
> Sent: Friday, August 29, 2014 9:40 AM
> To: Dmytriyenko, Denys
> Cc: meta-arago@arago-project.org
> Subject: Re: [meta-arago] Building meta-arago daisy
> 
> Hi Denys,
> 
> > -----Original Message-----
> > From: Denys Dmytriyenko [mailto:denys@ti.com]
> > Sent: Tuesday, August 26, 2014 10:21 AM
> > To: Devin Hughes
> > Cc: meta-arago@arago-project.org
> > Subject: Re: [meta-arago] Building meta-arago daisy
> >
> > Hi, Devin,
> >
> > On Tue, Aug 26, 2014 at 09:37:11AM -0400, Devin Hughes wrote:
> > > I am trying to build the daisy branch for my 335x-EVMSK. The build
> > > is
> > setup
> > > using arago-daisy-config.txt, and I am using the internal linaro
> > compiler. I
> > > get the same results described using the external linaro gcc4.7
> > toolchain
> > > mentioned on the wiki page. I have run into a couple of problems:
> > >
> > > 1.      The arago-base-tisdk-image builds successfully and boots on the
> > SK,
> > > but the splash screen fails to show with failure to find /dev/fb0 in
> > dmesg.
> > > After the boot is complete, I can manually display the splash properly.
> > This
> > > makes me think psplash is running before the lcd modules are loaded,
> > > and
> > I
> > > was curious if any of you have seen this behavior.
> >
> > Yes, it's a known issue, but not a critical one, so not yet being
> addressed.
> [Devin Hughes] No problem, I think I will use the kernel splash as a substitute.
> 
> >
> >
> > > 2.  Building arago-core-tisdk-image fails when building qt 5.2.1
> > > with
> > (from
> > > log.do_compile):
> > >
> > >
> > >
> > /home/devin/yocto/build/arago-tmp-eglibc/work/cortexa8t2hf-vfp-neon-
> oe
> > -lin
> > ux
> > >
> > -gnueabi/qtbase/5.2.1-r0-arago2/qtbase-opensource-src-5.2.1/src/tools/
> > qdoc
> > /q
> > > uoter.cpp: In constructor 'Quoter::Quoter()':
> > >
> > >
> > /home/devin/yocto/build/arago-tmp-eglibc/work/cortexa8t2hf-vfp-neon-
> oe
> > -lin
> > ux
> > >
> > -gnueabi/qtbase/5.2.1-r0-arago2/qtbase-opensource-src-5.2.1/src/tools/
> > qdoc
> > /q
> > > uoter.cpp:139:1: internal compiler error: in add_stores, at
> > > var-tracking.c:5918
> >
> > Internal compiler error in qtbase is also a known issue with Linaro
> toolchain
> > gcc-4.8 and Linaro developers are looking into it already. Right now
> > we
> are
> > using gcc-4.7 (2013.03) and evaluating gcc-4.9...
> [Devin Hughes] Is the daisy configured build stable? I rebuilt the image
> yesterday after the servers returned and it seems to run unexpectedly. No
> boot errors, but the touchscreen and application performance seem worse
> than the SDK release. 
[Franklin] Can you explain what you mean in terms of application performance issues?
I am going to build a customized image as a test next,
> and I was thinking arago-base from daisy would be a good starting point
> since I would like qt 5.2 or greater.
[Franklin] So by default we are using Wayland/Weston and for Qt 5 we are using the Wayland compositor. However, there are several touch screen related bugs in Weston and Qt 5 that we are working with the Qt 5 and Weston team to address. It will take some time to fix so if acceptable I would recommend just using a usb mouse as a work around for now if your running into those problems also.

> >
> > --
> > Denys
> >
> >
> > > }
> > >
> > > ^
> > >
> > > Please submit a full bug report,
> > >
> > > with preprocessed source if appropriate.
> > >
> > > See <http://gcc.gnu.org/bugs.html> for instructions.
> > >
> > > make[2]: *** [.obj/quoter.o] Error 1
> > >
> > > make[2]: *** Waiting for unfinished jobs....
> > >
> > >
> > >
> > > Any guidance is greatly appreciated.
> > >
> > >
> > >
> > > Regards,
> > >
> > > Devin Hughes
> > >
> > >
> > >
> >
> > > _______________________________________________
> > > meta-arago mailing list
> > > meta-arago@arago-project.org
> > > http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
> 
> 
> _______________________________________________
> meta-arago mailing list
> meta-arago@arago-project.org
> http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago

Re: Building meta-arago daisy

[Devin Hughes]

> -----Original Message-----
> From: Cooper Jr., Franklin [mailto:fcooper@ti.com]
> Sent: Friday, August 29, 2014 10:47 AM
> To: Devin Hughes; Dmytriyenko, Denys
> Cc: meta-arago@arago-project.org
> Subject: RE: [meta-arago] Building meta-arago daisy
> 
> 
> 
> > -----Original Message-----
> > From: meta-arago-bounces@arago-project.org [mailto:meta-arago-
> > bounces@arago-project.org] On Behalf Of Devin Hughes
> > Sent: Friday, August 29, 2014 9:40 AM
> > To: Dmytriyenko, Denys
> > Cc: meta-arago@arago-project.org
> > Subject: Re: [meta-arago] Building meta-arago daisy
> >
> > Hi Denys,
> >
> > > -----Original Message-----
> > > From: Denys Dmytriyenko [mailto:denys@ti.com]
> > > Sent: Tuesday, August 26, 2014 10:21 AM
> > > To: Devin Hughes
> > > Cc: meta-arago@arago-project.org
> > > Subject: Re: [meta-arago] Building meta-arago daisy
> > >
> > > Hi, Devin,
> > >
> > > On Tue, Aug 26, 2014 at 09:37:11AM -0400, Devin Hughes wrote:
> > > > I am trying to build the daisy branch for my 335x-EVMSK. The build
> > > > is
> > > setup
> > > > using arago-daisy-config.txt, and I am using the internal linaro
> > > compiler. I
> > > > get the same results described using the external linaro gcc4.7
> > > toolchain
> > > > mentioned on the wiki page. I have run into a couple of problems:
> > > >
> > > > 1.      The arago-base-tisdk-image builds successfully and boots on
the
> > > SK,
> > > > but the splash screen fails to show with failure to find /dev/fb0
> > > > in
> > > dmesg.
> > > > After the boot is complete, I can manually display the splash
properly.
> > > This
> > > > makes me think psplash is running before the lcd modules are
> > > > loaded, and
> > > I
> > > > was curious if any of you have seen this behavior.
> > >
> > > Yes, it's a known issue, but not a critical one, so not yet being
> > addressed.
> > [Devin Hughes] No problem, I think I will use the kernel splash as a
substitute.
> >
> > >
> > >
> > > > 2.  Building arago-core-tisdk-image fails when building qt 5.2.1
> > > > with
> > > (from
> > > > log.do_compile):
> > > >
> > > >
> > > >
> > > /home/devin/yocto/build/arago-tmp-eglibc/work/cortexa8t2hf-vfp-neon-
> > oe
> > > -lin
> > > ux
> > > >
> > > -gnueabi/qtbase/5.2.1-r0-arago2/qtbase-opensource-src-5.2.1/src/tool
> > > s/
> > > qdoc
> > > /q
> > > > uoter.cpp: In constructor 'Quoter::Quoter()':
> > > >
> > > >
> > > /home/devin/yocto/build/arago-tmp-eglibc/work/cortexa8t2hf-vfp-neon-
> > oe
> > > -lin
> > > ux
> > > >
> > > -gnueabi/qtbase/5.2.1-r0-arago2/qtbase-opensource-src-5.2.1/src/tool
> > > s/
> > > qdoc
> > > /q
> > > > uoter.cpp:139:1: internal compiler error: in add_stores, at
> > > > var-tracking.c:5918
> > >
> > > Internal compiler error in qtbase is also a known issue with Linaro
> > toolchain
> > > gcc-4.8 and Linaro developers are looking into it already. Right now
> > > we
> > are
> > > using gcc-4.7 (2013.03) and evaluating gcc-4.9...
> > [Devin Hughes] Is the daisy configured build stable? I rebuilt the
> > image yesterday after the servers returned and it seems to run
> > unexpectedly. No boot errors, but the touchscreen and application
> > performance seem worse than the SDK release.
> [Franklin] Can you explain what you mean in terms of application
performance
> issues?
[Devin Hughes] Performance was the wrong choice of words now that I know
about
the touchscreen trouble. It's more the permanent title bar and lack of
screen updates after closing an application. For instance, after running one
of the 3d demos in matrix gui, the title bar shows the last opengl rendering
on the top of the lcd.  
> I am going to build a customized image as a test next,
> > and I was thinking arago-base from daisy would be a good starting
> > point since I would like qt 5.2 or greater.
> [Franklin] So by default we are using Wayland/Weston and for Qt 5 we are
using
> the Wayland compositor. However, there are several touch screen related
bugs
> in Weston and Qt 5 that we are working with the Qt 5 and Weston team to
> address. It will take some time to fix so if acceptable I would recommend
just
> using a usb mouse as a work around for now if your running into those
problems
> also.
[Devin Hughes] USB mouse would be fine for me, but libusb is failing to
initialize. In
dmesg I can see musb_init_controller failures, and the platform driver
reports a deferred
probe. The only similar information I can find on google describes
improperly configured
device tree sources, but the fixes are already included in the daisy
referenced kernel.
> 
> > >
> > > --
> > > Denys
> > >
> > >
> > > > }
> > > >
> > > > ^
> > > >
> > > > Please submit a full bug report,
> > > >
> > > > with preprocessed source if appropriate.
> > > >
> > > > See <http://gcc.gnu.org/bugs.html> for instructions.
> > > >
> > > > make[2]: *** [.obj/quoter.o] Error 1
> > > >
> > > > make[2]: *** Waiting for unfinished jobs....
> > > >
> > > >
> > > >
> > > > Any guidance is greatly appreciated.
> > > >
> > > >
> > > >
> > > > Regards,
> > > >
> > > > Devin Hughes
> > > >
> > > >
> > > >
> > >
> > > > _______________________________________________
> > > > meta-arago mailing list
> > > > meta-arago@arago-project.org
> > > > http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
> >
> >
> > _______________________________________________
> > meta-arago mailing list
> > meta-arago@arago-project.org
> > http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago

Re: Building meta-arago daisy

[Denys Dmytriyenko]

On Fri, Aug 29, 2014 at 11:58:09AM -0400, Devin Hughes wrote:
> > > [Devin Hughes] Is the daisy configured build stable? I rebuilt the
> > > image yesterday after the servers returned and it seems to run
> > > unexpectedly. No boot errors, but the touchscreen and application
> > > performance seem worse than the SDK release.
> > [Franklin] Can you explain what you mean in terms of application
> performance
> > issues?
> [Devin Hughes] Performance was the wrong choice of words now that I know
> about
> the touchscreen trouble. It's more the permanent title bar and lack of
> screen updates after closing an application. For instance, after running one
> of the 3d demos in matrix gui, the title bar shows the last opengl rendering
> on the top of the lcd.  

3D demos don't talk to Wayland stack and they take over fbdev completely and 
previously Qt4-based refresh-screen app was used to update the screen 
afterwards.


> > I am going to build a customized image as a test next,
> > > and I was thinking arago-base from daisy would be a good starting
> > > point since I would like qt 5.2 or greater.
> > [Franklin] So by default we are using Wayland/Weston and for Qt 5 we are
> using
> > the Wayland compositor. However, there are several touch screen related
> bugs
> > in Weston and Qt 5 that we are working with the Qt 5 and Weston team to
> > address. It will take some time to fix so if acceptable I would recommend
> just
> > using a usb mouse as a work around for now if your running into those
> problems
> > also.
> [Devin Hughes] USB mouse would be fine for me, but libusb is failing to
> initialize. In
> dmesg I can see musb_init_controller failures, and the platform driver
> reports a deferred
> probe. The only similar information I can find on google describes
> improperly configured
> device tree sources, but the fixes are already included in the daisy
> referenced kernel.

Hmm, you said that is with 335x SK, right? I haven't seen this on BeagleBone 
Black or 335x EVM. I'll try to see if I can reproduce it with SK...

-- 
Denys

Re: Building meta-arago daisy

[Devin Hughes]

> -----Original Message-----
> From: Denys Dmytriyenko [mailto:denys@ti.com]
> Sent: Friday, August 29, 2014 12:46 PM
> To: Devin Hughes
> Cc: 'Cooper Jr., Franklin'; meta-arago@arago-project.org
> Subject: Re: [meta-arago] Building meta-arago daisy
> 
> On Fri, Aug 29, 2014 at 11:58:09AM -0400, Devin Hughes wrote:
> > > > [Devin Hughes] Is the daisy configured build stable? I rebuilt the
> > > > image yesterday after the servers returned and it seems to run
> > > > unexpectedly. No boot errors, but the touchscreen and application
> > > > performance seem worse than the SDK release.
> > > [Franklin] Can you explain what you mean in terms of application
> > performance
> > > issues?
> > [Devin Hughes] Performance was the wrong choice of words now that I
> > know about the touchscreen trouble. It's more the permanent title bar
> > and lack of screen updates after closing an application. For instance,
> > after running one of the 3d demos in matrix gui, the title bar shows
> > the last opengl rendering on the top of the lcd.
> 
> 3D demos don't talk to Wayland stack and they take over fbdev completely
and
> previously Qt4-based refresh-screen app was used to update the screen
> afterwards.
> 
[Devin Hughes] This makes sense. 
> 
> > > I am going to build a customized image as a test next,
> > > > and I was thinking arago-base from daisy would be a good starting
> > > > point since I would like qt 5.2 or greater.
> > > [Franklin] So by default we are using Wayland/Weston and for Qt 5 we
> > > are
> > using
> > > the Wayland compositor. However, there are several touch screen
> > > related
> > bugs
> > > in Weston and Qt 5 that we are working with the Qt 5 and Weston team
> > > to address. It will take some time to fix so if acceptable I would
> > > recommend
> > just
> > > using a usb mouse as a work around for now if your running into
> > > those
> > problems
> > > also.
> > [Devin Hughes] USB mouse would be fine for me, but libusb is failing
> > to initialize. In dmesg I can see musb_init_controller failures, and
> > the platform driver reports a deferred probe. The only similar
> > information I can find on google describes improperly configured
> > device tree sources, but the fixes are already included in the daisy
> > referenced kernel.
> 
> Hmm, you said that is with 335x SK, right? I haven't seen this on
BeagleBone
> Black or 335x EVM. I'll try to see if I can reproduce it with SK...
[Devin Hughes] Yes, it's the 335x SK, and a vanilla arago-daisy conf with
gcc-4.7. No custom layers have been added yet.
> 
> --
> Denys