Intel MCS48 User Manual page 458

Family of single chip microcomputers
Hide thumbs Also See for MCS48:
Table of Contents

Advertisement

B3.
IMon-lntellec
Hex
Paper
Tape Format
For
the non-lntellec
Hex
Format,
a
data
field
can contain
either
8
or
4-bit data.
Two
ASCII
hexadecimal
characters
must
be
used
to represent
both 8 and
4-bit data.
In
the case of
4-bit data,
only
one
of the characters
is
meaningful
and must
be
specified
on
the
Intel
PROM/ROM
Order Form.
Parity
is
allowed;
however,
it
is
not checked. Preceding
the
first
data
field
and
following the
last
data
field
there
must
be
a
leader/trailer
length
of
at least
25
null
characters or
rubout
punches.
The
format requirements
are
as
follows:
1.
The
start
of the
first
data
field
is
indicated
by
a
colon. After the
last
data
field, a
semicolon
must
be
punched
to
indi-
cate the end.
All
data
fields
are
to
be
punched
in
consecutive
order, starting
with data
field
00 H
(all
addresses low).
2.
Two
hex
characters
must
be used
to represent the
data
field
of
both
N word
x
8-bit
and
N
word
x
4-bit devices.
For an
8-bit
data
field,
the high order data
is
represented
by
the
left
justified
character of the
pair.
Either character of the
pair
may
be used
to represent the
word
field
of
a
N
word
x
4-bit device,
however,
it
must
be consistent
throughout
the
word
field.
The
other character
may
be
any hex
character.
A
field
of
"don't care" data
is
allowed.
Data
after
a field
of "don't care"
will
be
programmed
starting
at
an address
location
enclosed
in
parentheses.
In
the following
example,
data
is
entered
in
addresses
00
H
to
05
H
,
followed with
"don't
care"
from
addresses
06
H
to
25
H
,
data being entered again
starting at
address location
26h, and
followed with
"don't care"
data
to
the
last
address
location.
|:|
j70F2145100FF
||
(26)
l|
7B0890F1
| |
;,
?
Start
Character
Data
Fields
from
Address
00h
to
05h
Address Location
where
Data
is
to
be
Programmed
Data
Fields
from
Address
26h
to
2Ah
End
Character
3.
The
x character
may
be used
to
rubout any erroneous
character(s).
The
#
character
may
be used
to
rubout
an
entire
line
up
to the
previous
carriage return.
4.
Spaces
are
allowed only
between
separate
word
fields.
5.
After each
72
characters,
a
carriage return
followed
by
a line
feed
should be
punched
to
allow
a
print-out of the
tape.
6.
Comments
must
be placed only
between
the tape leader
and
the
start
of the
first
data
field.
C.
Computer Punched
Card
Format
The
following
general
format
is
applicable to the
programming
information
sent
on computer punched
cards:
1.
An
80 column
Hollerith
card
(interpreted)
punched on
an
IBM 026
or
029 keypunch
should be submitted.
2.
A
single
deck must
consist of
a
Title
Card followed
by
the data
cards.
There
will
be
N/8
or
N/14
data cards
for
N
words
x
8-bit
and
N
words
x
4-bit devices, respectively,
in
the
PN
format.
For
the
Intellec
Hex
format,
there
will
be
N/32
data cards
for
both
N
words
x
8-bit
and
N
words
x
4-bit devices,
and
one end
of
file
card.
CI.
Intellec
Hex Computer Punched
Card
Format
Two
hex
characters
must
be used
to represent
data
for
both
a
N word
x
8-bit
and
N word
x
4-bit device.
For
the
latter,
only
one
of the characters
is
meaningful and
must
be
specified
on
the
Intel
PROM/ROM
Order Form.
The
entire
data
field
for
all
bits
must
be
punched
even
if it is
"don't
care".
i
ii
i
I
HI
III
|iiii|||ioiii|:igti|:iiin
innmnlillnmnl)
CUSTOMER'S
DIVISION
OR CUSTOMER'S
LOCATION
P/N
DECIMAL
NUMBER
INDICATING
THE
TRUTH TABLE NUMBER
NO
OF OUTPUTS
INTEL
P/N
I
I
I
I
I
II II
I
I
I
I
I
Column
Data
1
Punch
a
T
2-3
Blank
4-28
Customer
Con-
pany
Name
29-30
Blank
31-50
Customer's
Co
mpany
Division or location
51-52
Blank
53-61
Customer
Part
Number
62-63
Blank
64-72
Punch
the
lot
1
4-digit basic
part
number
and
in
(
1
then umber
ot
output
bits, e.g.,
2708
(8),
2316
(81.
or
3605
(41
73-74
Blank
75-76
Chip
number
for
ROMs
with
programmable
chip
select
inputs
If
not
applicable, leave
blank
77-78
Blank
79-80
Punch
a
2-digit
decimal
number
to indicate
truth table
number. The
first
truth table
will
be 00.
econd
01.
third
02, etc
A2-8

Advertisement

Table of Contents
loading

Table of Contents