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

LAUNCHXL-F28379D: CPUTIMER0_BASE is undefined on CPU2

Sumit B
Prodigy 230 points

Part Number: LAUNCHXL-F28379D
Other Parts Discussed in Thread: C2000WARE

Tool/software:

Hello there,

I am working with dual core project where I am sending some data from core1 to core2 using IPC driver api which is working fine. Also using CPUTIMER0 (not interrupt but polling) on cpu1 which is also working fine.

Now I want to use the same timer in similar fashion in core2 but when I build the program I am running into this error (see below).

Note: These errors go away if I add [#include "device.h"] header in my cpu2 main program file but then my IPC breaks (I don't receive data on cpu2 from cpu1)

Could you tell me what might be causing this? as far as I know each CPU has its own timer so using the same timer base should not be the issue, I even tried with CPUTIMER1_BASE on cpu2 but problem remains the same.

Thank you,

  • 0
    TI__Mastermind 25340 points

    Hi Sumit,

    You are correct, there is also a CPU timer module for CPU2. All of the base addresses (included the define for CPUTIMER0_BASE) are defined in the /driverlib/inc/hw_memmap.h file. This gets included in driverlib.h, so as long as you have #include "driverlib.h" in your main C file for CPU2, the compiler should be able to locate the define for the CPUTIMER0_BASE in CPU2's code.

    I would suggest following one of the IPC examples in C2000ware to see how to set up the includes for both the CPU1 and CPU2 main C files.

    Best Regards,

    Delaney

  • 0 in reply to Delaney Woodward
    Prodigy 230 points

    Thank you Delaney.