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

Problems on rebuilding IBL

Nuoxi Lin
Intellectual 650 points

Hi eveyone,


     I am using a custom board, so i need to rebuild IBL to update EEPROM.

I conform to the instructions in build_instructions.txt, but there are still some problems.

     At the beginning of all, I downloaded mingw-get-inst-20120426.exe from

http://sourceforge.net/projects/mingw. And I installed it at C:\MinGW .

    Here are the my steps to rebuild IBL.

1. Add the follwing directories to environment variables.

C:\MinGW\msys\1.0\bin
C:\MinGW\bin
E:\ti\ccsv5\tools\compiler\c6000\bin
E:\ti\mcsdk_2_00_05_17\tools\boot_loader\ibl\src\make
E:\ti\ccsv5\tools\compiler\c6000\include


2. Double click msys.bat located at C:\MinGW\msys\1.0.

3. Then input command "cd E:\ti\mcsdk_2_00_05_17\tools\boot_loader\ibl\src\make" .

4. Modify setupenvLnx.sh to match my CCS installation directory.

5. Input command "source setupenvMsys.sh".

6. Input command "make evm_c6678_i2c ENDIAN=little I2C_BUS_ADDR=0x51" and press Enter.

   It will clue on errors.

   It prints out the follwing ingformation.

   ../../../arch /c64x / types.h ,line 55:fatal error #5 : could not open source file "stdlib.h"


7. So I copy stdlib.h to the directory E:\ti\mcsdk_2_00_05_17\tools\boot_loader\ibl\src\arch\c64x .

And Input the command "make evm_c6678_i2c ENDIAN=little I2C_BUS_ADDR=0x51" one more time.

    The error mentioned in step 6 disappears, but it prints out the follwing ingformation.


i2cparam.c line 56: fatal error #5:could not open file "stdio.h".

8. Then i copy stdio.h to directory E:\ti\mcsdk_2_00_05_17 \tools\boot_loader\ibl\src\util\i2cConfig .

File i2cparam.c is located in this directory.

Then Input the command "make evm_c6678_i2c ENDIAN=little I2C_BUS_ADDR=0x51" ,

the error  mentioned in step 7 appears again.

How to solve this problem ? Any Advice?

Hope someone helps. Thank you in advance.

Nuoxi


Regards

 

 

  • 0
    TI__Intellectual 2220 points

    Nuoxi,

    Can you double check step 4 and 5 as you listed? It says you modified setupenvLnx.sh and then sourced setupenvMsys.sh. If you are working in Windows, you should only work with setupenvMsys.sh.

    If this is not the cause of your problem, can you try adding your CGT/include link to your PATH? The C6000 Code Generation Tools has the .h files that the compilation is looking for.

    Let me know how this goes.

    -Ivan

  • 0 in reply to Ivan Pang
    Intellectual 650 points

    Hi Ivan,  

        I am sorry for the delay.

        I am working in Windows and I work with setupenvMsys.sh only.

    Ivan Pang said:
    If this is not the cause of your problem, can you try adding your CGT/include link to your PATH?

    Hi Ivan,

       Does the word "PATH" refer to the environment variables set in PC System Properties  or the PATH set in setupenvMsys.sh ?

    If it refers to the former, then i have added it before I started the post. If it refers to the latter, then i don't know whether i have added the path correctly

    for i don't know its fatal format. Anyway,so far  there are errors mentioned before.

     I have attached setupenvMsys.sh here. can you have a look at it? Thank you very much.

    PS: I transfered setupenvMsys.sh to .txt format to attanch it.

    Nuoxi

    Regards

  • 0 in reply to Ivan Pang
    Intellectual 650 points

    Hi Ivan,

        The cause is that I have modified setupenvMsys.sh uncorrectly.

    I forgot to modify C6X_BASE_DIR. Now I can re-build IBL correctly.

    Thank you for your help.

    Nuoxi

    Regards

  • 0 in reply to Nuoxi Lin
    TI__Intellectual 2220 points

    Nuoxi,

    Good to hear your problem is solved. To answer your earlier question, when I said PATH, I meant the PATH during your build environment. Msys shell inherits PATH from Windows' environment variable, so modifying either the .sh or the system properties will have the same effect during build time.

    Using our provided setup scripts is always preferred. Like in this case, it sets up variables to be used later on in the make files.

    -Ivan