Re: [yocto] [meta-raspberrypi] Building rpi-test-image for Pi3 64 bit

2017-04-29 Thread Andrea Galbusera
On Sat, Apr 29, 2017 at 2:39 AM, Luca Carlon  wrote:

> Hello,
> thank you very much for your advice. It seems I can build both a minimal
> image and rpi-basic-image. I would like to test to see if the Pi is able to
> boot with these images but it seems that the images directory does not
> contain any sdimg file. By reading https://github.com/agherzan/
> meta-raspberrypi and https://github.com/Nuand/bladeRF/wiki/Creating-Linux-
> based-Embedded-System-Images-with-Yocto it seems I should find a sdimg
> file to flash to the sdcard. I suppose this image file contains both the
> boot and rootfs partitions. But it seems I do not see this image at all,
> this is a list of what I can see in tmp/deploy/images/raspberrypi3-64:
> https://pastebin.com/8XsRHzUY. I see the rootfs filesystem that I can
> extract in a partition, but not the boot partition the Pi needs. Maybe I'm
> missing some line in the conf files?
>

If you are using the local.conf you previously posted, the line:

IMAGE_FSTYPES = "tar.xz"

is overriding default configuration from rpi-base.inc in meta-raspberrypi
which is:

IMAGE_FSTYPES ?= "tar.bz2 ext3 rpi-sdimg"

You can also consider using wic image format to generate a flashable image
(see Yocto documentation on how to do that).
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] Raspberry Pi 3 build issue

2017-04-29 Thread alexis . lothore
Hello,
I finally figured out what was messing my build, and it was a poor 
mistake from my side... I am posting it here for anyone who could encounter a 
similar issue.

I did let my custom layer in my bblayer.conf. I did not think it could 
break the build, but I forgot about the bbappends there. In fact there was one 
bbappend trying to 
patch a dts file, and I poorly mixed overrides in the bbappend : I used a 
SRC_URI_raspberrypi3 to add the patch in the bbappend, but I also have put 
the patch in a machine specific directory (raspberrypi3/xxx.patch). 
Letting only the second option seems to be the correct way to proceed
(http://www.yoctoproject.org/docs/1.5/dev-manual/dev-manual.html#best-practices-to-follow-when-creating-layers,
 
section "Place Machine-Specific Files in Machine-Specific Locations)

Regards,

On Tue, 25 Apr 2017, alexis.loth...@gmail.com wrote:

> Hello Paul,
> thanks for the try. It should means that there is a detail on my setup 
> which prevents the build from being done. I encounter the error on the 
> commits id your provided too. I also tried being on last tag on poky 
> project for morty branch, without success. I also suspected my python 
> configuration/version so I resintalled it completely, but It made no 
> change to the error.
> 
> On Tue, 25 Apr 2017, Paul Barker wrote:
> 
> > On Mon, Apr 24, 2017 at 7:25 PM,   wrote:
> > > Hello,
> > > I am currently encountering an issue with meta-raspberry and more
> > > specifically Raspberry Pi 3 build. Since I was not sure the problem was
> > > not my fault, I cloned a fresh copy of poky and meta-raspberrypi (both
> > > checked out on morty, and meta dependencies on morty too), but the problem
> > > is still appearing, trying to build the image rpi-hwup-image with BDISTRO
> > > poky for MACHINE
> > > raspberrypi3 :
> > >
> > > ➜ build git:(morty) bitbake rpi-hwup-image
> > > Loading cache: 100%
> > > |#|
> > > Time: 0:00:00
> > > Loaded 2 entries from dependency cache.
> > > WARNING:
> > > /home/alexis/Projets/poky/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.9.bb:
> > > Exception during build_dependencies for PKG_kernel-image | ETA: --:--:--
> > > WARNING:
> > > /home/alexis/Projets/poky/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.9.bb:
> > > Error during finalise of
> > > /home/alexis/Projets/poky/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.9.bb
> > > WARNING:
> > > /home/alexis/Projets/poky/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.4.bb:
> > > Exception during build_dependencies for PKG_kernel-image
> > > WARNING:
> > > /home/alexis/Projets/poky/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.4.bb:
> > > Error during finalise of
> > > /home/alexis/Projets/poky/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.4.bb
> > > ERROR: ExpansionError during parsing
> > > /home/alexis/Projets/poky/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.9.bb
> > > Traceback (most recent call last):
> > > bb.data_smart.ExpansionError: Failure expanding variable PKG_kernel-image,
> > > expression was
> > > kernel-image-${@legitimize_package_name('${@get_kernelversion_headers('/home/alexis/Projets/poky/build/tmp/work/raspberrypi3-poky-linux-gnueabi/linux-raspberrypi/1_4.9.21+git${SRCPV}-r0/linux-raspberrypi3-standard-build')}')}
> > > which triggered exception SyntaxError: invalid syntax (PKG_kernel-image,
> > > line 1)
> > > Summary: There were 4 WARNING messages shown.
> > > Summary: There was 1 ERROR message shown, returning a non-zero exit code.
> > >
> > > I am executing the build on an x86 machine with Debian 8.
> > >
> > > Unfortunately, since the problem seems to appear right at parsing, I
> > > cannot get the exact variable expansion with bitbake -e. Apparently my
> > > Yocto setup does not encounter the issue if I try the build for another
> > > RPI target, like raspberrypi0. Any advice on how to troubleshoot this
> > > issue ?
> > > --
> > 
> > I've just tried to reproduce this using a fresh clone of poky and
> > meta-raspberrypi on the morty branch. I edited bblayers.conf to add
> > the meta-raspberrypi layer and then edited local.conf to set MACHINE =
> > "raspberrypi3", those were my only changes. I then ran "bitbake
> > rpi-hwup-image" and it's correctly parsed all the recipes and started
> > the build.
> > 
> > Which exact commits of poky and meta-raspberrypi are you using? I have
> > the following:
> > 
> > meta
> > meta-poky
> > meta-yocto-bsp= "morty:924e576b8930fd2268d85f0b151e5f68a3c2afce"
> > meta-raspberrypi  = "morty:28d4404f89eb59d406b4976c0e3f5ca19137ba74"
> > 
> > Thanks,
> > 
> > -- 
> > Paul Barker
> > Co-Founder & Principal Engineer
> > Togán Labs Ltd
> > -- 
___
yocto mailing list
yocto@yoctop

[yocto] Release Candidate Build for yocto-2.3.rc3 now available.

2017-04-29 Thread Poky Build User

A release candidate build for yocto-2.3.rc3 is now available at:


http://autobuilder.yoctoproject.org/pub/releases/yocto-2.3.rc3


Please begin QA on this build as soon as possible.


Build hash information: 
meta-intel : 112643bbb731a6ccac7f4f5bde7f78d8fa2f9c15 
meta-qt4 : e120a2193be3982d55741fb9e51472db6ab9a5cd 
meta-mingw : 4bdb99650a053f254ccd158a6d0c25c80e79f6ee 
meta-qt3 : f33b73a9563f2dfdfd0ee37b61d65d90197a456f 
meta-gplv2 : de001bd6bfcec943d274b649c62be6848cc9c3e6 
poky : a00f8981d8d2b361cc2c5d08d7cc6040c79af3cb 

\nThis is an automated message from\nThe Yocto Project Autobuilder\nGit: 
git://git.yoctoproject.org/yocto-autobuilder\nEmail: joshua.g.l...@intel.com 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] [meta-rockchip][PATCH] README: remove irrelevant information

2017-04-29 Thread Trevor Woerner
As of openembedded-core commit 2b3ae58f5eaecc8474761c543ff5347aa0e3c4c8 hardfp
is enabled by default.

Signed-off-by: Trevor Woerner 
---
 README | 16 
 1 file changed, 16 deletions(-)

diff --git a/README b/README
index b2e89f3..7f4a499 100644
--- a/README
+++ b/README
@@ -49,7 +49,6 @@ Table of Contents
   I. Configure yocto/oe environment
  II. Building a second level bootloader based on kexec
 III. Booting your device
- IV. Performance
 
 I. Configure yocto/oe environment
 
@@ -127,18 +126,3 @@ linux-next from tftp='tftp://192.168.0.5/zImage 
dtb=tftp://192.168.0.5/
 Then, plug your SDCARD into your Rockchip device and power on the board. If
 everything worked fine, Petitboot should be started automatically and list all 
 entries found in the configuration file.
-
-IV. Performance
-===
-
-By default a BSP layer should not be tuning a build, this is a DISTRO-level
-decision. As such the default machine settings are meant to be the lowest
-common denominator in order to maximize generality. If you are interested in
-tweaking your build to maximize performance you can either use a DISTRO that
-has these same goals, or you can add settings in your configuration files
-(e.g. local.conf) as follows:
-
-   for rk3288:
-   DEFAULTTUNE = "cortexa17hf-neon-vfpv4"
-   for rk3066:
-   DEFAULTTUNE = "cortexa9-neon"
-- 
2.12.0.rc1.48.g076c053

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