Skip to contentSkip to conversation

Raspberry Pi 3

meta-raspberry David Weisgerber 7 participants 15 messages Mar 18, 2016 – Jul 8, 2016

lore
Share & tools
lore

David Weisgerber

author
#0 lore raw

Hi,
did anyone succeed in building an image that runs on Raspberry Pi 3? I set my conf/local.conf to

MACHINE ??= "raspberrypi3"
GPU_MEM = "128"
DISABLE_OVERSCAN = "1"

and built rpi-basic-image but when booting the Pi 3 up I only see 4 raspberries in the top right but nothing else happens. The image works perfectly on a Pi 2 though.

Thanks for help,
David

#1 lore raw
Quoted 11 lines · David Weisgerber

Hi,
did anyone succeed in building an image that runs on Raspberry Pi 3? I set my conf/local.conf to

MACHINE ??= "raspberrypi3"
GPU_MEM = "128"
DISABLE_OVERSCAN = "1"

and built rpi-basic-image but when booting the Pi 3 up I only see 4 raspberries in the top right but nothing else happens. The image works perfectly on a Pi 2 though.

I'm able to get a raspi3 image running on my Raspberry Pi 3, but my console is messed up. Everything works fine via the usb+hdmi ports, but plugging a console cable into the GPIO header is messed up.

It looks like what happens when the baud rate is set incorrectly, but I've tried every baud rate in my terminal emulator and it all looks the same (messed up).

Anyone got their console working? The same cable/setup works fine on the raspi2 (ttyAMA0) but doesn't work on my raspi3 (ttyS0).

#2 lore raw
Quoted 17 lines · Trevor Woerner
Quoted 11 lines · David Weisgerber

Hi,
did anyone succeed in building an image that runs on Raspberry Pi 3? I set my conf/local.conf to

MACHINE ??= "raspberrypi3"
GPU_MEM = "128"
DISABLE_OVERSCAN = "1"

and built rpi-basic-image but when booting the Pi 3 up I only see 4 raspberries in the top right but nothing else happens. The image works perfectly on a Pi 2 though.

I'm able to get a raspi3 image running on my Raspberry Pi 3, but my console is messed up. Everything works fine via the usb+hdmi ports, but plugging a console cable into the GPIO header is messed up.

Quoted 6 lines

It looks like what happens when the baud rate is set incorrectly, but I've tried every baud rate in my terminal emulator and it all looks the same (messed up).

Anyone got their console working? The same cable/setup works fine on the raspi2 (ttyAMA0) but doesn't work on my raspi3 (ttyS0).

I think you are seeing this problem:
https://github.com/raspberrypi/firmware/issues/553

/Josep

#3 lore raw
In reply to Trevor Woerner
Quoted 20 lines · Trevor Woerner
Quoted 11 lines · David Weisgerber

Hi,
did anyone succeed in building an image that runs on Raspberry Pi 3? I set my conf/local.conf to

MACHINE ??= "raspberrypi3"
GPU_MEM = "128"
DISABLE_OVERSCAN = "1"

and built rpi-basic-image but when booting the Pi 3 up I only see 4 raspberries in the top right but nothing else happens. The image works perfectly on a Pi 2 though.

I'm able to get a raspi3 image running on my Raspberry Pi 3, but my console is messed up. Everything works fine via the usb+hdmi ports, but plugging a console cable into the GPIO header is messed up.

Quoted 6 lines

It looks like what happens when the baud rate is set incorrectly, but I've tried every baud rate in my terminal emulator and it all looks the same (messed up).

Anyone got their console working? The same cable/setup works fine on the raspi2 (ttyAMA0) but doesn't work on my raspi3 (ttyS0).

did you try

https://www.mail-archive.com/[email protected]/msg28476.html

Quoted 5 lines

--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

#4 lore raw
Quoted 24 lines · Khem Raj
Quoted 24 lines · Trevor Woerner
Quoted 11 lines · David Weisgerber

Hi,
did anyone succeed in building an image that runs on Raspberry Pi 3? I set my conf/local.conf to

MACHINE ??= "raspberrypi3"
GPU_MEM = "128"
DISABLE_OVERSCAN = "1"

and built rpi-basic-image but when booting the Pi 3 up I only see 4 raspberries in the top right but nothing else happens. The image works perfectly on a Pi 2 though.

I'm able to get a raspi3 image running on my Raspberry Pi 3, but my console is messed up. Everything works fine via the usb+hdmi ports, but plugging a console cable into the GPIO header is messed up.

It looks like what happens when the baud rate is set incorrectly, but I've tried every baud rate in my terminal emulator and it all looks the same (messed up).

Quoted 6 lines
Quoted 2 lines

Anyone got their console working? The same cable/setup works fine on the raspi2 (ttyAMA0) but doesn't work on my raspi3 (ttyS0).

did you try

https://www.mail-archive.com/[email protected]/msg28476.html

As far as I can tell there are two raspberry pi OE layers which include this commit:

1. git://git.yoctoproject.org/meta-raspberrypi::master
2. https://github.com/kraj/meta-raspberrypi.git::kraj/master

Building two fresh, from-scratch Poky images using the latest up-to-date sources for:

meta-openembedded/meta-oe
openembedded-core/meta
meta-poky/meta-poky

and swapping in the two raspberrypi layers (one at a time) I get:

- Using 1 (the official layer from Andrei) I get an image that boots but the console remains messed up (as before).

- Using 2 (the layer from Khem) I get an image that flashes the rainbow pattern on the HDMI monitor, shows the 4 berries, then stops. Nothing else happens, no messages on the console.

In both cases I'm building core-image-full-cmdline, and the only tweak in local.conf is:

	ENABLE_SPI_BUS = "1"

As far as I can tell, the only difference between the two raspberry pi layers is the kernel. Andrei's uses 4.1 and Khem is using 4.4:

	$ git show-branch kraj/master origin/master 
	* [kraj/master] userland: Fix tearing effect seen with wayland compositors
	 ! [origin/master] userland: Fix tearing effect seen with wayland compositors
	--
	 + [origin/master] userland: Fix tearing effect seen with wayland compositors
	 + [origin/master^] firmware: Update to 20160326
	*  [kraj/master] userland: Fix tearing effect seen with wayland compositors
	*  [kraj/master^] firmware: Update to 20160326
	*  [kraj/master~2] linux-raspberrypi: Make 4.4 default kernel
	*+ [origin/master~2] userland: Implement dispmanx_wrap_buffer

I'll try core-image-minimal and no SPI flag. Unless someone else has better-sounding ideas?

Best regards,
Trevor

#5 lore raw
Quoted 5 lines · Trevor Woerner

As far as I can tell there are two raspberry pi OE layers which include this commit:

1. git://git.yoctoproject.org/meta-raspberrypi::master
2. https://github.com/kraj/meta-raspberrypi.git::kraj/master

[...]

Quoted 6 lines

- Using 1 (the official layer from Andrei) I get an image that boots but the console remains messed up (as before).

- Using 2 (the layer from Khem) I get an image that flashes the rainbow pattern on the HDMI monitor, shows the 4 berries, then stops. Nothing else happens, no messages on the console.

I get the same results with no local.conf tweaks and building the rpi-basic-image.

Does anyone have a run-tested, OE-built, raspi3 image with working console?

Best regards,
Trevor

#6 lore raw
Quoted 13 lines · Trevor Woerner
Quoted 5 lines · Trevor Woerner

As far as I can tell there are two raspberry pi OE layers which include this commit:

1. git://git.yoctoproject.org/meta-raspberrypi::master
2. https://github.com/kraj/meta-raspberrypi.git::kraj/master

[...]

Quoted 3 lines

- Using 1 (the official layer from Andrei) I get an image that boots but the console remains messed up (as before).

Quoted 9 lines
Quoted 3 lines

- Using 2 (the layer from Khem) I get an image that flashes the rainbow pattern on the HDMI monitor, shows the 4 berries, then stops. Nothing else happens, no messages on the console.

I get the same results with no local.conf tweaks and building the rpi-basic-image.

Does anyone have a run-tested, OE-built, raspi3 image with working console?

can you select 4.1 for kernel and try with master, Andre has merged all my changes today

Quoted 2 lines

Best regards,
Trevor

#7 lore raw
Quoted 17 lines · Khem Raj
Quoted 17 lines · Trevor Woerner
Quoted 5 lines · Trevor Woerner

As far as I can tell there are two raspberry pi OE layers which include this commit:

1. git://git.yoctoproject.org/meta-raspberrypi::master
2. https://github.com/kraj/meta-raspberrypi.git::kraj/master

[...]

Quoted 6 lines

- Using 1 (the official layer from Andrei) I get an image that boots but the console remains messed up (as before).

- Using 2 (the layer from Khem) I get an image that flashes the rainbow pattern on the HDMI monitor, shows the 4 berries, then stops. Nothing else happens, no messages on the console.

Quoted 8 lines
Quoted 5 lines

I get the same results with no local.conf tweaks and building the rpi-basic-image.

Does anyone have a run-tested, OE-built, raspi3 image with working console?

can you select 4.1 for kernel and try with master, Andre has merged all my changes today

Yes, that's one of the options I have already tried; it boots but the console is still garbled.

The 4.1 kernel is the default in Andrei's layer. Using the 4.4 kernel from your layer I can't get past the 4 raspberries.

#8 lore raw

Trevor,

I know with the Pi3 they swapped ttyAMA0 to support Bluetooth.

They put ttyS0 on the 40-pin header, but the clock used for the baud rate generation on ttyS0 is tied to the core frequency, and it can cause fluctuations when the core frequency scales up and down.

I believe the official fix is to set core_freq=250 so that the core clock is always at it's lowest value and never needs to change. There's also a dtoverlay that swaps the two UARTs back so you can get the stable UART on the 40-pin header.

Not clear to me that this is your exact problem, but it might be worth a quick test?

Some notes here:
https://www.raspberrypi.org/forums/viewtopic.php?f=107&t=138223

Hope this helps,

-Mike

Quoted 45 lines · Trevor Woerner
Quoted 5 lines · Khem Raj
Quoted 5 lines · Trevor Woerner
Quoted 1 line · Trevor Woerner

As far as I can tell there are two raspberry pi OE layers which

include this

Quoted 6 lines
Quoted 6 lines
Quoted 4 lines

commit:

1. git://git.yoctoproject.org/meta-raspberrypi::master
2. https://github.com/kraj/meta-raspberrypi.git::kraj/master

[...]

Quoted 1 line

- Using 1 (the official layer from Andrei) I get an image that boots

but the

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

console remains messed up (as before).

- Using 2 (the layer from Khem) I get an image that flashes the

rainbow

Quoted 1 line
Quoted 1 line
Quoted 1 line

pattern on the HDMI monitor, shows the 4 berries, then stops.

Nothing else

Quoted 6 lines
Quoted 6 lines
Quoted 1 line

happens, no messages on the console.

I get the same results with no local.conf tweaks and building the rpi-basic-image.

Does anyone have a run-tested, OE-built, raspi3 image with working

console?

Quoted 3 lines
Quoted 1 line

can you select 4.1 for kernel and try with master, Andre has merged all

my changes

Quoted 1 line

today

Yes, that's one of the options I have already tried; it boots but the console
is still garbled.

The 4.1 kernel is the default in Andrei's layer. Using the 4.4 kernel from your layer I can't get past the 4 raspberries.
--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

#9 lore raw
In reply to Trevor Woerner
Quoted 7 lines · Trevor Woerner
Quoted 5 lines · Khem Raj
Quoted 5 lines · Trevor Woerner
Quoted 1 line · Trevor Woerner

As far as I can tell there are two raspberry pi OE layers which

include this

Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 4 lines

commit:

1. git://git.yoctoproject.org/meta-raspberrypi::master
2. https://github.com/kraj/meta-raspberrypi.git::kraj/master

[...]

Quoted 1 line

- Using 1 (the official layer from Andrei) I get an image that boots

but the

Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines

console remains messed up (as before).

- Using 2 (the layer from Khem) I get an image that flashes the rainbow pattern on the HDMI monitor, shows the 4 berries, then stops.

Nothing else

Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 1 line

happens, no messages on the console.

I get the same results with no local.conf tweaks and building the rpi-basic-image.

Does anyone have a run-tested, OE-built, raspi3 image with working

console?

Quoted 3 lines
Quoted 3 lines
Quoted 1 line

can you select 4.1 for kernel and try with master, Andre has merged all

my changes

Quoted 7 lines
Quoted 1 line

today

Yes, that's one of the options I have already tried; it boots but the console is still garbled.

The 4.1 kernel is the default in Andrei's layer. Using the 4.4 kernel from your layer I can't get past the 4 raspberries.

Hi everyone,

this is nothing that depends on the kernel itself. There was a major change in the /dev/ttyAMA0 in order to make use of the bluetooth module. There is an overlay that allows using the console and the bluetooth module on parallel (pi3-miniuart-bt) with a lower baudrate while useing hciattach. If you don't want to use the bluetooth module you can switch back to the console by using the pi3-disalble-bt overlay.

See also: https://www.raspberrypi.org/forums/viewtopic.php?t=138120&p=926637

#10 lore raw
In reply to Trevor Woerner

Thanks to everyone for their help!! It looks like I've got something working, not sure if this is a "solution" or if most would just consider it a work-around:

1) use Andrei's meta-raspberrypi layer (which selects linux kernel 4.1 by default)

2) add the following to your local.conf:

	SERIAL_CONSOLE_forcevariable = "115200 ttyS0"
	CORE_FREQ = "250"

3) ??

4) profit!!

I've tested with poky building both core-image-x11 and core-image-full-cmdline.

Best regards,
Trevor

#11 lore raw
Quoted 6 lines · Trevor Woerner

Thanks to everyone for their help!! It looks like I've got something working, not sure if this is a "solution" or if most would just consider it a work-around:

1) use Andrei's meta-raspberrypi layer (which selects linux kernel 4.1 by default)

thats good.

Quoted 5 lines

2) add the following to your local.conf:

        SERIAL_CONSOLE_forcevariable = "115200 ttyS0"
        CORE_FREQ = "250"

Send a patch to document this in README.

Quoted 15 lines

3) ??

4) profit!!

I've tested with poky building both core-image-x11 and core-image-full-cmdline.

Best regards,
Trevor
--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

#12 lore raw
Quoted 9 lines · Khem Raj
Quoted 6 lines · Trevor Woerner

Thanks to everyone for their help!! It looks like I've got something working, not sure if this is a "solution" or if most would just consider it a work-around:

1) use Andrei's meta-raspberrypi layer (which selects linux kernel 4.1 by default)

thats good.

Here's some more details that will, hopefully, help others duplicate my results:

	Build Configuration:
	BB_VERSION        = "1.29.1"
	BUILD_SYS         = "x86_64-linux"
	NATIVELSBSTRING   = "openSUSE-project-13.2"
	TARGET_SYS        = "arm-poky-linux-gnueabi"
	MACHINE           = "raspberrypi3"
	DISTRO            = "poky"
	DISTRO_VERSION    = "2.0+snapshot-20160404"
	TUNE_FEATURES     = "arm armv7ve vfp thumb neon vfpv4 callconvention-hard cortexa7"
	TARGET_FPU        = "hard"
	meta-raspberrypi  = "contrib/twoerner/raspi3:7037617fca920f6e26c2a6968fa1ec67f495035d"
	meta-poky
	meta              = "master:af5f423887d1c41cf7279f6e537077726ae13082"

	meta-raspberrypi
		git://git.yoctoproject.org/meta-raspberrypi
		(branch based on master at 84af6e7de3b8ea64ab374028aa95dc3a288ae85c)

	meta-poky
		git://git.yoctoproject.org/poky

My bblayers just pulls in these two layers, my local.conf has no local tweaks, and you need to apply the two patches I recently sent to the mailing list.

Quoted 24 lines
Quoted 6 lines

2) add the following to your local.conf:

        SERIAL_CONSOLE_forcevariable = "115200 ttyS0"
        CORE_FREQ = "250"

Send a patch to document this in README.

Quoted 15 lines

3) ??

4) profit!!

I've tested with poky building both core-image-x11 and core-image-full-cmdline.

Best regards,
Trevor
--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

#13 lore raw
In reply to David Weisgerber
Quoted 12 lines · David Weisgerber

Hi,
did anyone succeed in building an image that runs on Raspberry Pi 3? I set my conf/local.conf to

MACHINE ??= "raspberrypi3"
GPU_MEM = "128"
DISABLE_OVERSCAN = "1"

and built rpi-basic-image but when booting the Pi 3 up I only see 4 raspberries in the top right but nothing else happens. The image works perfectly on a Pi 2 though.

Quoted 7 lines

Thanks for help,
David
--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

How do you check that the image is running or not?

PS: Please us the correct subject tag: meta-raspberrypi.

--
Andrei Gherzan

#14 lore raw
Quoted 1 line · Andrei Gherzan
Quoted 1 line

MACHINE ??= "raspberrypi3"

can you change it to MACHINE = "raspberrypi3"
and retry