[Tinyos-devel] TinyOS Application Assembler

[Vlado Handziski]

Such questions are better addressed to tinyos-help. This list is for
discussion of TinyOS development.

Just use the objdump tool from binutils on the resulting binary. For the
msp430:

msp430-objdump -D main.exe

Vlado

On Dec 3, 2007 3:54 PM, Jamie Coates <coatesj at dcs.gla.ac.uk> wrote:

>  Dear all,
>
> First let me apologise if I have made incorrect usage of this mailing
> list, if I haven't then any answers you can give me to my question will be
> greatly appreciated, else, would it be possible to be directed to the
> correct list (if any) :)
>
> Question:
>
> How do I change the compilation process for a TinyOS application so that I
> can view the assembler code?
>
> Background:
>
> I want to be able to view the prologue and epilogue code for an interrupt
> handler. So, after building a Tiny application (say, Blink) I have access to
> a source file containing the program (app.c).
>
> When I run the avr-gcc over the source file with the -S flag, the compiler
> will output the assembler for the application minus the required interrupt
> code. During the process the compiler outputs warnings that it is ignoring
> the __attribute((signal)), which would explain why I cannot see the
> assembler code that I am interested in viewing.
>
> The command I use is "avr-gcc -S app.c"
>
> I hope this is enough information to generate responses and any help that
> you could give me is greatly appreciated,
>
>
> Jamie
>
> _______________________________________________
> Tinyos-devel mailing list
> Tinyos-devel at Millennium.Berkeley.EDU
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://www.millennium.berkeley.edu/pipermail/tinyos-devel/attachments/20071203/f6c79ce6/attachment.htm