All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John" <jdowd@slashdevslashnull.org>
To: "John" <jdowd@slashdevslashnull.org>, yocto@lists.yoctoproject.org
Subject: Re: [yocto] Unable to boot a raspberry Pi Zero 2 W using the master branch of Yocto #raspberrypi #raspberrypi0-wifi
Date: Thu, 06 Feb 2025 08:42:36 -0800	[thread overview]
Message-ID: <22391.1738860156600922862@lists.yoctoproject.org> (raw)
In-Reply-To: <22391.1738859480398711450@lists.yoctoproject.org>

[-- Attachment #1: Type: text/plain, Size: 869 bytes --]

So, I'm at the same point in this excruciating exercise. The output is the same as what I reported before. I'm stuck at the loading of the linux kernel.

I have to set the dtparam arm_64bit=0 for my Yocto image. Could there be an issue with the Raspberry Pi bootcode.bin being unable to load a 32-bit kernel image? If I don't put that parameter in, I get an error from bootcode.bin about there being no loadable kernel image available.

Also, I've tried this with u-boot as well. I was thinking it would be easier as u-boot's start requirements are quite straight forward. However I get exactly the same issue.

Is this a device tree issue? I have the dtb file: bcm2710-rpi-zero-2.dtb being loaded. Is that the correct one?

Can anyone claim that they have a working Yocto image from the more recent repos booting on a Raspberry Pi Zero W 2 board?

Cheers!!

[-- Attachment #2: Type: text/html, Size: 1020 bytes --]

  reply	other threads:[~2025-02-06 16:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-05 18:38 Unable to boot a raspberry Pi Zero 2 W using the master branch of Yocto #raspberrypi #raspberrypi0-wifi jdowd
2025-02-06  6:00 ` [yocto] " Khem Raj
2025-02-06 15:54   ` John
2025-02-06 15:58     ` Khem Raj
2025-02-06 16:31       ` John
2025-02-06 16:42         ` John [this message]
2025-02-06 17:15           ` Khem Raj
2025-02-06 19:39             ` John
2025-02-06 19:46               ` Khem Raj
2025-02-07 13:39                 ` John
2025-02-07 16:10                   ` Khem Raj
2025-02-07 16:43                     ` John

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=22391.1738860156600922862@lists.yoctoproject.org \
    --to=jdowd@slashdevslashnull.org \
    --cc=yocto@lists.yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.