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.

Compiler/TMS320C6748: Where is timake?

Part Number: TMS320C6748
Other Parts Discussed in Thread: OMAP-L138, OMAPL138

Tool/software: TI C/C++ Compiler

I am attempting to change from UART 2 to UART 1 on a modified C6748 LCDK board (custom build, but almost identical to reference design). I finally figured out I need to recompile the DSP side of the SFH program, and when I execute "make" it tells me it can't find timake.  I have CCS installed, and I have compiled and tested many programs on the eval board, but now I want to change the flash loader UART.  How do I point to the C6748 compiler?

Thanks,

Mike

  • Mike,

    timake.exe was a utility that came with really old versions of CCS (v3) for building projects outside of the IDE.

    There is some more information on it here:

    processors.wiki.ti.com/.../CCStudio_FAQ

    What is prompting for timake? You mentioned that you run make and it asks for timake. Not sure how make would have any knowledge of timake. timake was generally invoked directly after running a batch file that setup the appropriate environment variables.

    I might need to loop in some C67x dsp folks.

    Regards,
    John
  • From directory: OMAP-L138_FlashAndBootUtils_2_40/OMAP-L138 I execute "make" in cygwin and get this:
    $ make
    make -C CCS all
    make[1]: Entering directory '/cygdrive/c/ti/OMAP-L138_FlashAndBootUtils_2_40/OMAP-L138/CCS'
    make[2]: Entering directory '/cygdrive/c/ti/OMAP-L138_FlashAndBootUtils_2_40/OMAP-L138/CCS/UBL_DSP'
    Building UBL_SPI_MEM.pjt for device C6748
    /bin/sh: line 4: timake: command not found
    .....

    A better question might be how do I recompile the DSP side using the CCS IDE? The host side does not need to be recompiled (should not need to be anyway).

    Thanks!
    Mike
  • Do you have CCSv3.3? If so you should be able to open the UBL_SPI_MEM.pjt project and use that to build the DSP side. I am going to loop in someone with experience flashing OMAPL138/C6748 to comment.

    Regards,
    John
  • I've got CCS 7.1. I will see if I can find that older version. Thanks!
  • Mike,

    I was able to build this project using CCSv6.1.3. You can import the project as a legacy CCSv3.3 project and build the .out file as you can see from below:

    The post build step in the project may fail as the the directory where the .out is installed has changed but you can manually pass the UBL to the AISGen tool to convert it to a boot binary.

    I am curious to know why you are using the bootloader from this older software package. Bootloaders are also supported in relatively newer packages like starterware and Processor SDK. but if you have already completed the development then it may be okay to stick to the older software baseline.

    Regards,

    Rahul

     

  • I'm using the C6748_StarterWare_1_20_04_01 along with OMAP-L138_FlashAndBootUtils_2_40 on the C6748-LCDK eval board. We essentially copied that reference design so the code developed would not have to change. Is there a more modern version of the sfh utility which can compile under the CCSv7? I'll be happy to use that.

    I am using the AISGen tool to create bootable images and write them to flash directly using noubl, and that works with UART2. I just want to change it to UART1. That's all I need to do. I will give version 6 a try!
    Thanks!
    Mike
  • Mike,

    If Rahul is able to import it into CCSv6 then I would expect that CCSv7 can do it as well. When you import into CCSv7 does it complain?

    John
  • John,

    I had some issue with CCSv7 when importing the same project. This may be due to CGTools 8.1.2 not support COFF binary build which was the default setup with CCSv3.3 projects. In CCS v6..1.3 , there is CGTools 7.4.x which allows those projects to build with COFF support.

    Regards,
    Rahul
  • I got 6.1.3, found UBL_NAND and got that to compile, hunted around and found the UBL_NAND.out and converted that to .ais.  So now I assume I have to recompile the host side of sfh so it will include this version of UBL_NAND.ais?  How does it know where to find the right version?

    Edit: I am now really confused: there is a directory "/OMAP-L138/GNU/ubl" which contains *.bin and *.out for lots of different platforms.  Does the UBL_NAND.out get copied there (and renamed for the C6748_LCDK version) and operated on by out2prc?  And then sfh gets recompiled?