2011-06-17 10:12:27     uboot +2010+Punching holes beyond the end of an LDR is not supported

Document created by Aaronwu Employee on Sep 25, 2013
Version 1Show Document
  • View in full screen mode

2011-06-17 10:12:27     uboot +2010+Punching holes beyond the end of an LDR is not supported

Shyam sundar (INDIA)

Message: 101385   

 

Hello world,

 

I do get the following error for uboot 2010

 

Adding DXE 'u-boot' ... [initcode 488] [ELF block: 129040 @ 0x01FC0000] [ELF block: 44 @ 0xFFA08000] [ELF block: 31624 @ 0x01FDF83C] bfin-uclinux-ldr: Punching holes beyond the end of an LDR is not supported

make[1]: *** [u-boot.ldr] Error 1

make[1]: Leaving directory `/home/shyam/Desktop/uboot/2010R1'

make: *** [bf531-DWAS] Error 2

 

Even with the above error, I was able to use the ldr successfully.The following is the env config

 

#define CONFIG_ENV_IS_IN_SPI_FLASH

#define CONFIG_ENV_OFFSET    0x40000

#define CONFIG_ENV_SIZE        0x2000

#define CONFIG_ENV_SECT_SIZE    0x1000

 

 

When I used the following env config

 

#define CONFIG_ENV_IS_IN_SPI_FLASH

#define CONFIG_ENV_OFFSET    0x10000

#define CONFIG_ENV_SIZE        0x2000

#define CONFIG_ENV_SECT_SIZE    0x1000

 

I dont get error, but when I use the save command I dont see the uboot message on the console and there was a need to reflash

QuoteReplyEditDelete

 

 

2011-06-17 11:16:21     Re: uboot +2010+Punching holes beyond the end of an LDR is not supported

Mike Frysinger (UNITED STATES)

Message: 101387   

 

you're trying to embed the env sector into an image which isnt big enough to fill said sector.  so dont embed it, or move the location of embedding up.

QuoteReplyEditDelete

 

 

2011-06-20 03:17:12     Re: uboot +2010+Punching holes beyond the end of an LDR is not supported

Shyam sundar (INDIA)

Message: 101468   

 

Thanks Mike,

 

My flash erase size was 4KB, By mistake I had defined CONFIG_ENV_SECT_SIZE 0x10000 instead of  CONFIG_ENV_SECT_SIZE 0x1000. So whenever I was trying to save the env variables, some part of the u-boot was getting erased and in the next hardware reset was not able to see the booting.

QuoteReplyEditDelete

Attachments

    Outcomes