Main Page

From ARMwiki
(Difference between revisions)
Jump to: navigation, search
(Added encryption section.)
(Edited top notice.)
Line 4: Line 4:
=We're not really ready yet...=
==We're almost ready!==
I had hoped to have this up and running in the autumn, but with my work hours and always feeling so damn tired, plus all the other stuff in my life, it is taking longer than I hoped.<br>
The base instruction set is now described, and we're on our way!<br>
''ARMwiki'' is live, it is active, it just has a lot that needs to be done. I hope you'll consider making a contribution to the information available.<br>
Okay, a little slower than I'd have liked, but getting there! &#9786;
When the base instruction set and some tutorials are ready, my assembler resources will be updated to point to here.
<table border="0" cellpadding="5" cellspacing="1" width="100%">
<table border="0" cellpadding="5" cellspacing="1" width="100%">

Revision as of 19:06, 9 January 2012

ARMwiki - ARM processor wiki
articles and information relating to the ARM processor

We're almost ready!

The base instruction set is now described, and we're on our way!
Okay, a little slower than I'd have liked, but getting there! ☺


IntroductionAn introduction to the ARM, and ARMwiki.
The ARM familyARM processor types/families.
Instruction setThe ARM instruction set.
Using RISC OSARM programming under RISC OS.
Using Linux & WindowsARM programming under Linux and Windows.
TutorialsStep by step tutorials.
Example codeExample code (currently predominantly RISC OS).
Related sitesOther ARM-related sites and resources.

Content wanted!

ARMwiki is always looking for user contributions. If you have anything to add, please do. To help spark your creative juices, please browse the list of pages that have not yet been written that are cited by existing pages. When writing pages, please follow the style guide.

Please note: You must be a registered user with email address confirmed in order to create or edit content.


With reference to the recent European Directive on the use of cookies, please be aware that ARMwiki may use cookies to uniquely identify you. This is necessary as registered users log in, have preferences, and the ability to edit pages. Cookies will be required to manage these activities.

There is no mechanism for you, the user, to explicitly "consent" to having cookies stored. However, if you have come here as an anonymous user, no cookies will have been placed on your machine. It is only when you create an account or login that the cookie is required. Therefore, it will be assumed that logging into ARMwiki is giving consent to having ARMwiki manipulate and store its own cookies on your computer.

Four cookies are stored, all beginning with irreleva_mysql followed by a bunch of numbers. This is a reference to the underlying database upon which ARMwiki is based. The cookies are Token, UserID, UserName, and session. Their function should be clear from the names. Check what cookies are being stored on your computer.

Feel free to wipe off the cookies at any time, or to configure your browser to retain cookies from this site on a session-by-session basis. It will not hurt anything, all you'll need to do is log in again.

Alternatively, you may block cookies from ARMwiki (exactly how depends upon your browser), but please be aware that your ability to interact with this site may be somewhat diminished without the use of cookies.

ARMwiki does not contain embedded advertising, therefore there are no issues with third-party cookies.

You may read the full (and rather boringly verbose) directive at:

Request for Content Removal


If you wish to view and use ARMwiki securely, you can connect via - but please note that your browser will warn you of a security problem, and that you will need to set an exception (refer to your browser's documentation for instructions). This is because HeyRick uses a generic security certificate in order to provide encryption. It does not guarantee that I am who I say I am, or anything like that. As I am not selling anything or requesting loads of personal details, this is seen as a workable compromise in order to allow safe use of ARMwiki in places where eavedropping could be a potential issue (schools, public WiFi hotspots, etc).

Personal tools