[yocto] Where to look when literally nothing happens?

[Erik Hoogeveen]

Hello,

I’m rather new to embedded software and Yocto. I hope this is the right place 
to ask. If not I’d appreciate it if someone could point me the right way to do 
so.

I’m trying to make a Yocto build for a raspberry pi 3. I’ve got it booting and 
doing things on a regular plain vanilla Raspberry pi 3 board. It boots and over 
serial console I can log in and do things.
But the ultimate target is to run this image on my own board which is built 
around a Raspberry Pi Compute Module 3 Lite. Since regular Raspbian (what’ I’ve 
used so far) works fine on both boards without modification I assumed that this 
would be the case as well with this image I made myself. But it turns out I was 
wrong.

When I take the image from the build and stick it in my compute module board, 
literally nothing happens. The boot sequence doesn’t seem to even begin, I get 
nothing on the serial console, and none of the peripherals like the ethernet 
ever come to life either.

And since nothing happens I really have no idea where to look for a solution. 
I’m guessing this is a bit of a noob issue? It would be great if someone could 
point me in a direction to look at.

Kind regards,
Erik Hoogeveen.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Where to look when literally nothing happens?

[Erik Hoogeveen]

Thank you for the tip Outback.

Since sending my email I’ve actually tried exactly that, I built a fresh image 
with target raspberrypi-cm3.
And the funny thing is, it does the exact same thing. It works fine on the 
regular pi, and nothing with my cm3 lite.

My current suspicion is that this is related to u-boot somehow. I need u-boot 
because I’d like to use Mender for the OTA updating of my devices.

I’m going to see if I can get a stripped down version with just u-boot but 
without Mender going first. Then maybe I can take it from there.

In the mean time all tips and tricks you could give me are very much 
appreciated.

Kind regards,
Erik
On 1 Nov 2018, 12:51 +0100, Outback Dingo , wrote:
On Thu, Nov 1, 2018 at 6:33 PM Erik Hoogeveen
 wrote:

Hello,

I’m rather new to embedded software and Yocto. I hope this is the right place 
to ask. If not I’d appreciate it if someone could point me the right way to do 
so.

I’m trying to make a Yocto build for a raspberry pi 3. I’ve got it booting and 
doing things on a regular plain vanilla Raspberry pi 3 board. It boots and over 
serial console I can log in and do things.
But the ultimate target is to run this image on my own board which is built 
around a Raspberry Pi Compute Module 3 Lite. Since regular Raspbian (what’ I’ve 
used so far) works fine on both boards without modification I assumed that this 
would be the case as well with this image I made myself. But it turns out I was 
wrong.

When I take the image from the build and stick it in my compute module board, 
literally nothing happens. The boot sequence doesn’t seem to even begin, I get 
nothing on the serial console, and none of the peripherals like the ethernet 
ever come to life either.

And since nothing happens I really have no idea where to look for a solution. 
I’m guessing this is a bit of a noob issue? It would be great if someone could 
point me in a direction to look at.

you probably built for a raspberrypi3 or raspberrypi3-64 ffor the 64bit

i believe the compute module 3 target is raspberrypi-cm3

you could pretty muuchh do a diff uunder the meta-raspberryypi ffor
the differences in whats built


Kind regards,
Erik Hoogeveen.
--
___
yocto mailing list
yocto@yoctoproject.org
https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.yoctoproject.org%2Flistinfo%2Fyocto&data=02%7C01%7C%7C0bd7e7fee835429b62b808d63ff0595e%7C84df9e7fe9f640afb435%7C1%7C0%7C636766698851268696&sdata=7aiUvFhvNbWvMN8VMy%2BnqlUh9VCAQpnCTMohVpYnmKs%3D&reserved=0
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Yocto - Rpi: u-boot --- hangs on boot?

[Erik Hoogeveen]

Hi,

I had something similar but with a RPI compute module 3.
For me it helped to put the u-boot.bin file in config.txt.
See: https://github.com/agherzan/meta-raspberrypi/issues/359

Cheers,
Erik
On 18 Dec 2018, 17:28 +0100, yocto-requ...@yoctoproject.org, wrote:
Date: Mon, 17 Dec 2018 18:37:04 +
From: Kman Devnull 
To: yocto@yoctoproject.org
Subject: [yocto] Yocto - Rpi: u-boot --- hangs on boot?
Message-ID:

Content-Type: text/plain; charset="utf-8"

Hi,
How do you get the u-boot built with yocto for Raspberry Pi 3?

- I used this link

 to get
the base build working for q5-image on Raspberry Pi 3.
- I have used the yocto 'thud' release.
- Now in order to get u-boot build I added the below line for local.conf
file.
RPI_USE_U_BOOT = "1"
- When I boot it just hangs on a rainbow colour screen.

Please find bblayers.conf and local.conf attached.

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

[yocto] [meta-java] How to include sound support?

[Erik Hoogeveen]

Hi,

I’m tying to install openjre-8 in my build for a raspberry pi cm3. I’m using 
the thud branch on all layers.
In my local.conf I have distro features like so:

DISTRO_FEATURES_append = " alsa bluetooth bluez5 systemd wifi”

My device layer has a bbappend file "recipes-core/openjdk/openjre-8_%.bbappend” 
with contents:

PACKAGECONFIG = " \
repack \
alsa \
gif \
jpeg \
png \
zlib \
“

I would expect this to enable sound in the build. But in 
"tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/openjre-8/172b11-r0/temp/log.do_compile”
 it keeps telling me.

NOTE: make BUILD_HEADLESS_ONLY=1 BUILD_HEADLESS=true BUILD_SOUNDLESS_ONLY=1 
X11_NOT_NEEDED=1 CUPS_NOT_NEEDED=1 PULSE_NOT_NEEDED=1

And sure enough on the device I get a JVM that does not give me any audio 
support.

I went through the recipe files to my best ability but I can't understand why I 
can’t get it to omit "BUILD_SOUNDLESS_ONLY=1 “ when building. As far as I can 
tell it should enable sound when alsa is both in PACKAGECONFIG and 
DISTRO_FEATURES.

Any hints as to what I’m overlooking? Thanks!

Kind regards,
Erik Hoogeveen
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Storing Sstate in S3 success stories?

[Erik Hoogeveen]

Hi Timothy,

The S3 protocol is HTTP(S) based, the overhead per object is quite significant. 
This is not much of a problem for large files but the sstate_cache contains 
mostly lots of really small files. I think in this case you’re better of 
storing the cache on a secondary EBS volume that you can attach as a regular 
block device to the EC2 instance. You can swtich on deletion protection to make 
it survive EC2 termination.

Since EBS volumes are quite a bit more expensive than S3 buckets  you could 
make snapshots to transfer the state between build runs in stead then you can 
destroy the EBS volume when nothing is running.

Alls the documentation about EBS is here 
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AmazonEBS.html

Cheers,
Erik
On 26 Feb 2019, 02:45 +0100, Timothy Froehlich , wrote:
I've been spending a bit too long this past week trying to build up a 
reproducable build infrastructure in AWS and I've got very little experience 
with cloud infrastucture and I'm wondering if I'm going in the wrong direction. 
I'm attempting to host my sstate_cache as a mirror in a private S3 bucket, and 
I believe I have everything configured properly, including exposing the bucket 
to http requests, since I can wget files that I've previously synced up to the 
bucket. However if I add in the SSTATE_MIRRORS to my build, bitbake slows to a 
crawl (it's a powerful VM) and barely seems to get anything. The EC2 instance 
is in the same region as the S3 bucket, roles have been configured properly to 
allow access, etc.

I'm not looking for help debugging this, I just want to know whether I'm right 
that hosting my sstate in an S3 bucket should work. I've only been able to find 
one mention of it being done with no reproduction hints.

--
___
yocto mailing list
yocto@yoctoproject.org
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.yoctoproject.org%2Flistinfo%2Fyocto&data=02%7C01%7C%7Cdc66c2ab9da44272220b08d69b8c2262%7C84df9e7fe9f640afb435%7C1%7C0%7C636867423506178146&sdata=TjwcnaFaZQpk9iuxL16%2FosjuqEH2S7aXB16JjBIDGko%3D&reserved=0
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] What is the right SRC_URI syntax for g...@bitbucket.org?

[Erik Hoogeveen]

Hi,

This works for me. I've have setup ssh my identity for Bitbucket.

I use this in my recipes:

SRC_URI = "gitsm://g...@bitbucket.org//.git;protocol=ssh;branch=${BRANCH}"

Cheers,
Erik
On 21 Apr 2019, 02:58 +0200, JH , wrote:
Hi,

Could someone kindly clarify what is the syntax to access git source
from bitbucket.org? I tried following different patterns, nothing
works:

SRC_URI = "git://bitbucket.org//;protocol=http;branch=${BRANCH}"

SRC_URI = "git://@bitbucket.org//.git;protocol=ssh";branch=${BRANCH}"

Thank you.

Kind regards,

- jupiter
On 4/20/19, JH  wrote:
Hi,

Sorry for a new starter questions, I searched Internet, there are a
few examples to set up:

SRC_URI = "git://@bitbucket.org//.git;protocol=ssh";branch=${BRANCH}"

Not only that does not work, I have set up the public key to access
the git bitbucket repository:

$ ssh -v g...@bitbucket.org

The Yocto also complained SRCREV, following some blog to add the
SRCREV = "${AUTOREV}" that not work either.

Thank you.

Kind regards,

- jh

--
___
yocto mailing list
yocto@yoctoproject.org
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.yoctoproject.org%2Flistinfo%2Fyocto&data=02%7C01%7C%7C5e970c621c2e4a0f349108d6c5f47377%7C84df9e7fe9f640afb435%7C1%7C0%7C636914051024571809&sdata=Ck9czRr02QsCIpJKbRtJTmcOAgQMPg64v7km9%2FAv3Ik%3D&reserved=0
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] What is the right SRC_URI syntax for g...@bitbucket.org?

[Erik Hoogeveen]

What I have is:

SRCREV = "${AUTOREV}"
PE = "1"
PV = "0.0+git${SRCPV}"

To make that work your recipe file name must have the format 
'_git.bb’

Cheers,
Erik
On 23 Apr 2019, 13:44 +0200, JH , wrote:
Thanks Eric, how did you set up SRCREV? I've got an error need to set
a valid SRCREV.

Thank you.

Kind regards,

- jupiter


On 4/23/19, Erik Hoogeveen  wrote:
Hi,

This works for me. I've have setup ssh my identity for Bitbucket.

I use this in my recipes:

SRC_URI = "gitsm://g...@bitbucket.org//.git;protocol=ssh;branch=${BRANCH}"

Cheers,
Erik
On 21 Apr 2019, 02:58 +0200, JH , wrote:
Hi,

Could someone kindly clarify what is the syntax to access git source
from bitbucket.org? I tried following different patterns, nothing
works:

SRC_URI = "git://bitbucket.org//;protocol=http;branch=${BRANCH}"

SRC_URI = "git://@bitbucket.org//.git;protocol=ssh";branch=${BRANCH}"

Thank you.

Kind regards,

- jupiter
On 4/20/19, JH  wrote:
Hi,

Sorry for a new starter questions, I searched Internet, there are a
few examples to set up:

SRC_URI = "git://@bitbucket.org//.git;protocol=ssh";branch=${BRANCH}"

Not only that does not work, I have set up the public key to access
the git bitbucket repository:

$ ssh -v g...@bitbucket.org

The Yocto also complained SRCREV, following some blog to add the
SRCREV = "${AUTOREV}" that not work either.

Thank you.

Kind regards,

- jh

--
___
yocto mailing list
yocto@yoctoproject.org
https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.yoctoproject.org%2Flistinfo%2Fyocto&data=02%7C01%7C%7Cb470080556df4454d26708d6c7e0fb71%7C84df9e7fe9f640afb435%7C1%7C0%7C636916166431553475&sdata=eBsjVtD0FArltADAHD8brMjgIaqaalg5pbEIEFQeR8s%3D&reserved=0

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

Re: [yocto] libGL missing. Which packages bring it?

[Erik Hoogeveen]

Hi Mauro,

Have you tried searching the layer index?
https://layers.openembedded.org/

Cheers,
Erik
On 21 Aug 2019, 11:11 +0200, Mauro Ziliani , wrote:
Hi all

I try to compile kivy for Pyro and Python3 for framebuffer con RPi3.

The builder cannot find libGL and -lGL linker fails.

Which are the packages that give libGL?


Best regards

Mauro

--
___
yocto mailing list
yocto@yoctoproject.org
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.yoctoproject.org%2Flistinfo%2Fyocto&data=02%7C01%7C%7Cc559b878bb3e4a61e35908d7261787b0%7C84df9e7fe9f640afb435%7C1%7C0%7C637019754810083255&sdata=ggeG6LliIFYT53MEGDuc2LT%2FuxtGGCIAgpvskS76ro8%3D&reserved=0
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Alternative to _git.bb convention for unstable versions?

[Erik Hoogeveen]

Hello Keith,

I’m not sure if this is any good, I’m not all that experienced with Yocto.
But would it be an idea to add PREFERRED_VERSION ?= “1.0” in your layer.conf to 
provide your users with a sane default?

Cheers,
Erik
On 13 Sep 2019, 18:00 +0200, keith.derrick , wrote:
Thanks Martin.

I was trying to avoid everyone in my org having to add anything manually to 
their local.conf (we will be using the _git version) – and dealing with the 
“help me” emails whenever they forgot.

I was thinking that you would want one or the other, but I suppose if there’s a 
way to screw up, users will find it ☹

Eventually, we’ll switch our build to a custom DISTRO and the problem will go 
away. Just wish there was somewhere else the PREFERRED_VERSION statements could 
go.



From: Martin Jansa 
Date: Friday, September 13, 2019 at 8:35 AM
To: "Keith Derrick/LGEUS Advanced Platform(keith.derr...@lge.com)" 

Cc: "yocto@yoctoproject.org" 
Subject: Re: [yocto] Alternative to _git.bb convention for unstable versions?

You can easily add .inc file which will set all the PREFERRED_VERSIONs for all 
components you need and then the users will just add an "require" of this .inc 
files to their local.conf.

"somepackage-unstable.bb"
 or 
"somepackage-devel.bb"
 this will make it 2 different components - not 2 different versions of the 
same component - which makes this much more complicated, you'll need 
PREFERRED_PROVIDERs for every dependency and in the end you will need to make 
sure that whole build is using the same set of providers, because if

A depends on somepackage-unstable
B depends on A and somepackage-devel

then building B will fail in prepare-recipe-sysrooot, because A will pull 
somepackage-unstable which will probably conflict with somepackage-devel by 
providing the same files (in just different version). You can see how openssl10 
and openssl "worked" if you build didn't use the same one for all the recipes.

Cheers,

On Fri, Sep 13, 2019 at 5:27 PM keith.derrick 
mailto:keith.derr...@lge.com>> wrote:

I am currently creating a new layer (which will eventually be made generally 
available). I need to provide both a versioned recipe, and an "unstable"  one.



Currently I have 
somepackage_1.0.bb
 and 
somepackage_git.bb
 which are working fine.



However, using the "_git" approach (with DEFAULT_PREFERENCE = "-1") requires 
the use of PREFERRED_VERSION in either local.conf or a distro.conf. I've tried 
putting it in the image files, and that doesn't work.



If you are not creating your own DISTRO, and instead just adding the layer to a 
straight poky/meta build, you seem to be pretty much stuck with adding 3 
PREFERRED_VERSION statements (target, -native, and nativesdk- variants) to 
local.conf. I'd rather not require that of users of the layer.



I'm considering instead using either 
"somepackage-unstable.bb"
 or 
"somepackage-devel.bb"
 instead of 
"sompackage_git.bb".
 This allows a simple selection of either  RDEPENDS = "somepackage" or RDEPENDS 
= "somepackage-devel" to add the desired one to an image.



However, neither "-devel" or "-unstable" have the right feel