• State Resolved
  • Locked Locked
  • Replies 10 replies
  • Subscribers 98 subscribers
  • Views 3524 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.

AM37xx doesn't start properly (a lot of sigkill's)

Peter Jans
Prodigy 60 points


Hello,

I'm trying to run gingerbread 2.3 on the AM37xx EVM board. I've followed the TI android gingerbread 2.3 devkit 1.0 development guide.
But when I insert the SD card and try to run it, it won't boot properly. It does boot after a long wait but almost every app I try is killed eventually.

Anyone got some hints to what might be wrong?

Serial output at boot:

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)
request_suspend_state: wakeup (3->0) at 36847717297 (2000-01-01 00:34:57.142761242 UTC)
select 1043 (putmethod.latin), adj 1, size 4061, to kill
send sigkill to 1043 (putmethod.latin), adj 1, size 4061
binder: release 1043:1089 transaction 872 out, still active
binder: release 1043:1090 transaction 874 out, still active
binder: 954:954 transaction failed 29189, size 1528-4
binder: send failed reply for transaction 874, target dead
binder: 954:1071 transaction failed 29189, size 1332-4
binder: send failed reply for transaction 872, target dead
select 593 (ueventd), adj 0, size 25, to kill
select 1062 (ndroid.launcher), adj 0, size 4437, to kill
send sigkill to 1062 (ndroid.launcher), adj 0, size 4437
binder: release 1062:1095 transaction 1901 out, still active
select 593 (ueventd), adj 0, size 25, to kill
select 1098 (d.process.acore), adj 0, size 3721, to kill
send sigkill to 1098 (d.process.acore), adj 0, size 3721
binder: release 1098:1098 transaction 1905 out, still active
select 593 (ueventd), adj 0, size 25, to kill
select 1142 (putmethod.latin), adj 0, size 3314, to kill
send sigkill to 1142 (putmethod.latin), adj 0, size 3314

  • 0
    TI__Expert 5400 points

    Hi Peter,

    Please provide output of logcat command so that we can look into the issue.

    Thanks and Regards,

    Pankaj Bharadiya

  • 0 in reply to Pankaj Bharadiya
    Prodigy 60 points

    Hello,

    Here's the logcat file.
    6327.logcat.txt

  • 0 in reply to Peter Jans
    TI__Expert 5400 points

    Hi Peter,

    Logcat looks fine for me. 

    We observed android booting and performance is poor with some SD cards.Please try with different SD card.

    Please refer to below link for SD card recommendations

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

     

    Thanks and Regards,

    Pankaj Bharadiya

  • 0 in reply to Pankaj Bharadiya
    Prodigy 60 points

    The first SD card I tried didn't work properly and I've been working with another one brand SD card since.
    I just used a sandisk SD card from the list and that yields the same result.

    In the logcat file I found Low memory warnings with a "process... has died" message a few lines above.
    These are the same processes as sigkills i get via serial.

    I compared with the logcat of original SW (SD card with android 2.3 provided with the board) and that does not have the Low memory messages.
    Memory usage seems to be about the same though (judging by the dalvikvm memory allocation messages).

    Regards,

    Peter

  • 0 in reply to Peter Jans
    TI__Expert 5400 points

    Hi Peter,

    Could you please provide your boot arguments and output of cat /proc/meminfo command.

     

    AM37x boot arguments for reference:

    setenv bootargs 'console=ttyS0,115200n8 androidboot.console=ttyS0 mem=256M root=/dev/mmcblk0p2 rw rootfstype=ext3 \
     rootdelay=1 init=/init ip=off mpurate=1000 omap_vout.vid1_static_vrfb_alloc=y'

     

    Thanks and Regards,

    Pankaj Bharadiya.

     

  • 0 in reply to Pankaj Bharadiya
    Prodigy 60 points

    That fixed it. The mkbootscr set the bootargs to the following:

    setenv bootargs 'console=ttyS0,115200n8 androidboot.console=ttyS0 mem=128M root=/dev/mmcblk0p2 rw rootfstype=ext3 rootdelay=1 init=/init ip=off mpurate=720 omap_vout.vid1_static_vrfb_alloc=y'

    After I switched this to 256M everything works fine.
    "cat /proc/meminfo" also shows 249MB total memory now iso 119MB.

    Thanks for the quick response.

    Regards,

    Peter

  • 0 in reply to Peter Jans
    Prodigy 50 points

    Hi

    I am having the same error even with 256M. The system is very slow, and applications usually fail to start for a minute and then start. It's not usable. Can I use the full 512M of RAM on the Beagleboard? Could this be caused by the SD card I use?

    plus I was wondering what the vram parameter is in this boot script, I just don't want to miss something :)

    setenv bootargs 'console=tty0 console=ttyO2,115200n8 rootwait ro earlyprintk \
    fixrtc nocompcache vram=32M omapfb.vram=0:8M mem=456M@0x80000000 \
    mem=512M@0xA0000000 init=/init androidboot.console=ttyO2 omapdss.def_disp=dvi \
    omapfb.mode=dvi:1280x720MR-24@60 consoleblank=0'

    Thanks!

  • 0 in reply to ferre adrien
    TI__Expert 5400 points

    Hi Ferre,

    Beagleboard has 256MB of ram. The system might be getting slow due to improper SD card. Please try with different SD card. Please refer to below link for SD card recommandation.

    http://processors.wiki.ti.com/index.php/TI-Android-GingerBread-2.3.4-DevKit-2.1_UserGuide#SD_Card_Recommendations

    Please refer to user guide for boot arguments.

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

    Thanks and Regards,

    Pankaj Bharadiya

  • 0 in reply to Pankaj Bharadiya
    Prodigy 50 points

    Hi,

    thanks for this.

    But changing SD Card doesn't seem to help. I just tried another one and it's the same thing: very laggy, every click on anything leadsto 10 to 60 seconds of freeze. I am using the boot arguments available on the dev kit 2.1 user guide :

      Beagleboard-xm:
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'
    I do this before booting:
    mmc init
    fatload mmc 0 0x82000000 uImage
    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'
    

    boot
    

    

    

    I'll try with another SD Card later on. (I will receive the Sony Micro sd card recommended on the user guide during this week).
    

    

    Here is the cat /proc/meminfo output
    

     cat /proc/meminfo
    

    
MemTotal:         245504 kB
MemFree:           41564 kB
Buffers:           24880 kB
Cached:            59892 kB
SwapCached:            0 kB
Active:            82052 kB
Inactive:          51900 kB
Active(anon):      49208 kB
Inactive(anon):      284 kB
Active(file):      32844 kB
Inactive(file):    51616 kB
Unevictable:           0 kB
Mlocked:               0 kB
SwapTotal:             0 kB
SwapFree:              0 kB
Dirty:                 4 kB
Writeback:             0 kB
AnonPages:         49188 kB
Mapped:            40092 kB
Shmem:               316 kB
Slab:               7688 kB
SReclaimable:       4020 kB
SUnreclaim:         3668 kB
KernelStack:        1808 kB
PageTables:         4556 kB
NFS_Unstable:          0 kB
Bounce:                0 kB
WritebackTmp:          0 kB
CommitLimit:      122752 kB
Committed_AS:     678472 kB
VmallocTotal:     647168 kB
VmallocUsed:       22856 kB
VmallocChunk:     611332 kB

    

    

    Everything seems fine during boot (even if I think it's taking a very long time to boot, compared to Froyo) until I start clicking away:
    

    binder: release 1389:1404 transaction 2782 out, still active
binder: release 1389:1405 transaction 2788 out, still active
binder: release 1389:1406 transaction 2808 out, still active
binder: 1238:1407 transaction failed 29189, size 28-4
binder: send failed reply for transaction 2808, target dead
binder: 1238:1256 transaction failed 29189, size 28-4
binder: send failed reply for transaction 2788, target dead
binder: 1238:1254 transaction failed 29189, size 28-4
binder: send failed reply for transaction 2782, target dead

    

    

    

    thanks

     

  • 0 in reply to ferre adrien
    TI__Expert 5400 points

    Hi,

    The procedure which you are following looks OK for  me.

    Please try with recommanded SD card. Let us know if you face same issue.

    Thanks and Regards,

    Pankaj Bharadiya