This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Profiler for ARM, consumption of RAM by the program in Keil

Is there any a way to determine how much ram/memory is being consumed by the entire project in keil uVision?

It looks like the program is using memory/addresses beyond the certain range allocated so I need to compute certain things.

Also, is there any profiler for ARM embedded systems (C++)?

Parents
  • So this is you too?
    http://www.keil.com/forum/62625/

    Won't the .MAP file describe the memory usage?
    Won't the Target IROM/IRAM settings constrain the LINKER to use just the memory that is physically available?
    Won't the startup.s file define the size of the stack and heap?

    Make sure the stack is large enough to accommodate your auto/local variables.
    Make sure the heap is large enough to accommodate your malloc/new operations.

    Start by observing what is FAILING, once you know the variables/data involved work backward to the point of origin, and to the places where it stops having the expected content vs the corrupt content.

Reply
  • So this is you too?
    http://www.keil.com/forum/62625/

    Won't the .MAP file describe the memory usage?
    Won't the Target IROM/IRAM settings constrain the LINKER to use just the memory that is physically available?
    Won't the startup.s file define the size of the stack and heap?

    Make sure the stack is large enough to accommodate your auto/local variables.
    Make sure the heap is large enough to accommodate your malloc/new operations.

    Start by observing what is FAILING, once you know the variables/data involved work backward to the point of origin, and to the places where it stops having the expected content vs the corrupt content.

Children