• State
  • Locked Locked
  • Replies 0 replies
  • Subscribers 97 subscribers
  • Views 521 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Increment malloc pool (uboot) in DM8168-EVM

David Soto - RidgeRun
Genius 3700 points

Hi all,

I'm using the following hardware and software:

  • DM8168-EVM
  • ezsdk 5.03.01.15


I'm trying to increment the malloc pool in order to use bzip2 in uboot which needs at least 4MB to work properly, however when I edit the file ti8168_evm.h located in src/include/configs to change the pool from

#define CONFIG_SYS_MALLOC_LEN (CONFIG_ENV_SIZE + (32 * 1024))

to 

#define CONFIG_SYS_MALLOC_LEN (CONFIG_ENV_SIZE + (4 * 1024 * 1024))

I got the following error:

m8168/u-boot.lds >u-boot.lds
start.S: Assembler messages:
start.S:161: Error: invalid constant (402000) after fixup
start.S:357: Error: invalid constant (402000) after fixup
start.S:358: Error: invalid constant (402000) after fixup
start.S:363: Error: invalid constant (402000) after fixup
start.S:364: Error: invalid constant (402000) after fixup
start.S:369: Error: invalid constant (402000) after fixup
start.S:370: Error: invalid constant (402000) after fixup
start.S:375: Error: invalid constant (402000) after fixup
start.S:376: Error: invalid constant (402000) after fixup
start.S:381: Error: invalid constant (402000) after fixup
start.S:382: Error: invalid constant (402000) after fixup
start.S:406: Error: invalid constant (402000) after fixup
start.S:407: Error: invalid constant (402000) after fixup
start.S:412: Error: invalid constant (402000) after fixup
start.S:413: Error: invalid constant (402000) after fixup
make[3]: *** [start.o] Error 1

I have notice that the maximum amount of memory that I can use for malloc is:

#define CONFIG_SYS_MALLOC_LEN (CONFIG_ENV_SIZE + (512 * 1024))

in this case I don't get the error mentioned above. 

According with this post  (http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/717/t/161597.aspx) uboot reallocates itself  DDR at address 0x80700000, and according with the uboot psp guide (http://processors.wiki.ti.com/index.php/TI81XX_PSP_U-Boot):

To avoid over-writing U-Boot when it is executing make sure that an address greater than 0x80800000 is used when downloading the kernel and/or filesystem images

Does that means that I can just use 1MB at maximum from uboot?

Is there any restriction to increment the amount of memory used by malloc in uboot? which could be the reason of this error?

Any suggestion about how to do this if it is possible would be really appreciated, thanks in advance

-David