All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Lisandro Damián Nicanor Pérez Meyer" <perezmeyer@gmail.com>
To: meta-ti@lists.yoctoproject.org
Subject: beaglebone-ai64: i2c errors ooting with u-boot-ti-staging
Date: Fri, 18 Aug 2023 10:31:54 -0300	[thread overview]
Message-ID: <3074167.fKoSnE5vHq@gryffindor> (raw)

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

Hi, and hope I get the right list for this.

I have built poky's core-image-minimal for the BeagleBone AI64 using meta-ti's kirkstone layer, current HEAD. When I boot I get stuff like:

```
Hit any key to stop autoboot:  2 \b\b\b 1 \b\b\b 0 
i2c_write: error waiting for data ACK (status=0x116)
pca953x gpio@22: Error reading output register
switch to partitions #0, OK
mmc1 is current device
i2c_write: error waiting for data ACK (status=0x116)
pca953x gpio@22: Error reading output register
SD/MMC found on device 1
Failed to load 'boot.scr'
Failed to load 'uEnv.txt'
i2c_write: error waiting for data ACK (status=0x116)
pca953x gpio@20: Error reading output register
i2c_write: error waiting for data ACK (status=0x116)
pca953x gpio@22: Error reading output register
```
and then I get stuck at 

```
Waiting for root device PARTUUID=18b27b92-02
```

I rebooted, entered u-boot's prompt and run fuinduuid manually, which also causes an I²C-related error:

```
=> run finduuid
i2c_write: error waiting for data ACK (status=0x116)
pca953x gpio@22: Error reading output register
```

Am I doing something wrong here, or should I be filing a bug somewhere? Of course feel free to ask me for more details.

Thanks in advance, Lisandro.


[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

                 reply	other threads:[~2023-08-18 13:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3074167.fKoSnE5vHq@gryffindor \
    --to=perezmeyer@gmail.com \
    --cc=meta-ti@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.