Linux SDK Installation

SDK Delivery

The Nayax EMV-Core SDK supports a wide range of Linux-based platforms. Each delivery includes optimized binaries for specific CPU architectures and library versions.

Supported Platforms

Target Name	Description	Bits	PIE	CPU ABI	Min Kernel	GLIBC	libCurl
x86_64	Ubuntu 64-bit	64	Yes	AMD64	3.2.0	2.34	7.81.0
armhf	ARM32 GCC "hard float"	32	Yes	ARM v7-A	3.2.0	2.34	7.81.0
armhf_7.5	Linaro 7.5 toolchain	32	No	ARM v7-A	3.2.0	2.17	7.86.0
armv8a	Poky Linux (Yocto)	64	Yes	ARM AArch64	5.15.0	2.38	8.4.0
aarch64-nuvoton	Nuvoton (Buildroot)	64	No	ARM AArch64	5.10.0	2.28	7.79.1
arm-inj	Buildroot	32	Yes	ARM v7-A VE	-	-	7.83.1
ql_oe_mdm9607	Quectel MDM9607	32	No	ARM v7-A	2.6.32	2.17	7.44.0
cortexa53-poky	Poky Linux	64	Yes	ARM AArch64	3.14.0	2.34	7.82.0
openwrt	Open-source firmware	32	No	MIPS	-	-	8.0.1
aarch64-gnu-13.2	GNU toolchain 13.2	64	-	ARM AArch64	3.7.0	2.34	8.9.0

Package Contents

Each platform folder contains four primary components:

otiKiosk: The primary EMV-Core service executable.
otiKioskDemo: The client Test Application executable.
kiosk-client-library-xxx.zip: Eclipse project containing the C source code and sample app.
otikiosk-xxx.zip: Package for remote updates via TMS (using the CON_PROG command).

Example Folder Structure (x86_64):

\Linux\x86_64\otiKiosk (EMV-Core Service)
\Linux\x86_64\otiKioskDemo (Test App)
\Linux\x86_64\Sources\... (Client library & source code)
\Linux\x86_64\TMS Update\... (Remote update package)

Installation on Linux

EMV-Core Installation Steps

Deploy Binaries: Copy the otiKiosk binary to your target device.

Note: Do not rename this file. The system expects the filename to be exactly otiKiosk.
Auto-Start Configuration: Configure your system (e.g., via systemd or init.d) to launch the EMV-Core binary automatically on boot.
Device Access (udev Rules): Ensure the application has read/write access to the reader hardware.
- USB HID: Access to /dev/hidrawX
- RS232: Access to /dev/ttyX
- Tip: Create a udev rule in /etc/udev/rules.d/ to grant permissions without requiring root: KERNEL=="hidraw*", SUBSYSTEM=="hidraw", MODE="0666"
Folder Permissions: Set the directory containing the binary to allow read/write/execute access for the user running the service: chmod +x otiKiosk
Environment Variables: If the application uses environment variables for specific folder paths, ensure those directories are created and have rwx permissions.