• Locked Locked
  • Replies 3 replies
  • Subscribers 119 subscribers
  • Views 2902 views
  • Users 0 members are here
Options
Related
How was your experience today?
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

ARM Instructions Viewer

Jolie Eid
Note: This was originally posted on 26th October 2010 at http://forums.arm.com

Hello

I was wondering what software program can help me translate a C/C++ code program to the corresponding set of ARM instructions. I DO care about browsing the ARM instructions.
Does RVDS4.1 serve this purpose, or it doesn't enable viewing the instructions? and any idea about the unsupported features of RVDS 4.1 evaluation product?

Thanks in advance
Jolie
  • Note: This was originally posted on 27th October 2010 at http://forums.arm.com

    Thank you!!
  • Note: This was originally posted on 29th October 2010 at http://forums.arm.com

    Hello, I didn't try this thing because it seems you are talking about some command window. However i'm using now RVDS4.1 along with the supported workbench.

    Do you have any idea if the set of instructions viewed in the "Disassembly" tab of my_code.o is subset of ARM ISA instructions, or is it of the ISA  my computer implements?
    Also, what does the my_code.s includes? No such file was shown in the "Project Explorer" of the RVDS workbench.

    I am still new in this domain, so sorry if my questions are sometimes ambiguous or severely simple.
    Thanks in advance!
  • Arm Employee Badge
    Note: This was originally posted on 27th October 2010 at http://forums.arm.com

    When you compile C/C++ files you can tell the compiler to generate an assembler listing as well as an object.  Just add "--asm" to the command.  For example:

      armcc --debug --cpu=ARM926EJ-S -O2 -c --asm my_code.c

    Assuming no compile errors, you see my_code.o and my_code.s generated.  The my_code.s file has the assembler listing.

    You can do pretty much the same thing post compile, or for a complete image, using the fromelf tool.  Just run:

      fromelf -c my_object.o/my_image.axf

    The output gets dumped to the console, so you probably want to re-direct it the a file. 

    The main difference between the two approaches is the output format.  The file generated by the compiler (something.s) can be run through the assembler (armasm) to generate an object.  The output of fromelf cannot.