Re: [BISECTED] BeagleBone Black doesn't boot after a58147c2dbbf

["Matwey V. Kornilov" <matwey.kornilov@gmail.com>]

чт, 11 авг. 2022 г. в 01:52, Nishanth Menon <nm@ti.com>:
>
> On 11:40-20220807, Matwey V. Kornilov wrote:
> > пт, 5 авг. 2022 г. в 18:01, Robert Nelson <robertcnelson@gmail.com>:
> > >
> > > On Fri, Jul 29, 2022 at 12:07 PM Matwey V. Kornilov
> > > <matwey.kornilov@gmail.com> wrote:
> > > >
> > > > пт, 29 июл. 2022 г. в 19:46, Tom Rini <trini@konsulko.com>:
> > > > >
> > > > > On Fri, Jul 29, 2022 at 07:38:28PM +0300, Matwey V. Kornilov wrote:
> > > > > > пт, 29 июл. 2022 г. в 19:32, Tom Rini <trini@konsulko.com>:
> > > > > > >
> > > > > > > On Fri, Jul 29, 2022 at 07:20:11PM +0300, Matwey V. Kornilov wrote:
> > > > > > >
> > > > > > > > Hi,
> > > > > > > >
> > > > > > > > I've tried to build an am335x_evm_defconfig u-boot to use it on my
> > > > > > > > BeagleBone Black board. Surprisingly, I've found that it doesn't work,
> > > > > > > > I see the silent console: no messages even from SPL.
> > > > > > > >
> > > > > > > > Using bisect I've found that the following commit breaks the booting:
> > > > > > > >
> > > > > > > >     a58147c2dbbf ("board: ti: common: board_detect: Do 1byte address
> > > > > > > > checks first.")
> > > > > > > >
> > > > > > > > Could you please help me?
> > > > > > >
> > > > > > > Can you share some more details about which BeagleBone Black you have,
> > > > > > > specifically the revision?
> > > > > >
> > > > > > It is an ordinary C revision. Unfortunately, I cannot remember who the
> > > > > > producer was. As far as I know many companies made BeagleBone Black
> > > > > > and EEPROM content can be different.
> > > > >
> > > > > OK, that'll help some.  Can you see what the specific part number of the
> > > > > EEPROM is?  That might also help Nishanth figure out what to do here.
> > > >
> > > > Attached here is the EEPROM dump.
> > >
> > > .U3.A335BNLT00C0
> > >
> > > Ah, the "CO"... i'm pretty sure that board was made by Element14,
> > > (they messed up the position of the "C") not that it really mattered
> > > as the A335BNLT is only used..
> >
> > Hi Robert,
> >
> > I have BBB from different vendors, and I do remember that I've
> > purchased the Element14 version at some point. However, I've messed
> > everything up and cannot figure out which board from which vendor. You
> > are the most probably right, but still I cannot confirm the origin.
> >
> > >
> > > Can you please take a quick snapshot of the eeprom, it should be...
> > > 24LC32AT-I/OT but maybe they used another variation..
> >
> > Attached here is U7. It says M67E. 24AA32A/24LC32A datasheet page 14
> > says that it should be 24LC32AI.
> >
>
> Wierd.. took me a bit of digging, but I did get the element14 beaglebone
> rev C black board as well.. but it boots fine for me.
>
> https://gist.github.com/nmenon/104f040a67a6af0b0418c95ad83ad50b
>
> I tested the very tip of master:
> 3dd4e916324e Merge https://source.denx.de/u-boot/custodians/u-boot-marvell
>
> Seemed to boot fine. Apparently it is supposed to be the same type as
> your board as well and it boots just fine on master.
>
> U7, however, on my board, is unmarked.
>
> Not really sure what to make of this.

Hi,

I am finally able to run debug UART (temporarily reverting 0dba4586),
and I see the following now:

<debug_uart>
Bad EEPROM or unknown board, cannot configure pinmux.


>
> --
> Regards,
> Nishanth Menon
> Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D



-- 
With best regards,
Matwey V. Kornilov