Motorola V186 User Manual - Page 67

Loads the Firmware Image into RAM from the MCPU using TCP., CPU MCPU via UDP/IP broadcast.

Get Motorola V186 - Cell Phone - GSM PDF manuals and user guides View all Motorola V186 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 67 highlights

I/O Expansion no yes The Expansion module discovers the main CPU (MCPU) via UDP/IP (broadcast). no Discovery succeeded- obtained self and MCPU IP address? yes 1. Loads the Firmware Image into RAM from the MCPU (using TCP). 2. Turns off all LEDs and runs the loaded Expansion Firmware Image. 3. Auto-recognizes actual I/O modules. Loads user files from the MCPU (using TCP) and saves in FLASH: 1. Configuration, if such exists 2. Application database, if such exists 3. Predefined input and output values and I/O link (if such exist) 4. Encryption files, if such exist yes Failed to load one or more files? no 1. Registers its actual I/O modules information in the MCPU (using TCP). 2. Initializes the Expansion Image (system startup). 3. Negotiates Ethernet addresses (MAC) and starts EMI with the MCPU via TCP. yes Failed to negotiate or start EMI? no Running: 1. Monitor EMI communication with the MCPU. 2. Monitor the MCPU status via TCP. 3. Monitor actual I/O modules change (hot-swap) and update the MCPU. yes Has the MCPU restarted, or disconnected for no more than fail time (60 seconds)? Expansion Loader Expansion Firmware Image 63

  • 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
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
I/O Expansion
The Expansion module discovers the main
CPU (MCPU) via UDP/IP (broadcast).
Discovery succeeded-
obtained self and MCPU IP address?
no
yes
no
yes
1. Loads the Firmware Image into RAM from the MCPU (using TCP).
2. Turns off all LEDs and runs the loaded Expansion Firmware Image.
3. Auto-recognizes actual I/O modules.
Loads user files from the MCPU (using TCP) and saves in FLASH:
1. Configuration, if such exists
2. Application database, if such exists
3. Predefined input and output values and I/O link (if such exist)
4. Encryption files, if such exist
Failed to load one or more files?
Running:
1. Monitor EMI communication with the MCPU.
2. Monitor the MCPU status via TCP.
3. Monitor actual I/O modules change (hot-swap) and update the MCPU.
1. Registers its actual I/O modules information in the MCPU (using TCP).
2. Initializes the Expansion Image (system startup).
3. Negotiates Ethernet addresses (MAC) and starts EMI with the MCPU via TCP.
Failed to negotiate or start EMI?
Has the MCPU restarted, or disconnected for
more than fail time (60 seconds)?
yes
no
yes
no
yes
no
Expansion
Loader
Expansion
Firmware
Image
63