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

Header file to reference statically created SYS BIOS objects?

CalvinC
Intellectual 990 points

In DSP BIOS 5.x, we inlcude a BIOS generated file "myprojectcfg.h" that contains the declarations for the statically created BIOS objects. I'm not including any such file with SYS BIOS projects but the compiler is not complaining about implicitly declared or undefined identifiers. How does the compiler know? Is there a generated header file I can reference?

While maybe not an issue for CCS4, we are required to run static analyzers on our source code (lint like). If I don't have a header file that declares the BIOS objects, I'll get a large number of "issues" that I then have to waste time explaining away.

 

Thanks,

Calvin

  • 0
    TI__Mastermind 37985 points

    Calvin,
    this document describes how RTSC and SYS/BIOS include statically created objects:
    http://rtsc.eclipse.org/docs-tip/Integrating_RTSC_Modules#Portable_Inclusion_of_Configuration_Constants

    If that page does not answer your question, please let me know.

  • 0 in reply to Sasha Slijepcevic
    Intellectual 990 points

    Sasha,

    Mostly. I had to do some spelunking but I found the *.h inferred by globals.h in ../Debug/configPkg/package/cfg. It is so indirectly referenced though, I'm not sure how I'm going to handle the static code analyzers.

    I really do appreciate all of your expert help. However, after spending time with it RTSC seems way more complicated than what is needed. I get the speil about having a single environment for ALL TI MCU/DSP parts but TI's solution may not be the best for your users. What TI has created is an environment so convoluted and alien (and is wierdly and incompletely documently - every tid bit is a day long scavenger hunt)  that most embeded developers won't be able to (or don't have time to) use it without serious handholding.  A better targeted and documented system wouldn't require so much of your help or so much of my time to be productive. The only reason I'm pursuing it is to get back all the real-time debug capabilities that I had in CCS 3.3 but lost in CCS4.x.

    Also, please do us all a favor and slap any TI tool developer that says CCS4/Eclipse is easy to learn and use. They obviously take great pleasure giving and receiving pain so oblige them and give them some more.

    Ok, got that off my chest - back to deciphering RTSC.

    Regards,

    -Calvin