Getnet DocsGetnet Docs

Maintenance and Updates

View as MarkdownView this page as plain textOpen in ChatGPTAsk questions about this pageOpen in ClaudeAsk questions about this pageOpen in PerplexityAsk questions about this page
Connect to CursorUse these docs in CursorConnect to VS CodeUse these docs in VS Code

This guide explains how to manage remote software updates using the YDL (Remote Download) command and provides the corrected, step-by-step procedure for extracting technical logs for deep troubleshooting.

Remote software download (YDL)

The Getnet Pinpad supports updating its internal firmware and application APK dynamically over the serial connection. This prevents the need for physical tech support visits for software upgrades. The Host System acts as the bridge, downloading the software package from its backend and streaming it sequentially to the Pinpad.

The update workflow

The process is divided into two main phases: Handshake/Initialization and Sequential Data Transfer.

Phase 1: Initiation

To start the update, the Host System sends a YDL requirement indicating the start of a transfer.

  • Operation Type (OPR): Set to “01” (Init).
  • Total Size (TAM): Total size of the APK file in bytes.
  • Packet Size (TPS): The size of each data block (e.g., “1024”).

Phase 2: Transmission Loop

For every block of the file, the Host System sends a subsequent YDL command containing the chunk data.

  1. Host Action: Sends YDL with OPR set to “02” (Transfer) and the binary data in the [DAT] field.
  2. Pinpad Action: Verifies each block’s integrity using a CRC algorithm. If the CRC fails, it returns an error, and the Host must retry that packet.
  3. Finalization: Once the final packet is received, the Pinpad reconstructs the file and triggers the internal installer.

Do not interrupt the power supply during the installation phase. The Host System should display a “Do Not Turn Off Terminal” message to the operator during this process.

Technical log extraction

For analyzing the behavior of both the application and the N750P terminal, you must extract logs to an external Micro SD memory. Because the terminal operates in a secure environment, filesystem access is restricted, and a specific hardware-triggered menu must be accessed.

Extraction via micro SD card

To extract application logs safely, follow these steps:

  1. Preparation: Obtain a Micro SD memory card and an N750P terminal.
  2. Insert Media: Power off the device, remove the battery cover, and insert the Micro SD card.
  3. Power On: Once inserted, turn the device on.
  4. Access Config Menu: Press and hold the top power button until a pop-up window appears. While still holding power, press the red volume button on the right side.
  5. Authentication: A password window will appear. Enter the password: 159953.
  6. Navigate to Logs: Access the Tools menu and select LOG.
  7. Data Transfer: The information will begin downloading to the Micro SD card. Wait for the tool to indicate that the process is complete and has been saved correctly.
  8. Safe Extraction: Power off the device again to safely remove the Micro SD card.
  9. Analyze: Insert the memory into a PC and locate the logcat.tar file, which contains the compressed logs.

Maintenance best practices

  • Version Verification: After an update and reboot, use the Y0I (Echo Request) command to verify that the [SOF] field matches the expected new version.
  • Stable Baud Rate: Maintain a stable 115200 baud rate for the duration of the transfer to minimize packet loss.
  • ChangeYDL Variant: If your project uses the ChangeYDL flag, remember that error screens during a failed download will remain visible indefinitely until manually dismissed.

Next steps

  1. Configuration and Connectivity: confirm the running version with the Y0I echo test after an update.
  2. Error Handling: interpret the Y0E codes returned when a download or log extraction fails.