Re: [yocto] Raspberry pi build with QT5 creator...... failing to compile.

[Steve Plant]

Hi Trevor,

Yes, you are correct, sorry if I had not made that clear. I’m currently cross 
compiling QT5 code on a windows machine running debian through VirtualBox which 
is then downloaded onto a Beaglebone Black embedded project. Although it works, 
its often prone to little idiosyncrasies which can take hours to figure out.

The idea is to compile the QT5 code on the raspberry pi and download straight 
to the target system, because both are ARM based is cuts out a lot of extra 
steps, hopefully making development smoother.

The idea of using the Yocto project is that I can custom build both platforms 
with pretty much an identical image (less GUI for the beaglebone)

That’s the plan.. could change at any time


Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10

From: Trevor Woerner<mailto:twoer...@gmail.com>
Sent: Saturday, 13 May 2017 7:00 AM
To: Steve Plant<mailto:ste...@hotmail.com>
Cc: yocto@yoctoproject.org<mailto:yocto@yoctoproject.org>
Subject: Re: [yocto] Raspberry pi build with QT5 creator.. failing to 
compile.

Hi Steve,

It seems like there's a lot of stuff going on at the same time. So to
start I'd like to just focus on one thing at a time.

On Wed, May 10, 2017 at 9:40 AM, Steve Plant <ste...@hotmail.com> wrote:
> I'm currently attempting to build a raspberry pi image, which I can use to
> develop QT5 code for a beaglebone black.

This statement is very confusing to me.

It sounds like you want to build an image for the raspi, boot that
image on a pi, hookup a keyboard, mouse, monitor to the pi, write qt5
code on the pi, and compile that code on the pi to run on a
beaglebone. Is that your goal?

Best regards,
Trevor

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

[yocto] Raspberry pi build with QT5 creator...... failing to compile.

[Steve Plant]

Hi all,


I'm currently attempting to build a raspberry pi image, which I can use to 
develop QT5 code for a beaglebone black.

Everything is going well and I have got toaster successfully compiling a 
rpi-sdimg of "rpi-basic-image" which I have added "xserver-xorg xinit openbox 
packagegroup-lxde-extended qtbase" to the IMAGE_INSTALL_append line.


However as soon as I add "qt5-creator" to the IMAGE_INSTALL_append line and run 
"rpi-basic-image" again, I get the following error...  Failed tasks - qtwayland 
do_compile  


I'm not sure why it is trying to compile qtwayland, is there a way I can 
override this???


I have attached the relevant error file. I'm new to all this Yocto world, so 
please explain everything in simple terms if you can.


Thanks for any help.


Regards, Steve.


log.do_compile.27031
Description: log.do_compile.27031
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Raspberry pi build with gstreamer1.0 error - No recipes avalible.

[Steve Plant]

Hi all,

Starting a brand new project for the rasberry pi2, on the master branch, using 
toaster to start/monitor the build.

Everything set up for the most basic build, however when I build 
"rpi-basic-image" it fails with this error:

No recipes available for:
  
/home/steve/Yocto/poky/_toaster_clones/_git___git.yoctoproject.org_meta-raspberrypi_master/recipes-multimedia/gstreamer/gstreamer1.0-omx_1.2.0.bbappend
  
/home/steve/Yocto/poky/_toaster_clones/_git___git.yoctoproject.org_meta-raspberrypi_master/recipes-multimedia/gstreamer/gstreamer1.0-omx_git.bbappend


Looking through some of the recent changes on this mailing list, the 
gstreamer1.0 package got a change recently. has anybody else come across this 
error?



Regards, Steve.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Raspberry Pi2 Fails to boot into LXDE.

[Steve Plant]

Hi Khem,


I was finally able to SSH into the raspberry pi and found the Xorg.log file, 
exactly where you said it would be.


Looking at it, for some reason Xorg cannot find the module evdev. I have looked 
for this but cannot find where it is supposed to be located.


I did notice that there was a "libevdev" which had not been included into the 
build, so I added that by updating the Bitbake variables with:


IMAGE_INSTALL_append
libevdev packagegroup-core-x11-base packagegroup-lxde-base connman


Rebuild the "rpi-basic-image" and copied the image to the SD card, booted up 
the rpi but no change. I have noticed that there is also a "python-evdev" 
package with is not included in the build, but that is part of the 
"meta-python" layer which I have not added. Do I need to add this???



Here is the Xorg.log file


[3087510.347]
X.Org X Server 1.18.4
Release Date: 2016-07-19
[3087510.347] X Protocol Version 11, Revision 0
[3087510.347] Build Operating System: Linux 3.16.0-4-amd64 x86_64
[3087510.347] Current Operating System: Linux raspberrypi2 4.4.48 #1 SMP Sat 
Feb 25 00:03:23 AEST 2017 armv7l
[3087510.347] Kernel command line: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=800 
bcm2708_fb.fbheight=480 bcm2709.boardrev=0xa21041 bcm2709.serial=0xf9e8fbc6 
smsc95xx.macaddr=B8:27:EB:E8:FB:C6 bcm2708_fb.fbswap=1 
bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=47 
bcm2709.disk_led_active_low=0 vc_mem.mem_base=0x3dc0 
vc_mem.mem_size=0x3f00  dwc_otg.lpm_enable=0 console=ttyAMA0,115200 
root=/dev/mmcblk0p2 rootfstype=ext4 rootwait
[3087510.347] Build Date: 07 March 2017  09:16:40PM
[3087510.347]
[3087510.347] Current version of pixman: 0.34.0
[3087510.347] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[3087510.347] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[3087510.348] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Mar 10 11:43:14 
2017
[3087510.359] (==) Using config file: "/etc/X11/xorg.conf"
[3087510.359] (==) Using config directory: "/etc/X11/xorg.conf.d"
[3087510.359] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[3087510.372] (==) No Layout section.  Using the first Screen section.
[3087510.372] (==) No screen section available. Using defaults.
[3087510.372] (**) |-->Screen "Default Screen Section" (0)
[3087510.372] (**) |   |-->Monitor ""
[3087510.379] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[3087510.380] (==) Automatically adding devices
[3087510.380] (==) Automatically enabling devices
[3087510.380] (==) Automatically adding GPU devices
[3087510.380] (==) Max clients allowed: 256, resource mask: 0x1f
[3087510.383] (WW) The directory "/usr/share/fonts/X11/misc/" does not exist.
[3087510.383] Entry deleted from font path.
[3087510.383] (WW) The directory "/usr/share/fonts/X11/TTF/" does not exist.
[3087510.383] Entry deleted from font path.
[3087510.383] (WW) The directory "/usr/share/fonts/X11/OTF/" does not exist.
[3087510.383] Entry deleted from font path.
[3087510.383] (WW) The directory "/usr/share/fonts/X11/Type1/" does not exist.
[3087510.383] Entry deleted from font path.
[3087510.383] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[3087510.383] Entry deleted from font path.
[3087510.383] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[3087510.383] Entry deleted from font path.
[3087510.383] (==) FontPath set to:

[3087510.383] (==) ModulePath set to "/usr/lib/xorg/modules"
[3087510.383] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[3087510.383] (II) Loader magic: 0x1c3b80
[3087510.383] (II) Module ABI versions:
[3087510.384] X.Org ANSI C Emulation: 0.4
[3087510.384] X.Org Video Driver: 20.0
[3087510.384] X.Org XInput driver : 22.1
[3087510.384] X.Org Server Extension : 9.0
[3087510.384] (II) no primary bus or device found
[3087510.384] (II) LoadModule: "glx"
[3087510.393] (WW) Warning, couldn't open module glx
[3087510.393] (II) UnloadModule: "glx"
[3087510.393] (II) Unloading glx
[3087510.393] (EE) Failed to load module "glx" (module does not exist, 0)
[3087510.394] (==) Matched modesetting as autoconfigured driver 0
[3087510.394] (==) Matched fbdev as autoconfigured driver 1
[3087510.394] (==) Assigned the driver to the xf86ConfigLayout
[3087510.394] (II) LoadModule: "modesetting"
[3087510.394] (WW) Warning, couldn't open module modesetting
[3087510.394] (II) UnloadModule: "modesetting"
[3087510.394] (II) Unloading modesetting
[3087510.394] (EE) Failed to load module "modesetting" (module does not exist, 
0)
[3087510.394] (II) LoadModule: "fbdev"
[3087510.395] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so

Re: [yocto] Raspberry Pi2 Fails to boot into LXDE.

[Steve Plant]

OK, I have spent the last day googling my heart out trying to find the Xorg.log 
file without any luck.


The problem is that due to the rpi hanging on boot, the only way I can access 
the SD card to look for the file is place it in a USB SD card reader and use my 
VirtualBox based Debian to "ls" directores etc.

Having established that there is no file located at /var/log/Xorg.log (there 
isn't a log directory) but there is a symbolic link in the var directory - goes 
nowhere.


After goggling I discovered that the file could also be in the 
~/.local/share/xorg/Xorg.0.log, however if I try to look there I get 
"permission denied" and cannot seem to get to the root directory of the card 
and I can't find a way around this as I'm trying to access this directory 
through the USB card reader.


Looked everywhere with no answers, Is there anyone who could help me here??


Regards, Steve.



From: Khem Raj <raj.k...@gmail.com>
Sent: Wednesday, 8 March 2017 5:17 p.m.
To: Steve Plant
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Raspberry Pi2 Fails to boot into LXDE.

On 17-03-08 12:40:51, Steve Plant wrote:
> Hi All,
>
>
> Very new to all this linux world, and especially Yocto.
>
>
> I'm working on a embedded project at the moment using a raspberry pi2 board.
>
>
> I have used toaster with Morty 2.2 to compile an image 
> using"rpi-basic-image", to this I have added the following bitbake variables:
>
> Bitbake variables
>
> DISTRO
> poky
> DL_DIR
> /home/steve/poky/downloads
> IMAGE_FSTYPES
> ext3 jffs2 tar.bz2 rpi-sdimg
> IMAGE_INSTALL_append
> packagegroup-core-x11-base packagegroup-lxde-base connman
> PACKAGE_CLASSES
> package_rpm
> SSTATE_DIR
> /home/steve/poky/sstate-cache
>
> DISABLE_OVERSCAN
> 1
> GPU_MEM_1024
> 512
>
> I have dd'ed the image to an SD card increased the sdb2 partition to the max 
> size and powered up the rpi. Everything looks fine to start with, as it 
> displays the four raspberrys in the top left, then the white "Yocto Project" 
> splash screen complete with small blue dot to the side appears, the progress 
> bar moves across to 100 percent, then the screen turns black with a white 
> cursor in the middle and it appears to freeze with only a very dim one second 
> flash of the "act" led.
>
>
> I have then connected the 7" touchscreen and apart from the added 
> multicolored square at the very beginning I get the exact same boot up 
> problem, hangs on the black screen with white cursor (good to see its all 
> resized correctly for the TfT through!!)
>
>
> Before adding the packagegroup-core-x11-base and packagegroup-lxde-base I 
> successfully copied over and ran the rpi-basic-image with no problem, ending 
> up with a usable console.
>
>
> Looking for any help here, I'm thinking I've missed adding a package, or some 
> type of local.conf instruction. any suggestions would be 
> appreciated.

Can you send the content of /var/log/Xorg.log file ?

>
>
>
> Regards, Steve.

> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
yocto Info Page<https://lists.yoctoproject.org/listinfo/yocto>
lists.yoctoproject.org
Discussion of all things about the Yocto Project. Read our Community Guidelines 
or learn more about how to participate in other community discussions.



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

[yocto] Raspberry Pi2 Fails to boot into LXDE.

[Steve Plant]

Hi All,


Very new to all this linux world, and especially Yocto.


I'm working on a embedded project at the moment using a raspberry pi2 board.


I have used toaster with Morty 2.2 to compile an image using"rpi-basic-image", 
to this I have added the following bitbake variables:

Bitbake variables

DISTRO
poky
DL_DIR
/home/steve/poky/downloads
IMAGE_FSTYPES
ext3 jffs2 tar.bz2 rpi-sdimg
IMAGE_INSTALL_append
packagegroup-core-x11-base packagegroup-lxde-base connman
PACKAGE_CLASSES
package_rpm
SSTATE_DIR
/home/steve/poky/sstate-cache

DISABLE_OVERSCAN
1
GPU_MEM_1024
512

I have dd'ed the image to an SD card increased the sdb2 partition to the max 
size and powered up the rpi. Everything looks fine to start with, as it 
displays the four raspberrys in the top left, then the white "Yocto Project" 
splash screen complete with small blue dot to the side appears, the progress 
bar moves across to 100 percent, then the screen turns black with a white 
cursor in the middle and it appears to freeze with only a very dim one second 
flash of the "act" led.


I have then connected the 7" touchscreen and apart from the added multicolored 
square at the very beginning I get the exact same boot up problem, hangs on the 
black screen with white cursor (good to see its all resized correctly for the 
TfT through!!)


Before adding the packagegroup-core-x11-base and packagegroup-lxde-base I 
successfully copied over and ran the rpi-basic-image with no problem, ending up 
with a usable console.


Looking for any help here, I'm thinking I've missed adding a package, or some 
type of local.conf instruction. any suggestions would be 
appreciated.



Regards, Steve.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto