Ipp Differences - VeriFone MX800 series Programmer's Manual

D D
EVICE RIVERS

IPP Differences

IPP Differences
56
M X 800 S P
ERIES ROGRAMMERS
<SI>0103 PROM Checksum
<SI>0108 IPP ROM Version Number
<SI>13 Select Baud Rate
<SI>15 Set IPP6 Key Management Mode
<SI>17 Set IPP7 Key Management Mode
<SI>02 Set master key
Multiple DUKPT
G
UIDE
The value of the checksum does not
match IPP7 since it is based on the M
series terminal code.
The return packet is:
<SI>14IPP8 EMULvvv mm/
yy<SO>{LRC}
where vvv is the version number, mm is
the release month, and yy is the release
year.
There is no IPP UART so setting the baud
rate does nothing. However, the baud rate
is stored in non-volatile memory so it can
be returned in diagnostics packets.
In platforms with an IPP chip, the
application must determine the baud rate
of the IPP by sending a test packet at all
possible baud rates until the IPP
responded with an ACK. In M
of terminals, there is no UART so baud
rate mismatch is not possible. Applications
that try all possible baud rates will get an
ACK on the first test packet. This speeds
up applications slightly.
Spain mode is not supported but switching
to Spain mode will erase keys. This is
included because some test programs
depend on this behavior to erase keys
between tests.
SM mode is not supported but switching to
SM mode will erase keys. This is included
because some test programs depend on
this behavior to erase keys between tests.
IPP7 has limited RAM so it can hold at
most three triple length keys. In M
series of terminals, all ten key locations
can hold a single, double, or triple length
key. This is a enhancement planned for
IPP8 so it has been implemented because
extra code would be required to enforce
the IPP7 key limitations.
IPP7 supports one DUKPT engine. The
x
M 800 series terminal IPP emulation
supports three DUKPT engine the same
way the IPP8 does.
x
800
x
800 series
x
800