Nintendo 1504166 Programming Manual - Page 127

Example, Cautions for Communication Function]

Page 127 highlights

AGB Programming Manual Communication Functions When changing communication modes, change only the communication mode flag first. Do not start a communication at the same time the mode is changed. This may cause a malfunction. Even if you think you have set different bits of same register separately using the C language, sometimes they are optimized by a compiler and changed to codes that are set simultaneously. When this happens, attach the type qualifier, volatile, in order to prevent optimization. Example: *(volatile unsigned short int*)REG_AGB =0x8000; *(volatile unsigned short int*)REG_AGB = 0x0040; /*REG_AGB:register name*/ If communication is not finished (SIO interrupt does not occur) after a certain period of time, or if there is a communication error after retries, enter another communication mode once and then re-enter the communication mode once again. By doing this, the communication circuit will be reset. [Cautions for Communication Function] For communication, take into consideration a case in which unexpected data is received. Be careful so that a lock up, destruction of saved data, or malfunction do not occur. (Example: To permit cancellation of communication by pressing a key.) The following situations are examples of communication problems. -When a peripheral device that is not supported is connected -When different software is connected to other device -When the communication mode is different from the other device -When the AGB Game Link cable is connected incorrectly ©1999 - 2001 Nintendo of America Inc. 127 D.C.N. AGB-06-0001-002B4

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171

AGB Programming Manual
Communication Functions
©1999 - 2001 Nintendo of America Inc.
127
D.C.N. AGB-06-0001-002B4
When changing communication modes, change only the communication mode flag first.
Do not
start a communication at the same time the mode is changed.
This may cause a malfunction.
Even if you think you have set different bits of same register separately using the C language,
sometimes they are optimized by a compiler and changed to codes that are set simultaneously.
When this happens, attach the type qualifier, volatile, in order to prevent optimization.
Example:
*(volatile unsigned short int*)REG_AGB =0x8000;
/*REG_AGB:register name*/
*(volatile unsigned short int*)REG_AGB = 0x0040;
If communication is not finished (SIO interrupt does not occur) after a certain period of time, or if
there is a communication error after retries, enter another communication mode once and then
re-enter the communication mode once again.
By doing this, the communication circuit will be
reset.
[Cautions for Communication Function]
For communication, take into consideration a case in which unexpected data is received.
Be careful so that a lock up, destruction of saved data, or malfunction do not occur.
(Example: To permit cancellation of communication by pressing a key.)
The following situations are examples of communication problems.
-When a peripheral device that is not supported is connected
-When different software is connected to other device
-When the communication mode is different from the other device
-When the AGB Game Link cable is connected incorrectly