fully loads u-boot from the same partition as SPL. SD card
and UART continue to boot.
Thanks Pali!
Tested-by: Martin Rowe
> ---
> board/solidrun/clearfog/README | 20 ++--
> 1 file changed, 10 insertions(+), 10 deletions(-)
>
> diff --git a/board/solidrun/clearfog
4K Native disks CONFIG_MVEBU_SPL_SATA_BLKSZ must be set to 4096.
>
> Signed-off-by: Pali Rohár
I only have 512 drives to test with, but there are no regressions with
MMC (SD and eMMC), SPI, UART, or SATA (512) booting on Clearfog.
Tested-by: Martin Rowe
> ---
> arch/arm/mach
it will be detected by Linux.
Ported from vendor repo at https://github.com/SolidRun/u-boot
Signed-off-by: Martin Rowe
---
Resend with correct header
Fixed spacing and removed __maybe_unused
arch/arm/mach-mvebu/Kconfig| 1 +
board/solidrun/clearfog/clearfog.c | 33
On Mon, 27 Mar 2023 at 07:26, Stefan Roese wrote:
>
> Hi Martin,
>
> On 3/25/23 01:02, Martin Rowe wrote:
> > [upstream of vendor commit 19a96f7c40a8fc1d0a6546ac2418d966e5840a99]
> >
> > The Clearfog devices have only one SDHC device. This is either eMMC if
> >
it will be detected by Linux.
Ported from vendor repo at https://github.com/SolidRun/u-boot
Signed-off-by: Martin Rowe
---
Fixed spacing and removed __maybe_unused
arch/arm/mach-mvebu/Kconfig| 1 +
board/solidrun/clearfog/clearfog.c | 33 ++
2 files changed, 34
eded to do with this patch series?
>
> Because the discussion in this patch thread just pointed to different
> issues, not related this this patch series.
Tested this patch with everything that just went into next, plus the
switch fix, and all boot successfully:
- MMC
- eMMC
- SD card
- UART via kwboot
- SATA (including UART via kwboot)
- SPI (including UART via kwboot)
- UART
Tested-by: Martin Rowe
it will be detected by Linux.
Ported from vendor repo at https://github.com/SolidRun/u-boot
Signed-off-by: Martin Rowe
---
arch/arm/mach-mvebu/Kconfig| 1 +
board/solidrun/clearfog/clearfog.c | 32 ++
2 files changed, 33 insertions(+)
diff --git a/arch/arm/mach
This new clearfog_spi_defconfig file is a copy of existing
clearfog_defconfig file modified to instruct build system to generate
final kwbimage for SPI booting and to store the environment in SPI.
Signed-off-by: Martin Rowe
---
configs/{clearfog_defconfig => clearfog_spi_defconfig} | 2 +-
A388 Clearfog MMC is either SD Card or eMMC with different behaviour for
both. Setting the device to non-removable in the u-boot.dtsi allows both
to correctly detect the device.
Signed-off-by: Martin Rowe
---
arch/arm/dts/armada-388-clearfog-u-boot.dtsi | 1 +
1 file changed, 1 insertion
/2023-March/511038.html
Signed-off-by: Martin Rowe
Martin Rowe (3):
arm: mvebu: clearfog: Fix MMC detection
arm: mvebu: clearfog: Add defconfig for SPI booting
arm: mvebu: clearfog: Detect MMC vs SDHC and fixup fdt
arch/arm/dts/armada-388-clearfog-u-boot.dtsi | 1 +
arch/arm/mach-mvebu
> 2 files changed, 48 insertions(+)
>
> --
> 2.20.1
>
Tested-by: Martin Rowe
On Thu, 23 Mar 2023 at 19:01, Pali Rohár wrote:
>
> On Thursday 23 March 2023 12:24:13 Martin Rowe wrote:
> > On Wed, 22 Mar 2023 at 19:09, Pali Rohár wrote:
> > >
> > > On Wednesday 22 March 2023 18:59:45 Pali Rohár wrote:
> > > > On Wednesda
On Wed, 22 Mar 2023 at 19:09, Pali Rohár wrote:
>
> On Wednesday 22 March 2023 18:59:45 Pali Rohár wrote:
> > On Wednesday 22 March 2023 13:45:56 Martin Rowe wrote:
> > > On Wed, 22 Mar 2023 at 12:38, Martin Rowe wrote:
> > > >
> > > > On
On Wed, 22 Mar 2023 at 18:09, Pali Rohár wrote:
>
> On Wednesday 22 March 2023 11:14:42 Martin Rowe wrote:
> > On Tue, 21 Mar 2023 at 17:26, Pali Rohár wrote:
> >
> > > On Tuesday 21 March 2023 08:34:24 Martin Rowe wrote:
> > > > On Mon,
On Wed, 22 Mar 2023 at 12:38, Martin Rowe wrote:
>
> On Tue, 21 Mar 2023 at 08:08, Pali Rohár wrote:
>>
>> On Tuesday 21 March 2023 08:01:16 Martin Rowe wrote:
>> > On Mon, 20 Mar 2023 at 17:33, Pali Rohár wrote:
>> >
>> > > On Monday 20 March
On Tue, 21 Mar 2023 at 08:08, Pali Rohár wrote:
> On Tuesday 21 March 2023 08:01:16 Martin Rowe wrote:
> > On Mon, 20 Mar 2023 at 17:33, Pali Rohár wrote:
> >
> > > On Monday 20 March 2023 11:48:59 Martin Rowe wrote:
> > > > On Sun, 19
On Tue, 21 Mar 2023 at 17:26, Pali Rohár wrote:
> On Tuesday 21 March 2023 08:34:24 Martin Rowe wrote:
> > On Mon, 20 Mar 2023 at 21:33, Pali Rohár wrote:
> >
> > > On Monday 20 March 2023 18:45:01 Pali Rohár wrote:
> > > > On Monday 20 March 2023 12:01:03
On Mon, 20 Mar 2023 at 21:33, Pali Rohár wrote:
> On Monday 20 March 2023 18:45:01 Pali Rohár wrote:
> > On Monday 20 March 2023 12:01:03 Martin Rowe wrote:
> > > On Sun, 19 Mar 2023 at 18:20, Pali Rohár wrote:
> > >
> > > > On Sunday 19 March 2023 17:47:5
On Mon, 20 Mar 2023 at 19:42, Pali Rohár wrote:
> On Monday 20 March 2023 12:01:03 Martin Rowe wrote:
> > Dedicated UART still works, patching an MMC for UART with kwboot still
> > hangs after finishing transfer; no change.
>
> One more question. Did you set boot mod
On Mon, 20 Mar 2023 at 17:33, Pali Rohár wrote:
> On Monday 20 March 2023 11:48:59 Martin Rowe wrote:
> > On Sun, 19 Mar 2023 at 16:22, Pali Rohár wrote:
> >
> > > On Sunday 19 March 2023 00:32:01 Martin Rowe wrote:
> > > > On Mon, 6 Mar 2023 at 11:53, Pali R
On Sun, 19 Mar 2023 at 18:20, Pali Rohár wrote:
> On Sunday 19 March 2023 17:47:57 Pali Rohár wrote:
> > On Sunday 19 March 2023 03:30:33 Martin Rowe wrote:
> > > On Sun, 5 Mar 2023 at 11:55, Pali Rohár wrote:
> > >
> > > > On Sunday 05 March 2023 04:21:42
On Sun, 19 Mar 2023 at 16:22, Pali Rohár wrote:
> On Sunday 19 March 2023 00:32:01 Martin Rowe wrote:
> > On Mon, 6 Mar 2023 at 11:53, Pali Rohár wrote:
> >
> > > Could you try to print mmc->part_config (ideally as early as possible)?
> > >
> >
> &
On Sun, 5 Mar 2023 at 11:55, Pali Rohár wrote:
> On Sunday 05 March 2023 04:21:42 Martin Rowe wrote:
> > On Sat, 4 Mar 2023 at 10:51, Pali Rohár wrote:
> >
> > > Improve code for checking strapping pins which specifies boot mode
> source.
> > >
> >
On Mon, 6 Mar 2023 at 18:40, Pali Rohár wrote:
> On Monday 06 March 2023 11:15:35 Martin Rowe wrote:
> > On Sun, 5 Mar 2023 at 16:04, Pali Rohár wrote:
> > > Could you try another test by completely erasing BOOT0, BOOT1 and USER
> > > > dat
On Mon, 6 Mar 2023 at 11:53, Pali Rohár wrote:
> On Monday 06 March 2023 11:15:35 Martin Rowe wrote:
> > On Sun, 5 Mar 2023 at 16:04, Pali Rohár wrote:
> >
> > > On Sunday 05 March 2023 12:46:34 Pali Rohár wrote:
> > > > On Sunday 05 March 2023 02:24:27 Ma
On Sun, 5 Mar 2023 at 16:04, Pali Rohár wrote:
> On Sunday 05 March 2023 12:46:34 Pali Rohár wrote:
> > On Sunday 05 March 2023 02:24:27 Martin Rowe wrote:
> > > On Sat, 4 Mar 2023 at 10:40, Pali Rohár wrote:
> > >
> > > > Boot configuration stored in
On Sun, 5 Mar 2023 at 12:43, Pali Rohár wrote:
> On Sunday 05 March 2023 21:31:00 Martin Rowe wrote:
> > [upstream of vendor commit 19a96f7c40a8fc1d0a6546ac2418d966e5840a99]
> >
> > The Clearfog devices have only one SDHC device. This is either eMMC if
> > it is p
On Sun, 5 Mar 2023 at 12:29, Pali Rohár wrote:
> On Sunday 05 March 2023 21:30:59 Martin Rowe wrote:
> > This new clearfog_spi_defconfig file is a copy of existing
> > clearfog_defconfig file modified to instruct build system to generate
> > final kwbimage for SPI
On Sun, 5 Mar 2023 at 12:27, Pali Rohár wrote:
> On Sunday 05 March 2023 21:30:58 Martin Rowe wrote:
> > Ensure that functionality of generated configs is identical between SATA
> > and MMC defconfigs for Clearfog boards. The only expected difference is
> > the boot mode and
On Sun, 5 Mar 2023 at 12:19, Pali Rohár wrote:
> On Sunday 05 March 2023 21:30:57 Martin Rowe wrote:
> > A388 Clearfog MMC is either SD Card or eMMC with different behaviour for
> > both. Setting MMC_BROKEN_CD allows both to correctly detect MMC.
>
> When you are send
it will be detected by Linux.
Ported from vendor repo at https://github.com/SolidRun/u-boot
Signed-off-by: Martin Rowe
---
board/solidrun/clearfog/clearfog.c | 42 ++
configs/clearfog_defconfig | 1 +
configs/clearfog_sata_defconfig| 1 +
configs
This new clearfog_spi_defconfig file is a copy of existing
clearfog_defconfig file modified to instruct build system to generate
final kwbimage for SPI booting and to store the environment in SPI.
Signed-off-by: Martin Rowe
---
configs/{clearfog_sata_defconfig => clearfog_spi_defconfig}
Ensure that functionality of generated configs is identical between SATA
and MMC defconfigs for Clearfog boards. The only expected difference is
the boot mode and environment location.
Signed-off-by: Martin Rowe
---
configs/clearfog_defconfig | 1 +
configs/clearfog_sata_defconfig | 11
A388 Clearfog MMC is either SD Card or eMMC with different behaviour for
both. Setting MMC_BROKEN_CD allows both to correctly detect MMC.
Signed-off-by: Martin Rowe
---
configs/clearfog_defconfig | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/configs/clearfog_defconfig b
depends on this patch series (has been merged to
u-boot-marvell/next):
https://lists.denx.de/pipermail/u-boot/2023-March/511038.html
Signed-off-by: Martin Rowe
Martin Rowe (4):
arm: mvebu: clearfog: Fix MMC detection
arm: mvebu: clearfog: Align defconfigs
arm: mvebu: clearfog: Add defconfig
On Sat, 4 Mar 2023 at 10:51, Pali Rohár wrote:
> Improve code for checking strapping pins which specifies boot mode source.
>
> Martin, could you test if Clearfog can be still configured into UART
> booting mode via HW switches and if it still works correctly? First
> patch is reverting UART
On Sat, 4 Mar 2023 at 10:51, Pali Rohár wrote:
> This allows to merge BOOT_FROM_MMC and BOOT_FROM_MMC_ALT constants to one
> macro. And also allows to extend other BOOT_FROM_* macros for other
> variants.
>
> Signed-off-by: Pali Rohár
> ---
> arch/arm/mach-mvebu/cpu.c | 16
On Sat, 4 Mar 2023 at 10:40, Pali Rohár wrote:
> Boot configuration stored in EXT_CSC register is completely ignored by
> BootROM:
>
> https://lore.kernel.org/u-boot/CAOAjy5SYPPzWKok-BSGYwZwcKOQt_aZPgh6FTbrFd3F=8dm...@mail.gmail.com/
>
> Reflect this eMMC booting in documentation and in the
On Sat, 4 Mar 2023 at 11:20, Pali Rohár wrote:
> On Saturday 04 March 2023 11:50:34 Pali Rohár wrote:
> > Disassembling A385 BootROM binary reveal how BootROM interprets strapping
> > pins for Boot Device Mode. All possible options are:
> >
> > 0x00..0x07 -> Parallel NOR
> > 0x08..0x15 ->
On Mon, 27 Feb 2023 at 08:04, Pali Rohár wrote:
> On Monday 27 February 2023 08:44:30 Stefan Roese wrote:
> > Hi Pali,
> >
> > On 2/25/23 23:00, Pali Rohár wrote:
> > > On Tuesday 21 February 2023 21:18:26 Pali Rohár wrote:
> > > > This patch series contains various improvements and fixes for
>
On Sun, 26 Feb 2023 at 11:18, Pali Rohár wrote:
> On Sunday 26 February 2023 01:45:16 Martin Rowe wrote:
> > On Sat, 25 Feb 2023 at 22:14, Pali Rohár wrote:
> > > On Saturday 25 February 2023 22:49:56 Pali Rohár wrote:
> > > > On Saturday 25 February 2
> > > I'm not sure how to run proper timing tests on the process, but
> > > stopwatch timing just between seeing "Trying to boot" and "U-Boot
> > > 2023.04-rc2" showed the return to BootROM under 1 second, and the
> > > direct from SPI around 4 seconds. I thought the goal of loading from
> > > SPI
On Sat, 25 Feb 2023 at 21:16, Pali Rohár wrote:
> I think that the remaining part is to patch linux DTB file at runtime
> for emmc support. So if u-boot mmc device is of eMMC type then fixup
> linux dtb file and others do nothing.
One question I didn't think of when suggesting this: does runtime
On Sat, 25 Feb 2023 at 22:14, Pali Rohár wrote:
> On Saturday 25 February 2023 22:49:56 Pali Rohár wrote:
> > On Saturday 25 February 2023 11:42:19 Martin Rowe wrote:
> > > A388 Clearfog MMC is either SD Card or eMMC with different behaviour for
> > > both. Settin
> While I haven't tested this patchset - I have tested SPI booting with
> v2022.01 after applying lots of patches.
> I found that the magic value reported by bootrom when booting from SPI will
> be 0x34 on clearfog.
> The current sources only handle 0x32, hence having or not having SPL_SPI will
On Sat, 25 Feb 2023 at 07:41, Pali Rohár wrote:
>
> On Saturday 25 February 2023 11:42:20 Martin Rowe wrote:
> > This new clearfog_spi_defconfig file is copy of existing
> > clearfog_defconfig file and changed to instruct build system to
> > generate final kwbimage for
This new clearfog_spi_defconfig file is copy of existing
clearfog_defconfig file and changed to instruct build system to
generate final kwbimage for SPI booting and to store the
environment in SPI as well.
Signed-off-by: Martin Rowe
---
.../{clearfog_sata_defconfig => clearfog_spi_defcon
A388 Clearfog MMC is either SD Card or eMMC with different behaviour for
both. Setting MMC_BROKEN_CD allows both to correctly detect MMC.
Signed-off-by: Martin Rowe
---
configs/clearfog_defconfig | 3 +--
configs/clearfog_sata_defconfig | 8
2 files changed, 5 insertions(+), 6
Minor defconfig updates to Pali's RFC "arm: mvebu: Various fixes" for
SolidRun's A388 Clearfog devices.
Martin Rowe (2):
arm: mvebu: clearfog: Fix MMC detection
arm: mvebu: clearfog: Add defconfig for SPI booting
configs/clearfog_defconfig| 3 +-
> When generating this patch, use git options -M, -C and
> --find-copies-harder. It will detect that you created this file as copy
> from other file and generate better diff.
Will do.
This thread has gotten quite long! I've:
- tested all the boot modes and bubt update types
- created the SPI
> Please note that this patch is sent to the list a s reply to the
> RFC patchset from Pali. Something went wrong here, so that the
> commit subject was not used. Also for the 2nd patch.
Ah, sorry, I'm not really set up for this. The first patch branches
from Pali's RFC, though, so maybe it would
[PATCH 2/2] arm: mvebu: clearfog: Add defconfig for SPI booting
This new clearfog_spi_defconfig file is copy of existing
clearfog_defconfig file and changed to instruct build system to
generate final kwbimage for SPI booting and to store the
environment in SPI as well.
Signed-off-by: Martin Rowe
[PATCH 1/2] arm: mvebu: clearfog: Fix MMC detection
A388 Clearfog MMC is either SD Card or eMMC with different behaviour for
both. Setting MMC_BROKEN_CD allows both to correctly detect MMC.
Signed-off-by: Martin Rowe
---
configs/clearfog_defconfig | 3 +--
configs/clearfog_sata_defconfig
> > boot0 - zeroed
> > boot1 - u-boot (with local version 'boot1')
> > user - u-boot (with local version 'user')
> Can you check if boot_ack argument has some effect on the initial
> choice? Or if completely disabling boot partitions (boot_enable to 0)
> have some effect?
boot_ack doesn't appear
> > > Have you tried booting from eMMC boot partition or eMMC user data
> > > partition? Because all 3 options should work, but I'm not fully sure if
> > > BootROM choose partition from eMMC register or if tries all 3 in some
> > > order. This is something which needs to be checked and verified.
>
Hi
> Could you send a patch which adds appropriate defconfig file for SPI
> boot? So this configuration would be tested in U-Boot CI automatically.
Will do. Does it need to be the same as the other defconfigs
otherwise? I suggest putting the environment in SPI as well if u-boot
is already there
with these changes are great! Thanks.
Tested-by: Martin Rowe
Martin
diff --git a/arch/arm/dts/armada-388-clearfog.dts
b/arch/arm/dts/armada-388-clearfog.dts
index e4164f49b2..29a608abcf 100644
--- a/arch/arm/dts/armada-388-clearfog.dts
+++ b/arch/arm/dts/armada-388-clearfog.dts
@@ -101,7 +101,7
Stefan,
> Could you please test with this attached patch, if this fixes this issue
> on your clearfog?
Your patch resolves the issue. Thanks for your fast work!
Regards
Martin
Tony,
> Did you build this clearfog board as is? i.e. did you make any change
> in the clearfog_defconfig?
clearfog_defconfig with:
CONFIG_MVEBU_SPL_BOOT_DEVICE_SATA=y
CONFIG_SPL_SATA=y
Plus a dts patch to sdhci@d8000 to make it work for eMMC (swap
cd-gpios for non-removable)
Plus a workaround
Hi,
Commit 5387b093 was a fix for early_init_done causing issues on Pogo
v4 [1]. The fix breaks armada-388-clearfog because the boot hangs
indefinitely.
It appears that the cause is an infinite loop in __udelay due to
get_ticks() always returning 0. After adding some printf statements it
became
Hello again
> So in order to move forward, the current plan is to find out/bisect first
> commit after v2021.01 which has introduced this BootROM SD/eMMC/SATA boot
> regression and inform involved folks (Author and Commiter) accordingly with a
> proper bug report.
I did try to bisect the eMMC
On Mon, 9 Jan 2023 at 21:34, Petr Štetiar wrote:
>
> Martin Rowe [2023-01-03 03:20:49]:
>
> [Adding Florian, Tomasz and Oli to the Cc: loop]
>
> Hi,
>
> > I'm following up on this bug report from September (
> > https://lists.denx.de/pipermail/u-boot/2022-Septe
Hi,
I'm following up on this bug report from September (
https://lists.denx.de/pipermail/u-boot/2022-September/494811.html )
I also hit this issue on my Clearfog Pro when booting with eMMC.
Florian's bug report was incredibly helpful in isolating the issue.
I've gone a bit further and gotten
63 matches
Mail list logo
