On 14:37-20240830, Beleswar Padhi wrote:
OSPI NOR flash was partitioned with a size of 1 MB for the initialWhy does the boot fail when > 512MB?
bootloader ("ospi.tiboot3"). On the AM69-SK board, boot failures were
sometimes observed when the initial bootloader size exceeded 512 KB. To
address this, the initial bootloader image has been optimized to beI am NOT a fan of redoing flash partition organization of platforms that
smaller than 512 KB.
Therefore, limit the first OSPI partition size to 512 KB and adjust the
remaining size across the subsequent partitions.
are already in production - all kinds of ecosystem messes happen as a
result. Alternatively - give the 512K to u-boot tispl partition and
leave all others as is - this will at least allow people's current env
to be retained.
Signed-off-by: Beleswar Padhi <b-padhi@xxxxxx>
---
arch/arm64/boot/dts/ti/k3-am69-sk.dts | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/arch/arm64/boot/dts/ti/k3-am69-sk.dts b/arch/arm64/boot/dts/ti/k3-am69-sk.dts
index 1e36965a1403..641236918379 100644
--- a/arch/arm64/boot/dts/ti/k3-am69-sk.dts
+++ b/arch/arm64/boot/dts/ti/k3-am69-sk.dts
@@ -1241,27 +1241,27 @@ partitions {
partition@0 {
label = "ospi.tiboot3";
- reg = <0x0 0x100000>;
+ reg = <0x0 0x80000>;
};
- partition@100000 {
+ partition@80000 {
label = "ospi.tispl";
- reg = <0x100000 0x200000>;
+ reg = <0x80000 0x200000>;
};
- partition@300000 {
+ partition@280000 {
label = "ospi.u-boot";
- reg = <0x300000 0x400000>;
+ reg = <0x280000 0x400000>;
};
- partition@700000 {
+ partition@680000 {
label = "ospi.env";
- reg = <0x700000 0x40000>;
+ reg = <0x680000 0x40000>;
};
- partition@740000 {
+ partition@6c0000 {
label = "ospi.env.backup";
- reg = <0x740000 0x40000>;
+ reg = <0x6c0000 0x40000>;
};
partition@800000 {
--
2.34.1