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.

TMS320F280025C: Generated device.h conflicts with driverlib/debug.h

Part Number: TMS320F280025C
Other Parts Discussed in Thread: SYSCONFIG, C2000WARE

Just wanted to make the software team aware they are supplying software which re-declares the __error__ function.  This in turn causes compilation to fail if both device.h and driverlib are included.  The problem looks to be in the debug.h file.  Previously (with F28004x for example), __error__ was declared as:

extern void __error__(char *filename, uint32_t line);

In the F28002x driverlib this is declared as follows:

extern void __error__(const char *filename, uint32_t line);

Since __error__ is also declared by the sysconfig generated device.h file as follows:

extern void __error__(char *filename, uint32_t line);

 

I feel as though the declaration in the f28002x driverlib needs to change to match everything else.

Best,

Trey

  • Trey,

    Thank you for reporting back this error. I will let Veena from the SW team respond about the function declaration for __error__ but I do have one question for you.

    You mentioned SysConfig generated device.h. I don't believe we are generating device.h using SysConfig. Unless you somehow read our minds since we plan on doing that for 2023 Slight smile, but we don't have it in any public release in 2022.

    Can you share where you saw device.h get generated from SysConfig? I want to make sure others don't run into the same confusion.

    Thank you,
    Nima Eskandari
    C2000 Application Manager

  • Hi Trey,

    Regarding change from char * to const char *, this change was rolled out in C2000ware v4.01.00 as the previous definition was causing MISRA violation. The change has been done for all Gen3 devices in both debug.h and device.h files. Let us know if you are seeing any discrepancy.

    Regards,

    Veena

  • Nima,

    Ahh ok my mistake.  I've been bouncing back and forth between a lot of different software lately.

    Veena,

    You're correct.  It appears I was referencing files from both 4.01 and 4.00.  Sorry for the false alarm.

    Trey