• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 30 subscribers
  • Views 434 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TM4C1294NCPDT: Stack usage for Tivaware ROM functions

Jiri Findejs
Prodigy 20 points
Part Number: TM4C1294NCPDT

Hello,

I'm trying to do stack usage analysis, but the tool needs to know stack usage for ROM_* (rom.h) functions. Is that information available somewhere?

Thank you.

  • 0
    TI__Guru*** 134845 points
    Hello Jiri,

    I am not aware of that information existing in a document. If you need access to the function calls and what they do for your tool, then you can definitely accomplish that goal. The ROM_ API's have TivaWare equivalents, so you could investigate the Stack usage of each of those functions.

    First off, I would recommend using the MAP_ functions instead as that way you will use the latest TivaWare functions if any changes were made from the ROM API.

    Then once you know which functions are actually being mapped to ROM_ calls, replace those with the TivaWare calls to do your stack analysis.

    After you have the stack analysis done, then you can use MAP_ again to return to using the ROM_ functions of the device.
  • 0 in reply to Ralph Jacobi
    Prodigy 20 points

    Hello Ralph,

    thank you for the suggestion. TivaWare analysis will probably gives me a bit different stack usage the actual ROM, because it depends on the compiler and the compiler settings, but such differences are not important for my goal at all.

    Thank you.

    Jiri