ARM VERSION 1.2 Guide de l'utilisateur Page 28
- Page / 133
- Table des matières
- DEPANNAGE
- MARQUE LIVRES
Noté. / 5. Basé sur avis des utilisateurs
To compile and link these modules:
1. Type tcc -c -apcs /interwork -o thumbmain.o thumbmain.c at the system prompt to compile the
Thumb code for interworking.
2. Type armcc -c -apcs /interwork -o armsub.o armsub.c to compile the ARM code for interworking.
3. Type armlink -o hello armsub.o thumbmain.o to link the object files.
Alternatively, type armlink -info veneers armsub.o thumbmain.o to view the size of the interworking
veneers (Example 3-4).
Example 3-4
Adding veneers to the image
Adding AT veneer (12 bytes) for call to '_printf' from armsub.o(.text).
Adding TA veneer (12 bytes) for call to 'arm_function' from thumbmain.o(.text).
Adding AT veneer (12 bytes) for call to '__rt_lib_init' from kernel.o(x$codeseg).
Adding AT veneer (12 bytes) for call to '__rt_lib_shutdown' from kernel.o(x$codeseg).
Adding AT veneer (12 bytes) for call to '_sys_exit' from kernel.o(x$codeseg).
Adding AT veneer (12 bytes) for call to '__raise' from rt_raise.o(x$codeseg).
Adding AT veneer (12 bytes) for call to '_no_fp_display' from printf2.o(x$codeseg).
7 Veneer(s) (total 84 bytes) added to the image.
3.3.2 Basic rules for interworking
The following rules apply to interworking within an application:
• You must use the -apcs /interwork command-line option to compile any C or C++ modules that contain
functions that might return to the other instruction set.
• You must use the -apcs /interwork command-line option to compile any C or C++ modules that contain
indirect or virtual function calls that might be to functions in the other instruction set.
• Never make indirect calls, such as calls using function pointers, to non-interworking code from code in the other
state.
• If any input object contains Thumb code, the linker selects the Thumb runtime libraries. These are built for
interworking.
If you specify one of your own libraries explicitly on the linker command line you must ensure that it is an
appropriate interworking library.
3.3.3 Using two copies of the same function
You can have two functions with the same name, one compiled for ARM and the other for Thumb. However, we do
not recommend this practice. In almost all cases there is no significant performance increase over having a single
version of the function.
Note
Both versions of the function must be compiled with the /interwork option as it is not guaranteed that the Thumb
version will only be called from Thumb state and the ARM version will only be called from ARM state.
The linker allows duplicate definitions provided that one definition defines a Thumb routine and the other defines an
ARM routine.
Interworking ARM and Thumb
Copyright ?1999 2001 ARM Limited 3-7
- ARM® Developer Suite 1
- Version 1.2 1
- Developer Guide 1
- About this book 2
- ARM publications 3
- Other publications 3
- Feedback 4
- 1 Introduction 5
- Introduction 6
- 1.3 Developing for the ARM 7
- 1.3.5 Writing Code for ROM 8
- 2.1.1 ATPCS variants 9
- 2.1.2 ARM C libraries 9
- • Read-only memory 10
- 2.2 Register roles and names 11
- 2.3 The stack 12
- 2.4 Parameter passing 14
- 2.5 Stack limit checking 15
- 2.6.2 Writing code for ROPI 17
- 2.7.1 Reentrant routines 18
- 2.9 Floating-point options 20
- 3 Interworking ARM and Thumb 22
- 3.1 About interworking 22
- Interworking ARM and Thumb 23
- 3.2.3 Example ARM header 24
- Building the example 25
- 3.2.4 ARM architecture v5T 25
- 3.2.5 Labels in Thumb code 26
- C interworking example 27
- 5. Type go to run the code 31
- String copying example 33
- Operand expressions 33
- Physical registers 33
- 4.1.4 Usage 35
- 4.1.5 Examples 36
- Dot product 37
- Long multiplies 37
- • LDRB/STRB for char 39
- • LDR/STR for int 39
- C++ calling conventions 42
- C++ data types 42
- Symbol name mangling 43
- 4.4.3 Examples 43
- Calling C from C++ 44
- Calling C++ from C 45
- Handling Processor Exceptions 48
- • the address of the handler 53
- 5.4 SWI handlers 55
- Nested SWIs in C and C++ 57
- 5.5 Interrupt handlers 61
- • Single-channel DMA transfer 63
- • Dual-channel DMA transfer 63
- • Interrupt prioritization 63
- • Context switch 63
- Interrupt prioritization 64
- Context switch 65
- 5.6 Reset handlers 67
- 5.8 Prefetch Abort handler 69
- 5.9 Data Abort handler 70
- • A single extended handler 71
- • Several chained handlers 71
- Handling the exception 72
- 5.11.2 The return address 72
- FIQ and IRQ handlers 73
- Prefetch Abort handlers 73
- Data Abort handlers 73
- 5.12 System mode 75
- 6 Writing Code for ROM 76
- 6.2.1 ROM at 0x0 77
- 6.2.2 RAM at 0x0 77
- Implementing RAM at 0x0 77
- System decoder 78
- 6.3 Initializing the system 79
- 6.4.1 Memory map 81
- 6.4.2 Sample code 82
- • five execution regions: 83
- 6.5.3 Sample code 84
- 6.5.4 Building the example 88
- Using the CodeWarrior IDE 89
- Using the command line 89
- 6.6.1 Memory map 90
- 6.6.3 Initialization code 91
- 6.6.4 Building the example 91
- 6.7.1 Memory map 93
- 6.7.2 Building the example 93
- 6.7.3 Sample code 93
- 6.8.1 Memory map 97
- 6.8.2 Building the example 97
- 6.8.4 Sample code 98
- 6.9.2 Using unions 100
- Using an array of shorts 100
- Using a struct 100
- 6.9.4 Using scatter loading 101
- 6.9.5 Code efficiency 102
- 6.10 Troubleshooting 103
- Writing Code for ROM 104
- Code (or read-only) segments 105
- Data (or read-write) segments 105
- Debug data 105
- 7.1.1 About caches 106
- ARMulator Pagetable model 106
- 7.1.4 Cache performance 107
- 7.3 Memory protection units 109
- 7.4 Configuring a PU 110
- 7.5 Memory management units 113
- 7.6 Configuring an MMU 115
- 7.7 Tightly coupled memory 117
- 7.7.3 ARM966E-S warm reset 118
- Debug Communications Channel 120
- 8.4 Target transfer of data 123
- • Using armsd 125
- • Using AXD 125
- Issuing commands 126
- Using AXD 126
- 8.7 Access from Thumb state 129
- 8.8 Semihosting 130
- Glossary 131
© 2020, manymanuals.fr. Tous droits réservés | 1.438 s |
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Commentaires sur ces manuels