Renesas Emulator System M3T-MR100 Bedienungsanleitung Seite 19
- Seite / 306
- Inhaltsverzeichnis
- LESEZEICHEN
Bewertet. / 5. Basierend auf Kundenbewertungen
- 3 -
2. General Information
2.1 Objective of MR100 Development
In line with recent rapid technological advances in microcomputers, the functions of microcomputer-based products have
become complicated. In addition, the microcomputer program size has increased. Further, as product development competi-
tion has been intensified, manufacturers are compelled to develop their microcomputer-based products within a short period
of time.
In other words, engineers engaged in microcomputer software development are now required to develop larger-size pro-
grams within a shorter period of time. To meet such stringent requirements, it is necessary to take the following considera-
tions into account.
1. To enhance software recyclability to decrease the volume of software to be developed.
One way to provide for software recyclability is to divide software into a number of functional modules wherever
possible. This may be accomplished by accumulating a number of general-purpose subroutines and other program
segments and using them for program development. In this method, however, it is difficult to reuse programs that
are dependent on time or timing. In reality, the greater part of application programs are dependent on time or tim-
ing. Therefore, the above recycling method is applicable to only a limited number of programs.
2. To promote team programming so that a number of engineers are engaged in the development
of one software package
There are various problems with team programming. One major problem is that debugging can be initiated only
when all the software program segments created individually by team members are ready for debugging. It is es-
sential that communication be properly maintained among the team members.
3. To enhance software production efficiency so as to increase the volume of possible software
development per engineer.
One way to achieve this target would be to educate engineers to raise their level of skill. Another way would be to
make use of a structured descriptive assembler, C-compiler, or the like with a view toward facilitating program-
ming. It is also possible to enhance debugging efficiency by promoting modular software development.
However, the conventional methods are not adequate for the purpose of solving the problems. Under these circumstances, it
is necessary to introduce a new system named real-time OS
3
To answer the above-mentioned demand, Renesas has developed a real-time operating system, tradenamed MR100, for use
with the R32C/100 series of 32-bit microcomputers .
When the MR100 is introduced, the following advantages are offered.
1. Software recycling is facilitated.
When the real-time OS is introduced, timing signals are furnished via the real-time OS so that programs depend-
ent on timing can be reused. Further, as programs are divided into modules called tasks, structured programming
will be spontaneously provided.
That is, recyclable programs are automatically prepared.
2. Ease of team programming is provided.
When the real-time OS is put to use, programs are divided into functional modules called tasks. Therefore, engi-
neers can be allocated to individual tasks so that all steps from development to debugging can be conducted inde-
pendently for each task.
Further, the introduction of the real-time OS makes it easy to start debugging some already finished tasks even if
the entire program is not completed yet. Since engineers can be allocated to individual tasks, work assignment is
easy.
3. Software independence is enhanced to provide ease of program debugging.
As the use of the real-time OS makes it possible to divide programs into small independent modules called tasks,
3
OS:Operating System
- To our customers 1
- M3T-MR100/4 V.1.00 3
- • Release Note 5
- • Users Manual (PDF file) 5
- Contents 7
- List of Figures 12
- List of Tables 15
- 2. General Information 19
- 2.3 MR100 Features 22
- 3. Introduction to Kernel 23
- Key input 25
- Monitor 26
- Register 28
- Memory map 28
- Register stored 29
- Register not stored 29
- 3.2 Service Call 30
- ID number 36
- Configurator 36
- 3.4 Task 37
- DORMANT 38
- SUSPENDED 38
- Priority 41
- Called the task context 43
- 3.5 System States 44
- 3.6 Regarding Interrupts 47
- • Kernel interrupt handler 47
- 3.7 Stacks 50
- • User Stack 50
- • System Stack 50
- 4. Kernel 51
- 4.1.2 Module Overview 52
- • Terminate Task (ter_tsk) 53
- 0 0 1 2 1 55
- Number of 56
- • Delay task (dly_tsk) 58
- Returned after use 59
- WAIT state 60
- Data Data 63
- Message Message 64
- Message 65
- • Processing speed 68
- • Memory usage efficiency 68
- • Ease of configuration 68
- • Set System Time (set_tim) 71
- Move the end of the queue 74
- Save Registers 75
- Task Selection 75
- 5. Service call reffernce 79
- No. Item Content 100
- - 102 118
- - 105 121
- .blkb 6 123
- : 123
- - 110 126
- - 112 128
- - 115 131
- - 117 133
- - 121 137
- - 124 140
- - 126 142
- - 132 148
- - 134 150
- - 138 154
- - 140 156
- (handler only) 157
- - 142 158
- - 147 163
- - 149 165
- - 152 168
- - 154 170
- - 158 174
- - 161 177
- - 164 180
- - 167 183
- - 173 189
- - 176 192
- - 190 206
- - 193 209
- - 198 214
- - 200 216
- - 202 218
- Overview 221
- - 206 222
- Figure 6.2 Program Example 224
- 6.2.4 System generation 225
- 6.2.5 Writing ROM 226
- 7. Detailed Applications 227
- - 214 230
- 7.2.1 Writing Task 231
- - 217 233
- For examples: 233
- - 219 235
- ; set timer mode 236
- ; set interval count 236
- ; system timer start 236
- - 221 237
- - 222 238
- 7.4 Memory Allocation 240
- • asm_sec.inc 240
- • c_sec.inc 240
- 8. Using Configurator 243
- Symbol 244
- MPU clock 247
- ID No 253
- ID name 253
- Number of data queues 254
- Select message queue 256
- Maximum message priority 256
- ID Name 258
- Section name 258
- Message buffer size 258
- Maximum message size 258
- Start address 261
- Extended information 261
- Vector No 262
- 8.2.1 Configurator Overview 270
- Configuration file name 272
- Error messages 273
- Warning messages 275
- 9.2 Program Source Listing 277
- 9.3 Configuration File 278
- XXX_XXX() 280
- System Stack 281
- Stack Section 281
- Sections used in MR100 282
- User stack size = 282
- Stack growing direction 283
- Σβi( γ) 284
- The necessary system stack 285
- Interrupt 285
- = register to be used 287
- 10.2 Necessary Stack Size 288
- 11. Note 291
- 17. Precautions 292
- 12. Appendix 295
- - 283 299
- - 284 300
- - 285 301
- - 288 304
- REJ10J1523-0100 306
- User’s Manual 306
Verwandte Produkte und Handbücher für Hardware Renesas Emulator System M3T-MR100
Hardware Renesas SH7124 Bedienungsanleitung
(6 Seiten)
(6 Seiten)
Hardware Renesas SH7085 Bedienungsanleitung
(50 Seiten)
(50 Seiten)
Hardware Renesas H8SX/1582 Bedienungsanleitung
(36 Seiten)
(36 Seiten)
Hardware Renesas TFP-80F Bedienungsanleitung
(22 Seiten)
(22 Seiten)
Hardware Renesas M16C/6NM Bedienungsanleitung
(106 Seiten)
(106 Seiten)
Hardware Renesas M3062PT2-EPB Bedienungsanleitung
(102 Seiten)
(102 Seiten)
Dell Wyse 909788-02L manuals
Owner’s manuals and user’s guides for Thin clients Dell Wyse 909788-02L.
We providing 1 pdf manuals Dell Wyse 909788-02L for download free by document types: Datasheet
Kommentare zu diesen Handbüchern