Kernel Boot Problem in my Board

Hi Eric,

This could be a boot argument issue.

Please verify your bootargs with bootargs mentioned in the user guide.

http://processors.wiki.ti.com/index.php/TI-Android-GingerBread-2.3-DevKit-1.0_UserGuide#Boot_arguments

Regards,

Pankaj Bharadiya

Hi, Pankaj,

               How do I  open and edit the boot.scr file? I cannot open it by editor.

Thanks

Eric

To extract the boot commands in boot.scr you can do as follows:

$ cat boot.scr

This will print the ASCII contents on screen. You can copy to any text file from this output.

Hi,  Vishveshwar,

   Thank you for your reply.

I got the following problem:

  I had rebuilt all x-loader, u-boot, android file system And then put all into SD Card.

OMAP3430/3530-GP ES3.1, CPU-OPP2 L3-165MHz
OMAP3 Beagle board + LPDDR/NAND
I2C:   ready
DRAM:  256 MiB
NAND:  HW ECC [Kernel/FS layout] selected
512 MiB
*** Warning - bad CRC or NAND, using default environment
 
In:    serial
Out:   serial
Err:   serial
Beagle unknown 0x03
Die ID #3530000400000000040373041501b006
Hit any key to stop autoboot: 10 9 8 7 6 5 4 3 2 1 0 
mmc1 is available
reading boot.scr
 
461 bytes read
Running bootscript from mmc ...
## Executing script at 82000000
reading uImage
 
2745092 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:    2745028 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.

.....................

..........................

I had find the following error:

EXT3-fs: barriers not enabled
kjournald starting.  Commit interval 5 seconds
EXT3-fs (mmcblk0p2): using internal journal
EXT3-fs (mmcblk0p2): mounted filesystem with ordered data mode
VFS: Mounted root (ext3 filesystem) on device 179:2.
Freeing init memory: 204K
init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj instead.
init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
enabling adb
adb_open
# warning: `zygote' uses 32-bit capabilities (legacy support in use)
binder: release 1715:1715 transaction 3897 out, still active
binder: 1198:1818 transaction failed 29189, size 14448-0
binder: send failed reply for transaction 3897, target dead
binder: release 2063:2063 transaction 5292 out, still active
binder: release 2063:2125 transaction 5245 out, still active
binder: release 2063:2126 transaction 5251 out, still active
binder: release 2063:2127 transaction 5271 out, still active
binder: 1689:1708 transaction failed 29189, size 28-4
binder: send failed reply for transaction 5245, target dead

 Do you have any comment for this?

hello,have you solved this problem? i came cross this same error,but i don't know how to do solving this problem,wish you can help me .

thank you.

luoyi