From: Mattijs Korpershoek <mkorpershoek@baylibre.com>
To: Nishanth Menon <nm@ti.com>
Cc: n-francis@ti.com, trini@konsulko.com, bb@ti.com, praneeth@ti.com,
afd@ti.com, Robert Nelson <robertcnelson@gmail.com>,
vigneshr@ti.com, u-boot@lists.denx.de
Subject: Re: [PATCH V3 0/4] board: ti: Add support for BeaglePlay
Date: Tue, 22 Aug 2023 17:55:23 +0200 [thread overview]
Message-ID: <87r0nvrs0k.fsf@baylibre.com> (raw)
In-Reply-To: <20230822154018.tcj6dlec5xanyzbc@overstay>
On mar., août 22, 2023 at 10:40, Nishanth Menon <nm@ti.com> wrote:
> On 17:33-20230822, Mattijs Korpershoek wrote:
>> On mar., août 15, 2023 at 11:44, Nishanth Menon <nm@ti.com> wrote:
>>
>> > Add support for BeaglePlay - rev 3
>> >
>> > Boot log: https://gist.github.com/nmenon/3e99b44380873263e39ba4d84788db89
>> >
>> > Full series(including dependencies) can be found at:
>> > https://github.com/nmenon/fix-k3-dt-u-boot/commits/beagleplay-v3
>> >
>> > Caveats:
>> > * I have kept networking out of picture for now as it is still in debug
>> > (See
>> > https://github.com/nmenon/fix-k3-dt-u-boot/commits/beagleplay-v3-enet-debug
>> > if anyone is interested)
>> >
>> > Changes since V2:
>> > * I have rebased to latest next branch
>> > bdc682437a67 (origin/next) Merge branch '2023-08-14-assorted-general-updates' into next
>> > * Uses config fragments by default.
>> > * Updated MAINTAINER file as well
>> >
>> > V2: https://lore.kernel.org/u-boot/20230727234446.3651836-1-nm@ti.com/
>> > V1: https://lore.kernel.org/all/20230725185253.2123433-1-nm@ti.com/
>> >
>> > Nishanth Menon (3):
>> > arm: dts: k3-am625-sk-binman: Add labels for unsigned binary
>> > board: ti: am62x: Add am62x_beagleplay_* defconfigs
>> > doc: board: ti: Add BeaglePlay documentation
>> >
>> > Robert Nelson (1):
>> > arm: dts: Add k3-am625-beagleplay
>>
>> I tried these series on top of next on my beagleplay with the intention of
>> booting U-Boot from eMMC.
>>
>> Base commit: 7e6e40c57233 ("Merge tag 'v2023.10-rc3' into next")
>>
>> I can't get this to boot. Seems to be stuck in the r5 spl.
>>
>> Boot log is:
>>
>> U-Boot SPL 2023.10-rc3-01591-ga4f9ddf99438 (Aug 22 2023 - 17:11:47 +0200)
>> SYSFW ABI: 3.1 (firmware rev 0x0009 '9.0.5--v09.00.05 (Kool Koala)')
>> SPL initial stack usage: 13400 bytes
>> Trying to boot from MMC1
>> mmc_load_image_raw_sector: mmc block read error
>> Partition 1 invalid on device 0
>> spl_register_fat_device: fat register err - -1
>> spl_load_image_fat: error reading image tispl.bin, err - -1
>> SPL: failed to boot from all boot devices
>> ### ERROR ### Please RESET the board ###
>>
>> It seems that when we try to find tispl.bin, we read from the mmc0boot0
>> hw partition instead of from the user partition.
>>
>> Per my understanding, BeaglePlay has the following (simplified) boot
>> flow:
>
> Thanks Mattijs, we have been discussing this in our discord channel, and
Indeed I saw some things on discord around this but wanted to notice a
broader audience (via the U-Boot list) that booting from eMMC was not
working for some folks.
> I have a new version I am working on. will fix it up and send it later
> today - fixing some other pending documentation aspects atm.
Looking forward to give it a try !
If it's not too much to ask, please cc me on the v4 series.
Thank you.
>
> --
> Regards,
> Nishanth Menon
> Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
prev parent reply other threads:[~2023-08-22 15:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 16:44 [PATCH V3 0/4] board: ti: Add support for BeaglePlay Nishanth Menon
2023-08-15 16:44 ` [PATCH V3 1/4] arm: dts: k3-am625-sk-binman: Add labels for unsigned binary Nishanth Menon
2023-08-15 16:44 ` [PATCH V3 2/4] arm: dts: Add k3-am625-beagleplay Nishanth Menon
2023-08-15 16:44 ` [PATCH V3 3/4] board: ti: am62x: Add am62x_beagleplay_* defconfigs Nishanth Menon
2023-08-15 16:44 ` [PATCH V3 4/4] doc: board: ti: Add BeaglePlay documentation Nishanth Menon
2023-08-22 15:33 ` [PATCH V3 0/4] board: ti: Add support for BeaglePlay Mattijs Korpershoek
2023-08-22 15:40 ` Nishanth Menon
2023-08-22 15:55 ` Mattijs Korpershoek [this message]
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=87r0nvrs0k.fsf@baylibre.com \
--to=mkorpershoek@baylibre.com \
--cc=afd@ti.com \
--cc=bb@ti.com \
--cc=n-francis@ti.com \
--cc=nm@ti.com \
--cc=praneeth@ti.com \
--cc=robertcnelson@gmail.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=vigneshr@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox