User guide
US
8,549,062
B2
13
SenINITiSENTRY
initialization
procedure.
This software
was
the
?rst
SENTRY
software
that
executes.
It
performs
hardware,
14
-continued
the
12C
tasks
via
signals
or
messages.
TskPCntl
“owns”
the
IPMO
and
PCRO
arrays
and
it
updates
the
status
?elds
in
5
software
(builds
the
Con?guration and
Operational
global
entries
in
these
arrays
as
necessary.
control
blocks),
and
OS
initialization.
This
code
spawns
the
SENTRY
operational
tasks
that
provide
the
system
services.
10
TskEUIiThis
was
the
external
user
interface
task
that
handles
the
push
button
functions
and
the
LED
display
I I
functions
for
the
system.
This
task
communicates
with
the
TslIisERfon?
1115mm“?
IofItIhls
task
Was
Spawn?d
for
‘Each
local
TskI2C
via
signals
or
messages
to
update
the
LED.
TskI2C
actlv?
Senal
POH-
111
the
lnltlal
Product
th?m
Was
on‘?
sends
signals
or
messages
to
this
task
when
the
state
of
the
instance
of
this
task.
This
task
spawns
TskUSR
when
a
logon
15
?xt?mal
push
button
chang?sI
was
detected.
This
task
owns
the
serial
port
operational
array
control
block
in
global
memory.
This
control
block
was
updated.
to
reflect
the
status
of
the
serial
port.
Once
a
TskUSR
was
spawned,
this
task
performs
serial
port
monitoring
functions
and
if
modem
status
signal
indicate
a
lost
connection,
this
task
W111
Slgnal
TSkUSR
(“a
an
OS
mt?rfac?)
Ofthls
?v?nt'
20
TskUSR
———
This
command
line
user
interface
task
was
spawned
by
TskSER
and
TskTELNET
when
a user
connection
was
detected.
This
task
veri?es
the
user
login
and
then
implements
the
command
line
interface.
This
routine
communicates
power
control
commands
via
signals
or
messages
to
TskPCntl.
This
routine
I I I
“owns”
the
active
command
line
user
array.
Because
there
were
TSkTELNET4OPe
1115mm‘?
Ofthls task
Was
Spawn?d
to
h§t6n
25
multiple
instances
of
this
task,
locks
were
used
to
serialize
for
telnet
connections.
When
a
connection
was
detected,
this
acc?ss
to
the
activ?
us?r
array
task
spawns
TskUSR
for
the
connection.
30
TskSYS
———
This
was
the
general
system
task.
Speci?c
functions
TSkFTP4O1IW
instanc?
ofthis
task
was
Spawn?d
to
listI?n
for for
this
task
were
de?ned
as
development
progressed.
FTP
connections.
The
function
of
this
task
was
to
provide
?eld
software
updates
for
the
system.
The
mechanism
used
was
determined
based
on
the
develo
er
kit
ca
abilities.
p p
The
control
blocks
were
globally
addressable
by
all
soft
35
ware
in
the
system.
Such
data
structures
exist
in
RAM
and
were
mirrored
in
EEPROM
memory.
They
were
constructed
during
system
initialization
using
the
non
volatile
versions
in
TskWEBiThis
task
was
to
provide
WEB
access
via the
system
EEPROM
memory‘
If
the
EEIPROM
memory
Was
empty:
the
provided
WEB
server.
The
mechanism
and
number
of
instances
of
control
blOCkS
were
bullt
11S1I1g
defaults
and
the
EEPROM
thls
tgsllif’vas
d?t?mmed
based
on
the
devdoper
k“
40
memory
was
initialized
using
defaults as
well.
All
software
ca
a
i i
ies.
.
p
has
read
access
to
all
of
the
data
structures.
The
data
in
these
control
blocks
was
con?guration
data
and
was
only
changed
as
a
result
of
con?guration
updates.
The
data
was
mostly
45
static
and
was
written
during
initialization
and
when
con?gu
TSkIZCiThm
were
two
Versions
ofthis
task.
the
local
ration
changes
occur
during
an
authorized
user
session.
All
version
that
controls
internal
12C
connections
and
the
global
write
access
to
this
data
consists
of
a
two
step
process
where
version
that
controls external
12C
connections.
For
the
?rst
the
Global
RAM
Copy
Ofthe
data
Was
updated
followed
by
an
implementation
there
were
two
instances
of
this
task,
one
to
control
the
single
12C
internal
connection
and one
to
control
update
of
the
EEPROM
Copy
of
the
delta‘
There
Were
Seven
the
single
120
external
connection
These
tasks
implement
the
50
global
con?guration
control
blocks
as
illustrated
below.
The
Protocol
for
Communicating
Control
r?qu?sts
from
th?
syst?m
to
following
Tables
describe
each
control
block
structure
used
in
the
12C
connected
devices.
Control
requests
were
received
via
the
roto
e
system
signals
or
messages
(depending
on
the
OS
capabilities)
p
typ
'
from
the
power
control
coordinating
task
(TskPCntl)
for
power
control
requests
and
from
the
external
user
interface
task
(TskEUI)
for
LED
control
requests.
This
task
communicates
55
power
control
status
updates
received
from
the
IPM’s
to
SENTRY
Con?guration
Table
(SCT)
— —
This
control
block
TskPCntl
and
external
button
status
updates
to
TskEUI
using
contains
global
con?guration
information.
There
was
a
single
system
signals
or
messages
as
necessary.
instance
ofthis
control
block.
60
TskPCntliThis
was
the
power
control
coordinating
task.
Username/Password
Array
(UNP)
— —
This
was
an
array
of
control
There
was
one
instance
of
this
task.
This
task
receives
power
blocks
with each
entry
representing
a
user
de?ned
to
the
control
request
from
the
user
interface
tasks
(TskUSR
and
system.
System
locks
were
used
to
serialize
access
to
this
TskWEB)
via
system
provided
signals
or
messages
and
passes
array
when
adding/deleting
users.
There
was
room
for sixty
65
them
to
the
correct
12C
task
(internal
or
external)
using
signals
or
messages.
This
task
receives
status
updates
from
four
entries
in
this
array.