Re: [yocto] [meta-raspberrypi][PATCH] wic: add swap partition and set /root and /swap size

Hi, On 14/11/2019 11:11, Paul Barker wrote: On Thu, 14 Nov 2019, at 06:04, Hongxu Jia wrote: - Add swap partition to workaround memory limitation - Support to set /root and /swap size, 4G /root and 1G /swap by default Signed-off-by: Hongxu Jia These settings feel distro-specific to me. The

Re: [yocto] [meta-raspberrypi][PATCH V3] wic: support to set /root size and add extra partition

On 11/14/19 8:40 PM, Paul Barker wrote: On Thu, 14 Nov 2019, at 07:33, Hongxu Jia wrote: - Support to add extra partition, such as add swap partition to workaround memory limitation - Support to set /root size Signed-off-by: Hongxu Jia If you want to make changes like this in a distro or

Re: [yocto] [meta-raspberrypi][PATCH V3] wic: support to set /root size and add extra partition

On Thu, 14 Nov 2019, at 07:33, Hongxu Jia wrote: > - Support to add extra partition, such as add swap partition > to workaround memory limitation > > - Support to set /root size > > Signed-off-by: Hongxu Jia If you want to make changes like this in a distro or local configuration, I think it

Re: [yocto] [meta-raspberrypi][PATCH] wic: add swap partition and set /root and /swap size

On Thu, 14 Nov 2019, at 06:04, Hongxu Jia wrote: > - Add swap partition to workaround memory limitation > > - Support to set /root and /swap size, 4G /root and 1G /swap by default > > Signed-off-by: Hongxu Jia These settings feel distro-specific to me. They're not required for how many of us u

[yocto] [meta-raspberrypi][PATCH V3] wic: support to set /root size and add extra partition

- Support to add extra partition, such as add swap partition to workaround memory limitation - Support to set /root size Signed-off-by: Hongxu Jia --- conf/machine/include/rpi-base.inc | 11 ++- ...age-raspberrypi.wks => sdimage-raspberrypi.wks.in} | 3 ++- 2 file

[yocto] [meta-raspberrypi][PATCH V2] wic: support to set /root size and add extra partition

- Support to add extra partition, such as add swap partition to workaround memory limitation - Support to set /root size Signed-off-by: Hongxu Jia --- conf/machine/include/rpi-base.inc | 11 ++- ...age-raspberrypi.wks => sdimage-raspberrypi.wks.in} | 3 ++- 2 file

Re: [yocto] [meta-raspberrypi][PATCH] wic: add swap partition and set /root and /swap size

On 11/14/19 2:30 PM, Khem Raj wrote: On Thu, 2019-11-14 at 06:04 +, Hongxu Jia wrote: - Add swap partition to workaround memory limitation - Support to set /root and /swap size, 4G /root and 1G /swap by default Signed-off-by: Hongxu Jia --- conf/machine/include/rpi-base.inc

Re: [yocto] [meta-raspberrypi][PATCH] wic: add swap partition and set /root and /swap size

On Thu, 2019-11-14 at 06:04 +, Hongxu Jia wrote: > - Add swap partition to workaround memory limitation > > - Support to set /root and /swap size, 4G /root and 1G /swap by > default > > Signed-off-by: Hongxu Jia > --- > conf/machine/include/rpi-base.inc | 5 > -

[yocto] [meta-raspberrypi][PATCH] wic: add swap partition and set /root and /swap size

- Add swap partition to workaround memory limitation - Support to set /root and /swap size, 4G /root and 1G /swap by default Signed-off-by: Hongxu Jia --- conf/machine/include/rpi-base.inc | 5 - wic/{sdimage-raspberrypi.wks => sdimage-raspberrypi.wks.in} | 3 ++-

Re: [yocto] [meta-raspberrypi] poky linux build fails if ARM erratum mfix linker switch is specified

On Thu, Nov 7, 2019 at 10:42 AM Steve Pavao wrote: > > On Nov 4, 2019, at 4:26 PM, Steve Pavao wrote: > > > >> On Nov 4, 2019, at 11:32 AM, Steve Pavao wrote: > >>> > >>> On Nov 4, 2019, at 11:16 AM, Steve Pavao wrote: > > On Nov 4, 2019, at 11:11 AM, Adrian Bunk wrote: > > >>>

Re: [yocto] [meta-raspberrypi] poky linux build fails if ARM erratum mfix linker switch is specified

> On Nov 4, 2019, at 4:26 PM, Steve Pavao wrote: > >> On Nov 4, 2019, at 11:32 AM, Steve Pavao wrote: >>> >>> On Nov 4, 2019, at 11:16 AM, Steve Pavao wrote: On Nov 4, 2019, at 11:11 AM, Adrian Bunk wrote: On Mon, Nov 04, 2019 at 10:48:57AM -0500, Steve Pavao wrote:

Re: [yocto] [meta-raspberrypi] poky linux build fails if ARM erratum mfix linker switch is specified

> On Nov 4, 2019, at 11:32 AM, Steve Pavao wrote: > >> >> On Nov 4, 2019, at 11:16 AM, Steve Pavao > > wrote: >> >>> >>> On Nov 4, 2019, at 11:11 AM, Adrian Bunk >> > wrote: >>> >>> On Mon, Nov 04, 2019 at 10:48:57AM -0500, Steve Pavao wrote:

Re: [yocto] [meta-raspberrypi] poky linux build fails if ARM erratum mfix linker switch is specified

> On Nov 4, 2019, at 11:16 AM, Steve Pavao wrote: > >> >> On Nov 4, 2019, at 11:11 AM, Adrian Bunk > > wrote: >> >> On Mon, Nov 04, 2019 at 10:48:57AM -0500, Steve Pavao wrote: >>> On Nov 3, 2019, at 1:25 PM, Adrian Bunk >>> > wrote: >>

Re: [yocto] [meta-raspberrypi] poky linux build fails if ARM erratum mfix linker switch is specified

> On Nov 4, 2019, at 11:11 AM, Adrian Bunk wrote: > > On Mon, Nov 04, 2019 at 10:48:57AM -0500, Steve Pavao wrote: >> >>> On Nov 3, 2019, at 1:25 PM, Adrian Bunk wrote: >>> >>> On Sun, Nov 03, 2019 at 05:56:45PM +, Andrei Gherzan wrote: On 3 November 2019 13:18:53 GMT, Khem Raj wrot

Re: [yocto] [meta-raspberrypi] poky linux build fails if ARM erratum mfix linker switch is specified

On Mon, Nov 04, 2019 at 10:48:57AM -0500, Steve Pavao wrote: > > > On Nov 3, 2019, at 1:25 PM, Adrian Bunk wrote: > > > > On Sun, Nov 03, 2019 at 05:56:45PM +, Andrei Gherzan wrote: > >> On 3 November 2019 13:18:53 GMT, Khem Raj wrote: > >>> On Sun, Nov 3, 2019 at 2:46 AM Andrei Gherzan >

Re: [yocto] [meta-raspberrypi] poky linux build fails if ARM erratum mfix linker switch is specified

> On Nov 3, 2019, at 1:25 PM, Adrian Bunk wrote: > > On Sun, Nov 03, 2019 at 05:56:45PM +, Andrei Gherzan wrote: >> On 3 November 2019 13:18:53 GMT, Khem Raj wrote: >>> On Sun, Nov 3, 2019 at 2:46 AM Andrei Gherzan >>> wrote: I was thinking about this. The erratum seems to show that t

Re: [yocto] [meta-raspberrypi] poky linux build fails if ARM erratum mfix linker switch is specified

On Sun, Nov 03, 2019 at 05:56:45PM +, Andrei Gherzan wrote: > On 3 November 2019 13:18:53 GMT, Khem Raj wrote: > >On Sun, Nov 3, 2019 at 2:46 AM Andrei Gherzan > >wrote: > >> I was thinking about this. The erratum seems to show that this > >applies > >> to all revisions of a53. So it sounds l

Re: [yocto] [meta-raspberrypi] poky linux build fails if ARM erratum mfix linker switch is specified

On Sun, Nov 3, 2019 at 9:56 AM Andrei Gherzan wrote: > > > On 3 November 2019 13:18:53 GMT, Khem Raj wrote: > >On Sun, Nov 3, 2019 at 2:46 AM Andrei Gherzan > >wrote: > > > >> On 01/11/2019 17:18, Khem Raj wrote: > >> > On Fri, Nov 1, 2019 at 1:28 AM Andrei Gherzan > >wrote: > >> >> > >> >> Hi

Re: [yocto] [meta-raspberrypi] poky linux build fails if ARM erratum mfix linker switch is specified

On 3 November 2019 13:18:53 GMT, Khem Raj wrote: >On Sun, Nov 3, 2019 at 2:46 AM Andrei Gherzan >wrote: > >> On 01/11/2019 17:18, Khem Raj wrote: >> > On Fri, Nov 1, 2019 at 1:28 AM Andrei Gherzan >wrote: >> >> >> >> Hi Steve, >> >> >> >> On 01/11/2019 05:32, Steve Pavao wrote: >> >>> poky lin

Re: [yocto] [meta-raspberrypi] poky linux build fails if ARM erratum mfix linker switch is specified

On Sun, Nov 3, 2019 at 2:46 AM Andrei Gherzan wrote: > On 01/11/2019 17:18, Khem Raj wrote: > > On Fri, Nov 1, 2019 at 1:28 AM Andrei Gherzan wrote: > >> > >> Hi Steve, > >> > >> On 01/11/2019 05:32, Steve Pavao wrote: > >>> poky linux build fails when ARM erratum mfix linker switch is specified

Re: [yocto] [meta-raspberrypi] poky linux build fails if ARM erratum mfix linker switch is specified

On 01/11/2019 17:18, Khem Raj wrote: On Fri, Nov 1, 2019 at 1:28 AM Andrei Gherzan wrote: Hi Steve, On 01/11/2019 05:32, Steve Pavao wrote: poky linux build fails when ARM erratum mfix linker switch is specified in local.conf: TARGET_LD_ARCH_append += " -mfix-cortex-a53-843419” causes buil

Re: [yocto] [meta-raspberrypi] poky linux build fails if ARM erratum mfix linker switch is specified

On Fri, Nov 1, 2019 at 1:28 AM Andrei Gherzan wrote: > > Hi Steve, > > On 01/11/2019 05:32, Steve Pavao wrote: > > poky linux build fails when ARM erratum mfix linker switch is specified > > in local.conf: > > > > TARGET_LD_ARCH_append += " -mfix-cortex-a53-843419” > > > > causes build failure. >

Re: [yocto] [meta-raspberrypi] poky linux build fails if ARM erratum mfix linker switch is specified

Hi Steve, On 01/11/2019 05:32, Steve Pavao wrote: poky linux build fails when ARM erratum mfix linker switch is specified in local.conf: TARGET_LD_ARCH_append += " -mfix-cortex-a53-843419” causes build failure. Please advise how to use this switch successfully.  I am synced current in maste

[yocto] [meta-raspberrypi] poky linux build fails if ARM erratum mfix linker switch is specified

poky linux build fails when ARM erratum mfix linker switch is specified in local.conf: TARGET_LD_ARCH_append += " -mfix-cortex-a53-843419” causes build failure. Please advise how to use this switch successfully. I am synced current in master branch in all layers as of today. The switch cause

Re: [yocto] [meta-raspberrypi][ostree] build errors

On Thu, Sep 12, 2019 at 12:17 AM Greg Wilson-Lindberg wrote: > > I'm trying to include ostree into a raspberry pi boot2qt build based on thud. > > I'm getting a warning: > WARNING: linux-raspberrypi-1_4.14.112+gitAUTOINC+6b5c4a2508-r0 > do_kernel_metadata: defconfig detected in WORKDIR. bcm2709_d

[yocto] [meta-raspberrypi][ostree] build errors

I'm trying to include ostree into a raspberry pi boot2qt build based on thud. I'm getting a warning: WARNING: linux-raspberrypi-1_4.14.112+gitAUTOINC+6b5c4a2508-r0 do_kernel_metadata: defconfig detected in WORKDIR. bcm2709_defconfig skipped Which I figure that I can probably ignore, but may find

Re: [yocto] [meta-raspberrypi] Confusion about U-Boot setup

ptember 04, 2019 12:44 PM > > To: Greg Wilson-Lindberg > > Cc: Belisko Marek ; Yocto list discussion > > > > Subject: Re: [yocto] [meta-raspberrypi] Confusion about U-Boot setup > > > > > There should be some way to change the u-boot delay that waits for &

Re: [yocto] [meta-raspberrypi] Confusion about U-Boot setup

> From: Belisko Marek > > BR, A two-letter answer is too cryptic. He's not just asking what the variable name is, he's asking where the file is that contains the variable. -- Ciao, Paul D. DeRocco Paulmailto:pdero...@ix.netcom.com --

Re: [yocto] [meta-raspberrypi] Confusion about U-Boot setup

> -Original Message- > From: Zoran Stojsavljevic [mailto:zoran.stojsavlje...@gmail.com] > Sent: Wednesday, September 04, 2019 12:44 PM > To: Greg Wilson-Lindberg > Cc: Belisko Marek ; Yocto list discussion > > Subject: Re: [yocto] [meta-raspberrypi] Confusi

Re: [yocto] [meta-raspberrypi] Confusion about U-Boot setup

om] > > Sent: Wednesday, September 04, 2019 12:26 AM > > To: Greg Wilson-Lindberg > > Cc: Yocto list discussion > > Subject: Re: [yocto] [meta-raspberrypi] Confusion about U-Boot setup > > > > Hi, > > > > On Tue, Sep 3, 2019 at 8:58 PM Greg Wilson-Lin

Re: [yocto] [meta-raspberrypi] Confusion about U-Boot setup

Hi, On Wed, Sep 4, 2019 at 6:56 PM Greg Wilson-Lindberg wrote: > > > -Original Message- > > From: Belisko Marek [mailto:marek.beli...@gmail.com] > > Sent: Wednesday, September 04, 2019 12:26 AM > > To: Greg Wilson-Lindberg > > Cc: Yocto list discussio

Re: [yocto] [meta-raspberrypi] Confusion about U-Boot setup

> -Original Message- > From: Belisko Marek [mailto:marek.beli...@gmail.com] > Sent: Wednesday, September 04, 2019 12:26 AM > To: Greg Wilson-Lindberg > Cc: Yocto list discussion > Subject: Re: [yocto] [meta-raspberrypi] Confusion about U-Boot setup > > Hi, >

Re: [yocto] [meta-raspberrypi] Confusion about U-Boot setup

Hi, On Tue, Sep 3, 2019 at 8:58 PM Greg Wilson-Lindberg wrote: > > I've configured a sumo build, by way of QT's boot2qt to use u-boot and I am > seeing a u-boot prompt for keypress to drop out of automatic booting on > startup, but I don't see any configuration scripts for u-boot (uEnv.txt or a

[yocto] [meta-raspberrypi] Confusion about U-Boot setup

I've configured a sumo build, by way of QT's boot2qt to use u-boot and I am seeing a u-boot prompt for keypress to drop out of automatic booting on startup, but I don't see any configuration scripts for u-boot (uEnv.txt or a script) on the image or in the build tmp/ dir. For the raspberry pi, h

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

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

Re: [yocto] [meta-raspberrypi] Error trying to generate Raspberry Pi initramfs

Hello Greg, This, what I have posted as answer work for me on BBB (BeagleBone Black) seamlessly. I did not try it on Sabre Automotive, but as we speak, I just straightened out the optimal local.conf for it (with very rich networking services on the top of Linux), and I am 100% sure the above init

Re: [yocto] [meta-raspberrypi] Error trying to generate Raspberry Pi initramfs

Hi Zoran, Thanks for your comments. I'm adding [meta-raspberrypi] to the as I have realized that some might have missed this Raspberry-pi specific question. Thanks, Greg Wilson-Lindberg  > -Original Message- > From: Zoran Stojsavljevic [mailto:zoran.stojsavlje...@gmail.com] > Sent: W

Re: [yocto] [meta-raspberrypi] Issues building bcm2835_bootfiles in Thud

Hello, On 14/08/2019 17.39, Phillip Marks wrote: > We are building Thud for a raspberry-pi0+wifi and we've noticed that > the recipe bcm2835_bootfiles > under meta-raspberrypi/recipes-bsp/bootfiles is not pulling in the > proprietary *.dtb modules from the firmware repository. This is > causing li

[yocto] [meta-raspberrypi] Issues building bcm2835_bootfiles in Thud

We are building Thud for a raspberry-pi0+wifi and we've noticed that the recipe bcm2835_bootfiles under meta-raspberrypi/recipes-bsp/bootfiles is not pulling in the proprietary *.dtb modules from the firmware repository. This is causing linux-raspberrypi to fail as it tries to build those modules a

Re: [yocto] Meta-raspberrypi

Hi Shravan, You need to checkout warrior from your meta-raspberrypi repo that you cloned. It looks as it is on the latest master. :rjs On 7/22/19 3:07 PM, Shravan Singh wrote: > Hello All, > > I am trying to create a base image for raspberry-pi cm3(compute module 3) > > I am using warrior-21.0.1

Re: [yocto] Meta-raspberrypi

On Mon, Jul 29, 2019 at 2:15 AM Shravan Singh wrote: > > Hello All, > > I am trying to create a base image for raspberry-pi cm3(compute module 3) > > I am using warrior-21.0.1 > I downloaded meta-raspberry-pi from > https://git.yoctoproject.org/git/meta-raspberrypi > I added the layer in bblayer

[yocto] Meta-raspberrypi

Hello All, I am trying to create a base image for raspberry-pi cm3(compute module 3) I am using warrior-21.0.1 I downloaded meta-raspberry-pi from https://git.yoctoproject.org/git/meta-raspberrypi I added the layer in bblayer.conf and I have changed the machine variable in local.conf to *raspberr

Re: [yocto] [meta-raspberrypi] RPi 7" Touch Display

Khem, Yes, the 32-bit image (raspberrypi3 machine) works. :rjs On 5/19/19 9:11 AM, Khem Raj wrote: On Sat, May 18, 2019 at 11:02 PM Rudolf Streif mailto:rudolf.str...@ibeeto.com>> wrote: Thanks, Khem. 64 bit, raspberrypi3-64 machine with vc4graphics. Please try 32bit we only have hd

Re: [yocto] [meta-raspberrypi] RPi 7" Touch Display

I tried to build for 32 bit with: Build Configuration: BB_VERSION   = "1.43.0" BUILD_SYS    = "x86_64-linux" NATIVELSBSTRING  = "universal" TARGET_SYS   = "arm-poky-linux-gnueabi" MACHINE  = "raspberrypi3" DISTRO   = "poky" DISTRO_VERSION  

Re: [yocto] [meta-raspberrypi] RPi 7" Touch Display

On Sat, May 18, 2019 at 11:02 PM Rudolf Streif wrote: > Thanks, Khem. 64 bit, raspberrypi3-64 machine with vc4graphics. > Please try 32bit we only have hdmi tested in 64bit this far > > On Sat, May 18, 2019, 22:13 Khem Raj wrote: > >> >> >> On 5/16/19 9:01 AM, Andrei Gherzan wrote: >> > HI, >

Re: [yocto] [meta-raspberrypi] RPi 7" Touch Display

Thanks, Khem. 64 bit, raspberrypi3-64 machine with vc4graphics. On Sat, May 18, 2019, 22:13 Khem Raj wrote: > > > On 5/16/19 9:01 AM, Andrei Gherzan wrote: > > HI, > > > > On 16/05/2019 16.31, Rudolf J Streif wrote: > >> I am trying to use the "official" RPi 7" touch display > >> (https://www.ra

Re: [yocto] [meta-raspberrypi] RPi 7" Touch Display

On 5/16/19 9:01 AM, Andrei Gherzan wrote: HI, On 16/05/2019 16.31, Rudolf J Streif wrote: I am trying to use the "official" RPi 7" touch display (https://www.raspberrypi.org/products/raspberry-pi-touch-display/) with meta-raspberrypi (most recent from master). However, I cannot get it to wor

Re: [yocto] [meta-raspberrypi] RPi 7" Touch Display

I don't know if it's helpful, but I'm struggling with a similar issue on my RPi 3 B+, where the official touchscreen, as well as, the HDMI don't output any graphics, although detected correctly. (See: https://lists.yoctoproject.org/pipermail/yocto/2019-May/045277.html) After experimenting with sumo

Re: [yocto] [meta-raspberrypi] RPi 7" Touch Display

No, unfortunately not. HDMI works just fine but no video on the touch display. On 5/16/19 9:46 AM, Andrei Gherzan wrote: Hi, On 16/05/2019 17.24, Rudolf J Streif wrote: Thank you, Paul. I did read Andrei's excellent documentation and enabled I2C and SPI etc. And it didn't work? -- - Ru

Re: [yocto] [meta-raspberrypi] RPi 7" Touch Display

Hi, On 16/05/2019 17.24, Rudolf J Streif wrote: > Thank you, Paul. I did read Andrei's excellent documentation and > enabled I2C and SPI etc. And it didn't work? -- Andrei Gherzan gpg: rsa4096/D4D94F67AD0E9640 | t: @agherzan -- ___ yocto mailing list

Re: [yocto] [meta-raspberrypi] RPi 7" Touch Display

Thank you, Paul. I did read Andrei's excellent documentation and enabled I2C and SPI etc. :rjs On 5/16/19 8:39 AM, Paul Barker wrote: On Thu, 16 May 2019, at 16:33, Rudolf J Streif wrote: I am trying to use the "official" RPi 7" touch display (https://www.raspberrypi.org/products/raspberry-pi

Re: [yocto] [meta-raspberrypi] RPi 7" Touch Display

Thank you, Andrei. Much appreciated. https://pastebin.com/bHUHaRkL It's the config.txt that is packaged with the image. :rjs On 5/16/19 9:01 AM, Andrei Gherzan wrote: HI, On 16/05/2019 16.31, Rudolf J Streif wrote: I am trying to use the "official" RPi 7" touch display (https://www.raspberr

Re: [yocto] [meta-raspberrypi] RPi 7" Touch Display

HI, On 16/05/2019 16.31, Rudolf J Streif wrote: > I am trying to use the "official" RPi 7" touch display > (https://www.raspberrypi.org/products/raspberry-pi-touch-display/) > with meta-raspberrypi (most recent from master). However, I cannot get > it to work. As a matter of fact the display does

Re: [yocto] [meta-raspberrypi] RPi 7" Touch Display

On Thu, 16 May 2019, at 16:33, Rudolf J Streif wrote: > I am trying to use the "official" RPi 7" touch display > (https://www.raspberrypi.org/products/raspberry-pi-touch-display/) with > meta-raspberrypi (most recent from master). However, I cannot get it to > work. As a matter of fact the displ

[yocto] [meta-raspberrypi] RPi 7" Touch Display

I am trying to use the "official" RPi 7" touch display (https://www.raspberrypi.org/products/raspberry-pi-touch-display/) with meta-raspberrypi (most recent from master). However, I cannot get it to work. As a matter of fact the display does not even show the GPU rainbow screen making me think

[yocto] [meta-raspberrypi] Screen(s) remain black on Raspberry Pi 3 B+

Hi! I'm facing some trouble with the X-Server on the Raspberry Pi 3 B+. No matter if I use a screen on the HDMI port or running the 7" touch screen, they remain black. After testing with sumo - where at least a splash screen was shown - I moved on to thud, as recommended by Andrei Gherzan to sort

Re: [yocto] [meta-raspberrypi] Rainbow screen with Raspberry Pi 3 A+ but not on B+

Hi Markus, On Fri, Feb 1, 2019 at 2:54 PM Markus W wrote: > Thanks Marek! > > I pretty sure it doesn't boot, but I haven't confirmed it as you suggested > it. > > I have never connected to the uart interface directly on the GPIO or via > bluetooth. It probably takes me more time to figure it out

Re: [yocto] [meta-raspberrypi] Rainbow screen with Raspberry Pi 3 A+ but not on B+

Thanks Marek! I pretty sure it doesn't boot, but I haven't confirmed it as you suggested it. I have never connected to the uart interface directly on the GPIO or via bluetooth. It probably takes me more time to figure it out and to do this than trying the thud branch as @agherzan has mentioned he

Re: [yocto] [meta-raspberrypi] Rainbow screen with Raspberry Pi 3 A+ but not on B+

On Fri, Feb 1, 2019 at 1:11 PM Markus W wrote: > Hi! > > I have been running a yocto image (sumo) on a raspberry 3 B+ without any > problems, but wanted to test the new raspberry Pi 3 A+ board with it but I > just get the Rainbow screen on boot. I have updated meta-openembedded to > the latest su

[yocto] [meta-raspberrypi] Rainbow screen with Raspberry Pi 3 A+ but not on B+

Hi! I have been running a yocto image (sumo) on a raspberry 3 B+ without any problems, but wanted to test the new raspberry Pi 3 A+ board with it but I just get the Rainbow screen on boot. I have updated meta-openembedded to the latest sumo and meta-raspberry was still up to date with the latest (

[yocto] [meta-raspberrypi] change kernel version from recipe

Hi, which is the right way to change the Kernel version to build when using meta-raspberrypi ? For example I want to change from 4.14.39 to 4.14.52, without changing anything else in the meta-raspberrypi layer. is it possible ? Is it just to define "LINUX_VERSION" in the local.conf file ? Should

Re: [yocto] [meta-raspberrypi][PATCH] CAN: Add Pican2 support

Hi Fabien, On Fri, Nov 16, 2018 at 5:29 PM Fabien Lahoudere < fabien.lahoud...@collabora.com> wrote: > In order to make Pican 2 work, we : > - add mcp2515.dto to the overlay list > - add a variable to enable it in local.conf > - create a udev rule to mount interface > > > http://skpang.co.uk/cat

[yocto] [meta-raspberrypi][PATCH] CAN: Add Pican2 support

In order to make Pican 2 work, we : - add mcp2515.dto to the overlay list - add a variable to enable it in local.conf - create a udev rule to mount interface http://skpang.co.uk/catalog/pican2-canbus-board-for-raspberry-pi-23-p-1475.html Signed-off-by: Fabien Lahoudere --- docs/extra-build-conf

[yocto] [meta-raspberrypi]

Hi! I want to append the rules in the recipe-core/udev/udev-rules-rpi/99-com.rules with the rules below from within my own recipe. I can´t figure out how to do that. I have tried to add those rules as separate rules file in a recipe in my own layer. After the build I can see that the rules file i

Re: [yocto] [meta-raspberrypi] Problem enabling w1-gpio

Hi again! I should have mentioned that the image will also include a meta-mender layer for updates. Additionally an extra layer for setting up the wifi & ble for rpi and an application layer. So I am looking for an automated approach where I can make production updates through mender. I also have

Re: [yocto] [meta-raspberrypi] Problem enabling w1-gpio

On Fri, Oct 5, 2018 at 9:27 AM Andrei Gherzan wrote: > > Hi Markus, > > On Fri, Oct 5, 2018 at 4:28 PM Markus W wrote: >> >> Hi! >> >> I'm creating a yocto image (sumo) for the raspberrypi and got stuck on how >> to enable the one-wire interface on boot. >> >> I have enabled the SPI bus and I2C

Re: [yocto] [meta-raspberrypi] Problem enabling w1-gpio

Hi Markus, On Fri, Oct 5, 2018 at 4:28 PM Markus W wrote: > Hi! > > I'm creating a yocto image (sumo) for the raspberrypi and got stuck on how > to enable the one-wire interface on boot. > > I have enabled the SPI bus and I2C in my local.conf file. > > ENABLE_SPI_BUS = "1" > ENABLE_I2C = "1" > >

[yocto] [meta-raspberrypi] Problem enabling w1-gpio

Hi! I'm creating a yocto image (sumo) for the raspberrypi and got stuck on how to enable the one-wire interface on boot. I have enabled the SPI bus and I2C in my local.conf file. ENABLE_SPI_BUS = "1" ENABLE_I2C = "1" and checked that they are loaded on boot. I'm struggling to figure out where

[yocto] [meta-raspberrypi] issue booting image containing alternate kernel

Hello, Sometimes, I need to build an image containing the raspberrypi / linux kernel as specified by the meta-raspberrypi layer recipes. Other times, I need to build an image containing the ipipe-arm64 kernel instead. This alternate kernel builds fine outside of Yocto and boots, so it should

[yocto] [meta-raspberrypi] Id "s0" respawning too fast on Raspberry pi3

Hello Everyone, I build a rpi-hwup-image and run it on my raspberry pi3(Model B V1.2). After the system boots up, I keep seeing such message: INIT: Id "S0" respawning too fast: disabled for 5 minutes. I notice that yocto adds the following line to /etc/inittab when install sysvinit,

Re: [yocto] [meta-raspberrypi] core-image-minimal for raspberrypi3-64 manifest/sdimg contains no kernel modules

On Wed, Aug 15, 2018 at 1:42 PM Steve Pavao wrote: > > Hello, > > > On Aug 15, 2018, at 4:27 PM, Khem Raj wrote: > > > > On Wed, Aug 15, 2018 at 1:25 PM Steve Pavao wrote: > > >> I would like to state my opinion though that to unconditionally warn the > >> user to use core-image-minimal instead

Re: [yocto] [meta-raspberrypi] core-image-minimal for raspberrypi3-64 manifest/sdimg contains no kernel modules

Hello, > On Aug 15, 2018, at 4:27 PM, Khem Raj wrote: > > On Wed, Aug 15, 2018 at 1:25 PM Steve Pavao wrote: >> I would like to state my opinion though that to unconditionally warn the >> user to use core-image-minimal instead of rpi-hwup-image (which definitely >> packages kernel modules i

Re: [yocto] [meta-raspberrypi] core-image-minimal for raspberrypi3-64 manifest/sdimg contains no kernel modules

On Wed, Aug 15, 2018 at 1:25 PM Steve Pavao wrote: > > Hello, > > On Aug 15, 2018, at 11:54 AM, Khem Raj wrote: > > On Tue, Aug 14, 2018 at 11:48 PM Steve Pavao wrote: > > > There seems to be a problem with the core-image-minimal bitbake for > raspberrypi3-64 target at head of sumo in all repos

Re: [yocto] [meta-raspberrypi] core-image-minimal for raspberrypi3-64 manifest/sdimg contains no kernel modules

Hello, > On Aug 15, 2018, at 11:54 AM, Khem Raj wrote: > > On Tue, Aug 14, 2018 at 11:48 PM Steve Pavao > wrote: >> >> There seems to be a problem with the core-image-minimal bitbake for >> raspberrypi3-64 target at head of sumo in all repos. I wonder if it’s also

Re: [yocto] [meta-raspberrypi] core-image-minimal for raspberrypi3-64 manifest/sdimg contains no kernel modules

On Wed, Aug 15, 2018 at 12:08 PM, Max Krummenacher wrote: > Hi > > Am Mittwoch, den 15.08.2018, 02:47 -0400 schrieb Steve Pavao: >> There seems to be a problem with the core-image-minimal bitbake for >> raspberrypi3-64 target at head >> of sumo in all repos. I wonder if it’s also a problem for t

Re: [yocto] [meta-raspberrypi] core-image-minimal for raspberrypi3-64 manifest/sdimg contains no kernel modules

Hi Am Mittwoch, den 15.08.2018, 02:47 -0400 schrieb Steve Pavao: > There seems to be a problem with the core-image-minimal bitbake for > raspberrypi3-64 target at head > of sumo in all repos. I wonder if it’s also a problem for the raspberrypi3 > target. > > No kernel modules appear in the .ma

Re: [yocto] [meta-raspberrypi] core-image-minimal for raspberrypi3-64 manifest/sdimg contains no kernel modules

On Tue, Aug 14, 2018 at 11:48 PM Steve Pavao wrote: > > There seems to be a problem with the core-image-minimal bitbake for > raspberrypi3-64 target at head of sumo in all repos. I wonder if it’s also a > problem for the raspberrypi3 target. > > No kernel modules appear in the .manifest, and no

[yocto] [meta-raspberrypi] core-image-minimal for raspberrypi3-64 manifest/sdimg contains no kernel modules

There seems to be a problem with the core-image-minimal bitbake for raspberrypi3-64 target at head of sumo in all repos. I wonder if it’s also a problem for the raspberrypi3 target. No kernel modules appear in the .manifest, and no kernel modules are put into the sdimg. It’s hard to believe i

Re: [yocto] [meta-raspberrypi] - X11 EGLSV2 Chromium

02feabeac4e4f58a09fe76edfd1" meta-browser = "master:d807b901b0b68b478093964bd60a77b9376b3f12" Thanks From: Trevor Woerner [mailto:twoer...@gmail.com] Sent: Sunday, July 22, 2018 5:48 PM To: Gillani, Karim CITZ:EX Cc: yocto@yoctoproject.org Subject: R

Re: [yocto] [meta-raspberrypi] - X11 EGLSV2 Chromium

Hi Karim, Can you please also include the "Build Configuration" block that's printed at the start of the build? That way we know what layers you're using, and which branches/commits of those layers. Best regards, Trevor -- ___ yocto mailing list yo

[yocto] [meta-raspberrypi] - X11 EGLSV2 Chromium

I am new to yocto and I am trying to build Chromium with userland. I am not sure what I am missing to have userland build libGLESv2.so, libGLESv2.so.2 and libEGL. All builds great but when I start Chromium, it complains there is no libGLESv2.so.2. I searched for libG* and only the following sho

Re: [yocto] [meta-raspberrypi] - X11 EGLSV2 Chromium

Karim Gillani writes: > I am new to yocto and I am trying to build Chromium with userland. I am not > sure what I am missing to have userland build libGLESv2.so, libGLESv2.so.2 > and libEGL. > > All builds great but when I start Chromium, it complains there is no > libGLESv2.so.2. I don't test

[yocto] [meta-raspberrypi] - X11 EGLSV2 Chromium

I am new to yocto and I am trying to build Chromium with userland. I am not sure what I am missing to have userland build libGLESv2.so, libGLESv2.so.2 and libEGL. All builds great but when I start Chromium, it complains there is no libGLESv2.so.2. I searched for libG* and only the following sho

Re: [yocto] [meta-raspberrypi] dtb mising from raspberrypi3-64.conf

Hi Steve Can you open an issue on https://github.com/agherzan/meta-raspberrypi On Tue, Jul 10, 2018 at 11:52 AM Steve Pavao wrote: > > Would you please add the bcm2710-rpi-cm3.dtb to the KERNEL_DEVICETREE listing > in raspberrypi3-64.conf in sumo branch? It’s missing. > > - Steve Pavao > Korg R

[yocto] [meta-raspberrypi] dtb mising from raspberrypi3-64.conf

Would you please add the bcm2710-rpi-cm3.dtb to the KERNEL_DEVICETREE listing in raspberrypi3-64.conf in sumo branch? It’s missing. - Steve Pavao Korg R&D -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi] Waveshare touchscreen

On Tue, Jul 3, 2018 at 4:40 AM, Michele Tirinzoni wrote: > Anyway, the config.txt is just enough to be able to use the screen with > touch functionality ? No need to have any driver installed ? > These panels have two cables that must be connected to the board: HDMI and USB. The HDMI handles al

Re: [yocto] [meta-raspberrypi] Waveshare touchscreen

Thanks Trevor. I don't see he zero in their supported device list, I will try to contact them. Anyway, the config.txt is just enough to be able to use the screen with touch functionality ? No need to have any driver installed ? On Tue, 3 Jul 2018 at 04:33, Trevor Woerner wrote: > On Wed, Jun 27,

Re: [yocto] [meta-raspberrypi] Waveshare touchscreen

On Wed, Jun 27, 2018 at 7:38 AM, Michele Tirinzoni wrote: > > I saw in the documentation page that the Waveshare touchscreen is > supported. > Before buying one of those I'd like to know if anyone tried it recently > with a rpi zero w or if there's any known issue. > I added the support for the w

[yocto] [meta-raspberrypi] Waveshare touchscreen

Hi, I saw in the documentation page that the Waveshare touchscreen is supported. Before buying one of those I'd like to know if anyone tried it recently with a rpi zero w or if there's any known issue. Thanks in advance. ## Michele -- ___ yocto mailing l

[yocto] [meta-raspberrypi] raspberrypi3 at head of sumo has broken console

I just built raspberrypi3 at head of sumo. The attached keyboard and mouse don’t work in the console, although a window and the prompt is displayed. The mouse and keyboard work fine when booting Raspbian or other raspberrypi3 images I’ve built in other branches in the past. Build info below:

Re: [yocto] [Yocto][meta-raspberrypi] troubling warning "postinstall intercept hook 'update_gio_module_cache-nativesdk' failed"

On 05/17/2018 12:17 PM, Steve Pavao wrote: I am trying to build for raspberrypi3 near head of sumo. I get the following troublesome warning fairly often since I started doing some builds in sumo and master the past week.: WARNING: core-image-minimal-1.0-r0 do_populate_sdk: The postinstall inte

[yocto] [Yocto][meta-raspberrypi] troubling warning "postinstall intercept hook 'update_gio_module_cache-nativesdk' failed"

I am trying to build for raspberrypi3 near head of sumo. I get the following troublesome warning fairly often since I started doing some builds in sumo and master the past week.: WARNING: core-image-minimal-1.0-r0 do_populate_sdk: The postinstall intercept hook 'update_gio_module_cache-nativesd

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

Hi Andrei, Thanks so much for confirming the issue. > On May 15, 2018, at 4:18 AM, Andrei Gherzan wrote: > > Hi, > > On Tue, May 15, 2018 at 1:48 AM, Bill Jenkins > wrote: > > > On May 14, 2018, at 2:43 PM, Bill Jenkins > > wrote: > > > > Hi,

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

Hi, On Tue, May 15, 2018 at 1:48 AM, Bill Jenkins wrote: > > > On May 14, 2018, at 2:43 PM, Bill Jenkins 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

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

> On May 14, 2018, at 2:43 PM, Bill Jenkins 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" du

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

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 commit

Re: [yocto] [meta-raspberrypi] Compute Module 3 machine .conf questions

Currently, the cm3 machine is only there as for people to see clearly what machine as supported. As well, in some cases, we need some machine specific tweaks so we need a new machine - it's not the case here. -- Andrei Gherzan On Wed, May 2, 2018 at 11:56 PM, Steve Pavao wrote: > Hi Andrei, > >

Re: [yocto] [meta-raspberrypi] Compute Module 3 machine .conf questions

Hi Andrei, We were able to verify that we could directly use the raspberrypi3-64.conf for the cm3 as 64-bit, as you had suggested. Thanks for that suggestion. It just seemed a bit confusing that there is only one cm3 machine conf, and it tunnels through to a rpi2. All the online doc about the

Re: [yocto] [meta-raspberrypi] Compute Module 3 machine .conf questions

Hi Steve, On Tue, May 1, 2018 at 12:40 AM, Steve Pavao wrote: > Hello, > > My company has bought a Raspberry Pi Compute Module 3 for evaluation, and > I have a 2 questions about the supplied machine .conf files for it. > > 1. Should the supplied raspberrypi-cm3.conf file internally refer to the

[yocto] [meta-raspberrypi] Compute Module 3 machine .conf questions

Hello, My company has bought a Raspberry Pi Compute Module 3 for evaluation, and I have a 2 questions about the supplied machine .conf files for it. 1. Should the supplied raspberrypi-cm3.conf file internally refer to the Raspberry Pi 3 instead of the Raspberry Pi 2, since the RPi3 is the hardw

  1   2   3   4   5   6   7   8   9   10   >