• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 537 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.

CCS/CODECOMPOSER: CC2640R2 Code Composer finding code

Daniel Benkman
Intellectual 525 points

Part Number: CODECOMPOSER
Other Parts Discussed in Thread: CC2640R2F

Tool/software: Code Composer Studio

I'm new to Code Composer.  We are trying to get some code written for a CC2640R2F processor on a custom designed board, NOT a standard TI SDK board.

So we need to be able to look at some of the basic TI source code, but are unable to do so.  For example, we cannot see what the GPIO_init() code is doing.  We cannot see what Board_initGeneral() is doing.  We can call them.  We can compile them.  But we can't see what's inside them, specifically to perhaps modify the source code or copy it and modify it for our own use on our own custom designed board.

Is the source code for basic functions like these available?  Or perhaps they are only available as libraries to compile into user code?  If they are available, how can we see the source code for them?

If the source code for these low level functions are NOT available to the user, does that mean that if we don't know for sure what's in them, and perhaps can't use them, that we have to develop our own low level code for functions like GPIO_init() from scratch?

Thanks for any assistance you can give.

  • 0
    TI__Guru**** 475051 points

    Hello,

    If you highlight the function call in the editor and press F3, CCS should jump to the declaration of the function. For example, Board_initGeneral() is declared in Board.h, which is defined as CC2640R2_LAUNCHXL_initGeneral(). Pressing F3 on that will jump to the the declaration in CC2640R2_LAUNCHXL.c.

    You can also always use the Modules view to browse the debug symbols. Under 'Functions', you can look for the function of interest and double-click on it to open the source file in the editor:

    Thanks

    ki