The terminal automatically performs a full security check every 24 hrs. The terminal can be configured by the application to trigger this security test when the terminal is idle. During this time the Bluetooth will be switched off. The files that failed the security check will be removed from the terminal. 3.8.2 Software Update The software on the terminal can be updated by the application on the smart device. The software update will be transferred to the terminal over the Bluetooth or WiFi, once this is complete the soft-
ware update will start. The terminal will indicate if a software update is in progress and will report success/failure. If the software update fails, the operator has to acknowledge the failure by pressing ENTER(
) to proceed further. In the unlikely event that a software update fails, a Factory-reset (see ReviveTM section) may be required to make the terminal operational. Software update in progress. The terminal will display the success or failure message accordingly. 3.9 as above or OK (
) continue to return back to idle screen of MPI. BACK (X) to return to previous menu BACK (X) to cancel or OK (
) continue to restart MPI. OK (
) to reboot the terminal. BACK (X) to cancel the reboot or BACK (X) to cancel the shutdown of the terminal or select OK (
) to completely shut down the terminal. 3.10 3.10.1 System Tampered If the terminal identifies a tamper, the terminal will immediately close the Payment application abort-
ing any transaction in progress. The tamper state is indicated on the display. A Tampered terminal should be returned for investigation. 3.10.2 Ready To Install The terminal will be in Ready To Install state if no application has been installed or has been deleted. A terminal in Ready to Install state should be returned for investigation. 4 Miura products include a ReviveTM feature which is activated using a pin-hole reset switch, this is situ-
ated next to the power button. Pressing the ReviveTM button will trigger a hardware reset, and the terminal will display the Revive Menu. This is best done when there is no external power applied, if external power has been applied the terminal will request to disconnect the external power. The end-user should use this feature if the ower button. The ReviveTM Menu has three options, namely:-
4.1 Selecting this option will reboot the terminal resulting in a complete hardware and software reset. 4.2 be-
comes unresponsive to power button or is not running as expected and option 1 in the revive menu terminal was unsuccessful in recovering the terminal, unintentional sys-
tem restoration. the success or failure message for the System Restore. If the system Restore process fails, the opera-
tor has to acknowledge the failure by pressing the ENTER(
restore fails, the terminal may be in an unusable state. The operator
) key. In the unlikely event that a system is The terminal will display 4.3
-user to reset all software and configuration back to the state it was in when the terminal left the factory. This feature should be used if there are any is-
controlling application on the smart device will need to perform any software configuration and key process, and the in order to avoid unintentional factory reset operation.
; Factory Reset in progress. The terminal will accordingly display the success or failure message for the Total Factory Reset. If the Total factory reset process fails, the operator has to acknowledge the failure by pressing the EN-
TER(
) key. If the factory reset fails the terminal has to be returned for further investigation. 4.4 The ReviveTM button can also be used to activate the terminal's diagnostics facilities. This involves ex-
porting operating system log files and running a built-in hardware functional test. It is not envisaged that this will be done by an end-user. The diagnostics state is entered by activating the ReviveTM button whilst holding the '0' key. Once the terminal has booted, it will export XXX-XXXXXX-Conf.txt, XXX-XXXXXX-Info.txt and XXX-
XXXXXXEvents.txt diagnostic files in the USB Mass Storage Device, where XXX-XXXXXX is the serial number of the terminal. Example contents and format of these files are described in Appendix A: Ex-
ample diagnostics Files. When returning a terminal under RMA, these files should be returned as well. Once these files have been retrieved the USB cable can be removed and the terminal automatically starts the functional test, see the Functional Test section. Creating Terminal diagnostic data: This state is notified when the diagnostics state is entered by acti-
vating the pin-hole switch. Terminal diagnostics data exported in USB Mass Storage Device: Once the diagnostics log files have been created, the files will be exported in the Mass storage device. The files can be retrieved by con-
necting the USB lead to a computer. Unplugging USB lead after this will start functional tests. Failed to export Terminal diagnostics data in Mass storage device: If the terminal fails to export the diagnostics log files in mass storage device, the terminal will display a failure message. The terminal should be identified as a return under warranty and all details of the terminal, and the fault recorded. 5 The Miura Operating System contains a built-in functional test which fully tests the hardware. In order to perform the tests the following are required (and can be obtained from Miura):
-swipe and smartcard. Or alternatively, a modified terminal provided by Miura running specific software with a pre-set Bluetooth address capable of supplying at least 1 Amp. An M020 fast charging cradle
-clip (not a sharp object) to activate the pin-hole reset switch. The functional tests are activated when the USB lead is unplugged after the retrieval of the diagnos-
tics files from USB Mass Storage Device (MSD). The following are general points for functional tests:
test. Pressing CANCEL(X) when a Test has failed will abort the functional test. CANCEL(X) ENTER(
) to continue to next ass the final result will be pass. XXX-XXXXXX_Results.txt will be exported in the MSD. Where XXX-XXXXXX is the serial number of the terminal. NOTE: If tests are skipped or performed incorrectly (e.g. if a card was swiped badly or the Bluetooth responder was not switched on), the terminal will appear to have failed when it is not faulty. It is therefore important to make sure all test are performed correctly. The sections below describe the procedure for functional tests. 5.1 The beeper will sound for 2 seconds at the start of the factory test. After hearing the beeper a confir-
mation screen to which the operator has to press ENTER(
CANCEL(X) otherwise.
) if the beeper is working correctly or 5.2 Five colour test screens will be displayed, each for 2 seconds. These are red, green, blue, white and lastly black. The operator has to look for a colour problem, stuck pixels or any abnormalities in the dis-
play. The black screen is a confirmation screen to which the operator has to press ENTER(
display is working correctly or CANCEL(X) otherwise.
) if the 5.3 The operator will be asked to touch a crosshair shown on the screen to perform a test of the touchscreen. After each touch, the crosshair will move to a different location to test different areas on the screen. After tapping or touching all the required positions, the test will automatically indicate whether it has passed or failed. 5.4 The green LED at the top right corner of the terminal will blink, to which the operator has to press EN-
TER(
) if the LED is working correctly or CANCEL(X) otherwise. 5.5 The keypad backlight will blink, to which the operator has to press ENTER(
or CANCEL(X) otherwise.
) if it is working correctly 5.6 The terminal requires the operator to press each of the keys on the Keypad. The terminal will indicate which key should be pressed and then moves to the next key if the press was successfully registered, until all keys have been tested. 5.7 The operator should swipe the test card provided. The terminal, on reading the swipe card, will record the success or failure. The operator is allowed a second try if the first swipe was not done properly. If it is not possible to run this test, it can be skipped by pressing the CANCEL(X) key. 5.8 The terminal will request the operator to insert the test card provided into the chip card slot. The ter-
minal will read the card and record the result. The terminal will then request the operator to remove the card to proceed to the next test. If it is not possible to run this test, it can be skipped by pressing the CANCEL(X) key. 5.9 The operator has to bring a contactless card near the contactless logo when prompted. The terminal will read the card and record the success or failure accordingly. 5.10 The terminal will request the operator to insert the USB cable connected to PC or USB wall adapter and check for Red charging LED next to the USB connector, if ON press ENTER(
) otherwise CAN-
CEL(X). The terminal will then request the operator to remove the USB and check if the Red LED is off, if OFF press ENTER(
). o o o o 5.11 This will test that the charging contacts for use with a Fast Charge Cradle are working correctly. This test can be skipped if a Fast Charge Cradle is not available. The contacts to be tested are 5V fast charge and GND, as shown in item 2 in the M020 Features sec-
tion. The terminal will request the operator to place the terminal in the Fast Charge Cradle. After a short period, the terminal will then request the operator to remove it from the charging cradle, which removes power from the charging contacts. The operator will be notified if the test fails. Note: on certain OS versions a Smartcard charging test will follow this test. In that case, please repeat the procedure indicated for the Charging Cradle Test or skip if a Fast Charge Cradle is not available. 5.12 For this test, the operator should have one of the following:
- Dedicated Miura terminal configured as a BT responder The operator should have the provided Bluetooth responder powered on and in Bluetooth range for this test. This test is automated and does not require any other input from the operator. The result will be recorded accordingly by the terminal and the operator will be notified if the test fails. 5.13 For this test, the operator should have one of the following:
- WiFi router or Access point configured with the following details:
o Router or access point type: standard 2.4 GHz, 802.11n or newer o network name (SSID): miura-wrt-belk o network security type: WPA2-AES o network security key: W!F!m1ur@
Either has to be powered on and in range. This test is automated and does not require any other in-
put from the operator. The result will be recorded accordingly by the terminal and the operator will be notified if the test fails. If it is not possible to run this test, it can be skipped by pressing the CAN-
CEL(X) key. 5.14 This is an automated test of the Apple Co-processor. The operator will be notified if the test fails. 5.15 Once all the tests have been executed, the test results will be exported in the MSD. The terminal will indicate on the display that the results have been exported in MSD. The results can be retrieved and attached to any reports as needed. The terminal can then be powered off. 6 It is not possible for Miura to define end-user troubleshooting, as there are many components in the end-user experience which are not defined or controlled by Miura. It is envisaged that the partner will define the troubleshooting process, in part using information from this document. This section gives some suggestions about what should be included as part of this process. Note that problems reported as the terminal not responding may in fact be caused by an issue with the smart device or the application running on it. Does the device power on?
Charging the battery). The red charging LED can be used as an indication that the terminal is charging correctly. source and USB cable being used should be veri-
fied. Does the terminal perform as expected?
System Tampered it should be returned for investigation believed to be with the terminal as opposed to the smart device, then the user should Reboot the terminal using the ReviveTM feature. the smart device and application, a System Restore should be performed. rule out Total Factory Reset should be performed. 7 This section is aimed at determining if a given terminal is functioning correctly and is acceptable for use in the field. It is not envisaged that this process will be carried out by the end-user, but will form the basis of testing performed by Miura and the partner at various stages in the terminal's life cycle including: Miura OBA (Out of Box Audit), Partner QA Testing, Partner returns filtering and Miura re-
turns filtering. Each of these stages will no doubt include other additional tests and processes as de-
fined by the organisation performing the stage (and documented separately) but the filtering process defined in this section should be common to all. Equipment required is as detailed in Functional Test plus the following:
avoid leaving fingerprints on new units)
-filtering) Step1: Perform a visual inspection on the terminal (to check for imperfections, damage, rattles etc) go to step 2. Step 2: Charge the terminal and Power it on. t on (if it is not on already) Step 3: Check the terminal starts up. Operating the M020 Payment Terminal), go to step 4. system tampered, the terminal is faulty. terminal diagnostics files and attempt to recover the terminal by performing a factory reset. Step 4: Run the Terminal Diagnostics and Functional Test. terminal diagnostics and functional test. they will be needed in any diagnostics which may be carried out. retained as NOTE: The terminal will also report a failure after a Factory Test if the tests are carried out incorrectly, or if any test is skipped, in which case the test needs to be repeated in full. If a particular test fails, the operator can choose to continue with the remaining tests. 8 020-000110-Conf.txt This file identifies the hardware and software configuration of the Terminal. Customer=Generic Sound=N/A GSM=N/A Charge_cradle=5V Smartcard=TDA8029HN Flash=NAND 2kblocks*64pages*2112bytes*8b USB_WiFi=N/A RAM=LPDDR 4Banks*8Mwords*16b Contactless=M020-EMVPCDHW-V1 Hardware=M020-TEST01-V2-0 Series=M020 USB_Bluetooth=6223E-UUD Backlight=N/A Serial=020-000050 Power=LP3910 OS=M000-DEVOS-V7-2 Ethernet=N/A Printer=N/A Light_sense=N/A Battery_Low=N/A Mag_sense=N/A Battery_Stats=N/A USB_OTG=500mA Display=Mono 128*64 SSD1309 Processor=MCIMX258CJM4A Keyboard=3x5(NA,M020,CLR,1,2,3,4,5,6,7,8,9,CNL,0,ENT)+Pwr+Revive KB_backlight=N/A MFi=MFI337S3959 LEDs=M020 PCBA=M020-PCBA01A-V1-5 Mag=3-Track MRD532 020-000110-Info.txt This file provides information about the Terminal, including: hardware part number, current OS part number, Serial Number, current application part number and finger print of the Remote Key Injection CA certificate loaded in manufacture. Hardware : M020-PROD01-V2-0 Software : M000-OS-V7-4 Serial : 020-000050 App-version : M000-MPI-V1-28-CONF15-V1 CA-fingerprint: 93:DD:63:E0:19:50:FE:15:FF:57:F7:59:C7:34:65:5A:0E:75:4C:F8 020-000110-Events.txt The File records the system events happened from the manufacture of the Terminal. Jun 18 11:32:41 miura miura-monitor: Couldn't access shutdown time data Jun 18 11:32:41 miura miura-monitor: Startup time - Wed Jun 12 11:32:08 2013 Jun 18 11:32:42 miura miura-monitor: Start-Up event - Wipe (4) Jun 18 11:32:44 miura factory-test: Starting terminal key verification Jun 18 11:32:44 miura factory-test: Terminal key verification success Jun 18 11:32:46 miura factory-test: Ready to install Application Jun 18 11:34:33 miura factory-test: Application installation starting Jun 18 11:34:56 miura miura-auth: Request for make_factory Jun 18 11:34:57 miura miura-auth: Request for make_restore Jun 18 11:34:57 miura factory-test: Application installation successful Jun 18 11:36:23 miura miura-monitor: Shutdown time - Wed Jun 12 11:35:01 2013 Jun 18 11:36:23 miura miura-monitor: Startup time - Wed Jun 12 11:35:57 2013 Jun 18 11:41:26 miura miura-monitor: Shutdown time - Wed Jun 12 11:35:01 2013 Jun 18 11:41:26 miura miura-monitor: Startup time - Wed Jun 12 11:41:00 2013 Jun 18 11:41:26 miura miura-monitor: Start-Up event - Start Terminal Diagnostics (7) 020-000110-Results.txt Summary of the functional tests.
********* LCD Test *********
LCD Test: SUCCESS
********* LED Test *********
Pinpad LED Test: SUCCESS
************* Keypad Test **************
Keypad Test: SUCCESS
*********** Mag-Swipe Test *************
Mag-swipe-test: TRK1 - PASS Mag-swipe-test: TRK2 - PASS Mag-swipe-test: TRK3 - PASS Mag Swipe Test: SUCCESS
*********** Smart-Card Test ************
Smart card Test: ATR Received: Size = 19. Smart card Test: ATR: 3b5f9500807300010059434c5a1b0011409000 Smart card Test: SUCCESS
********* Contactless Card Test *********
Contactless: Card Detected!!!
Card in field Contactless card Test: SUCCESS
************* Charger Test *************
Charger Test: SUCCESS
************* Cradle Test *************
Cradle Test: SUCCESS
************ Bluetooth Test ************
Manufacturer: Fn Link Firmware tbd HCI version: 4.0, LMP version: 4.0 Waiting for connection... accepted connection from 20:12:11:15:16:5D received [hello!]
Bluetooth Test: SUCCESS
************ Apple co-processor test ************
Apple co-processor test co-processor info:
Device version 5 Firmware Version 1 Protocol Major version 2 Protocol minor version 0 Device ID 0x00000200 Apple Co-Pro Test: SUCCESS Factory Test: Functionality tests completed. 9 Battery: This product uses a Lithium-Poly battery. Do not use it in a humid, wet and/or corrosive environment. Do not put, store, or leave your product in or near a heat source, in a high temperature location, in strong direct sunlight, in a microwave oven or in a pressurised container, do not subject to extremely low air pressure and do not expose it to temperatures over 60C (140F). Failure to follow these guidelines may cause the battery to leak, become hot, explode, or ig-
nite and cause injury and/or damage. Do not pierce, crush, cut, open or disassemble the battery. If the battery leaks and you come into contact with the leaked fluids, rinse thoroughly with water and seek medical attention immediately. For safety reasons, and to prolong the lifetime of the battery, when not in use store your product in a cool, dry place. Charging will not occur at low (below 0C/32F) or high (over 45C/113F) temperatures. CAUTION:
Do not remove or attempt to remove the non-user-replaceable battery. Risk of explosion if the battery is replaced with an incorrect type. THE BATTERY CONTAINED IN THE PRODUCT MUST BE RECYCLED OR DISPOSED OF PROPERLY ACCORDING TO THE LOCAL LAWS AND REGULATIONS AND ALWAYS KEPT SEPARATE FROM HOUSEHOLD WASTE. BY DOING THIS YOU WILL HELP CONSERVE THE ENVIRONMENT. CE marking This equipment complies with the requirements for CE marking when used in a residential, commercial, or light industrial environment, achieving all the appropriate provisions of the relevant legislation in the EU. RED directive Hereby, Miura Systems Ltd declares that Miura Systems Ltd products and accessories are in compliance with the essential requirements and other relevant provisions of the EU Directive 2014/53/EU. The declaration of conformity can be found here: www.miurasystems.com/certifications WEEE directive The wheelie bin symbol on the product or its packaging indicates that this product shall not be treated as household waste. In line with EU Directive 2002/96/EC for waste electrical and electronic equipment (WEEE), this electrical product must not be disposed of as unsorted municipal waste. Please dispose of this product by returning it to the point of sale or to your local municipal collection point for recycling. By doing this you will help conserve the environment. Pacemakers Pacemaker manufacturers recommend that a minimum of 15cm (6 inches) be maintained between a handheld wireless device and a pacemaker to avoid potential interference with the pacemaker. These recommendations are consistent with independent research and recommendations by Wireless Technology Research. Guidelines for people with pacemakers Other medical devices Please consult your physician or the manufacturer of the medical device, to determine if the operation of your wireless product may interfere with the medical device. The exposure standard for wireless device employsa unit of measurement known as the Specific Absorption Rate, or SAR. The SAR limit set by the FCC is 1.6W/kg. For body worn operation, this Mobile Point of Sales terminal been tested and meets FCC RF exposure guidelines when used with an accessory that contains no meta and that positions the product a minimum of 0 mm from the body. Use of other accessories may not ensure compliance with FCC RF exposure guidelines The exposure standard for wireless device employsa unit of measurement known as the Specific Absorption Rate, or SAR. The SAR limit set by the RSS is 1.6W/kg. For body worn operation, this Mobile Point of Sales terminal been tested and meets RSS RF exposure guidelines when used with an accessory that contains no meta and that positions the product a minimum of 0 mm from the body. Use of other accessories may not ensure compliance with RSS RF exposure guidelines Lappareil peut tre utilis en condition dexposition portable sans restriction. La norme dexposition pour les appareils sans fil emploie une unit de mesure appele dbit dabsorption spcifique, Ou SAR. La limite de SAR fixe par le RSS est de 1.6W/kg. Pour le corps us opration, Ce terminal de Point de vente Mobile a t test Et rpond aux directives dexposition RF RSS lorsquil est utilis avec un accessoire qui ne contient pas de meta et qui positionne le Produit un minimum de 0 mm du corps. Lutilisation dautres accessoires peut ne pas assurer la conformit avec Lignes directrices sur lexposition aux RF RSS 10