• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 99 subscribers
  • Views 304 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.

timake problem

Zaf
Prodigy 130 points
Other Parts Discussed in Thread: OMAP-L138, OMAP-L137

I am trying to build the OMAP-L138_FlashAndBootUtils_2_30. I type make in the "OMAP-L138" directory. It has 3 subdirectories, CCS, Common and GNU. I guees it first goes into GNU directory and starts a make there. Everything build successfully up to:

make[4]: Entering directory `./OMAP-L138/GNU/AISUtils/AISextra/src'
make[4]: *** No rule to make target `timake'.  Stop.

I looked at the previous posts and it says this tool is included in CC3.3. But I am not using 3.3. As a matter of fact, CCS is not even installed in my Ubuntu system. Instead I have "ti_cgt_c6000_6.1.14_setup_linux_x86.bin" set up. The compiler, linker etc. is called from that directory.

Why is it asking about the timake? And how can I get rid of this problem. (make clean did not help)

Thanks

  • 0
    TI__Guru** 116170 points

    I think you are trying to build OMAP-L138_FlashAndBootUtils_2_40 instead of 2_30 that you have mentioned. You need the timake utility provided in the CCSv3.3 release to be able to built the CCS projects in the package. Also you need Microsoft .Net Framework. The rebuild procedure is primarily tested on windows platform with cygwin environment only so you might face some issues trying to rebuild this on the ubuntu platform.

    Regards
    Rahul

  • 0 in reply to Rahul Prabhu
    Prodigy 250 points

    I was able to get everything working under linux for the OMAP-L137 Flash and Boot Util package, so it is probably possible for the L138 as well. Basically, you need to hide the CCS make file, install the TI C6000 linux compiler package and a suitable ARM cross-compiler (such as the one from Code Sourcery) and install the mono package to do the .NET stuff. There are a few mods you have to make to some makefiles (I don't remember them all at this moment) and voilla, you can modify, build and flash.

  • 0 in reply to Richard Tennis
    TI__Guru** 116170 points

    Richard,

    If you elaborate on what files you changed or share your versions of the make files here, others going down this path might benefit from your effort. Do post the steps you followed to get this to work when you get a chnace.

    Thanks and Regards,

    Rahul

  • 0 in reply to Rahul Prabhu
    Prodigy 130 points

    The problem is solved when I made the files at  "OMAP-L138/GNU" level, not at  "OMAP-L138" level.

    Because at the "OMAP-L138" level. it tries to build the files in the "CCS" directory. I realize that I don't need the files in CCS directory in order to create the sfh and the ubl files.

    After buildning those files I was able to download the ubl successfully   over serial line and run u-boot on top of it. I did not need the code composer and .net environment. I use Timesys build environment for building for the TI L138 eval board.

    Thanks and best regards

  • 0 in reply to Zaf
    Prodigy 250 points

    Hi Zaf,

    Zaf said:

    The problem is solved when I made the files at  "OMAP-L138/GNU" level, not at  "OMAP-L138" level.

    This is basically what I did for the L137 by renaming the makefile at that level.

    Because at the "OMAP-L138" level. it tries to build the files in the "CCS" directory. I realize that I don't need the files in CCS directory in order to create the sfh and the ubl files.

    Exactly, these projects are just an alternative means of building the ubl etc.

    After buildning those files I was able to download the ubl successfully   over serial line and run u-boot on top of it. I did not need the code composer and .net environment. I use Timesys build environment for building for the TI L138 eval board.

    So you did a native compile rather than a cross-compile like I did. Pretty neat!

    I looked to see what modifications I had to make for cross compiling and found that the main thing was to replace OMAP-L137/GNU/AISUtils/HexAIS_OMAP-L137.exe with a script that runs mono on the original HexAIS_OMAP-L137.exe (renamed HexAIS_OMAP-L137.mono) since on my system (openSUSE 12.2) the program loader is not set to recognize and run mono executables. I know some distributions do that by default, but it carries a security risk.