Gemalto MagIC3 X-series, Maintenance Manual, Page: 34 / 37

E-Payment
MagIC
3
X-series - MAINTENANCE MANUAL
Chapter 2 :
TROUBLESHOOTING
Ref: 22000-00-MAN-I-09004 June 2009 Ch.2 - 34/37
Copyright Gemalto – 2008 No disclosure to a third party without prior written consent of Gemalto
3.1 SP STATUS ticket information
Look at the ticket that is printed:
*** MagIC3 SP Status ***
SP Status : 0
¾ 0
: OK. At least AUTH_SP and AUTH_CUST keys have been loaded and no attack has been
detected. The Terminal is not tampered.
¾
1
: Reserved for Manufacturing.
¾ 2
: NOK. Multiple causes (Physical and/or Keys issue):
¾
AUTH_SP = 0x1 (default key) :: you must load an A AUTH_CUST (
1
).
¾
AUTH_SP loaded but not AUTH_CUST :: you must load AUTH_CUST.
¾
Security keys are present but an attack has been detected by the Secure Processor :: you
must investigate security registers to identify the root cause (Mesh opened, switch opened,
low voltage on the lithium buttom cell, …).
Opening Cntr : 0
Number of times the Terminal was opened from the last load of AUTH_SP key. Feature supported
from FWSP 1.10.00. Besides, if the firmware is upgraded from versions below 1.10.00, this value is
meaningless.
UKSR (Sav) : 0x00000000
Value of the UKSR (Curr) before the last Unlock operation. Please, read UKSR (Curr) to understand
usefulness of UKSR (Sav). Note that b0 of UKSR (Sav) is always 0.
UKSR (Curr) : 0x00000001
This register gives some information about the last event impacting the security state. When (at
least) AUTH_SP and AUTH_CUST have been loaded and no attack has been detected, the UKSR
(Curr) must be equal to 0x00000001.
As soon as an attack is detected, this register changes and indicates the origin of the SECURITY
ALERT (mesh or switch for instance). Then, an image of UKSR (Curr) is copied in UKSR (Sav).
UKSR (Curr) keeps the information while it has not been reset by unlocking operation. Unlocking
operation reset the UKSR (Curr) to 0x00000001.
When a Terminal has been unlock, if you want to know what was the last event that impacted the
security state, you just need to read UKSR (Sav).
SECIRQ (Sav) : 0x00000000
R&D relevant only.
SECIRQ (Cur) : 0x00000000
Consider that this register works like UKSR (Curr), with one important exception. Unlike UKSR
(Curr), SECIRQ (Cur) does not keep the information. Its state is refreshed in real time. It is usefull to
know the current state of the security triggers.
1
Terminal is in this state when it has not been personalized, or perzonalized failed