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.

Jelly Bean porting on Panda Board

Hi,

   We formated the SD card as fat32 which contains the MLO,U-boot.bin and uImage(3.5 Linux kernel) and as ext3 which is having Jelly Bean File system.

   We took    Linux kernel version 3.5 from mainline linux git and linux kernel is compiled with tool chain Sourcery G++ Lite 2010q1-202 . We compiled the Jelly Bean 

   source as procedure available in the link http://source.android.com/source/building.html .

   We are getting the following error   with  Panda board while when we  tried for booting jelly bean File system (zoom).  

Error:

[    5.189758] init: skipping insecure file '/default.prop'
[    5.198059] init: skipping insecure file '/init.rc'
[    9.516693] init: Timed out waiting for /dev/.coldboot_done
[    9.532562] init: skipping insecure file '/system/build.prop'
[    9.544921] init: Unable to open persistent property directory /data/property errno: 2

Complete Log is also provided. 

4263.Logfile.txt

Please help us on this.


Thanks & Regards

Bhimesh


  • kumar bhimesh1 said:

    [    5.189758] init: skipping insecure file '/default.prop'
    [    5.198059] init: skipping insecure file '/init.rc'
    [    9.532562] init: skipping insecure file '/system/build.prop'

    In jellybean, init.rc, default.prop etc should be writable only by the owner. You need to change the file permission to 644 (owner writable, world read-only) when you write the filesystem.

  • Thanks  for the reply Vishveswar. With this we cleared few issues But still getting few more issues.

    Error :


    [    6.403869] init: cannot open '/initlogo.rle'
    [   11.005218] fs_mgr: Cannot mount filesystem on /dev/block/platform/omap/omap_hsmmc.0/by-name/system at /system
    [   11.015747] init: fs_mgr_mount_all returned an error
    [   13.162353] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
    [   13.207794] init: cannot find '/vendor/bin/pvrsrvinit', disabling 'pvrsrvinit'
    [   13.217102] init: cannot find '/system/bin/rild', disabling 'ril-daemon'
    [   13.271636] init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
    [   13.474822] warning: `adbd' uses 32-bit capabilities (legacy support in use)
    [   13.526336] init: untracked pid 852 exited
    [   13.533538] init: untracked pid 853 exited
    [   13.538909] init: untracked pid 854 exited
    [   13.543426] init: untracked pid 855 exited
    shell@android:/ $ [   14.666198] init: untracked pid 850 exited

    Complete Log file.

    7367.Log.txt

    Help us on this.

    Regards

    Bhimesh

  • Dear Vishveshwar,

    We are able to proceed further with the above changes but we got few more errors and the details are given below .

    592681] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
    [    4.601501] VFS: Mounted root (ext4 filesystem) on device 179:2.
    [    4.608093] Freeing init memory: 244K
    [    4.663726] init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj instead.
    [    4.918670] init: cannot open '/initlogo.rle'
    [   21.017425] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
    [   21.054473] init: Unable to open persistent property directory /data/property errno: 2
    [   21.091400] init: cannot find '/system/bin/rild', disabling 'ril-daemon'
    [   21.166534] init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
    [   21.339050] init: untracked pid 853 exited
    $ [   21.351745] init: untracked pid 852 exited
    [   21.356262] init: untracked pid 854 exited
    [   21.361389] init: untracked pid 855 exited
    [   22.329711] init: untracked pid 850 exited
    [   22.334320] init: untracked pid 862 exited

    Please help us to resolve this errors

    Thanks in advance,

    roy

  • I am not working on the AOSP pandaboard release, so I am not in a position to comment on its status. I would suggest you go to the official Android Building google groups forum for help on this.

    With respect to the TI Android DevKit that we work on, the error regarding rild and install-recovery is expected as those features are not implemented here.

  • I get the same problem and I resolved it by commenting out all "on fs" sections in init.rc and init.BOARDNAME.rc.

    Next boot is normal until below error:

    [ 65.193084] VFS: Mounted root (ext2 filesystem) on device 179:2.
    [ 65.199981] Freeing init memory: 252K
    [ 72.073791] init: cannot find '/vendor/bin/pvrsrvinit', disabling 'pvrsrvinit'
    [ 72.099151] init: cannot find '/system/bin/rild', disabling 'ril-daemon'
    [ 72.137481] init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
    [ 72.153869] android_usb: already disabled
    [ 72.433959] warning: `adbd' uses 32-bit capabilities (legacy support in use)
    [ 72.443939] adb_open
    [ 72.447204] adb_bind_config
    shell@android:/ $ [ 75.004547] init: untracked pid 92 exited
    [ 77.310882] init: untracked pid 239 exited
    [ 82.647003] init: untracked pid 245 exited
    [ 86.105834] alarm_set_rtc: no RTC, time will be lost on reboot
    [ 87.987396] init: untracked pid 251 exited
    [ 88.001220] init: untracked pid 255 exited

  • Dear Vishveshwar,

    Currently we are able to get the JB android console but are not able to proceed further because of SGX library problem.We are using SGX ddk 1.8 version(CustomerGoogle_Android_ogles1_ogles2_GPL sgxddk 18 1.8@" PVR_STR2(PVRVERSION_BUILD).Because of SGX library compatibility problem we have switched to 3.0.8 kernel as earlier we were using 3.4.4.we are getting the following errors.

    5.506317] Power Management for TI OMAP4.
    [    5.511627] OMAP4 PM: Static dependency added between MPUSS <-> EMIF, MPUSS <-> L4_PER/CFG MPUSS <-> L3_MAIN_1.
    [    5.522338] OMAP4 PM: Static dependency added between DUCATI <-> L4_PER/CFG and DUCATI <-> L3.
    [    5.539184] clock: disabling unused clocks to save power
    [    5.545959] cannot apply mgr(lcd) on inactive device
    [    5.551269] omapfb omapfb: failed to apply dispc config
    [    5.556854] cannot apply mgr(lcd2) on inactive device
    [    5.562255] omapfb omapfb: failed to apply dispc config
    [    5.567779] omapfb omapfb: cannot find default display

    logcat message:

    D/AndroidRuntime(   92): >>>>>> AndroidRuntime START com.android.internal.os.ZygoteInit <<<<<<
    D/AndroidRuntime(   92): CheckJNI is ON
    I/SurfaceFlinger(   91): SurfaceFlinger is starting
    I/SurfaceFlinger(   91): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
    I/gralloc (   91): using (fd=14)
    I/gralloc (   91): id           = omapfb
    I/gralloc (   91): xres         = 0 px
    I/gralloc (   91): yres         = 0 px
    I/gralloc (   91): xres_virtual = 0 px
    I/gralloc (   91): yres_virtual = 0 px
    I/gralloc (   91): bpp          = 0
    I/gralloc (   91): r            =  0:0
    I/gralloc (   91): g            =  0:0
    I/gralloc (   91): b            =  0:0
    I/gralloc (   91): width        = 0 mm (NaN dpi)
    I/gralloc (   91): height       = 0 mm (NaN dpi)
    I/gralloc (   91): refresh rate = 60.00 Hz
    E/FramebufferNativeWindow(   91): couldn't open framebuffer HAL (Permission denied)
    E/SurfaceFlinger(   91): Display subsystem failed to initialize. check logs. exiting...
    D/AndroidRuntime(  266):
    D/AndroidRuntime(  266): >>>>>> AndroidRuntime START com.android.internal.os.ZygoteInit <<<<<<
    D/AndroidRuntime(  266): CheckJNI is ON
    D/dalvikvm(  266): Trying to load lib libjavacore.so 0x0
    D/dalvikvm(  266): Added shared lib libjavacore.so 0x0

    please provide your valuable suggestion to solve this problem.

  • Hi Chao,

     U missed to install sgx support thats why u r getting : init: cannot find '/vendor/bin/pvrsrvinit', disabling 'pvrsrvinit'

    If installed  change the init.rc in which u r enabling the support for sgx to  

    service pvr /system/bin/sgx/rc.pvr start
    class core
    oneshot.

    .

    With this i think u can resolve the issue .Let me know if u faces any other problem.

    Thanks and regards

    Subrat Kumar Ojha

  • In  Prasad Roy's  Post We said that

    below said fields are not update

    I/gralloc (   91): using (fd=14)
    I/gralloc (   91): id           = omapfb
    I/gralloc (   91): xres         = 0 px
    I/gralloc (   91): yres         = 0 px
    I/gralloc (   91): xres_virtual = 0 px
    I/gralloc (   91): yres_virtual = 0 px
    I/gralloc (   91): bpp          = 0
    I/gralloc (   91): r            =  0:0
    I/gralloc (   91): g            =  0:0
    I/gralloc (   91): b            =  0:0
    I/gralloc (   91): width        = 0 mm (NaN dpi)
    I/gralloc (   91): height       = 0 mm (NaN dpi)
    I/gralloc (   91): refresh rate = 60.00

    but now changing the bootargs to 

    bootargs     :    console=ttyO2,115200n8 androidboot.console=ttyO2 mem=456M@0x80000000 mem=512M@0xA0000000 root=/dev/mmcblk0p2 rw rootdelay=2 init=/init vram=32M omapfb.vram=0:16M     omapdss.def_disp=dvi  omapdss.debug=y omapfb.debug=y consoleblank=0 rootfstype=ext4

    initially omapdss.def_disp=hdmi we used now changed it to dvi  so that fields are updated

    But still on console is blank.

    Please help us on this. Proving complete Logcat and dmesg

    3302.Dmesg.txt

    0550.Logcat.txt

    --

    Bhimesh

  • Hi Bhimeseh,

    As per your logcat msgs you can do some changes in device.mk , for the time being use system/build.prop.

    Add this line to system/build.prop:

    1.ro.sf.lcd_density=<some numerical value that suits your monitor>(for me its 120).

    As on dmesg, i found that u have boot arguments problem i use this on beagleboard , have a try

    2.Boot argument:-

    setenv bootargs 'console=ttyO2,115200n8 androidboot.console=ttyO2 rw rootwait mem=512M rootfstype=ext3 rootdelay=1 init=/init ip=off root=/dev/nfs omap_vout.vid1_static_vrfb_alloc=y vram=8M omapfb.vram=0:8M omapdss.def_disp=dvi omapfb.mode=dvi:1024x768-16'

    3.Be sure to sgx service , follow my previous reply for sgx 

    Check this and let me know about the progress 

    Thanks and regards

    Subrat Kumar Ojha

  • Dear all,

    I want to build Jelly Bean for Pandaboard but I only downloaded source for Blaze. If anyone has guide or tutorial for Pandaboard JB, please give me. Thanks.

  • Hello

    I booted my pandaboard es by below way. But below URL has not source but only images to boot. May help you!

    https://android-build.linaro.org/builds/~linaro-android/panda-jb-gcc47-tilt-stable-blob/  

  • Thanks for your reply. But I'm finding source for Jelly Bean-Pandaboard. I'v done follow this link :http://omappedia.org/wiki/4AJ.1.1_OMAP4_Jelly_Bean_Release_Notes#Introduction. but not success because This source is responsible to Blaze tablet not Pandaboard and I dont have Patch file for Panda too (Like this link: http://omappedia.org/wiki/4AI.1.4_OMAP4_Icecream_Sandwich_Panda_Notes). So Who has successed with Building JB Panda or has Guide for building this? Please give me. Thanks so much.

    NHT.