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

servicemanager exited

Chris Read
Genius 3345 points
Other Parts Discussed in Thread: TPS65950, OMAP3530

I'm porting the TI-Android-FroYo-DevKit-V2.2 release to our custom OMAP3530/TPS65950 board, which we have been using successfully with Linux for some time.  However, I'm totally new to Android.  I built a custom kernel using the omap3_evm_android_defconfig as a template, but with changes as needed for our board.  Similarly I built the x-loader and u-boot from the same Android release, but with changes required for our board.  I used the pre-built root filesystem, and have it mounted over NFS.  All this seems to function OK until the actual Android processes start.  I keep getting messages in the log such as

init: process 'servicemanager', pid 879 exited

I can't determine why servicemananger is exiting, however.  I set loglevel to 8 in init.rc, but it doesn't give any indication of why servicemanager is exiting.  I have searched various Android sites and the above message is asked about a few times, but no one has any answers that seem to help.  I have searched for servicemanager command-line options that might make it give verbose output, but there don't seem to be any.

Our board doesn't have WiFi or Bluetooth on it.  It does have an LCD display.  I get a partial display of the green Android logo on it, but never a real Android screen.

Any suggestions?

 

Thanks, in advance...

  • 0
    TI__Expert 4390 points

    Hi Chris,

    1.  Can you post your bootargs  and complete boot log ? It will help us to understand what is going on.

    2. Could try pre-built images on SD card and try to boot from SD card ? It is just to check if mmc boot gives same problem or not.

    3. Have you change anything in init.rc apart from log level

    BR,

    satish

  • 0 in reply to Satish Patel
    TI__Expert 5400 points

    Hi Chris,

    Kindly run logcat command on console and provide output of that.

    Best Regards,

    Pankaj Bharadiya

  • 0 in reply to Satish Patel
    Genius 3345 points

    Satish, thanks for your response.  Here are my responses to your requests:

    Item 1:  Boot Args and Boot Log

    Boot Args: bootargs=init=/init console=ttyS0,115200n8 ip=dhcp rw root=/dev/nfs nfsroot=192.168.0.43:/opt/rfs/android,nolock mem=256M noinitrd androidboot.console=ttyS0 eth=e6:e5:e4:e3:e2:01 omap_vout.vid1_static_vrfb_alloc=y

    Boot Log: 7774.AndroidLog.txt

    Item 2:  Prebuilt image on SD card:

    1. While it auto-boots on the Mistral EVM, it doesn't on our board (though I can make cards that will).
    2. Use of the EVM's image won't work because our system has a different LCD panel (480x272 24bpp), which needs a different driver.
    3. Using the manual method to boot from MMC using boot.scr yields the following log:  4885.AndroidLog-evm.txt
    4. Replacing the uImage file with our kernel still gives the init: process 'servicemanager', pid 955 exited message.

    Item 3:  init.rc file

    I have tried various things, including removing references to bluetooth and WLAN which our board doesn't have, but I get similar problems with the original init.rc

     

    Thanks very much for looking at this.  -- Chris

  • 0 in reply to Pankaj Bharadiya
    Genius 3345 points

    Thanks Pankaj,

    Attempting the logcat command, I'm currently getting:

    Unable to open log device '/dev/log/main': No such file or directory

    Thanks for your attention.  -- Chris

  • 0 in reply to Chris Read
    TI__Expert 5400 points

    Hi Chris,

    Did you enable android log driver?

    If not, please enable android log driver and try logcat again.

    Location:
        -> Device Drivers             
          -> Staging drivers (STAGING [=y])
             -> Exclude Staging drivers from being built (STAGING_EXCLUDE_BUILD [=n])
               -> Android
                 -> Android Drivers (ANDROID [=y])
                                                    

    Thanks and Regards,

    Pankaj Bharadiya

  • 0 in reply to Pankaj Bharadiya
    Genius 3345 points

    Pankaj,  You pointed me in the right direction!

    It turned out to be that I was missing the Staging/Android drivers, including the log driver.

    After enabling those in the kernel, servicemanager doesn't exit anymore.

    Thanks and best regards!

    - Chris