Changing boot.scr to 512MB RAM on BeagleBoard xM don't work

```
What steps will reproduce the problem?
1. create boot.script from pre-build boot.scr: dd if=boot.scr of=boot.script
bs=1 skip=72
2. change 256MB RAM to 512MB RAM
3. make the boot.scr again with mkimage tool from DevKit: ./mkimage -A arm -O
linux -T script -C none -a 0 -e 0 -n "" -d boot.script boot.scr

What is the expected output? What do you see instead?

original prebuild boot.scr looks:

'V\E8\E1\CE\EBN<\D3\00\00
\8C\00\00\00\00\00\00\00\00T\CD2\C8\00Execute
uImage.bin\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00
\84\00\00\00\00if
fatload mmc 0 82000000 uImage
then
echo ***** Kernel: /dev/mmcblk0p1/uImage *****
fi
echo ***** RootFS: /dev/mmcblk0p2 *****
setenv bootargs 'console=ttyO2,115200n8 androidboot.console=ttyO2 mem=256M
root=/dev/mmcblk0p2 rw rootfstype=ext3 rootdelay=1 init=/init ip=off
omap_vout.vid1_static_vrfb_alloc=y vram=8M omapfb.vram=0:8M'

bootm 0x82000000

and my new version look:

'V?\B3\89xN\AB\EA\D7\00\00
\8C\00\00\00\00\00\00\00\00S\99A\CB\00\00\00\00\
00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00
\00\00\00\00
\84\00\00\00\00if fatload mmc 0 82000000 uImage
then
echo ***** Kernel: /dev/mmcblk0p1/uImage *****
fi
echo ***** RootFS: /dev/mmcblk0p2 *****
setenv bootargs 'console=ttyO2,115200n8 androidboot.console=ttyO2 mem=512M
root=/dev/mmcblk0p2 rw rootfstype=ext3 rootdelay=1 init=/init ip=off
omap_vout.vid1_static_vrfb_alloc=y vram=8M omapfb.vram=0:8M'

bootm 0x82000000

so, when I want to boot with this src, it stuck on:

reading boot.scr

460 bytes read
Running bootscript from mmc ...
## Executing script at 82000000
reading uImage

2745172 bytes read
***** Kernel: /dev/mmcblk0p1/uImage *****
***** RootFS: /dev/mmcblk0p2 *****
## Booting kernel from Legacy Image at 82000000 ...
Image Name: Linux-2.6.37-g06ebbba
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2745108 Bytes = 2.6 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

then nothing happens.

What version of the product are you using? On what operating system?

TI_Android_GingerBread_2_3_4_DevKit_2_1 and my OS is Lubuntu 11.10

Please provide any additional information below.

```

Original issue reported on code.google.com by `Nesrovna...@gmail.com` on 29 Oct 2011 at 12:35

Begin by comparing the original and regenerated boot.scr payloads and the U-Boot output in the report, then inspect the TI Android GingerBread boot arguments and BeagleBoard xM RAM support. Done means identifying why the 512M boot path stops after kernel decompression and documenting or validating a reproducible correction.

Written by the indexing model from the issue text.