[yocto] [meta-raspberrypi] Cannot see /dev/ttyS0 on CM3+ with 4.19.66 yocto build.

[Bill Jenkins]

The 4.14.112 yocto builds that we have been using show both /dev/ttyS0 and 
/dev/ttyAMA0 
initialization strings in dmesg and both can be successfully used. After 
updating to the latest
to try out the 4.19.66 kernel, we see the initialization message for 
/dev/ttyAMA0 and can use
it, but there is no message for /dev/ttyS0 and we are unable to use that uart.

Is there anything that we need to change in our conf file or elsewhere when 
doing this update
in order to get both serial ports to work with the latest kernel?

Any help/info greatly appreciated!
~Bill
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi] No package 'wayland-egl' found

[Bill Jenkins]

Hi Andrei,

Thanks so much for confirming the issue.

> On May 15, 2018, at 4:18 AM, Andrei Gherzan <and...@gherzan.ro> wrote:
> 
> Hi,
> 
> On Tue, May 15, 2018 at 1:48 AM, Bill Jenkins <b...@korgrd.com 
> <mailto:b...@korgrd.com>> wrote:
> 
> > On May 14, 2018, at 2:43 PM, Bill Jenkins <b...@korgrd.com 
> > <mailto:b...@korgrd.com>> wrote:
> > 
> > Hi,
> > 
> > I just sync'd to the head of the master branch in the poky and 
> > meta-raspberrypi repos today 
> > and tried a build that successfully completed last week, but now fails with 
> > the error message
> > "No package 'wayland-egl' found" during the gtk+3_3.22.29.bb:do_configure 
> > task.
> > 
> > I see some recent commits in both branches related to egl movement between 
> > wayland
> > and userland. I made sure to be up-to-date in both repos. What could I be 
> > missing?
> > 
> 
> I found that by removing the do_install_append_rpi() from commit de8912cb, 
> the build
> finishes successfully. Is there something else that this commit is depending 
> on that I do
> not have?
> 
> 
> I can confirm this is an issue introduced by 
> https://github.com/agherzan/meta-raspberrypi/pull/247 
> <https://github.com/agherzan/meta-raspberrypi/pull/247> . We will be fixing 
> this soon but in the meanwhile could you create a new issue in github?

Done. It is entered as issue 259 in the meta-raspberry repo 
(https://github.com/agherzan/meta-raspberrypi/issues/259 
<https://github.com/agherzan/meta-raspberrypi/issues/259>).

Best regards,
Bill


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

Re: [yocto] [meta-raspberrypi] No package 'wayland-egl' found

[Bill Jenkins]

> On May 14, 2018, at 2:43 PM, Bill Jenkins <b...@korgrd.com> wrote:
> 
> Hi,
> 
> I just sync'd to the head of the master branch in the poky and 
> meta-raspberrypi repos today 
> and tried a build that successfully completed last week, but now fails with 
> the error message
> "No package 'wayland-egl' found" during the gtk+3_3.22.29.bb:do_configure 
> task.
> 
> I see some recent commits in both branches related to egl movement between 
> wayland
> and userland. I made sure to be up-to-date in both repos. What could I be 
> missing?
> 

I found that by removing the do_install_append_rpi() from commit de8912cb, the 
build
finishes successfully. Is there something else that this commit is depending on 
that I do
not have?

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

[yocto] [meta-raspberrypi] No package 'wayland-egl' found

[Bill Jenkins]

Hi,

I just sync'd to the head of the master branch in the poky and meta-raspberrypi 
repos today 
and tried a build that successfully completed last week, but now fails with the 
error message
"No package 'wayland-egl' found" during the gtk+3_3.22.29.bb:do_configure task.

I see some recent commits in both branches related to egl movement between 
wayland
and userland. I made sure to be up-to-date in both repos. What could I be 
missing?

I'm running the command "bitbake core-image-minimal -c populate_sdk"  and the 
relevant 
lines in local.conf are:

MACHINE ??= "raspberrypi3-64"

IMAGE_INSTALL_append = " apt gdbserver openssh-sftp-server mdns-dev 
perfcnt-enable libasound alsa-utils-alsactl alsa-utils-alsamixer 
${VIRTUAL-RUNTIME_alsa-state} libjack jack-server jack-utils"

CORE_IMAGE_EXTRA_INSTALL += " avahi-daemon"

TOOLCHAIN_HOST_TASK_append = " nativesdk-cmake"

EXTRA_IMAGE_FEATURES ?= "debug-tweaks x11-base tools-debug splash 
ssh-server-dropbear package-management"


Everything else is pretty much the default. I've also tried it without the 
populate_sdk command 
with the same result.

Any advice is greatly appreciated.

Thanks
Bill

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

Re: [yocto] [meta-raspberry-pi] needing newer or patched version of g++

[Bill Jenkins]

> On Sep 15, 2017, at 7:43 AM, Khem Raj <raj.k...@gmail.com> wrote:
> 
> On Fri, Sep 15, 2017 at 7:35 AM, Bill Jenkins <b...@korgrd.com> wrote:
>> 
>>> On Sep 15, 2017, at 6:54 AM, Khem Raj <raj.k...@gmail.com> wrote:
>>> 
>>> On Thu, Sep 14, 2017 at 10:14 PM, Bill Jenkins <b...@korgrd.com> wrote:
>>>> After creating an SDK for a 32-bit Raspberry Pi3 target, I ran into the 
>>>> following compiler error when
>>>> compiling an application using the SDK:
>>>> 
>>>> internal compiler error: Max. number of generated reload insns per insn is 
>>>> achieved (90)
>>>> 
>>>> It turns out that a patch was submitted for g++ early last year for the 
>>>> above problem,
>>> 
>>> We need to backport the patch to 6.3.0 and regenerate SDK. If you can
>>> point to patch that will be helpful.
>> 
>> Thanks Khem, here's a link to the commit:
>> 
>> https://github.com/gcc-mirror/gcc/commit/4fe01ba94e99e792ebe9da2ccb3b071aa1bac388#diff-af18d9175d034b2b3726f1ddc05fae55
>> 
> 
> OK and which release are you on ?

I've been building in the pyro branch. DISTRO_VERSION reports 2.3.2.

> 
>>> but apparently that
>>>> patch is not in the 6.3.0 version within the SDK. When I try to specify a 
>>>> newer version,
>>>> (by using PREFERRED_VERSION_gcc-cross-${TARGET_ARCH}) bitbake reports that 
>>>> only 5.4.0 or 6.3.0
>>>> are available. Any suggestions on how to resolve this? (i.e. is there some 
>>>> way to use a newer g++ or to
>>>> apply the patch?)
>>>> 
>>>> Thanks,
>>>> Bill
>>>> --
>>>> ___
>>>> yocto mailing list
>>>> yocto@yoctoproject.org
>>>> https://lists.yoctoproject.org/listinfo/yocto
>> 

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

Re: [yocto] [meta-raspberry-pi] needing newer or patched version of g++

[Bill Jenkins]

> On Sep 15, 2017, at 6:54 AM, Khem Raj <raj.k...@gmail.com> wrote:
> 
> On Thu, Sep 14, 2017 at 10:14 PM, Bill Jenkins <b...@korgrd.com> wrote:
>> After creating an SDK for a 32-bit Raspberry Pi3 target, I ran into the 
>> following compiler error when
>> compiling an application using the SDK:
>> 
>> internal compiler error: Max. number of generated reload insns per insn is 
>> achieved (90)
>> 
>> It turns out that a patch was submitted for g++ early last year for the 
>> above problem,
> 
> We need to backport the patch to 6.3.0 and regenerate SDK. If you can
> point to patch that will be helpful.

Thanks Khem, here's a link to the commit:

https://github.com/gcc-mirror/gcc/commit/4fe01ba94e99e792ebe9da2ccb3b071aa1bac388#diff-af18d9175d034b2b3726f1ddc05fae55

> 
> but apparently that
>> patch is not in the 6.3.0 version within the SDK. When I try to specify a 
>> newer version,
>> (by using PREFERRED_VERSION_gcc-cross-${TARGET_ARCH}) bitbake reports that 
>> only 5.4.0 or 6.3.0
>> are available. Any suggestions on how to resolve this? (i.e. is there some 
>> way to use a newer g++ or to
>> apply the patch?)
>> 
>> Thanks,
>> Bill
>> --
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto

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

[yocto] [meta-raspberry-pi] needing newer or patched version of g++

[Bill Jenkins]

After creating an SDK for a 32-bit Raspberry Pi3 target, I ran into the 
following compiler error when
compiling an application using the SDK:

internal compiler error: Max. number of generated reload insns per insn is 
achieved (90)

It turns out that a patch was submitted for g++ early last year for the above 
problem, but apparently that
patch is not in the 6.3.0 version within the SDK. When I try to specify a newer 
version, 
(by using PREFERRED_VERSION_gcc-cross-${TARGET_ARCH}) bitbake reports that only 
5.4.0 or 6.3.0 
are available. Any suggestions on how to resolve this? (i.e. is there some way 
to use a newer g++ or to 
apply the patch?)

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

Re: [yocto] raspberrypi3-64 target not booting

[Bill Jenkins]

> On Aug 26, 2017, at 12:36 AM, Herve Jourdain  wrote:
> 
> Hi,
> 
> Are you using vc4 as graphics, or are you using the default userland?
> If you want graphics with 64 bits, you need to use vc4.
> 

The raspberrypi3-64.conf file has the line:

MACHINE_FEATURES_append = " vc4graphics"

I assume this means it is using vc4? There is no use of "userland" in my 
build/conf
directory. I am fairly new to Yocto, so I am wondering if there is a definitive 
way to 
tell whether the vc4 graphics were used to build the image.

>> Any ideas on how to get the HDMI port to function the same way as it 
>> does for the 32-bit case?
>> 
> 
> Readding the mailing list.
> 
> what you have is exactly what I had when I submitted the port to
> meta-raspberrypi. Haven;t had a chance to revisit it. but this could
> be related to device tree files we are using here. I have had reports
> from other devs of having been able to boot into graphics using older
> kernels but I never got
> that far myself.
> -- 
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
> 

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

[yocto] raspberrypi3-64 target not booting

[Bill Jenkins]

I am trying to just get the simple 64-bit rpi-basic-image to work, but the
Raspberry Pi 3 seems to hang with the rainbow screen at startup.

If I build with MACHINE ?= raspberrypi3, the 32-bit image works just fine.

Is there something special that needs to be set in order for the
"MACHINE ?= raspberrypi3-64" image to boot successfully? 

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