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

[GoogleCodeExporter]

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

[GoogleCodeExporter]

ok, the problem is that with 256MB it is working, but for 512MB not..

Original comment by Nesrovna...@gmail.com on 2 Nov 2011 at 9:57

[GoogleCodeExporter]

Can you try with the boot.scr generated from mkbootscr script available from 
the TI Android DevKit Tools bundle available here:
http://software-dl.ti.com/dsps/dsps_public_sw/sdo_tii/TI_Android_DevKit/TI_Andro
id_GingerBread_2_3_4_DevKit_2_1/index_FDS.html

Original comment by vishvesh...@aim.com on 4 Nov 2011 at 10:50

[GoogleCodeExporter]

Hello,
I am facing similar issue.
I am working on customized board which is very similar to beagleboard. This 
board was having 256MB of RAM. I had ported Gingerbread and it was working fine.
But, with RAM upgraded to 512MB, it is not working.

The kernel can boot till console properly. But, when the bootanimation starts, 
after some time kernel is panic.
The bootargs being used are as follows:

if mmcinit 0; then

                setenv memsize "512M"
                setenv loadaddr 0x81c00000
                setenv console "ttyS2,115200n8  init=/init 
androidboot.console=ttyS2"
                setenv mmcroot "/dev/mmcblk0p2"
                setenv video "videoout=omap24xxvout 
omap_vout.video1_numbuffers=6 omap_vout.vid1_static_vrfb_alloc=y vram=32M 
omapfb.vram=0:8M"
                setenv bootargs "console=${console} 
root=${mmcroot} rootdelay=2 mem=${memsize} ${video}"

                echo "Memory size set to ${memsize}"
                echo "Rootfs set to ${mmcroot}"

                if fatload mmc 0:1 ${loadaddr} uImage; then
                                bootm ${loadaddr}
                fi;
fi;

Please find the attached kernel panic log.

Also, if I revert back the settings (that of 256MB) in bootloader and boot.scr, 
the system is up and running properly.
I have tried different vram values as well, but could not get through.

Any pointers in this regard are helpful.

Thanks and regards,
Chaitral Purkar

Original comment by chaitral...@gmail.com on 17 Jul 2012 at 1:14

Attachments:

• kpanic

[GoogleCodeExporter]

i am facing same issue. 
i tried to modify RAMSIZE in u-boot
Original:
    #define RAMSIZE_128     (0x40 << 8) /* RAM size in 2MB chunks */
Modified:
    #define RAMSIZE_128     (0x80 << 8) /* RAM size in 2MB chunks */

but it did not work.

i added print in /*
 * dram_init -
 *  - Sets uboots idea of sdram size
 */
int dram_init(void)

the output is:
DRAM_0: 256 MiB
DRAM_1: 0 Bytes

Original comment by Wendell....@gmail.com on 22 Aug 2012 at 7:29

[GoogleCodeExporter]

i use the patch below to update u-boot sources

    http://gitorious.org/rowboat/u-boot/commits/OMAPPSP_04.02.00.07

now u-boot can detect 512M RAM, but still can not boot kernel, hangs at 
"Uncompressing Linux... done, booting the kernel."

Original comment by Wendell....@gmail.com on 22 Aug 2012 at 9:01

[GoogleCodeExporter]

the path OMAPPSP_04.02.00.07 can not fixed the issue. I run mem_ok() to check 
the memory in 256~512M, mem_ok() failed. That means the memory>256M is 
invariable.

Original comment by Wendell....@gmail.com on 27 Aug 2012 at 6:38

[GoogleCodeExporter]

Did anybody fixed this issue? 

Original comment by ezequiel.aceto on 3 Nov 2012 at 7:18