• Locked Locked
  • Replies 2 replies
  • Subscribers 100 subscribers
  • Views 407 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.

TIs documentation "strategy"

Markus Grunwald
Expert 2060 points

Hello,

 

because of my last odyssey on trying to get ACPY3 working, I would like to know if TI is aware if its documentation strategy: spread as much information about a topic as possible to as many locations as possible. You can find documentation here:

  • Several PDFs scattered on my hard drive. Named intuitively "spruxyz", "spra0815" and so on. Rarely, one of the PDFs describes a topic completely so that I can start working (or understanding.

  • The "Texas Instruments Embedded Processors Wiki"

  • The sources

  • doxygen documentation derived from the sources

  • CCS4 online help (never found anything usefull there)

  • This forum

Now I come from the linux world (been there since kernel 2.0.22) and am not tampered regarding documentation. But starting to develop software for the OMAP or C6747 DSPs seems to be very, very complicated for me.

Since there seem to be many Developers here who don't have a problem with that, I would like to know: What am I doing wrong?

 

Thanks, I hope it was not too much of a rant ;)

Markus

  • TI__Guru*** 125430 points

    Markus,

    Hardware documentation can all be found in the product folder.  For example, for 6747 you can find it here:

    http://focus.ti.com/docs/prod/folders/print/tms320c6747.html

    Software documentation is shipped inside the actual software installation in a docs directory.  Depending on the software team this might be pdf, doxygen, or a combination.

    The wiki provides a place where anybody can contribute.  For example, I'm an FAE and so I wouldn't generally write any of the documentation, but I have written many wiki pages.  In my opinion the "correct" use of the wiki is to complement the existing documentation.  Ideally it should provide extra help, though we recognize that conflicting/duplicate/overlapping info can sometimes be confusing.

    Best regards,
    Brad

  • Genius 4615 points

    Welcome to the world of TI software development.

     

    Lee Holeva