[BISECTED] BeagleBone Black doesn't boot after a58147c2dbbf

[Matwey V. Kornilov]

Can somebody please advise me working CONFIG_DEBUG_UART _* values for
the board? I think I need to obtain some output from the board to
debug it further.

чт, 11 авг. 2022 г. в 09:56, Matwey V. Kornilov <matwey.kornilov at gmail.com>:
>
> чт, 11 авг. 2022 г. в 01:52, Nishanth Menon <nm at ti.com>:
> >
> > On 11:40-20220807, Matwey V. Kornilov wrote:
> > > пт, 5 авг. 2022 г. в 18:01, Robert Nelson <robertcnelson at gmail.com>:
> > > >
> > > > On Fri, Jul 29, 2022 at 12:07 PM Matwey V. Kornilov
> > > > <matwey.kornilov at gmail.com> wrote:
> > > > >
> > > > > пт, 29 июл. 2022 г. в 19:46, Tom Rini <trini at konsulko.com>:
> > > > > >
> > > > > > On Fri, Jul 29, 2022 at 07:38:28PM +0300, Matwey V. Kornilov wrote:
> > > > > > > пт, 29 июл. 2022 г. в 19:32, Tom Rini <trini at 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
>
> 3dd4e916324e doesn't work,
> 3dd4e916324e + reverted a58147c2dbbf boots:
>
> U-Boot SPL 2022.10-rc2-00029-g3dd4e91632-dirty (Aug 11 2022 - 09:50:59 +0300)
> Trying to boot from MMC1
>
>
> U-Boot 2022.10-rc2-00029-g3dd4e91632-dirty (Aug 11 2022 - 09:50:59 +0300)
>
> CPU  : AM335X-GP rev 2.1
> Model: TI AM335x BeagleBone Black
> DRAM:  512 MiB
> Core:  160 devices, 18 uclasses, devicetree: separate
> WDT:   Started wdt at 44e35000 with servicing (60s timeout)
> NAND:  0 MiB
> MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
> Loading Environment from FAT... Unable to read "uboot.env" from mmc0:1...
> <ethaddr> not set. Validating first E-fuse MAC
> Net:   eth2: ethernet at 4a100000, eth3: usb_ether
> Hit any key to stop autoboot:  0
> => i2c dev 0 ; i2c md 0x50 0x00.2 400
> Setting bus to 0
> 0000: aa 55 33 ee 41 33 33 35 42 4e 4c 54 30 30 43 30    .U3.A335BNLT00C0
> 0010: 34 34 31 34 42 42 42 4b 31 30 30 30 ff ff ff ff    4414BBBK1000....
> 0020: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
> 0030: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
> 0040: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
> 0050: 58 41 4e 30 30 31 30 30 30 58 58 58 58 58 58 58    XAN001000XXXXXXX
> 0060: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
> 0070: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
> 0080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
> 0090: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
> 00a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
>
>
>
>
> >
> > 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.
> >
> > --
> > Regards,
> > Nishanth Menon
> > Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D
>
>
>
> --
> With best regards,
> Matwey V. Kornilov



-- 
With best regards,
Matwey V. Kornilov