Skip to contentSkip to conversation

configs: vf610: increase maximum size and enforce correct limit

PATCH New Stefan Agner 3 participants 4 messages Oct 17, 2017 – Oct 31, 2017

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 configs: vf610: increase maximum size and enforce correct limit

From: Stefan Agner <[email protected]>

On Vybrid SoCs U-Boot gets loaded into GFX SRAM which is 512KiB. Currently 32KiB is reserved for the IMX header. However, this is not reflected in the size limit. In v2017.11-rc2 the actual size limit (512KiB-32KiB) has been reached for Colibri VF61, which lead to a successful build of U-Boot but not a working binary.

The IMX header is much smaller than 32KiB, typically around 1KiB. Decrease the reserved size to 4KiB and specify the correct U-Boot size limit. Apply this new base address and limit for all Vybrid based boards.

---

 include/configs/colibri_vf.h | 4 ++--
 include/configs/pcm052.h     | 4 ++--
 include/configs/vf610twr.h   | 4 ++--
 3 files changed, 6 insertions(+), 6 deletions(-)
include/configs/colibri_vf.h +2 -2
index 8166aa4afb..bf3bbffe24 100644
@@ -75,8 +75,8 @@
 #define CONFIG_FDTADDR			0x84000000
 
 /* We boot from the gfxRAM area of the OCRAM. */
-#define CONFIG_SYS_TEXT_BASE		0x3f408000
-#define CONFIG_BOARD_SIZE_LIMIT		524288
+#define CONFIG_SYS_TEXT_BASE		0x3f401000
+#define CONFIG_BOARD_SIZE_LIMIT		520192
 
 #define SD_BOOTCMD \
 	"sdargs=root=/dev/mmcblk0p2 rw rootwait\0"	\
include/configs/pcm052.h +2 -2
index 8144a83db2..060928bd30 100644
@@ -89,8 +89,8 @@
 #define CONFIG_LOADADDR			0x82000000
 
 /* We boot from the gfxRAM area of the OCRAM. */
-#define CONFIG_SYS_TEXT_BASE		0x3f408000
-#define CONFIG_BOARD_SIZE_LIMIT		524288
+#define CONFIG_SYS_TEXT_BASE		0x3f401000
+#define CONFIG_BOARD_SIZE_LIMIT		520192
 
 /* if no target-specific extra environment settings were defined by the
    target, define an empty one */
include/configs/vf610twr.h +2 -2
index 3430f27c40..ddfcd6f618 100644
@@ -79,8 +79,8 @@
 #define CONFIG_SYS_LOAD_ADDR		0x82000000
 
 /* We boot from the gfxRAM area of the OCRAM. */
-#define CONFIG_SYS_TEXT_BASE		0x3f408000
-#define CONFIG_BOARD_SIZE_LIMIT		524288
+#define CONFIG_SYS_TEXT_BASE		0x3f401000
+#define CONFIG_BOARD_SIZE_LIMIT		520192
 
 /*
  * We do have 128MB of memory on the Vybrid Tower board. Leave the last
Signature · 1 line
2.14.2
#1 lore raw

PATCH 1/1 configs: vf610: increase maximum size and enforce correct limit

Hi Tom, Stefano,

Any chance to get this still into 2017.11? It allows to use 2017.11 on my board...

--
Stefan

Quoted 66 lines · Stefan Agner

From: Stefan Agner <[email protected]>

On Vybrid SoCs U-Boot gets loaded into GFX SRAM which is 512KiB. Currently 32KiB is reserved for the IMX header. However, this is not reflected in the size limit. In v2017.11-rc2 the actual size limit (512KiB-32KiB) has been reached for Colibri VF61, which lead to a successful build of U-Boot but not a working binary.

The IMX header is much smaller than 32KiB, typically around 1KiB. Decrease the reserved size to 4KiB and specify the correct U-Boot size limit. Apply this new base address and limit for all Vybrid based boards.

---

 include/configs/colibri_vf.h | 4 ++--
 include/configs/pcm052.h     | 4 ++--
 include/configs/vf610twr.h   | 4 ++--
 3 files changed, 6 insertions(+), 6 deletions(-)
include/configs/colibri_vf.h +2 -2
index 8166aa4afb..bf3bbffe24 100644
@@ -75,8 +75,8 @@
 #define CONFIG_FDTADDR			0x84000000
 
 /* We boot from the gfxRAM area of the OCRAM. */
-#define CONFIG_SYS_TEXT_BASE		0x3f408000
-#define CONFIG_BOARD_SIZE_LIMIT		524288
+#define CONFIG_SYS_TEXT_BASE		0x3f401000
+#define CONFIG_BOARD_SIZE_LIMIT		520192
 
 #define SD_BOOTCMD \
 	"sdargs=root=/dev/mmcblk0p2 rw rootwait\0"	\
include/configs/pcm052.h +2 -2
index 8144a83db2..060928bd30 100644
@@ -89,8 +89,8 @@
 #define CONFIG_LOADADDR			0x82000000
 
 /* We boot from the gfxRAM area of the OCRAM. */
-#define CONFIG_SYS_TEXT_BASE		0x3f408000
-#define CONFIG_BOARD_SIZE_LIMIT		524288
+#define CONFIG_SYS_TEXT_BASE		0x3f401000
+#define CONFIG_BOARD_SIZE_LIMIT		520192
 
 /* if no target-specific extra environment settings were defined by the
    target, define an empty one */
include/configs/vf610twr.h +2 -2
index 3430f27c40..ddfcd6f618 100644
@@ -79,8 +79,8 @@
 #define CONFIG_SYS_LOAD_ADDR		0x82000000
 
 /* We boot from the gfxRAM area of the OCRAM. */
-#define CONFIG_SYS_TEXT_BASE		0x3f408000
-#define CONFIG_BOARD_SIZE_LIMIT		524288
+#define CONFIG_SYS_TEXT_BASE		0x3f401000
+#define CONFIG_BOARD_SIZE_LIMIT		520192
 
 /*
  * We do have 128MB of memory on the Vybrid Tower board. Leave the last
#2 lore raw

PATCH 1/1 configs: vf610: increase maximum size and enforce correct limit

Quoted 4 lines · Stefan Agner

Hi Tom, Stefano,

Any chance to get this still into 2017.11? It allows to use 2017.11 on my board...

Stefano, this is your call, thanks!

Quoted 75 lines

--
Stefan

Quoted 56 lines · Stefan Agner

From: Stefan Agner <[email protected]>

On Vybrid SoCs U-Boot gets loaded into GFX SRAM which is 512KiB. Currently 32KiB is reserved for the IMX header. However, this is not reflected in the size limit. In v2017.11-rc2 the actual size limit (512KiB-32KiB) has been reached for Colibri VF61, which lead to a successful build of U-Boot but not a working binary.

The IMX header is much smaller than 32KiB, typically around 1KiB. Decrease the reserved size to 4KiB and specify the correct U-Boot size limit. Apply this new base address and limit for all Vybrid based boards.

---

 include/configs/colibri_vf.h | 4 ++--
 include/configs/pcm052.h     | 4 ++--
 include/configs/vf610twr.h   | 4 ++--
 3 files changed, 6 insertions(+), 6 deletions(-)
include/configs/colibri_vf.h +2 -2
index 8166aa4afb..bf3bbffe24 100644
@@ -75,8 +75,8 @@
 #define CONFIG_FDTADDR			0x84000000
 
 /* We boot from the gfxRAM area of the OCRAM. */
-#define CONFIG_SYS_TEXT_BASE		0x3f408000
-#define CONFIG_BOARD_SIZE_LIMIT		524288
+#define CONFIG_SYS_TEXT_BASE		0x3f401000
+#define CONFIG_BOARD_SIZE_LIMIT		520192
 
 #define SD_BOOTCMD \
 	"sdargs=root=/dev/mmcblk0p2 rw rootwait\0"	\
include/configs/pcm052.h +2 -2
index 8144a83db2..060928bd30 100644
@@ -89,8 +89,8 @@
 #define CONFIG_LOADADDR			0x82000000
 
 /* We boot from the gfxRAM area of the OCRAM. */
-#define CONFIG_SYS_TEXT_BASE		0x3f408000
-#define CONFIG_BOARD_SIZE_LIMIT		524288
+#define CONFIG_SYS_TEXT_BASE		0x3f401000
+#define CONFIG_BOARD_SIZE_LIMIT		520192
 
 /* if no target-specific extra environment settings were defined by the
    target, define an empty one */
include/configs/vf610twr.h +0 -0
index 3430f27c40..ddfcd6f618 100644

include/configs/vf610twr.h line 86

Quoted 10 lines
include/configs/vf610twr.h +2 -2
@@ -79,8 +79,8 @@
 #define CONFIG_SYS_LOAD_ADDR		0x82000000
 
 /* We boot from the gfxRAM area of the OCRAM. */
-#define CONFIG_SYS_TEXT_BASE		0x3f408000
-#define CONFIG_BOARD_SIZE_LIMIT		524288
+#define CONFIG_SYS_TEXT_BASE		0x3f401000
+#define CONFIG_BOARD_SIZE_LIMIT		520192
 
 /*
  * We do have 128MB of memory on the Vybrid Tower board. Leave the last

_______________________________________________
U-Boot mailing list
U-Boot at lists.denx.de
https://lists.denx.de/listinfo/u-boot

Signature · 8 lines
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20171030/72b37f2f/attachment.sig>
#3 lore raw

PATCH 1/1 configs: vf610: increase maximum size and enforce correct limit

Hi Tom, Stefan,

Quoted 7 lines · Tom Rini
Quoted 4 lines · Stefan Agner

Hi Tom, Stefano,

Any chance to get this still into 2017.11? It allows to use 2017.11 on my board...

Stefano, this is your call, thanks!

I looking into the list to pick up all remaining patches - this go in !

Regards,
Stefano

Quoted 77 lines
Quoted 76 lines

--
Stefan

Quoted 56 lines · Stefan Agner

From: Stefan Agner <[email protected]>

On Vybrid SoCs U-Boot gets loaded into GFX SRAM which is 512KiB. Currently 32KiB is reserved for the IMX header. However, this is not reflected in the size limit. In v2017.11-rc2 the actual size limit (512KiB-32KiB) has been reached for Colibri VF61, which lead to a successful build of U-Boot but not a working binary.

The IMX header is much smaller than 32KiB, typically around 1KiB. Decrease the reserved size to 4KiB and specify the correct U-Boot size limit. Apply this new base address and limit for all Vybrid based boards.

---

 include/configs/colibri_vf.h | 4 ++--
 include/configs/pcm052.h     | 4 ++--
 include/configs/vf610twr.h   | 4 ++--
 3 files changed, 6 insertions(+), 6 deletions(-)
include/configs/colibri_vf.h +2 -2
index 8166aa4afb..bf3bbffe24 100644
@@ -75,8 +75,8 @@
 #define CONFIG_FDTADDR			0x84000000
 
 /* We boot from the gfxRAM area of the OCRAM. */
-#define CONFIG_SYS_TEXT_BASE		0x3f408000
-#define CONFIG_BOARD_SIZE_LIMIT		524288
+#define CONFIG_SYS_TEXT_BASE		0x3f401000
+#define CONFIG_BOARD_SIZE_LIMIT		520192
 
 #define SD_BOOTCMD \
 	"sdargs=root=/dev/mmcblk0p2 rw rootwait\0"	\
include/configs/pcm052.h +2 -2
index 8144a83db2..060928bd30 100644
@@ -89,8 +89,8 @@
 #define CONFIG_LOADADDR			0x82000000
 
 /* We boot from the gfxRAM area of the OCRAM. */
-#define CONFIG_SYS_TEXT_BASE		0x3f408000
-#define CONFIG_BOARD_SIZE_LIMIT		524288
+#define CONFIG_SYS_TEXT_BASE		0x3f401000
+#define CONFIG_BOARD_SIZE_LIMIT		520192
 
 /* if no target-specific extra environment settings were defined by the
    target, define an empty one */
include/configs/vf610twr.h +0 -0
index 3430f27c40..ddfcd6f618 100644

include/configs/vf610twr.h line 86

Quoted 10 lines
include/configs/vf610twr.h +2 -2
@@ -79,8 +79,8 @@
 #define CONFIG_SYS_LOAD_ADDR		0x82000000
 
 /* We boot from the gfxRAM area of the OCRAM. */
-#define CONFIG_SYS_TEXT_BASE		0x3f408000
-#define CONFIG_BOARD_SIZE_LIMIT		524288
+#define CONFIG_SYS_TEXT_BASE		0x3f401000
+#define CONFIG_BOARD_SIZE_LIMIT		520192
 
 /*
  * We do have 128MB of memory on the Vybrid Tower board. Leave the last

_______________________________________________
U-Boot mailing list
U-Boot at lists.denx.de
https://lists.denx.de/listinfo/u-boot

Signature · 5 lines
=====================================================================
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de
=====================================================================