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

DRV8301-69M-KIT: #16008-D Error

Terry Harrison
Intellectual 615 points
Part Number: DRV8301-69M-KIT
Other Parts Discussed in Thread: MOTORWARE, TMS320F28069

On my dev machine I have installed CCS 10.2 and Motorware. I have been working on Lab10a in Motorware and also built a custom version of the lab which is customized to my application. It has been working for about 1.5 months. I have not touched the app for about 2 weeks and today I opened the app and tried to do a build. It gave me two errors: 

fatal error #16008: file "/db/lang/msp/exec/rts430x.lib" specifies
   ISA revision "MSPX", which is not compatible with ISA revision "MSP"
   specified in a previous file or on the command line
fatal error #16008: file "/db/lang/msp/exec/rts430x.lib" specifies
   ISA revision "MSPX", which is not compatible with ISA revision "MSP"
   specified in a previous file or on the command line

The remedy says that if you are explicitly specifying a RTS library to change that to Automatic. I have always had it to automatic. I have cleaned, rebuilt, etc everything I can think of but nothing help. I found
an online reference that suggested that something may have been built without FPU support. The app ONLY uses TI libs from the Motorware download. I have no other linked libs in the solution.

I found that by going to the compiler options and unselecting the FPU34 support that the solution will compile. However since I am working on a motor and the 
IQ table math uses the FPU that when I compile and download the file to Flash the operation is horrible. 

What could have rendered this solution unusable just sitting on the hard drive? I have tried to select other RTS combinations but nothing works. This is another thing I get in the 
error listing
error #16008-D: file "boot28.asm.obj in
 C:\ti\ccs1010\ccs\tools\compiler\ti-cgt-c2000_20.2.4.LTS\lib\rts2800_fpu32.l
 ib" specifies ISA revision "C28FPU32", which is not compatible with ISA
 revision "C2700" specified in a previous file or on the command line

Please help! We are at release for the motor card and this is a huge issue at the last minute. Thanks, Terry
  • 0
    Intellectual 615 points

    This is some more of the error:

    error #16008-D: file
    "C:/ti/motorware/motorware_1_01_00_18/sw/modules/fast/lib/32b/f28x/f2806x/28
    06xRevB_FastSpinROMSymbols.lib<TMS320x2806x_REVB_boot_rom_out_FD$$MPY_tmp.ob
    j>" specifies ISA revision "C2800", which is not compatible with ISA
    revision "C28FPU32" specified in a previous file or on the command line
    error #16008-D: file
    "C:/ti/motorware/motorware_1_01_00_18/sw/modules/fast/lib/32b/f28x/f2806x/28
    06xRevB_FastSpinROMSymbols.lib<TMS320x2806x_REVB_boot_rom_out_FD$$TOL_tmp.ob
    j>" specifies ISA revision "C2800", which is not compatible with ISA
    revision "C2700" specified in a previous file or on the command line
    error #16008-D: file
    "C:/ti/motorware/motorware_1_01_00_18/sw/modules/fast/lib/32b/f28x/f2806x/28
    06xRevB_FastSpinROMSymbols.lib<TMS320x2806x_REVB_boot_rom_out_FS$$DIV_tmp.ob
    j>" specifies ISA revision "C2800", which is not compatible with ISA
    revision "C2700" specified in a previous file or on the command line

  • 0 in reply to Terry Harrison
    TI__Guru** 115650 points

    You have to re-install CCS and enable C2000 support during the installation process.

    And the lab10a doesn't use the FPU32 version, please try to run the example lab10a to see what happen.

  • 0 in reply to Yanming Luo
    Intellectual 615 points

    I tried that prior to contacting the forum. The same issue occurs. This app had been working for months but suddenly developed this issue. CCS had updated to 10.2 since the last time I ran this app but even after reinstalling 10.1 the issue is still here. I found a reference in another posting that someone else had the same error message. It was never resolved by TI. I also searched ever filename and file content on my hard drive and  can find no such file by the name of rts430x.lib. In the other post the TI respondent mentioned that this  file is part of the MSP series but I have never dealt with those products. The complete project compiles just fine but when the  linker runs it finds this reference somewhere. I have checked all the  project files and no such entry exists. This is a serious issue it would seem with CCS.

    Also when i try to run lab10a the errors that I showed above are what happens and it  is labeled fatal. If I could run this lab all would be fine.

  • 0 in reply to Terry Harrison
    TI__Guru** 115650 points

    Did you try to install the CCS?

    You might click the "Window"->"Preferences"->"Code Composer Studio"->"Build"->"Compilers", to check if there is any C2000 compiler is installed in the "Discovered tools" table.

    And check if there is any C2000 compiler folder in "\ccs\tools\compiler" folder in CCS installation directory. If not, please re-install the CCS.

    CCS

    https://www.ti.com/tool/CCSTUDIO

  • 0 in reply to Yanming Luo
    Intellectual 615 points

    Ok I have solved this issue. It is apparently two defects in the CCS. I have seen it happen before but I repeated this and can see what happens. When you set the properties of the project and save them. It is not unusual to see them not stay. I set the properties to indicate that the processor was the TMS320F28069 and set the other parameters as well. After I closed the settings and tried to do a build I got the errors. What had happened was the processor settings in the properties had defaulted back to the generic C2000. When it did that I started getting the erroneous lib errors. The linker has an issue and pointed to a file that does not even exist on my machine so clearly it has a defect. In addition once this has occurred the error will never clear without reloading the CCS. Major time waste for sure. I now have it working.