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

rowboat gingerbread with TI-Android-GingerBread-2.3-DevKit-2.0.xml

Gunter Schmer
Genius 14312 points


Hi,

 

from rowboat, I am trying to build the filesystem for the TI-Android-GingerBread-2.3-DevKit-2.0.xml tag

# repo init -u git://gitorious.org/rowboat/manifest.git -m TI-Android-GingerBread-2.3-DevKit-2.0.xml
# repo sync

 

I noticed that I had to build the kernel separately first with

 # cd kernel/
 # make ARCH=arm CROSS_COMPILE=arm-eabi- distclean
 # make ARCH=arm CROSS_COMPILE=arm-eabi- ti8168_evm_android_defconfig
 # make ARCH=arm CROSS_COMPILE=arm-eabi- uImage -j2

Then the filesystem with

# make TARGET_PRODUCT=ti816xevm TARGET_BUILD_VARIANT=tests -j2 OMAPES=5.x

 

But I am getting an error on syslink. Am I missing something?

 

Compiling: /home/gunter/rowboat-android-gingerbread/hardware/ti/ti81xx/syslink_vpss/syslink_02_00_00_67_alpha2/ti/syslink/samples/hlos/procMgr/ProcMgrApp.c
Compiling: /home/gunter/rowboat-android-gingerbread/hardware/ti/ti81xx/syslink_vpss/syslink_02_00_00_67_alpha2/ti/syslink/samples/hlos/procMgr/usr/Linux/ProcMgrAppOS.c
mv: cannot stat `/home/gunter/rowboat-android-gingerbread/hardware/ti/ti81xx/syslink_vpss/syslink_02_00_00_67_alpha2/ti/syslink/obj/TI816X/samples/procmgrapp.exe_debug': No such file or directory
make[1]: *** [move_debug] Error 1
make[1]: Leaving directory `/home/gunter/rowboat-android-gingerbread/hardware/ti/ti81xx/syslink_vpss/syslink_02_00_00_67_alpha2/ti/syslink/samples/hlos/procMgr/usr/Linux'
make: *** [syslink] Error 2

 

Thanks,

--Gunter

  • 0
    TI__Expert 5400 points

    Hi Gunter,

    Please try building filesystem without -j2 option with following command.

    make TARGET_PRODUCT=ti816xevm TARGET_BUILD_VARIANT=tests OMAPES=6.x

    To build syslink separately please refer to

    http://processors.wiki.ti.com/index.php/TI-Android-GingerBread-2.3-DevKit-2.0_DeveloperGuide#To_build_syslink.2C_kernel_modules_and_sgx_.28SEPARATELY.29


    Thanks and Regards,

    Pankaj Bharadiya

     

     

  • 0 in reply to Pankaj Bharadiya
    Prodigy 120 points

    Pankaj

    I used you suggestion.

    But I still get same result as Gunter.

  • 0 in reply to Matt Chang73902
    TI__Expert 5400 points

     

    Did you try buildilng syslink separately?

    Kindly provide build logs.

     

    Thanks and Regards,

    Pankaj Bharadiya.

     

  • 0 in reply to Pankaj Bharadiya
    TI__Genius 14312 points

    Hi,

     

    on my side, if I do a

    # make clean

    # make TARGET_PRODUCT=ti816xevm TARGET_BUILD_VARIANT=tests OMAPES=6.x

    I am getting still an issue compiling dev2mem, with arm-eabi-g++ not found. (there may be a makefile issue)

    So I manually export

    # export PATH=/home/gunter/rowboat-android-gingerbread/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin:$PATH

    After that another

    # make TARGET_PRODUCT=ti816xevm TARGET_BUILD_VARIANT=tests OMAPES=6.x

    and that build goes thru. Syslink builds fine. BTW, I had to do also the following, since dos2unix was missing I noticed.

    2189  sudo apt-get install tofrodos
     2190  which fromdos
     2191  cd /usr/bin/
     2192  sudo ln -s fromdos dos2unix
     2193  sudo ln -s todos unix2dos

     

    Regards,

    --Gunter

     

     

     

  • 0 in reply to Gunter Schmer
    TI__Expert 5400 points

    Hi Guntur,

    Yes. Devmem2 build will fail if toolchain path is not set. Please apply below patch to <android root>/hardware/ti/sgx directory to fix this.


    diff --git a/tools/devmem2/Makefile b/tools/devmem2/Makefile
    index 6264d2f..c86a7d8 100755
    --- a/tools/devmem2/Makefile
    +++ b/tools/devmem2/Makefile
    @@ -7,9 +7,9 @@ include ../../Rules.make
     TARGETFSDIR  = ../../targetfs/
     CROSS_COMPILE=arm-eabi-
     
    -PLAT_CC  = $(CROSS_COMPILE)gcc
    -PLAT_CPP = $(CROSS_COMPILE)g++
    -PLAT_AR  = $(CROSS_COMPILE)ar
    +PLAT_CC  = $(CSTOOL_PATH)/$(CROSS_COMPILE)gcc
    +PLAT_CPP = $(CSTOOL_PATH)/$(CROSS_COMPILE)g++
    +PLAT_AR  = $(CSTOOL_PATH)/$(CROSS_COMPILE)ar
     
     DEBUG_RELEASE = Release
     PLAT_CFLAGS   = -Wall -DRELEASE -O2

    Thanks and Regards,
    Pankaj Bharadiya