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

Compiling for android rootfs

Prasun Sinha
Prodigy 160 points

Hi,

I am working on DM37XX and through with x-loader, u-boot build . I go stuck in building android filesystem.

Here are the steps that I am following to build android filesystem:

make ARCH= arm TARGET_PRODUCT=omap3evm OMAPES=5.x -j8

I am getting below message:

============================================
find: `frameworks/base/frameworks/base/docs/html': No such file or directory
find: `out/target/common/docs/gen': No such file or directory
find: `frameworks/base/frameworks/base/docs/html': No such file or directory
find: `out/target/common/docs/gen': No such file or directory
find: `frameworks/base/frameworks/base/docs/html': No such file or directory
find: `out/target/common/docs/gen': No such file or directory
find: `frameworks/base/frameworks/base/docs/html': No such file or directory
find: `out/target/common/docs/gen': No such file or directory
find: `frameworks/base/frameworks/base/docs/html': No such file or directory
find: `out/target/common/docs/gen': No such file or directory


The path, make file is searching is correct? becasue the files are in

`frameworks/base/docs/html'

if the path is not correct then ,How to change the search path ...or I am getting correct message ,  is it suppose to work like this...?

I am getting error at the end of build ....

  • 0
    TI__Guru**** 167271 points

    Those messages are just for docs, which do not affect build and run Android on the board.

    The problem is 'ARCH= arm', which should be 'ARCH=arm', no space between '=' and 'arm'.

    If you still have build error, please attach the full build log.

  • 0
    TI__Genius 10210 points

    Prasun Sinha said:

    make ARCH= arm TARGET_PRODUCT=omap3evm OMAPES=5.x -j8

     

    You don't need ARCH=arm when building the android filesystem.
    ARCH=arm is required only for building u-boot and kernel uImage.

  • 0 in reply to Vishveshwar Bhat
    Prodigy 160 points

    Thanks for reply,

    Yes now I am able to build android filesystem. I follwed all the instruction mentioned in developer's guide and able to make SDCARD too.

    but my EVM is not booting., I have created boot.scr with boot arguments mentioned in user's guide. I am getting follwing message on putty:

     

    Texas Instruments X-Loader 1.51 (Jul 21 2011 - 16:40:58)
    Starting X-loader on MMC
    Reading boot sector

    217404 Bytes Read from MMC
    Starting OS Bootloader from MMC...
    Starting OS Bootloader...


    U-Boot 2010.06 (Jul 21 2011 - 16:46:38)

    OMAP34xx/35xx-GP ES2.1, CPU-OPP2 L3-165MHz
    OMAP3 EVM 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
    Read back SMSC id 0x92200000
    Die ID #090a00029ff80000016071640702a016
    Net:   smc911x-0
    Hit any key to stop autoboot:  0
    mmc1 is available
    reading boot.scr

    667 bytes read
    Running bootscript from mmc ...
    ## Executing script at 82000000
    reading uImage

    3329452 bytes read
    ***** Kernel: /dev/mmcblk0p1/uImage *****
    ***** RootFS: /dev/mmcblk0p2 *****
    syntax error

  • 0 in reply to Prasun Sinha
    TI__Expert 5400 points

    Hi Prasan,

    I think your boot.scr is incorrect as you are getting syntax error.

    Please refer to mk-bootscr (README) utility  present inside tools or use boot.scr from our pre-built image.

    You can download tools and pre-built images form below link.

    http://software-dl.ti.com/dsps/dsps_public_sw/sdo_tii/TI_Android_DevKit/TI_Android_GingerBread_2_3_4_DevKit_2_1/index_FDS.html

    Regards,

    Pankaj Bharadiya

  • 0 in reply to Pankaj Bharadiya
    Prodigy 160 points

    I modified mkbootscr file with the boot args, which is mentioned in user's guide... and that should work. According to my understanding boot.scr provides boot args to kernel, I got the point that my boot .scr is wrong..but curious what is wrong in boot args;

    This is my mkbootscr file looks like:

    #!/bin/sh
    cat <<EOF > boot.cmd
    if fatload mmc 0 82000000 uImage
    then
     echo ***** Kernel: /dev/mmcblk0p1/uImage *****
    fi
    echo ***** RootFS: /dev/mmcblk0p2 *****
    setenv bootargs 'console=ttyO0,115200n8 androidboot.console=ttyO0 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

     

    The default  Tools/mk-bootscr/mkbootscr have mem=128M and I changed it to 256M , rest is same. What is difference between the prebuilt boot.scr and this one?

  • 0 in reply to Prasun Sinha
    TI__Expert 5400 points

    I think you are missing  single quote symbol ( ' ) in bootargs.

    setenv bootargs 'console=ttyO0,115200n8 androidboot.console=ttyO0 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'

     Please make sure that you are writing mkbootscr with proper syntax.

    Thanks and Regards,

    Pankaj Bharadiya.