From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from aws-us-west-2-korg-lkml-1.web.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.lore.kernel.org (Postfix) with ESMTP id E2EA6C433EF for ; Wed, 12 Jan 2022 13:37:35 +0000 (UTC) Received: from ds.tools (ds.tools [158.69.194.164]) by mx.groups.io with SMTP id smtpd.web12.23390.1641994649114781775 for ; Wed, 12 Jan 2022 05:37:29 -0800 Authentication-Results: mx.groups.io; dkim=pass header.i=@lebel.pro header.s=dkim header.b=a9FVJAq6; spf=pass (domain: lebel.pro, ip: 158.69.194.164, mailfrom: jp@lebel.pro) Received: from [127.0.0.1] (localhost [127.0.0.1]) by localhost (Mailerdaemon) with ESMTPSA id CE6C21271 for ; Wed, 12 Jan 2022 08:37:26 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lebel.pro; s=dkim; t=1641994647; h=from:subject:date:message-id:to:cc:mime-version:content-type: in-reply-to:references; bh=meM2ZIREzZDeeuIMARgmCWDnqpAqT8oYOERNZBMZBYE=; b=a9FVJAq6VCwztKpHXzMbjBA1Q0poQ6P9quLseVvOjOu/IYAEAB5fPmhmFDOquuPKU0dAwO Rj75EUK8Od6kyS9aS5pjl6IoyjxEd7AuQtdTogcMfvpIPVs80gPM04KmLYa9/jZp9nmJsT 3kPBNLmuM9bm7GW5VMZBAK2o/c4Uc2UpItpp/nANT8gUmP2kvTOHvWkLHRz5bo+yICWN8E B1EZ/FGOuRFyVm66TwU330YuLUxuUVmv8Obp4gm6xNploR68iA9gQRrrwOZtHmovdo3iuK 5dqcI22PDuSEZQzTMOvgZrQ1WmTe2TGLM7CAyQoLaQ0IGuiVOfV45xIh7McEPg== Received: by mail-qk1-f182.google.com with SMTP id 193so1757695qkh.13 for ; Wed, 12 Jan 2022 05:37:26 -0800 (PST) X-Gm-Message-State: AOAM532B2rwAMXGdZUy2V+tBSSKnRMVEAj7jZM/+LrSmy5DAWw2mz4k5 qF8YFdWk3li9SacoY4vR5cqE4TQ5K8xE+Sna/BY= X-Google-Smtp-Source: ABdhPJxI3cjj9mot4LSuEetTMEdd/dI8+Tt8mtZCkn1MQkazKFrPSxZgKEuh2yDPXx/ch5BXxgQvvsQrA/DYHuwYubc= X-Received: by 2002:a05:620a:cc7:: with SMTP id b7mr6444676qkj.176.1641994646096; Wed, 12 Jan 2022 05:37:26 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Jean-Philippe Lebel Date: Wed, 12 Jan 2022 08:37:15 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [yocto] [meta-raspberrypi] Problem with RPI_USE_U_BOOT with RaspberryPi4 To: Matthias Klein Cc: "yocto@lists.yoctoproject.org" Content-Type: multipart/alternative; boundary="0000000000009a979305d562abf9" X-Last-TLS-Session-Version: TLSv1.3 List-Id: X-Webhook-Received: from li982-79.members.linode.com [45.33.32.79] by aws-us-west-2-korg-lkml-1.web.codeaurora.org with HTTPS for ; Wed, 12 Jan 2022 13:37:35 -0000 X-Groupsio-URL: https://lists.yoctoproject.org/g/yocto/message/55814 --0000000000009a979305d562abf9 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thanks Matthias for your input. I have the same problem using the raspberrypi4-64 target. On my end, the mere fact of enabling RPI_USE_U_BOOT yields a non-bootable image. The image I generated/burned can be found here: https://www.dropbox.com/s/6glmmgtx0pcd06t/core-image-base-raspberrypi4-64-2= 0220112004201.rootfs.wic.bz2?dl=3D0 Thanks a lot. ------------- Jean-Philippe Lebel, ing. MBA jp@lebel.pro http://www.lebel.pro cell: 418-931-3800 *AVIS IMPORTANT:* Ce courriel est strictement r=C3=A9serv=C3=A9 =C3=A0 l'us= age de la (des) personne(s) =C3=A0 qui il est adress=C3=A9 et peut contenir de l'informatio= n privil=C3=A9gi=C3=A9e et confidentielle. Toute divulgation, distribution, c= opie, ou autre utilisation de ce courriel par une autre personne est strictement prohib=C3=A9e. Si vous avez re=C3=A7u ce courriel par erreur, veuillez s'il= vous pla=C3=AEt communiquer imm=C3=A9diatement avec l'exp=C3=A9diteur et d=C3=A9= truire le courriel sans en faire de copie sous quelque forme. *WARNING:* This e-mail contains confidential information intended only for the person(s) named above. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution, or any other use of this e-mail is strictly prohibited. If you have received this e-mail by mistake, please notify us immediately and destroy this e-mail without making any copy of any kind. On Wed, Jan 12, 2022 at 3:59 AM Matthias Klein wrote: > Hello Jean-Philippe, > > > > >I'm trying to create a simple image that uses the RPI_USE_U_BOOT option > but the pi hangs with the rainbow image. I'm able to generate bootable > images when not using the RPI_USE_U_BOOT option (but I need to use > swupdate). > > >I have the same problem with using the Hardknott branch, leading me to > think the problem is not the layer but the way I use it. > > For me the combination of raspberrypi4-64 machine, U-Boot and RAUC > (instead of swupdate) works. > > I think the raspberrypi4 should also work (but haven't tested it). > > > > I built and tested my (Poky master branch based) image this morning: > https://github.com/matthiasklein/meta-yocto-coffee-rpi > > > > I don't use HDMI output though, but a serial console (ENABLE_UART =3D "1"= ). > > > > Best regards, > > Matthias > > > --0000000000009a979305d562abf9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks Matthias for your input.

I have = the same problem using the raspberrypi4-64 target. On my end, the mere fact= of enabling RPI_USE_U_BOOT yields a non-bootable image.

The image I generated/burned can be found here:

Thanks a lot.
<= br clear=3D"all">
<= div dir=3D"ltr">
-------------
Jean-Philippe Lebel, ing. MBAjp@lebel.pro
http://www.lebel.procell: 418-931-3800

AVIS IMPORTANT:=C2=A0Ce = courriel est strictement r=C3=A9serv=C3=A9 =C3=A0 l'usage de la (des) p= ersonne(s) =C3=A0 qui il est adress=C3=A9 et peut contenir de l'informa= tion privil=C3=A9gi=C3=A9e et confidentielle. Toute divulgation, distributi= on, copie, ou autre utilisation de ce courriel par une autre personne est s= trictement prohib=C3=A9e. Si vous avez re=C3=A7u ce courriel par erreur, ve= uillez s'il vous pla=C3=AEt communiquer imm=C3=A9diatement avec l'e= xp=C3=A9diteur et d=C3=A9truire le courriel sans en faire de copie sous que= lque forme.

WARNING:=C2=A0This e-m= ail contains confidential information intended only for the person(s) named= above. If you are not the intended recipient you are hereby notified that = any disclosure, copying, distribution, or any other use of this e-mail is s= trictly prohibited. If you have received this e-mail by mistake, please not= ify us immediately and destroy this e-mail without making any copy of any k= ind.


On Wed, Jan 12, 2022 at 3:59 A= M Matthias Klein <matthias.klein@optimeas.de> wrote:

Hello Jean-Philippe,

=C2=A0

>I'm trying to create a simple image that use= s the=C2=A0RPI_USE_U_BOOT option but the pi hangs with the rainbow image. I= 'm able to generate bootable images when not using the RPI_USE_U_BOOT o= ption (but I need to use swupdate).

>I have the same problem with using the Hardknott= branch, leading me to think the problem is not the layer but the way I use= it.

For me the combination of raspberrypi4-64 machine, U-Boot and RAUC (instead= of swupdate) works.

I think the raspberrypi4 should also work (but haven= 't tested it).

=C2=A0

I built and tested my (Poky master branch based) ima= ge this morning: https://github.com/matthiasklein/meta-yocto-coffee-rpi

=C2=A0

I don't use HDMI output though, but a serial con= sole (ENABLE_UART =3D "1").

=C2=A0

Best regards,

Matthias

=C2=A0

--0000000000009a979305d562abf9--