From: Konstantin Kletschke <konstantin.kletschke@inside-m2m.de>
To: barebox@lists.infradead.org
Subject: [PATCH] ARM: beaglebone: add delay in lowlevel.c
Date: Wed, 8 Jan 2025 16:18:40 +0100 [thread overview]
Message-ID: <Z36XUNDVMLVullNh@hephaistos> (raw)
Some Beaglebone Black devices are not able to cope with a warm start.
When system is powered up and booted hitting reset button (S1) or
issuing "reset" at barebox prompt the new instance of first stage gets
stuck after PLL init.
Adding a delay of ~1.8ms in lowlevel.c after PLL init solves this.
Signed-off-by: Konstantin Kletschke <konstantin.kletschke@inside-m2m.de>
---
arch/arm/boards/beaglebone/lowlevel.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/boards/beaglebone/lowlevel.c b/arch/arm/boards/beaglebone/lowlevel.c
index 5dc49dfaaf..ccae1d1122 100644
--- a/arch/arm/boards/beaglebone/lowlevel.c
+++ b/arch/arm/boards/beaglebone/lowlevel.c
@@ -97,6 +97,12 @@ extern char __dtb_z_am335x_boneblack_start[];
extern char __dtb_z_am335x_bone_common_start[];
extern char __dtb_z_am335x_bone_start[];
+static void __udelay(int us)
+{
+ volatile int i;
+ for (i = 0; i < us; i++);
+}
+
/**
* @brief The basic entry point for board initialization.
*
@@ -135,6 +141,7 @@ static noinline int beaglebone_sram_init(void)
am33xx_enable_uart0_pin_mux();
omap_debug_ll_init();
putc_ll('>');
+ __udelay(3000); // Fix for Beaglebone Black warm start after reset
barebox_arm_entry(0x80000000, sdram_size, fdt);
}
--
next reply other threads:[~2025-01-08 15:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-08 15:18 Konstantin Kletschke [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-08 15:36 Konstantin Kletschke
2025-01-07 15:01 Konstantin Kletschke
2025-01-08 14:32 ` Sascha Hauer
2025-01-08 15:14 ` Konstantin Kletschke
2025-01-08 15:19 ` Ahmad Fatoum
2025-01-08 15:27 ` Konstantin Kletschke
2025-01-08 15:31 ` Ahmad Fatoum
2025-01-08 15:38 ` Konstantin Kletschke
2025-01-08 15:46 ` Lucas Stach
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=Z36XUNDVMLVullNh@hephaistos \
--to=konstantin.kletschke@inside-m2m.de \
--cc=barebox@lists.infradead.org \
/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