Skip to contentSkip to conversation

Watchdog DM conversion, sram overflow(SPL)

U-Boot Suniel Mahesh 4 participants 8 messages Jun 26, 2019

lore
Share & tools
lore
#0 lore raw

Hi,

I am trying to convert watchdog driver(omap3_wdt) on TI AM33XX platform to Driver Model. Since DM is also enabled in SPL, size of SPL image generated(with watchdog DM enabled) is bigger compared to the SRAM size(.u_boot_list section doesn't fit in the region alloted) and build is failing with the following error:

  LD      spl/drivers/usb/gadget/built-in.o
  LD      spl/drivers/usb/musb-new/built-in.o
  LD      spl/drivers/built-in.o
  LD      spl/u-boot-spl

arm-linux-ld.bfd: u-boot-spl section .u_boot_list' will not fit in region .sram' arm-linux-ld.bfd: region `.sram' overflowed by 48 bytes
make[1]: *** [spl/u-boot-spl] Error 1
make: *** [spl/u-boot-spl] Error 2

The SRAM size in the device is 130047 bytes, of which 110592 bytes are allocated for SPL Image, 6144 bytes for stack and the rest 12799 bytes for RAM Exec vectors, tracing data and static variables.

Maximum SPL image size is fixed at 110592 bytes

SPL size without Watchdog driver model is 110880 bytes.

So, the reason for such error is straight forward.

I can think of two possible approaches (might be wrong):

1. either disable DM in SPL for watchdog ?
(dm: mmc: Allow disabling driver model in SPL - by Simon Glass)

2. The stack allocated for SPL in SRAM is 6KB and 12799 bytes for RAM Exec vectors, tracing data and static variables. can we do something here, by borrowing some bytes ?

Or any possible solutions ?

Regards

Signature · 1 line
Suniel Mahesh
#1 lore raw
Quoted 29 lines · Suniel Mahesh

Hi,

I am trying to convert watchdog driver(omap3_wdt) on TI AM33XX platform to Driver Model. Since DM is also enabled in SPL, size of SPL image generated(with watchdog DM enabled) is bigger compared to the SRAM size(.u_boot_list section doesn't fit in the region alloted) and build is failing with the following error:

  LD      spl/drivers/usb/gadget/built-in.o
  LD      spl/drivers/usb/musb-new/built-in.o
  LD      spl/drivers/built-in.o
  LD      spl/u-boot-spl

arm-linux-ld.bfd: u-boot-spl section .u_boot_list' will not fit in region .sram' arm-linux-ld.bfd: region `.sram' overflowed by 48 bytes
make[1]: *** [spl/u-boot-spl] Error 1
make: *** [spl/u-boot-spl] Error 2

The SRAM size in the device is 130047 bytes, of which 110592 bytes are allocated for SPL Image, 6144 bytes for stack and the rest 12799 bytes for RAM Exec vectors, tracing data and static variables.

Maximum SPL image size is fixed at 110592 bytes

SPL size without Watchdog driver model is 110880 bytes.

So, the reason for such error is straight forward.

I can think of two possible approaches (might be wrong):

Quoted 7 lines

1. either disable DM in SPL for watchdog ?
(dm: mmc: Allow disabling driver model in SPL - by Simon Glass)

2. The stack allocated for SPL in SRAM is 6KB and 12799 bytes for RAM Exec vectors, tracing data and static variables. can we do something here, by borrowing some bytes ?

Or any possible solutions ?

00: platdata
01: CONFIG_*_TINY_* configs

If still unoccupied and want the DM for SPL in anycase, got for

02: TPL

#2 lore raw
In reply to Suniel Mahesh
Quoted 28 lines · Suniel Mahesh

Hi,

I am trying to convert watchdog driver(omap3_wdt) on TI AM33XX platform to Driver Model. Since DM is also enabled in SPL, size of SPL image generated(with watchdog DM enabled) is bigger compared to the SRAM size(.u_boot_list section doesn't fit in the region alloted) and build is failing with the following error:

   LD      spl/drivers/usb/gadget/built-in.o
   LD      spl/drivers/usb/musb-new/built-in.o
   LD      spl/drivers/built-in.o
   LD      spl/u-boot-spl

arm-linux-ld.bfd: u-boot-spl section .u_boot_list' will not fit in region .sram' arm-linux-ld.bfd: region `.sram' overflowed by 48 bytes
make[1]: *** [spl/u-boot-spl] Error 1
make: *** [spl/u-boot-spl] Error 2

The SRAM size in the device is 130047 bytes, of which 110592 bytes are allocated for SPL Image, 6144 bytes for stack and the rest 12799 bytes for RAM Exec vectors, tracing data and static variables.

Maximum SPL image size is fixed at 110592 bytes

SPL size without Watchdog driver model is 110880 bytes.

So, the reason for such error is straight forward.

I can think of two possible approaches (might be wrong):

Quoted 7 lines

1. either disable DM in SPL for watchdog ?
(dm: mmc: Allow disabling driver model in SPL - by Simon Glass)

2. The stack allocated for SPL in SRAM is 6KB and 12799 bytes for RAM Exec vectors, tracing data and static variables. can we do something here, by borrowing some bytes ?

Or any possible solutions ?

You could also disable the watchdog in SPL and only enable it later in U-Boot proper.

Thanks,
Stefan

#3 lore raw
Quoted 42 lines · Stefan Roese
Quoted 41 lines · Suniel Mahesh

Hi,

I am trying to convert watchdog driver(omap3_wdt) on TI AM33XX platform to Driver Model.
Since DM is also enabled in SPL, size of SPL image generated(with watchdog DM enabled) is
bigger compared to the SRAM size(.u_boot_list section doesn't fit in the region alloted)
and build is failing with the following error:

   LD      spl/drivers/usb/gadget/built-in.o
   LD      spl/drivers/usb/musb-new/built-in.o
   LD      spl/drivers/built-in.o
   LD      spl/u-boot-spl
arm-linux-ld.bfd: u-boot-spl section .u_boot_list' will not fit in region .sram'
arm-linux-ld.bfd: region `.sram' overflowed by 48 bytes make[1]: *** [spl/u-boot-spl] Error 1
make: *** [spl/u-boot-spl] Error 2

The SRAM size in the device is 130047 bytes, of which 110592 bytes are allocated for SPL
Image, 6144 bytes for stack and the rest 12799 bytes for RAM Exec vectors, tracing data
and static variables.

Maximum SPL image size is fixed at 110592 bytes

SPL size without Watchdog driver model is 110880 bytes.

So, the reason for such error is straight forward.

I can think of two possible approaches (might be wrong):

1. either disable DM in SPL for watchdog ?
(dm: mmc: Allow disabling driver model in SPL - by Simon Glass)
  2. The stack allocated for SPL in SRAM is 6KB and 12799 bytes for RAM Exec vectors,
tracing data and static variables. can we do something here, by borrowing some bytes ?

Quoted 4 lines
Quoted 1 line

Or any possible solutions ?

You could also disable the watchdog in SPL and only enable it later in U-Boot proper.

Agreed

Signature · 2 lines
Best regards,
Marek Vasut
#4 lore raw
In reply to Stefan Roese
Quoted 33 lines · Stefan Roese
Quoted 31 lines · Suniel Mahesh

Hi,

I am trying to convert watchdog driver(omap3_wdt) on TI AM33XX platform to Driver Model. Since DM is also enabled in SPL, size of SPL image generated(with watchdog DM enabled) is bigger compared to the SRAM size(.u_boot_list section doesn't fit in the region alloted) and build is failing with the following error:

   LD      spl/drivers/usb/gadget/built-in.o
   LD      spl/drivers/usb/musb-new/built-in.o
   LD      spl/drivers/built-in.o
   LD      spl/u-boot-spl

arm-linux-ld.bfd: u-boot-spl section .u_boot_list' will not fit in region .sram' arm-linux-ld.bfd: region `.sram' overflowed by 48 bytes
make[1]: *** [spl/u-boot-spl] Error 1
make: *** [spl/u-boot-spl] Error 2

The SRAM size in the device is 130047 bytes, of which 110592 bytes are allocated for SPL Image, 6144 bytes for stack and the rest 12799 bytes for RAM Exec vectors, tracing data and static variables.

Maximum SPL image size is fixed at 110592 bytes

SPL size without Watchdog driver model is 110880 bytes.

So, the reason for such error is straight forward.

I can think of two possible approaches (might be wrong):

1. either disable DM in SPL for watchdog ?
(dm: mmc: Allow disabling driver model in SPL - by Simon Glass)

Quoted 7 lines
Quoted 4 lines

2. The stack allocated for SPL in SRAM is 6KB and 12799 bytes for RAM Exec vectors, tracing data and static variables. can we do something here, by borrowing some bytes ?

Or any possible solutions ?

You could also disable the watchdog in SPL and only enable it later in U-Boot proper.

May be his requirement is to reset the watchdog if SPL hang or something.

#5 lore raw
Quoted 37 lines · Jagan Teki
Quoted 36 lines · Stefan Roese
Quoted 34 lines · Suniel Mahesh

Hi,

I am trying to convert watchdog driver(omap3_wdt) on TI AM33XX platform to Driver Model. Since DM is also enabled in SPL, size of SPL image generated(with watchdog DM enabled) is bigger compared to the SRAM size(.u_boot_list section doesn't fit in the region alloted) and build is failing with the following error:

   LD      spl/drivers/usb/gadget/built-in.o
   LD      spl/drivers/usb/musb-new/built-in.o
   LD      spl/drivers/built-in.o
   LD      spl/u-boot-spl

arm-linux-ld.bfd: u-boot-spl section .u_boot_list' will not fit in region .sram' arm-linux-ld.bfd: region `.sram' overflowed by 48 bytes
make[1]: *** [spl/u-boot-spl] Error 1
make: *** [spl/u-boot-spl] Error 2

The SRAM size in the device is 130047 bytes, of which 110592 bytes are allocated for SPL Image, 6144 bytes for stack and the rest 12799 bytes for RAM Exec vectors, tracing data and static variables.

Maximum SPL image size is fixed at 110592 bytes

SPL size without Watchdog driver model is 110880 bytes.

So, the reason for such error is straight forward.

I can think of two possible approaches (might be wrong):

1. either disable DM in SPL for watchdog ?
(dm: mmc: Allow disabling driver model in SPL - by Simon Glass)

2. The stack allocated for SPL in SRAM is 6KB and 12799 bytes for RAM Exec vectors, tracing data and static variables. can we do something here, by borrowing some bytes ?

Quoted 6 lines
Quoted 4 lines
Quoted 1 line

Or any possible solutions ?

You could also disable the watchdog in SPL and only enable it later in U-Boot proper.

May be his requirement is to reset the watchdog if SPL hang or something.

Non-DM WDT support can do that just fine.

Signature · 2 lines
Best regards,
Marek Vasut
#6 lore raw
Quoted 38 lines · Marek Vasut
Quoted 37 lines · Jagan Teki
Quoted 36 lines · Stefan Roese
Quoted 34 lines · Suniel Mahesh

Hi,

I am trying to convert watchdog driver(omap3_wdt) on TI AM33XX platform to Driver Model. Since DM is also enabled in SPL, size of SPL image generated(with watchdog DM enabled) is bigger compared to the SRAM size(.u_boot_list section doesn't fit in the region alloted) and build is failing with the following error:

   LD      spl/drivers/usb/gadget/built-in.o
   LD      spl/drivers/usb/musb-new/built-in.o
   LD      spl/drivers/built-in.o
   LD      spl/u-boot-spl

arm-linux-ld.bfd: u-boot-spl section .u_boot_list' will not fit in region .sram' arm-linux-ld.bfd: region `.sram' overflowed by 48 bytes
make[1]: *** [spl/u-boot-spl] Error 1
make: *** [spl/u-boot-spl] Error 2

The SRAM size in the device is 130047 bytes, of which 110592 bytes are allocated for SPL Image, 6144 bytes for stack and the rest 12799 bytes for RAM Exec vectors, tracing data and static variables.

Maximum SPL image size is fixed at 110592 bytes

SPL size without Watchdog driver model is 110880 bytes.

So, the reason for such error is straight forward.

I can think of two possible approaches (might be wrong):

1. either disable DM in SPL for watchdog ?
(dm: mmc: Allow disabling driver model in SPL - by Simon Glass)

2. The stack allocated for SPL in SRAM is 6KB and 12799 bytes for RAM Exec vectors, tracing data and static variables. can we do something here, by borrowing some bytes ?

Quoted 9 lines
Quoted 6 lines
Quoted 4 lines
Quoted 1 line

Or any possible solutions ?

You could also disable the watchdog in SPL and only enable it later in U-Boot proper.

May be his requirement is to reset the watchdog if SPL hang or something.

Non-DM WDT support can do that just fine.

My question was that can we do a Non-DM WDT in SPL, which was my first item above.

I will try for a Non-DM WDT in SPL.

Thanks Jagan, Stefan, Marek for the quick reply and suggestions.

Regards
Suniel Mahesh

#7 lore raw
Quoted 44 lines · Suniel Mahesh
Quoted 43 lines · Marek Vasut
Quoted 42 lines · Jagan Teki
Quoted 40 lines · Stefan Roese
Quoted 28 lines · Suniel Mahesh

Hi,

I am trying to convert watchdog driver(omap3_wdt) on TI AM33XX platform to Driver Model. Since DM is also enabled in SPL, size of SPL image generated(with watchdog DM enabled) is bigger compared to the SRAM size(.u_boot_list section doesn't fit in the region alloted) and build is failing with the following error:

   LD      spl/drivers/usb/gadget/built-in.o
   LD      spl/drivers/usb/musb-new/built-in.o
   LD      spl/drivers/built-in.o
   LD      spl/u-boot-spl

arm-linux-ld.bfd: u-boot-spl section .u_boot_list' will not fit in region .sram' arm-linux-ld.bfd: region `.sram' overflowed by 48 bytes
make[1]: *** [spl/u-boot-spl] Error 1
make: *** [spl/u-boot-spl] Error 2

The SRAM size in the device is 130047 bytes, of which 110592 bytes are allocated for SPL Image, 6144 bytes for stack and the rest 12799 bytes for RAM Exec vectors, tracing data and static variables.

Maximum SPL image size is fixed at 110592 bytes

SPL size without Watchdog driver model is 110880 bytes.

So, the reason for such error is straight forward.

I can think of two possible approaches (might be wrong):

Quoted 7 lines

1. either disable DM in SPL for watchdog ?
(dm: mmc: Allow disabling driver model in SPL - by Simon Glass)

2. The stack allocated for SPL in SRAM is 6KB and 12799 bytes for RAM Exec vectors, tracing data and static variables. can we do something here, by borrowing some bytes ?

Or any possible solutions ?

You could also disable the watchdog in SPL and only enable it later in U-Boot proper.

Quoted 7 lines
Quoted 4 lines
Quoted 1 line

May be his requirement is to reset the watchdog if SPL hang or something.

Non-DM WDT support can do that just fine.

My question was that can we do a Non-DM WDT in SPL, which was my first item above.

I will try for a Non-DM WDT in SPL.

Yes, non-DM in SPL is OK.

Signature · 2 lines
Best regards,
Marek Vasut