Use your forum account to login.

LOGIN

TOP Contributors

  1. MikroElektronika Team (436 codes)
  2. Shawon Shahryiar (246 codes)
  3. Alcides Ramos (96 codes)
  4. Dany (66 codes)
  5. O B (61 codes)
  6. MikroBUS.NET Team (35 codes)
  7. NART SCHINACKOW (34 codes)
  8. Alberto Trasimeni (25 codes)
  9. Roman Toropov (25 codes)
  10. Arezki YOUYOU (24 codes)

Most Downloaded

  1. Timer Calculator (77371 times)
  2. Network Ethernet Library (37711 times)
  3. FAT32 Library (36414 times)
  4. USB Device Library (28353 times)
  5. Network WiFi Library (27120 times)
  6. FT800 Library (19780 times)
  7. PID Library (18898 times)
  8. GSM click - Example (18497 times)
  9. microSD click - Example (15828 times)
  10. GPS click - Example (12694 times)
Libstock prefers package manager

Package Manager

We strongly encourage users to use Package manager for sharing their code on Libstock website, because it boosts your efficiency and leaves the end user with no room for error. [more info]

< Back
Project

Tool: Function Calls Display

Rating:

Author: Dany

Last Updated: 2017-10-26

Category: Other Codes

Downloaded: 692 times

Not followed.

Shows the function calls of the project in a number of views (a.o. graphical tree).

For mP, mC and mB for PIC and dsPIC.

No Abuse Reported

Do you want to subscribe in order to receive notifications regarding "Tool: Function Calls Display" changes.

Do you want to unsubscribe in order to stop receiving notifications regarding "Tool: Function Calls Display" changes.

Do you want to report abuse regarding "Tool: Function Calls Display".

  • Information
  • Comments (4)
DOWNLOAD LINK RELATED COMPILER CONTAINS
Other Compiler
  • lib
  • src
  • exa
  • hlp
  • hex
  • sch
  • pcb
  • doc

Project Blog

For mP, mC and mB for PIC and dsPIC.

* Shows the function calls (1 level deep) of the project in a number of views:

- which functions use which other functions (-1- left main window)

- which functions are used by other functions (-2- right main window)

* Additionally the following info is given:

- the (deepest) stack call level, the needed stack depth and the call frequency of a function (3)

- the deeptest call stack (the names of its subsequent called functions) of a function (4)

- the full call stack (the names of its subsequent called functions) of a function (5)

(1), (2) and (3): see ScreenShot

(4) and (5): see ScreenShot

- Selecting a function in one view shows all its occurences in the other view.

- Double clicking a function goes "down" in the call stack in the "uses" view, and "up" in the call stack in the "is used by" view.

- Right clicking a function shows its call stacks in a separate screen.


* The call tree of the last selected function in one of both main windows can be shown graphically (and saved to a file).

* The call depth shown can be limited in the graphical view. One can click one of the procedures on the screen to see its caller tree, and go to previous procedures selected via the history. Single functions (and their callees) or all functions from specific libraries can be ingored in the graphicall call tree.


* The inverse graphical tree (which routines do call the selected one) is also provided.


* The Project's Module tree (which modules/units use other modules/units) and a Module's Routine tree (the call graph of all routines inside a module/unit) are also present.


Keep in mind that all info that you see is that of the current project. This means e.g. that unused procedures are not shown!

So: always compile the project before tool usage, the tool needs the listfile and the callertable.

The tool is to be started up from within the IDE, it can not be used stand alone.

Tool settings in the IDE (Options-Tools).

Screenshot (1), (2), and (3)

Screenshot (1), (2), and (3)

Screenshot (1), (2), and (3)

View full image
Screenshot (4) and (5)

Screenshot (4) and (5)

Screenshot (4) and (5)

View full image
Call tree

Call tree

Call tree

View full image
Inverse graphical tree

Inverse graphical tree

Inverse graph tree

View full image
Project's Module tree

Project's Module tree

Project's Module tree

View full image
Module's routine tree

Module's routine tree

Module's routine tree

View full image
Tool settings in the IDE (Options-Tools).

Tool settings in the IDE (Options-Tools).

Tool settings in the IDE (Options-Tools).

View full image

------------------------------------------------------------------------------------------------------------------------------------------
Version 10.2: Problems with finding PIC32 interrupt routines solved.

------------------------------------------------------------------------------------------------------------------------------------------
Version 10.4: Problem for P18 solved.

ALSO FROM THIS AUTHOR

Tool: PIC Oscillator configuration and initialisation code generator

This tool helps, starting from the PIC18 or PIC24 oscillator block diagram, to define the oscillator related configuration settings and initialisation code. Only a limited number of PIC's is supported so far.

[Learn More]

LCD

* 2 (alternative) libs to drive LCD's (4 bits connections): - One lib specific for 2x16, - one more generic (upto 4 rows, 16-20 chars per row). * A library to drive LCD via I2c (PCF2116 based, 1 to 4 rows, 12 or 24 chars per row * A library to drive standard LCD's via I2c * A library to drive standard LCD's via SPI.

[Learn More]

TempSensors

The basic functions for the DS18(S/B)20 (onewire digital temperature sensor), including string output, ready to display. A routine to convert a more than 9 bits temperature read from a DS18B20 to a string (to e.g. display on an LCD) is also present. Including Parasite Power and Configuration routines. The LM35 basic functions, code efficient.

[Learn More]