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.

Creating the sdcard image for JB - TI Sitara starter kit

I am trying to create and JB image for the TI sitara stater kit using the pre-packaged source. I am following the TI-Android-JB-4.2.2-DevKit-4.1.1 DeveloperGuide.

  1. I downloaded the TI_Android_JB_4.2.2_DevKit_4.1.1.bin $HOME/Android_JB
  2. cd $HOME/Android_JB
  3. chmod a+x TI_Android_JB_4.2.2_DevKit_4.1.1.bin
  4. ./TI_Android_JB_4.2.2_DevKit_4.1.1.bin
  5. make TARGET_PRODUCT=am335xevm_sk OMAPES=4.6 -j6 sdcard_build
    
    
    I get an error "No rule to make target sdcard_build
    
    
    What am I doing wrong?
    
    
    Thanks
  • Hi,

    There is a typo in your build command. The word OMAPES=4.6 needs to be changed to OMAPES=4.

    Recently we identified some issues with -j<N> options with the sdcard_build build target. We will be resolving this soon.

    For now, you can either do

    make TARGET_PRODUCT=am335xevm_sk OMAPES=4 -j1 sdcard_build

    Or execute the build commands seperately

    make TARGET_PRODUCT=am335xevm_sk OMAPES=4

    make TARGET_PRODUCT=am335xevm_sk OMAPES=4 u-boot_build

    make TARGET_PRODUCT=am335xevm_sk OMAPES=4 fs_tarball

    ./external/ti_android_utilities/make_distribution.sh ./ am335xevm_sk

    Let us know if you face any further issues.

  • Im running into the same issue, and get an error: OMAPES value not specified (Mandatory value)

    Load Address: 80008000
    Entry Point:  80008000
      Image arch/arm/boot/uImage is ready
    make[1]: Leaving directory `/home/jesper/TI_Android_JB_4.2.2_DevKit_4.1.1/kernel'
    make -C hardware/ti/sgx ANDROID_ROOT_DIR=/home/jesper/TI_Android_JB_4.2.2_DevKit_4.1.1
    make[1]: Entering directory `/home/jesper/TI_Android_JB_4.2.2_DevKit_4.1.1/hardware/ti/sgx'
    OMAPES value not specified (Mandatory value)
    exit 1
    make[1]: *** [buildkernel] Error 1
    make[1]: Leaving directory `/home/jesper/TI_Android_JB_4.2.2_DevKit_4.1.1/hardware/ti/sgx'
    make: *** [sgx] Error 2
    jesper@jesper-VirtualBox:~/TI_Android_JB_4.2.2_DevKit_4.1.1$ ^C

    Even though it is defined in the call: 

    make TARGET_PRODUCT=am335xevm_sk OMAPES=4 -j1 sdcard_build

    Im quite frustrated about not being able to figure this out, so any help is appreciated.

    Did you succeed in making it work?

  • Hello Jesper,

    Yes, I was able to get it working using the second method specified by Arun. I also notice that you were using virtual box. I was not successful with virtual box (I did't try hard enough). I used the dedicated ubuntu 12.04 LTS machine. 

    Also we have temporarily migrated to a different vendor due to business reason. 

    If you still have questions please post, I will try to respond as best as I can.

    Good luck, 

  • I also fail using that method after a long compilation time. 

    I have tracked the error down to building the SGX kernel files. That makefile seems to be made for reacting on OMAPES=4.x and not OMAPES=4 

    The file that fail is:

    hardware/ti/sgx/Makefile.KM.Android

    It seems as this is just plain broken. I look forward to see if TI can help.

    Kind regards and thank you for your help.

    Jesper

  • Hello Jesper,

       You must use OMAPES=4.x for the build. Seems there was a typo in the previous post.

    Please have a look at the developer guide for further info.

    Regards,

    Aditya

  • Hi Aditya,

    I have tried: 

    OMAPES=4

    OMAPES=4.x

    OMAPES=4.6

    All without success. :(

    Im following the guide here

    I am working from the pre packaged sources here (very slow to download), as the lonk to the repo tool is dead. Could there be a problem with that package? 

    I am on a Ubuntu 12.04 64bit and have followed the guide installing all the extra software including Java.

    What could I be doing wrong?

    Kind regards

    Jesper

  • Using "make TARGET_PRODUCT=am335xevm_sk OMAPES=4.x -j1 sdcard_build"

    I get the following error:

    make[2]: Entering directory `/home/jesper/rowboat-android/hardware/ti/sgx/eurasiacon/build/linux2/omap4430_android'
    ../common/android/platform_version.mk:141: *** Must build against Android >= 2.0. Stop.
    make[2]: Leaving directory `/home/jesper/rowboat-android/hardware/ti/sgx/eurasiacon/build/linux2/omap4430_android'
    make[1]: *** [buildkernel] Error 2
    make[1]: Leaving directory `/home/jesper/rowboat-android/hardware/ti/sgx'
    make: *** [sgx] Error 2

    This seems to be an error that is different from the OMAPES=4 error.

    Do I need to update something with the precompiled package before building?

    Kind regards

    Jesper

  • I am finally making some progress.  I tried running this command before:

    make TARGET_PRODUCT=am335xevm_sk OMAPES=4.x -j1 

    followed by this:

    make TARGET_PRODUCT=am335xevm_sk OMAPES=4.x -j1 sdcard_build

    That made a bunch of files that I could write to a SD card. It threw an error though, so I suspect something is wrong. (error listed below)

    xevm_sk$ sudo ./mkmmc-android.sh /dev/sdb

    Assuming Default Locations for Prebuilt Images
    All data on /dev/sdb now will be destroyed! Continue? [y/n]
    y
    [Unmounting all existing partitions on the device ]
    umount: /dev/sdb: not mounted
    umount: /dev/sdb1: not mounted
    [Partitioning /dev/sdb...]
    Disk /dev/sdb doesn't contain a valid partition table
    DISK SIZE - 15935209472 bytes
    CYLINDERS - 1937
    [Making filesystems...]
    [Copying files...]
    [Copying START_HERE folder to boot partition]
    cp: cannot stat `START_HERE': No such file or directory
    [Copying all clips to data partition]
    [Done]

    It is taking ages to boot and when finally getting up its very slow. I tried pressing a menu and it just waits.

    What could cause such speed?

    Kind regards

    Jesper

     

     

     

  • /proc/meminfo says I have 256mb on the device, so I guess I need to configure something?

  • @Jesper

    Are you still using Virtual box?

  • yes

    My computer is running OSX mavericks, where I run Virtualbox with an Ubuntu 64bit 12.04.1 Desktop edition inside.

    I am piping the USB connection through to the Ubuntu machine (inside Virtiual box), to be able to create a SD image using the script.  

    kind regards

    Jesper

  • Hello Jesper,

             Please make sure that you pass the correct partition (on which your sdcard is mounted) to the script.

    For the first boot it is expected to take some time as it needs to cache all data.  Also boot time depends on the class of SD card you use. It is recommended to use class 4 or higher for better performance

    Regards,

    Aditya.

  • Now I can make the SD card allright. Its just kind of slow. When i look at /proc/meminfo i read:

    |root@android:/ # cat /proc/meminfo

    MemTotal: 250328 kB

    Should the am335x Starter Kit not have 2G memory?

    Kind regards

    Jesper 

  • i used this command

    1555:~/beagleboard-xm-jb$ sudo ./mkmmc-android.sh /dev/sdb

    and got result like this


    Assuming Default Locations for Prebuilt Images
    All data on /dev/sdb now will be destroyed! Continue? [y/n]
    y
    [Unmounting all existing partitions on the device ]
    umount: /dev/sdb: not mounted
    [Partitioning /dev/sdb...]
    Disk /dev/sdb doesn't contain a valid partition table
    DISK SIZE - 3965190144 bytes
    CYLINDERS - 482
    [Making filesystems...]
    [Copying files...]
    [Copying START_HERE floder to boot partition]
    cp: cannot stat `START_HERE': No such file or directory
    [Copying all clips to data partition]
    [Done]

    is there error in this. i got my sd card partitioned but i din't get anything displayed in my monitor after connecting beagleboard-xm via hdmi cable.

    any suggestions please.

    Regards,

    Kamal

  • Me also struggling with this issue.Have you solved it?
  • I think I ended up rolling back to an earlier version, before my client chose a different solution.

    Its been a long time.

    Jesper

  • I am a green-horn in embedded android development with beaglebone.I

    I am following http://processors.wiki.ti.com/index.php/TI-Android-JB-4.2.2-DevKit-4.1.1_DeveloperGuide this guide.

    Everything works fine with

    "make TARGET_PRODUCT=<product-name> OMAPES=4.x -j<N>" followed by a

    "make TARGET_PRODUCT=<product-name> OMAPES=4.x -j<N> sdcard_build"

    4-Partitions are created but OS doesn;t booting up.

    I don't know how to fix this issue..

    Coulde you please help me ?
  • I remember being able to create a sd card, but I could not boot it either.

    I think thats where i stranded too.

    I seem to remember that that guide was just not working. I also seem to remember rolling back to a different one wrked, but i cant remember for sure.

    Jesper
  • If you got any hint regarding the worked one , please inform me ...
  • Hi Jesper,

    Most of the times it is due to the SDCard itself, some are very slow. Have you tried with different SDCards? Could you tell us which class of SDCard you are using?

    Here is a link that should help knowing which one is yours:

    https://www.sdcard.org/developers/overview/speed_class/

  • @Jesper,

    It has been a while since I have worked with TI Sitara Starter kit, but I suggest that you investigagte the console output during boot up to research where the process is getting hung up.

    Review this link 

    http://processors.wiki.ti.com/index.php/TI-Android-JB-4.2.2-DevKit-4.1.1_DeveloperGuide#Getting_serial_console_on_AM335x_Starter_Kit_and_BeagleBone

    Good luck

  • Hai . Actually i don't know , how to start a new thread in E2E community.

    I have a new site proposal for BeagleBone in StackExchange .

    Please visit and support. http://area51.stackexchange.com/proposals/81367/beaglebone

  • Thanks for the invitation! We're glad to see more community support around the BeagleBone.
    Our Q&A support has to remain in this e2e forum though because it is part of the scope of support we can provide. Our support team supports TI EVMs but also the BeagleBone Black with the last release JB4.2.2 in this site. Beyond that we defer to community support.

    Thanks!