Đang chuẩn bị nút TẢI XUỐNG, xin hãy chờ
Tải xuống
ARM Architecture Reference Manual- P11: The ARM instruction set architecture has evolved significantly since it was first developed, and will continue to be developed in the future. In order to be precise about which instructions exist in any particular ARM implementation, five major versions of the instruction set have been defined to date. | The Thumb Instruction Set 6.6.3 List of Load and Store Multiple instructions The following instructions follow the formats shown above. LDMIA Load Multiple. See LDMIA on page A7-40. POP Pop Multiple. See POP on page A7-75. PUSH Push Multiple. See PUSH on page A7-78. STMIA Store Multiple. See STMIA on page A7-84. ARM DDI 0100E Copyright 1996-2000 ARM Limited. All rights reserved. A6-19 The Thumb Instruction Set 6.7 Exception-generating instructions The Thumb instruction set provides two types of instruction whose main purpose is to cause a processor exception to occur The Software Interrupt SWI instruction is used to cause a SWI exception to occur see Software Interrupt exception on page A2-16 . This is the main mechanism in the Thumb instruction set by which User mode code can make calls to privileged Operating System code. The Breakpoint BKPT instruction is used for software breakpoints in T variants of ARM architecture versions 5 and above. Its default behavior is to cause a Prefetch Abort exception to occur see Prefetch Abort instruction fetch memory abort on page A2-16 . A debug monitor program that has previously been installed on the Prefetch Abort vector can handle this exception. If debug hardware is present in the system it is allowed to override this default behavior. Details of whether and how this happens are IMPLEMENTATION DEFINED. 6.7.1 Instruction encodings SWI immed 8 15 14 13 12 11 10 9 8 7 0 1 1 0 1 1 1 1 1 immed 8 BKPT immed 8 15 14 13 12 11 10 9 8 7 0 1 0 1 1 1 1 1 0 immed 8 In both SWI and BKPT the immed_8 field of the instruction is ignored by the ARM processor. The SWI or Prefetch Abort handler can optionally be written to load the instruction that caused the exception and extract these fields. This allows them to be used to communicate extra information about the Operating System call or breakpoint to the handler. 6.7.2 List of exception-generating instructions BKPT Breakpoint. See BKPT on page A7-24. SWI Software Interrupt. See SWI on page
