SLAU132V User guide | 德州仪器 TI.com.cn

SLAU132V October 2004 – February 2020

1
1. 2
2. 3
3. 4
4. 5
5. 6
7
1. 8
2. 9
3. 10
4. 11
5. 12
13
1. 14
2. 15
3. 16
  1. 17
  2. 18
  3. 19
  4. 20
  5. 21
  6. 22
  7. 23
  8. 24
  9. 25
  10. 26
  11. 27
  12. 28
4. 29
  1. 30
  2. 31
5. 32
  1. 33
  2. 34
    1. 35
  3. 36
  4. 37
  5. 38
  6. 39
  7. 40
  8. 41
  9. 42
  10. 43
6. 44
7. 45
  1. 46
  2. 47
8. 48
9. 49
10. 50
11. 51
  1. 52
  2. 53
12. 54
  1. 55
13. 56
14. 57
58
1. 59
2. 60
3. 61
  1. 62
4. 63
  1. 64
  2. 65
5. 66
6. 67
  1. 68
  2. 69
7. 70
  1. 71
    1. 72
    2. 73
    3. 74
    4. 75
    5. 76
    6. 77
    7. 78
    8. 79
  2. 80
  3. 81
  4. 82
8. 83
  1. 84
    1. 85
    2. 86
  2. 87
    1. 88
    2. 89
    3. 90
9. 91
10. 92
11. 93
  1. 94
  2. 95
12. 96
13. 97
  1. 98
  2. 99
  3. 100
  4. 101
  5. 102
  6. 103
  7. 104
  8. 105
  9. 106
  10. 107
  11. 108
  12. 109
  13. 110
111
1. 112
  1. 113
  2. 114
  3. 115
2. 116
  1. 117
  2. 118
3. 119
  1. 120
    1. 121
      1. 122
    2. 123
    3. 124
  2. 125
  3. 126
  4. 127
  5. 128
  6. 129
  7. 130
  8. 131
  9. 132
    1. 133
134
1. 135
  1. 136
2. 137
3. 138
4. 139
5. 140
6. 141
  1. 142
7. 143
8. 144
  1. 145
  2. 146
  3. 147
    1. 148
    2. 149
  4. 150
    1. 151
9. 152
10. 153
11. 154
12. 155
  1. 156
  2. 157
  3. 158
  4. 159
  5. 160
  6. 161
    1. 162
    2. 163
    3. 164
    4. 165
  7. 166
  8. 167
    1. 168
    2. 169
    3. 170
  9. 171
  10. 172
  11. 173
  12. 174
  13. 175
  14. 176
  15. 177
  16. 178
  17. 179
  18. 180
  19. 181
  20. 182
  21. 183
  22. 184
  23. 185
  24. 186
  25. 187
  26. 188
  27. 189
  28. 190
  29. 191
  30. 192
    1. 193
    2. 194
    3. 195
  31. 196
  32. 197
13. 198
14. 199
15. 200
16. 201
  1. 202
  2. 203
  3. 204
17. 205
  1. 206
  2. 207
  3. 208
  4. 209
  5. 210
18. 211
212
1. 213
  1. 214
  2. 215
  3. 216
  4. 217
  5. 218
  6. 219
2. 220
  1. 221
    1. 222
    2. 223
    3. 224
    4. 225
  2. 226
3. 227
4. 228
  1. 229
  2. 230
  3. 231
5. 232
6. 233
  1. 234
  2. 235
    1. 236
    2. 237
  3. 238
    1. 239
      1. 240
      2. 241
    2. 242
      1. 243
      2. 244
  4. 245
  5. 246
7. 247
  1. 248
  2. 249
  3. 250
  4. 251
  5. 252
8. 253
  1. 254
  2. 255
  3. 256
  4. 257
    1. 258
      1. 259
    2. 260
      1. 261
9. 262
  1. 263
  2. 264
  3. 265
    1. 266
    2. 267
    3. 268
    4. 269
      1. 270
      2. 271
      3. 272
      4. 273
    5. 274
    6. 275
  4. 276
    1. 277
    2. 278
10. 279
280
1. 281
  1. 282
  2. 283
  3. 284
  4. 285
  5. 286
  6. 287
  7. 288
  8. 289
2. 290
  1. 291
    1. 292
  2. 293
  3. 294
  4. 295
    1. 296
  5. 297
    1. 298
3. 299
4. 300
  1. 301
  2. 302
    1. 303
    2. 304
      1. 305
      2. 306
      3. 307
      4. 308
  3. 309
    1. 310
    2. 311
312
1. 313
2. 314
  1. 315
  2. 316
  3. 317
318
1. 319
320
1. 321

6.9.2 Run-Time Stack

The run-time stack is allocated in a single continuous block of memory and grows down from high addresses to lower addresses. The SP points to the top of the stack.

The code does not check to see if the run-time stack overflows. Stack overflow occurs when the stack grows beyond the limits of the memory space that was allocated for it. Be sure to allocate adequate memory for the stack.

The stack size can be changed at link time by using the --stack_size link option on the linker command line and specifying the stack size as a constant directly after the option.

The C/C++ boot routine shipped with the compiler sets up the user/thread mode run-time stack. If your program uses a run-time stack when it is in other operating modes, you must also allocate space and set up the run-time stack corresponding to those modes.