sci.electronics.design Arm Cortex assembley code Does the Arm Cortex support both the "thumb" 16 bit machine codes and also the 32 bit codes? I had been under the impression that Cortex devices only provided the thumb codes but a little time going through "Arm v7-M Architecture Reference Manual" indicates otherwise. Whether or not that reference manual is suitable for Cortex information needs verification also. There may be a more pertinent text available. And another question: the thumb instructions show 8 available registers rather than 16. However, somewhere on the internet a site states that 16 registers are available & which group of 8 varies with the "processor state". Any suggestions on an Arm manual or text that defines "processor state"? The CPS (change processor state) machine code description in the "Arm v7-M Architecture Reference Manual" doesn't mention register groups. Hul
Arm registers
Started by ●April 16, 2021
Reply by ●April 16, 20212021-04-16
On 4/16/21 3:30 PM, Hul Tytus wrote:> sci.electronics.design > Arm Cortex assembley code > > Does the Arm Cortex support both the "thumb" 16 bit machine codes and also > the 32 bit codes? I had been under the impression that Cortex devices only > provided the thumb codes but a little time going through "Arm v7-M > Architecture Reference Manual" indicates otherwise. Whether or not that > reference manual is suitable for Cortex information needs verification also. > There may be a more pertinent text available. > And another question: the thumb instructions show 8 available registers > rather than 16. However, somewhere on the internet a site states that 16 > registers are available & which group of 8 varies with the "processor state". > Any suggestions on an Arm manual or text that defines "processor state"? The > CPS (change processor state) machine code description in the "Arm v7-M > Architecture Reference Manual" doesn't mention register groups. > > Hul >Thumb instructions can be 16 or 32 bit, the 32 bit instruction are different than the non-thumb 32-bit mode, which may be the confusion, and are sometimes called Thumb-2 instructions, as they weren't available in the first version of the Arm Processors that just had the basic 16 bit Thumb instructions. The Arm v7-M processor has 16 32-bit registers, but the top 3 are special purpose (LR, SP, PC), so only R0-R12 are really general purpose. Most of the 16-bit thumb instruction can only access R0-R7, (but some will use the special registers implicitly), to get to the full set of registers you often need to use a 32-bit Thumb instructions.
Reply by ●April 16, 20212021-04-16
Richard - you've verified that the v7-m processors use both the 16 bit and the 32 bit instructions and for that I thank you. I'm guessing now the Cortex processors, not the v7-m types, are what I should be looking at. Do you know the title of Arm's Architectural Reference Manual for the Cortex versions? Hul Richard Damon <Richard@damon-family.org> wrote:> On 4/16/21 3:30 PM, Hul Tytus wrote: > > sci.electronics.design > > Arm Cortex assembley code > > > > Does the Arm Cortex support both the "thumb" 16 bit machine codes and also > > the 32 bit codes? I had been under the impression that Cortex devices only > > provided the thumb codes but a little time going through "Arm v7-M > > Architecture Reference Manual" indicates otherwise. Whether or not that > > reference manual is suitable for Cortex information needs verification also. > > There may be a more pertinent text available. > > And another question: the thumb instructions show 8 available registers > > rather than 16. However, somewhere on the internet a site states that 16 > > registers are available & which group of 8 varies with the "processor state". > > Any suggestions on an Arm manual or text that defines "processor state"? The > > CPS (change processor state) machine code description in the "Arm v7-M > > Architecture Reference Manual" doesn't mention register groups. > > > > Hul > >> Thumb instructions can be 16 or 32 bit, the 32 bit instruction are > different than the non-thumb 32-bit mode, which may be the confusion, > and are sometimes called Thumb-2 instructions, as they weren't available > in the first version of the Arm Processors that just had the basic 16 > bit Thumb instructions.> The Arm v7-M processor has 16 32-bit registers, but the top 3 are > special purpose (LR, SP, PC), so only R0-R12 are really general purpose.> Most of the 16-bit thumb instruction can only access R0-R7, (but some > will use the special registers implicitly), to get to the full set of > registers you often need to use a 32-bit Thumb instructions.
Reply by ●April 16, 20212021-04-16
I was looking in the Arm®v7-M Architecture Reference Manual manual. One thing to note, there are multiple 'Cortex' lines, the Cortex-A, the Cortex-R, and the Cortex-M Which one you are looking at will change the -M in the manual name. Arm v7 updated the Thumb instruction set from the Thumb-1 set which was 16 bits only, to include the Thumb-2 instructions (using unused codes in the Thumb-1 set). On 4/16/21 6:12 PM, Hul Tytus wrote:> Richard - you've verified that the v7-m processors use both the 16 bit > and the 32 bit instructions and for that I thank you. I'm guessing now > the Cortex processors, not the v7-m types, are what I should be looking > at. Do you know the title of Arm's Architectural Reference Manual for the > Cortex versions? > > Hul >
Reply by ●April 17, 20212021-04-17
On 16/04/2021 21:30, Hul Tytus wrote:> sci.electronics.design > Arm Cortex assembley code > > Does the Arm Cortex support both the "thumb" 16 bit machine codes and also > the 32 bit codes? I had been under the impression that Cortex devices only > provided the thumb codes but a little time going through "Arm v7-M > Architecture Reference Manual" indicates otherwise. Whether or not that > reference manual is suitable for Cortex information needs verification also. > There may be a more pertinent text available. > And another question: the thumb instructions show 8 available registers > rather than 16. However, somewhere on the internet a site states that 16 > registers are available & which group of 8 varies with the "processor state". > Any suggestions on an Arm manual or text that defines "processor state"? The > CPS (change processor state) machine code description in the "Arm v7-M > Architecture Reference Manual" doesn't mention register groups. >You seem to be mixing up a range of different things here. (That is not surprising - ARM has /seriously/ confusing terminology here, with similar names for different things, different names for similar things, different numbers for instruction sets, architectures, and implementations.) The answers you got from Richard are all correct - I am just wording things a little differently, to see if that helps your understand. In the beginning, Arm used a 32-bit fixed-size instruction set. It was fast, but not very compact. Most instructions had three registers (so you have "Rx = Ry + Rz"), with 16 registers - that adds up to 12 bits of instruction just for the registers. When they started getting serious in the microcontroller market, this extra space was a cost - it meant code was bigger than for other microcontrollers, and you needed a bigger and more expensive flash. So they invented the "Thumb" mode. Here, instructions are 16-bit only and so much more compact. These were a subset of the ARM instructions - instructions only cover two registers, and for many operations these could only come from 8 registers (so only needed 6 bits of the instruction set). The cpu decoder expanded the Thumb instructions into 32-bit ARM instructions before executing them. Thumb gave more compact code, but slower code, and there were some things you simply could not do in Thumb mode. So the microcontrollers had to support both instruction sets, and you would switch sets in code (interrupts, for example, would be in ARM mode for speed). It was all a bit of a mess. So ARM invented "Thumb-2". This was a set of 32-bit instructions that can be mixed along with the slightly re-named "Thumb-1" 16-bit instructions. Sometimes it is now all called "Thumb2", or just "Thumb" (since for the vast majority of ARM programmers, 16-bit only thumb was ancient history from before they started using the devices). 16-bit and 32-bit instructions are called "narrow" and "wide" forms. These new 32-bit additions to thumb meant you could get a mixed code that was compact, fast, and covered all needs (including full access to all registers). So for the Cortex-M devices, Thumb2 is the only set needed - they don't support "old-style" 32-bit Arm instructions. You no longer need to worry about changing states or modes, you are always in "thumb2" mode. Different Cortex-M processors support different subsets and extensions of this, so it is important that you inform your compiler of exactly which device you are using. Do that, and you don't really need to care about the details for the most part - the compiler does the work. But it can be interesting to know what is going on. There are also Cortex-A devices for applications processors - basically, running Linux (including Android) or, occasionally, Windows. And there are Cortex-R devices for safety-critical systems. But I expect you are talking about Cortex-M devices here.
Reply by ●April 17, 20212021-04-17
Thanks again Richard. I will assume that the "Arm v7-m Architecture Reference Manual" is most current. The only similiarly titled text on Arm's web site was for a 64 bit version. Hul Richard Damon <Richard@damon-family.org> wrote:> I was looking in the Arm??v7-M Architecture Reference Manual manual.> One thing to note, there are multiple 'Cortex' lines, the Cortex-A, the > Cortex-R, and the Cortex-M> Which one you are looking at will change the -M in the manual name.> Arm v7 updated the Thumb instruction set from the Thumb-1 set which was > 16 bits only, to include the Thumb-2 instructions (using unused codes in > the Thumb-1 set).> On 4/16/21 6:12 PM, Hul Tytus wrote: > > Richard - you've verified that the v7-m processors use both the 16 bit > > and the 32 bit instructions and for that I thank you. I'm guessing now > > the Cortex processors, not the v7-m types, are what I should be looking > > at. Do you know the title of Arm's Architectural Reference Manual for the > > Cortex versions? > > > > Hul > >
Reply by ●April 17, 20212021-04-17
David - I'm in the process of putting together an assembler for the Arm 32 bit processors. There is no all-knowing compiler envolved so I need to know what machine codes are valid for a given processor. Any suggestions on where that information can be found? Hul David Brown <david.brown@hesbynett.no> wrote:> On 16/04/2021 21:30, Hul Tytus wrote: > > sci.electronics.design > > Arm Cortex assembley code > > > > Does the Arm Cortex support both the "thumb" 16 bit machine codes and also > > the 32 bit codes? I had been under the impression that Cortex devices only > > provided the thumb codes but a little time going through "Arm v7-M > > Architecture Reference Manual" indicates otherwise. Whether or not that > > reference manual is suitable for Cortex information needs verification also. > > There may be a more pertinent text available. > > And another question: the thumb instructions show 8 available registers > > rather than 16. However, somewhere on the internet a site states that 16 > > registers are available & which group of 8 varies with the "processor state". > > Any suggestions on an Arm manual or text that defines "processor state"? The > > CPS (change processor state) machine code description in the "Arm v7-M > > Architecture Reference Manual" doesn't mention register groups. > >> You seem to be mixing up a range of different things here. (That is not > surprising - ARM has /seriously/ confusing terminology here, with > similar names for different things, different names for similar things, > different numbers for instruction sets, architectures, and implementations.)> The answers you got from Richard are all correct - I am just wording > things a little differently, to see if that helps your understand.> In the beginning, Arm used a 32-bit fixed-size instruction set. It was > fast, but not very compact. Most instructions had three registers (so > you have "Rx = Ry + Rz"), with 16 registers - that adds up to 12 bits of > instruction just for the registers.> When they started getting serious in the microcontroller market, this > extra space was a cost - it meant code was bigger than for other > microcontrollers, and you needed a bigger and more expensive flash. So > they invented the "Thumb" mode. Here, instructions are 16-bit only and > so much more compact. These were a subset of the ARM instructions - > instructions only cover two registers, and for many operations these > could only come from 8 registers (so only needed 6 bits of the > instruction set). The cpu decoder expanded the Thumb instructions into > 32-bit ARM instructions before executing them.> Thumb gave more compact code, but slower code, and there were some > things you simply could not do in Thumb mode. So the microcontrollers > had to support both instruction sets, and you would switch sets in code > (interrupts, for example, would be in ARM mode for speed). It was all a > bit of a mess.> So ARM invented "Thumb-2". This was a set of 32-bit instructions that > can be mixed along with the slightly re-named "Thumb-1" 16-bit > instructions. Sometimes it is now all called "Thumb2", or just "Thumb" > (since for the vast majority of ARM programmers, 16-bit only thumb was > ancient history from before they started using the devices). 16-bit and > 32-bit instructions are called "narrow" and "wide" forms. These new > 32-bit additions to thumb meant you could get a mixed code that was > compact, fast, and covered all needs (including full access to all > registers).> So for the Cortex-M devices, Thumb2 is the only set needed - they don't > support "old-style" 32-bit Arm instructions. You no longer need to > worry about changing states or modes, you are always in "thumb2" mode.> Different Cortex-M processors support different subsets and extensions > of this, so it is important that you inform your compiler of exactly > which device you are using. Do that, and you don't really need to care > about the details for the most part - the compiler does the work. But > it can be interesting to know what is going on.> There are also Cortex-A devices for applications processors - basically, > running Linux (including Android) or, occasionally, Windows. And there > are Cortex-R devices for safety-critical systems. But I expect you are > talking about Cortex-M devices here.
Reply by ●April 17, 20212021-04-17
On 17/04/2021 17:53, Hul Tytus wrote:> David - I'm in the process of putting together an assembler for the Arm > 32 bit processors. There is no all-knowing compiler envolved so I need > to know what machine codes are valid for a given processor. Any suggestions > on where that information can be found? >Why? There are perfectly good Arm assemblers available freely. Is this just for fun, or do you have a good reason behind it? Arm use what they call "Unified Assembly Language" to let people write assembly in a single consistent format that can be used to generated object code in the various instruction formats. That means a single UAL instruction might lead to multiple object code instructions if necessary (for example, loading a register with a constant might need multiple instructions depending on the constant value and the instruction set). Add to that there /lots/ of different subsets of the instructions that are available on different devices. It is a big effort writing an assembler her.> > David Brown <david.brown@hesbynett.no> wrote: >> On 16/04/2021 21:30, Hul Tytus wrote: >>> sci.electronics.design >>> Arm Cortex assembley code >>> >>> Does the Arm Cortex support both the "thumb" 16 bit machine codes and also >>> the 32 bit codes? I had been under the impression that Cortex devices only >>> provided the thumb codes but a little time going through "Arm v7-M >>> Architecture Reference Manual" indicates otherwise. Whether or not that >>> reference manual is suitable for Cortex information needs verification also. >>> There may be a more pertinent text available. >>> And another question: the thumb instructions show 8 available registers >>> rather than 16. However, somewhere on the internet a site states that 16 >>> registers are available & which group of 8 varies with the "processor state". >>> Any suggestions on an Arm manual or text that defines "processor state"? The >>> CPS (change processor state) machine code description in the "Arm v7-M >>> Architecture Reference Manual" doesn't mention register groups. >>> > >> You seem to be mixing up a range of different things here. (That is not >> surprising - ARM has /seriously/ confusing terminology here, with >> similar names for different things, different names for similar things, >> different numbers for instruction sets, architectures, and implementations.) > >> The answers you got from Richard are all correct - I am just wording >> things a little differently, to see if that helps your understand. > >> In the beginning, Arm used a 32-bit fixed-size instruction set. It was >> fast, but not very compact. Most instructions had three registers (so >> you have "Rx = Ry + Rz"), with 16 registers - that adds up to 12 bits of >> instruction just for the registers. > >> When they started getting serious in the microcontroller market, this >> extra space was a cost - it meant code was bigger than for other >> microcontrollers, and you needed a bigger and more expensive flash. So >> they invented the "Thumb" mode. Here, instructions are 16-bit only and >> so much more compact. These were a subset of the ARM instructions - >> instructions only cover two registers, and for many operations these >> could only come from 8 registers (so only needed 6 bits of the >> instruction set). The cpu decoder expanded the Thumb instructions into >> 32-bit ARM instructions before executing them. > >> Thumb gave more compact code, but slower code, and there were some >> things you simply could not do in Thumb mode. So the microcontrollers >> had to support both instruction sets, and you would switch sets in code >> (interrupts, for example, would be in ARM mode for speed). It was all a >> bit of a mess. > >> So ARM invented "Thumb-2". This was a set of 32-bit instructions that >> can be mixed along with the slightly re-named "Thumb-1" 16-bit >> instructions. Sometimes it is now all called "Thumb2", or just "Thumb" >> (since for the vast majority of ARM programmers, 16-bit only thumb was >> ancient history from before they started using the devices). 16-bit and >> 32-bit instructions are called "narrow" and "wide" forms. These new >> 32-bit additions to thumb meant you could get a mixed code that was >> compact, fast, and covered all needs (including full access to all >> registers). > >> So for the Cortex-M devices, Thumb2 is the only set needed - they don't >> support "old-style" 32-bit Arm instructions. You no longer need to >> worry about changing states or modes, you are always in "thumb2" mode. > >> Different Cortex-M processors support different subsets and extensions >> of this, so it is important that you inform your compiler of exactly >> which device you are using. Do that, and you don't really need to care >> about the details for the most part - the compiler does the work. But >> it can be interesting to know what is going on. > > > > >> There are also Cortex-A devices for applications processors - basically, >> running Linux (including Android) or, occasionally, Windows. And there >> are Cortex-R devices for safety-critical systems. But I expect you are >> talking about Cortex-M devices here.
Reply by ●April 17, 20212021-04-17
The ARM Architecture Reference Manuela give the detailed encoding of every instruction. You may need to look at the documentation for a given processor class to see which instructions are legal for that given processor, as that varies by machine class/sub-class. It will be a bit of work to assemble the info, a lot of 'paper' to wade through. On 4/17/21 11:53 AM, Hul Tytus wrote:> David - I'm in the process of putting together an assembler for the Arm > 32 bit processors. There is no all-knowing compiler envolved so I need > to know what machine codes are valid for a given processor. Any suggestions > on where that information can be found? > > Hul >
Reply by ●April 17, 20212021-04-17
On 17.4.21 18.53, Hul Tytus wrote:> David - I'm in the process of putting together an assembler for the Arm > 32 bit processors. There is no all-knowing compiler envolved so I need > to know what machine codes are valid for a given processor. Any suggestions > on where that information can be found?Why on earth? What is wrong with the GNU arm-none-eabi-as? The arm-none-eabi-gcc has switches for different processor architectures. ARM has an instruction reference card for Thumb2, with different processors marked on the card. -- -TV