You could just run doxygen on the resulting app.c file. There are configuration parameters that let you generate both forward and reverse call graphs from.
Kevin On Mon, Mar 22, 2010 at 4:12 PM, Eric Decker <[email protected]> wrote: > I know about nesdoc (built via make <platform> docs). And I need something > a bit different. > I'm interested in a full call graph. Not the pieces that nesdoc gives you. > Also interested in a reverse call graph (what calls). > For example I trying to analyze the resource usage of various devices. Who > is using what device. > So I'd like to answer the question who wires into HplMsp430UsciB1C (msp430X > h/w). But I'm > not that interested in the first level wiring but rather where does the call > graph start and who is > wired in along the way. > It helps answer the question of who is wired into this device when things > are screwy for a complex > system. > Anyone done something like this? > -- > Eric B. Decker > Senior (over 50 :-) Researcher > > > > _______________________________________________ > Tinyos-help mailing list > [email protected] > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help > -- ~Kevin _______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
