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

TMS320F28379D: Timer on F28379D with SYS/BIOS

Zvi Traiger1
Intellectual 450 points
Part Number: TMS320F28379D

Hello,

There are three CPU timers in the device, SYS/BIOS uses the TIMER2 for tick which leaves two timers ( 0 and 1 ).

I need to configure one timer:

#include <ti/sysbios/family/c28/Timer.h>

Timer_Params timerParams;

After compilation I get this Error:

'Timer_Params' is ambiguous '
Candidates are:
 ti_sysbios_family_c28_Timer_Params()
 ti_sysbios_family_c28_Timer_Params(const ti_sysbios_family_c28_Timer_Params &)
'

When I try to do Open Declation:

C:\ti\bios_6_76_04_02\packages\ti\sysbios\hal\Timer.h
C:\ti\bios_6_76_04_02\packages\ti\sysbios\family\c28\Timer.h

So it looks like compiler could not resolve which header to use.

Any ideas why ?

  • 0
    Intellectual 450 points

    Ok, 

    I had this line:

    #include <xdc/cfg/global.h>

    After removing it all compiled Ok.

    I just copied it from other project … What is this include ??

  • 0 in reply to Zvi Traiger1
    TI__Guru 53765 points

    The global.h file #includes the local header file that gets generated based off your SYS/BIOS .cfg file. It basically allows you to refer to symbols defined in your .cfg file in your C code.

    Not sure why this caused an issue for you though. I was able to include both in the same file without issue...

    Whitney

  • 0 in reply to Whitney Dewey
    Intellectual 450 points

    Somehow this error appeared again and without any change in the code.. 

    The code builds ok, but I do get errors in the Problems tab

    Looks like it has some connection to IDE (restarting CCS removes the error and later reappears until next CCS restart) :

  • 0 in reply to Zvi Traiger1
    Intellectual 450 points

    I was able to find fix for the problem

    https://e2e.ti.com/support/tools/ccs/f/81/t/628484

    Static code analysis:

    By default, Code Analysis checks are internally disabled for CCS projects.

    The reason they are disabled by default is that the rules defined in the Eclipse static analysis tool are somewhat different than those defined by the TI tools. Users who are typically developing for TI embedded parts using TI compiler tools are more interested in the errors reported by the TI tools rather than the generic Eclipse CDT errors. To avoid confusion between the two sets of error checks, code analysis checks are disabled.

    To confirm that code analysis is disabled, go to Project Properties → C/C++ General → Code Analysis → Launching, and observe that the “Run with build” and “Run as you type” boxes are unchecked.

    If you click on Apply or Apply and Close in the Code Analysis dialog, it will turn on code analysis. This may trigger syntax and programming errors. If errors are reported only in the Problems view and CCS editor margins but not in the CCS build console, then they are likely coming from Eclipse CDT and not from TI compiler tools, hence do not impact the build.