All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Nelson <robertcnelson@gmail.com>
To: "Vaittinen, Matti" <Matti.Vaittinen@fi.rohmeurope.com>
Cc: "H. Nikolaus Schaller" <hns@goldelico.com>,
	"Matti Vaittinen" <mazziesaccount@gmail.com>,
	"Tony Lindgren" <tony@atomide.com>,
	"Grygorii Strashko" <grygorii.strashko@ti.com>,
	"Paul Barker" <paul.barker@sancloud.com>,
	"Peter Ujfalusi" <peter.ujfalusi@gmail.com>,
	"Benoît Cousson" <bcousson@baylibre.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Suman Anna" <s-anna@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: beaglebone black boot failure Linux v5.15.rc1
Date: Fri, 24 Sep 2021 13:40:35 -0500	[thread overview]
Message-ID: <CAOCHtYhC7f43wz+G-mxwutzoJDm8rhZWxf4Jd9+VHAbxPfPjTw@mail.gmail.com> (raw)
In-Reply-To: <9c80c7af-daf5-c521-fe59-1f0c222a23e1@fi.rohmeurope.com>

On Wed, Sep 22, 2021 at 4:28 AM Vaittinen, Matti
<Matti.Vaittinen@fi.rohmeurope.com> wrote:
>
> On 9/21/21 19:40, H. Nikolaus Schaller wrote:
> > Hi Matti, Tony,
> >
> >> Am 21.09.2021 um 18:07 schrieb Suman Anna <s-anna@ti.com>:
> >>
> >> Hi Matti, Tony,
> >>
> >> On 9/21/21 2:47 AM, Tony Lindgren wrote:
> >>> * Matti Vaittinen <mazziesaccount@gmail.com> [210920 08:23]:
> >>>> Finally, adding the udelay(100); (as Tony suggested) at the end of the
> >>>> omap_reset_deassert() did make the oops go away even when pruss_tm was
> >>>> enabled. I don't know what would be a proper fix though.
> >>
> >> I have been able to boot v5.15-rc1 just fine on my BBB without any additional
> >> changes [1].
> >
> > Same for me with a v5.15-rc1 based kernel.
> >
> >> May I ask what is your BBB board version? My board is rev.A5C.
> >
> > I have an Rev B6 with EXP41 display attached. I think Matti reported a Rev C board?
>
> Oops. Yes I did. I _thought_ I have Rev-C (3?) boards. Not exactly sure
> why I think so - perhaps that was what I ordered... And I really think
> the ones connected to automated test setup at the office are Rev-C.
>
> Now that I tried to verify this - The one which I used to reproduce this
> issue (and now verify the patch from Tony) at home, seems to have say
> "PCB Rev6B" on PCB. However the u-boot says:
>
> =>  printenv board_rev
> board_rev=00C0
> =>
>
> but I have no idea where the environment variable comes from...
>
> Maybe a stupid question - how to find out the exact revision?

Run:

hexdump -e '8/1 "%c"' /sys/bus/i2c/devices/0-0050/eeprom -n 28 | cut -b 5-28

Then lookup:

https://github.com/beagleboard/image-builder/blob/master/readme.md

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

  reply	other threads:[~2021-09-24 18:41 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-16  9:15 beaglebone black boot failure Linux v5.15.rc1 Vaittinen, Matti
2021-09-17  6:14 ` Tony Lindgren
2021-09-17 10:28   ` Vaittinen, Matti
2021-09-17 10:47     ` Tony Lindgren
2021-09-17 10:57     ` Grygorii Strashko
2021-09-17 11:01       ` Grygorii Strashko
2021-09-17 11:34         ` Vaittinen, Matti
2021-09-17 12:36           ` Grygorii Strashko
2021-09-20 10:05             ` Matti Vaittinen
2021-09-21  7:47               ` Tony Lindgren
2021-09-21 16:07                 ` Suman Anna
2021-09-21 16:40                   ` H. Nikolaus Schaller
2021-09-21 16:49                     ` Suman Anna
2021-09-22  9:27                     ` Vaittinen, Matti
2021-09-24 18:40                       ` Robert Nelson [this message]
2021-09-30  8:10                         ` Tony Lindgren
2021-09-30  9:41                           ` Vaittinen, Matti
2021-09-21 20:29                   ` Drew Fustini
2021-09-21 21:49                     ` Suman Anna
2021-09-21 22:00                       ` Robert Nelson
2021-09-21 23:53                         ` Suman Anna
2021-09-22  8:44                 ` Vaittinen, Matti
2021-09-22  8:48                   ` Tony Lindgren
2021-09-30  8:06                     ` Tony Lindgren

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=CAOCHtYhC7f43wz+G-mxwutzoJDm8rhZWxf4Jd9+VHAbxPfPjTw@mail.gmail.com \
    --to=robertcnelson@gmail.com \
    --cc=Matti.Vaittinen@fi.rohmeurope.com \
    --cc=bcousson@baylibre.com \
    --cc=grygorii.strashko@ti.com \
    --cc=hns@goldelico.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mazziesaccount@gmail.com \
    --cc=paul.barker@sancloud.com \
    --cc=peter.ujfalusi@gmail.com \
    --cc=s-anna@ti.com \
    --cc=tony@atomide.com \
    /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.