• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 83 subscribers
  • Views 309 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.

TMS320F28388D: Invalid agruments ' error in my pinConfiguration file.

Wilko Moritz
Intellectual 255 points

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

Tool/software:

Hello,

I'm encountering an issue where all the functions in my pinConfiguration file are suddenly showing an "invalid arguments" error.

When I click on one of the functions, I get the following message:

Invalid arguments 
Candidates are:
void GPIO_setControllerCore(unsigned long int, enum {C:\ti\c2000\C2000Ware_4_00_00_00\driverlib\f2838x\driverlib\gpio.h:7153})

Recently, I made a few changes to my project:

  1. I implemented SysConfig.
  2. I upgraded C2000Ware to version 5_03, as it was required for the correct CLB simulation.

Since the error message references the old version of C2000Ware (4_00_00_00), I suspect the issue is related to this, but I’m unsure how to resolve it.

Any guidance would be greatly appreciated.

Regards,

Wilko

  • 0
    TI__Genius 16476 points

    Hi Wilko,

    You would need to change the include path in your project settings.

    Thanks

  • 0 in reply to Prarthan Bhatt
    Intellectual 255 points

    Hello Prarthan,

    Are you referring to the Properties > CCS Build > C2000 Compiler > Include Options? If so, I have checked them, and they appear to be correct.

    One thing to note is that the errors don't appear as typical code errors; instead, they show up as red bug icons on a lamp symbol.

    Additionally, here’s some further information that may be relevant:

    I was able to reproduce the same errors in a different file. The behavior is as follows: the file initially shows no errors, even after compiling. However, once I open the file, the errors appear and persist, even after closing or compiling again.

    I have a file linked to both CPU1 and CPU2. Interestingly, the errors only occur in the CPU1 version, while in CPU2 the code is recognized correctly.

    For both CPUs, I am using the same workspace settings for Code Analysis.

    Best regards,

    Wilko

  • 0 in reply to Wilko Moritz
    TI__Genius 16476 points

    Wilko,

    Can you share screenshot of the error.

    Thanks.

  • 0 in reply to Prarthan Bhatt
    Intellectual 255 points

    Hello Prarthan,

    I managed to "fix" the issue by navigating to Properties -> C/C++ General -> Code Analysis -> Launching and unchecking both checkboxes.

    After that, I deleted the errors and rebuilt the project.

    However, I would prefer not to have to disable the Code Analysis feature. Do you have any alternative solutions or suggestions?

    Regards,

    Wilko

  • 0 in reply to Wilko Moritz
    TI__Genius 16476 points

    Hi Wilko,

    Since this is not a GPIO question, I will transfer this thread to CCS expert to assist in your query.

    Thanks