TMS320F2806: Not compatible with ISA revision

6th Sep is a holiday in US and hence please expect a delay in response.

Hello,

Is there a requirement that you keep using CCSv5 and v6 of the SFO library? I would encourage you to migrate to the latest versions if possible.

Best Regards,

Marlyn

Marlyn Rosales Castaneda20 said:

Is there a requirement that you keep using CCSv5 and v6 of the SFO library? I would encourage you to migrate to the latest versions if possible.

Dear Sir Marlyn,

This is what I wanted to know actually. If you look my old version you can see it might be 6.0.1 version explained in .ccsproject file. Do you want me to work in version 10?

<deviceVariant value="TMS320C28XX.TMS320F28069"/>
	<deviceFamily value="C2000"/>
	<codegenToolVersion value="6.1.0"/>
	<isElfFormat value="false"/>
	<connection value="common/targetdb/connections/TIXDS2XXUSB_Connection.xml"/>
	<linkerCommandFile value="28069_RAM_lnk.cmd"/>
	<rts value="libc.a"/>
	<templateProperties value="id=com.ti.common.project.core.emptyProjectTemplate,"/>
	<isTargetManual value="true"/>
</projectOptions>

Thank you for your response, actually can you please check if you have FPU support enabled first. Within your current version of CCS right click on the project, select properties, and then go to Build -> C2000 Compiler -> Processor Options. Within the processor options window you should see an option that says "Specify floating point support", does this show as fpu32? If not, can you please select this option and try to build your project once more.

Best Regards,

Marlyn

Dear Sir Marlyn,

My project has SFO_TI_Build_V6b.lib, but while I have ported ccs 10.3 this file link showing error.

I have delete it from tree.

Marlyn Rosales Castaneda20 said:

Thank you for your response, actually can you please check if you have FPU support enabled first. Within your current version of CCS right click on the project, select properties, and then go to Build -> C2000 Compiler -> Processor Options. Within the processor options window you should see an option that says "Specify floating point support", does this show as fpu32? If not, can you please select this option and try to build your project once more.

Yes, after doing so my project is going to more difficult errors, 

Take a look here, https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/f/c2000-microcontrollers-forum/1034386/tms320f2806-16000-object-files-have-incompatible-formats/3825967#3825967

Hello,

MD MUBDIUL HASAN said:

I have delete it from tree.

To clarify, you have removed "SFO_TI_Build_V6b.lib" from your project?

MD MUBDIUL HASAN said:

Yes, after doing so my project is going to more difficult errors, 

Are you still facing the error related to SFO_TI_Build_V6b.lib? If not, I will close this thread and we can continue working through the errors you do have in the thread that you linked to.

Best Regards,

Marlyn

Marlyn Rosales Castaneda20 said:

To clarify, you have removed "SFO_TI_Build_V6b.lib" from your project?

I am sorry, in this thread I am using ccs version 5. The library I am talking about  SFO_V6.H.Kindly consider my first post. I am using  SFO_V6.H now.

I am trying to have a good result both in ccs v.5 and ccs 10.3. I got to manage remove many errors but suddenly in v10.3 its raises 3 to 104. 

Hello,

Marlyn asked me to take a look at your issue to see if I can give some help as well. 

I'd like to confirm if the error you seeing in CCS v5 is from the original post?  The error you posted there is related to the SFO .lib being built with the FPU32 option selected   --float_support=fpu32 as well as the runtime support library  rts2800_fpu32.lib being used.

Can you confirm the above, and if there is any new error?

Best,

Matthew

MatthewPate said:

I'd like to confirm if the error you seeing in CCS v5 is from the original post?  The error you posted there is related to the SFO .lib being built with the FPU32 option selected   --float_support=fpu32 as well as the runtime support library  rts2800_fpu32.lib being used.

Can you confirm the above, and if there is any new error?

Dear Sir Matthew,

Thank you once again to join here.

Lets consider this project only in ccs v.5.

Take look what you wanted to check.

The error console says' 
#16008 file DEMO C/C++ Problem

MatthewPate said:

Thanks for the additional info.  I looked into a controlSUITE install that has the V6 build, there is a FPU and non FPU version of this library in this directory: C:\ti\controlSUITE\device_support\f2806x\v151\F2806x_common\lib\

Dear Sir,

Thank you once again. I am not using controlSUITE, take a look my file search path,

Now I have just one error'  "C:/F2806x_common/lib": Permission denied 

MatthewPate said:

Since you are compiling with FPU32 and rts2800_fpu32.lib you will need to use the SFO_TI_Build_V6b_FPU.lib vs the SFO_TI_Build_V6b.lib you mentioned at the top.  The error is related to SFO_TI_Build_V6b.lib was built with the floating point option set to "softlib", meaning not using the FPU that is on the F2806x for increase floating point performance.

Yes, well said. This problem is moved to just upper one. 

MatthewPate said:

The top portion of the screen shot you attached is only for direct file names, not paths; so you should just need to remove the line with the C:/F2806x_common/lib since that is a directory.

If I remove it again previous problem appears. Including memory SECTION, unresolved issues and so on.   

I want to make sure we are talking about the same dialogue boxes, appreciate your patience here.  I want to remove the red lined items below only, leaving the rest alone.  Confirming that this change results in the unresolved issues?

Best,

Matthew

MatthewPate said:

want to make sure we are talking about the same dialogue boxes, appreciate your patience here.  I want to remove the red lined items below only, leaving the rest alone.  Confirming that this change results in the unresolved issues?

According to your advice, following errors are coming,

#10010 errors encountered during linking; "DEMO.out" not built 

warning #10247-D: creating output section ".ebss" without a SECTIONS
   specification
warning #10247-D: creating output section ".econst" without a SECTIONS
   specification
warning #10247-D: creating output section ".reset" without a SECTIONS
   specification
warning #10247-D: creating output section ".switch" without a SECTIONS
   specification
warning #10247-D: creating output section "CLA1mathTables" without a SECTIONS
   specification
warning #10247-D: creating output section "ClaDataRam2" without a SECTIONS
   specification
warning #10247-D: creating output section "ramfuncs" without a SECTIONS
   specification

 undefined             first referenced
  symbol                   in file     
 ---------             ----------------

 _AdcRegs              ./CLA.obj       
 _AdcResult            ./CLATask.obj   
 _Cla1Regs             ./CLA.obj       
 _Cla1funcsLoadSize    ./CLA.obj       
 _Cla1funcsLoadStart   ./CLA.obj       
 _Cla1funcsRunStart    ./CLA.obj       
 _ConfigCpuTimer       ./Main_Timer.obj
 _CpuTimer0            ./Main_Timer.obj
 _CpuTimer0Regs        ./Main_Timer.obj
 _CpuTimer2            ./ADC.obj       
 _CpuTimer2Regs        ./ADC.obj       
 _DSP28x_usDelay       ./ADC.obj       
 _ECanaMboxes          ./eCAN.obj      
 _ECanaRegs            ./eCAN.obj      
 _EPwm1Regs            ./PWM.obj       
 _EPwm2Regs            ./PWM.obj       
 _EPwm3Regs            ./PWM.obj       
 _EPwm4Regs            ./PWM.obj       
 _EPwm5Regs            ./PWM.obj       
 _EPwm6Regs            ./PWM.obj       
 _EPwm7Regs            ./PWM.obj       
 _EnableInterrupts     ./main.obj      
 _GpioCtrlRegs         ./main.obj      
 _GpioDataRegs         ./main.obj      
 _GpioIntRegs          ./AC_SYNC.obj   
 _InitFlash            ./main.obj      
 _InitPeripheralClocks ./main.obj      
 _InitPieCtrl          ./main.obj      
 _InitPieVectTable     ./main.obj      
 _PieCtrlRegs          ./eCAN.obj      
 _PieVectTable         ./eCAN.obj      
 _RamfuncsLoadEnd      ./main.obj      
 _RamfuncsLoadStart    ./main.obj      
 _RamfuncsRunStart     ./main.obj      
 _SciaRegs             ./SCI.obj       
 _ScibRegs             ./SCI.obj       
 _SpiaRegs             ./EEPRom.obj    
 _SysCtrlRegs          ./main.obj      
 _XIntruptRegs         ./AC_SYNC.obj   
>> Compilation failure

 
#10234-D unresolved symbols remain  DEMO

I'm not completely sure why the top most /common/lib is needed or accepted by CCS.  The errors the CCS is generating are related to the header file includes which are not in /common/lib.

This path is from controlSUITE path where common/lib/ contained the ROM libraries and the SFO libraries.

At any rate, let's go ahead a put those back, I looked into the permissions error, this occurs when the folder does not have write permissions enabled.  Let's try to enable write permissions on that folder path and see if this allows the build to finish.

Best,
Matthew

MatthewPate said:

let's go ahead a put those back, I looked into the permissions error, this occurs when the folder does not have write permissions enabled.  Let's try to enable write permissions on that folder path and see if this allows the build to finish.

What to do then ? Kindly explain how to do write permission  to folder path. 

From what I read, you need to right click on the folder in question in windows explorer and click properties.  Then make sure "Read Only" is not checked.

Best,

Matthew

MatthewPate said:

From what I read, you need to right click on the folder in question in windows explorer and click properties.  Then make sure "Read Only" is not checked.

Do mean this one? This has non checked mode. If you click on the check box the black portion will go away, if you click again then the box will clear. Do you want me to make the box same as like below Hidden option?

Correct, I want you to make the box empty, this will make the files in the folder writable.

Best,

Matthew

MatthewPate said:

Correct, I want you to make the box empty, this will make the files in the folder writable.

Dear Sir,

Even if I do error remains same.

Hasan,

I need some additional time to think about this issue, I'm not certain the cause if the write protections didn't fix the issue.

Best,

Matthew

MatthewPate said:

I need some additional time to think about this issue, I'm not certain the cause if the write protections didn't fix the issue.

Best,

Keep in  mind that this is existing project opened in ccs version 5

Hasan,

You mentioned that you are not using controlSUITE, is this a TI example or a custom example?  Would it be possible to share the project and files to see if I can get it to compile on my machine?

Best,
Matthew

MatthewPate said:

You mentioned that you are not using controlSUITE, is this a TI example or a custom example?  Would it be possible to share the project and files to see if I can get it to compile on my machine?

Dear Sir,

Thank you again for reply here. My project is customized one and confidential property. 

Its similar to Picolllo, if you can see the pervious thread of this post  I am using F2806x_common and F2806x_header. I have solved few problem regarding adding suitable file path, including libraries.

I have another option, C:\Users\F2806x_examples_ccsv5

Do you want me to use it?

Hasan,

Is that last path from the import of the project into CCS, or the path where the example director is installed?  The reason I ask is that when you import a project into CCS it creates a local copy in the User/workspace name/ path on your machine.

I believe it attempts to copy over everything in the target directory, but I think where things get messy is if there are alot of relative paths going on.  Sometimes it is simpler to just add the dependent files in the project directory that is imported for the sake of the path resolution.

I'm not really sure why CCSv5 would be much different than CCSv10 in this regard.

The example you mentioned, is this from a TI source, where I could install it in a similar path on my machine?

Best,

Matthew

MatthewPate said:

Is that last path from the import of the project into CCS, or the path where the example director is installed?  The reason I ask is that when you import a project into CCS it creates a local copy in the User/workspace name/ path on your machine.

Dear Sir,

In this regards what I did is copied my project folder from different cloud storage then make a workspace in Onedrive and pest it. This project only supported by C:\F2806x_common and C:\F2806x_headers. CCS installed here C:\ti\ccsv5

If I need any files to add in project tree I usually use those location. Dont you think onedrive is a problem? both of them stays in C drive!

MatthewPate said:

I believe it attempts to copy over everything in the target directory, but I think where things get messy is if there are alot of relative paths going on.  Sometimes it is simpler to just add the dependent files in the project directory that is imported for the sake of the path resolution.

I do believe what you said again. Let me show you, project>properties>Recourses>Link Resources>  

Workspace location went wrong?

I'm not sure the effect of the workspace_loc in this regard.  Can you create a new workspace and re-import the project to see if we can get alignment?

Matt

MatthewPate said:

I'm not sure the effect of the workspace_loc in this regard.  Can you create a new workspace and re-import the project to see if we can get alignment?

Dear Sir,

Its true that those workspace_loc parameter and path cant be change in the properties.

Let me make again a workspace.