FASMARM is a free ARM cross-assembler add-on for FASM. It currently supports the full range of instructions for 32-bit and 64-bit ARM processors and coprocessors up to and including v8.

Most of the FASMARM code assembler style is the same as standard ARM style with a few differences to account for FASM specific style. For those of you interested in ARM code you might like to look at the ReadMe.txt and perhaps also the source to see a description of the differences.

A new output format is added "DWARF" which is the ELF specification for inclusion of symbols and line numbers. The files generated in ELF DWARF format can be named *.AXF if you want to use the ARM ADS AXD for full source code symbolic debugging of your code. This is a major feature to have FASM generate embedded debugging information, check it out.

You might like to use FASMARM to augment the ARM ADS and/or third party development tools. FASMARM is faster, can generate binaries directly and the macros are easier to use.

Included in the download file are binaries for most platforms supported by FASM, as well as the source code to generate the binaries. Just something to note in case you are confused, FASMARM generates ARM code binaries but FASMARM still runs on the X86 processor, it does not run on the ARM processor. So strickly speaking FASMARM is a cross assembler.

I have packaged it in a similar fashion the the normal FASM releases on the download pages. You can unzip it to the same directories as FASM. No existing files are altered so I have only included the new files and binaries. Full source code is given.

So far I have tested the WIN32 console and WIN32 IDE variants only. If you get a chance to test the other variants and find a problem report it here. Indeed if you get a chance to test any version and find a problem then report it here.

For those of you that are not sure what ARM is: ARM=Advanced Risc Machines. See http://www.arm.com

I think you should at least replace the FORMATS.INC with the alternative for ARM, too - all the formats (with the exception for flat binary) implemented there are the ones for x86 and it makes not much sense to use them with code for other processors.

I had thought about doing that but decided against it. I wanted to see how far I could get by only changing one file. But there is not reason why it can't be done in the future.

BTW: I thought that PE and COFF were ARM compatible, with a few small minor post processing changes after the formatter has made the PE or COFF I think it would make an ARM versions easily.

Great. Thanks

Wow, great stuff!

Adding elf-arm format will make me very happy

Do you have any examples for e.g. a WindowsCE app? What is the calling convention etc? Do the 'import' macros work as on x86?

Thanks!!

[ Post removed by author. ]

Not yet, that will need the PE format working for ARM and also I don't have such knowledge about the WinCE system at this time. But these are things I want to extend this code to soon. Any information that you may have would be much appreciated if you can mention here. The dwarf format is a combination of the executable and debugging info. Try to use the output as it is, I think it can probably execute, but the alignment may be wrong. Let me know how it goes if you get a chance to try it.

Try to make you own module. Use the code above as a basis if you like.

I have updated the attachment at the top of this thread.

Support for ARMv6 and VFPv2 is now included along with a few enhancements and bug fixes.

revolution, where to get the complete ARMv5TE instruction set reference with opcodes? All the datasheets I tried to download from www.arm.com contain instructions only but no hex opcodes. Help, please.

This is major stumbling block with using ARM processors. The information is not published on the web. You have three options:

1) Buy the ARM ADS which comes complete with the documentation.
2) Buy the book "ARM Architechure Reference Manual" (ARM ARM).
3) Use other sources that have been placed on the web by mistake.

I purchased the ARM ADS and have the v5TE manual in full. So I can now help you out. The document has this name: "DDI0100E_ARM_ARM.pdf" (those are zeros, not letter O's). You can search for this in google and download it (13Meg).

Don't be fooled by ordering the Technical Publications CD. I did this and was disappointed to find it does not have the opcode manuals.

filesearching.com

Oh, great! Download in progress...
I'm thinking about osdev for PDA. But is it possible without ADS? My PDA is only three days old and I don't know alot about it, yet. The main question is how to install another OS.

zhak -

Be careful -- VERY careful -- doing that. You might end up with an expensive door-stop if you mess things up.

That is tricky. Some PDA's have a removable rom module that you can swap for another. Some have the ability to 'flash' the rom with a new OS. Some cannot do it at all without a soldering iron. Depends what you have.

My recomendation would be not to bother, as ronware mentions you can get into a lot of trouble if you get it wrong.

Although I think a door stop is not a probable outcome, more likely a paper weight

Updated file at the top of this thread. Some bug fixes.

Great work thanks.
Maybe i will try some gameboy programming .

revolution, do you know where to get information on low-level coding for PDAs (for example, vga programming)?
And one more thing. I thought about porting fasm to ARM architecture. I think it would be nice.

You will have to ask the manufacturer of the specific PDA for the spec. There are many different brands, models, shapes and sizes of PDA's. That would be great. Don't forget to post it here.

Did you know that most cell phones also use ARM processor cores?

sure.

But the architecture is the same. The OS core is the same, or it is different for every single model? No, I don't think so. It must be as IA-32 architecture - common I/O ports and so on. It MUST be a standard. Or I'm wrong?

(I speak about xScale based PDAs)