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.

Compiler/TM4C123GH6PGE: How are the internal ROM_ functions linked in?

Part Number: TM4C123GH6PGE

Tool/software: TI C/C++ Compiler

This should be a simple question, but, looking through the examples in the Tiva release package (and reading the library information) I am missing how the ROM_xxx functions are linked in. That is, I've build the driverlib so I can step in the functions and understand at a lower level what they do. I know know where liba is and plan to compile that for the same reasons. In the interim, I've been reading "Digital Signal Processing Using the ARM Cortex M4" building CCS projects, from scratch, example by example and found that I could not figure out how to link the ROM_xxx calls in the BOOST AUDIO file tm4c123_aic3104_init.c renaming ROM_xxx functions to remove the leading "ROM_". Stupid, I know, but can someone please point me in the right direction?

Thanks,

Dave

  • OK, it was a dumb question. i just re-read the ROM User's Guide Introduction and realize I had missed the "#define TARGET_IS_TM4C123_R<devicerevision>" MACRO not to mention the need to include driverlib/rom.h. So, before anyone wastes their time answering, I thought I'd nip it in the bud now. Sorry for the inconvenience.

    Dave
  • Thank you for posting the question and answer. This may help the next person when they search e2e with the same question.
  • Rather than "inconvenience" - both your "Clear & Detailed Subject Line" and then methodical discovery & (shared) presentation of your findings - deserve thanks & are appreciated...

    Your post surely deserves a, "Series of "LIKES" - which would surely arrive - had they not been (SO mistakenly) "banned!"

  • Thanks for the kind words. I try not to shoot from the hip and post, and try to put the information in such that there is a minimal amount of re-posting. In a nut shell, I am getting better about understanding the Tiva/CCS tool set and am digging into the dark corners to become somewhat knowledgeable about the Tiva ecosystem. It's pretty good!