iTEMP 하드웨어를 갖고 계신가요? 모델명부터 시작하세요.

Enter the model printed on the label — or scan the QR code on the box — on the support page. The model hub links the board’s wiki page, flashing and recovery guides, the system API, downloads and warranty service.

Yes. The developer wiki is public, with no account and no NDA: board pin tables and serial maps, flashing and MaskRom recovery, the full system API and on-device AI guides. Engineers usually check it before choosing a board.

Attach a serial console first — the boot log tells you whether the board boots and the problem is the display, or whether it stops earlier.

• Boots fine (adb works) → check the panel cable, the panel’s power and backlight, and that the firmware is configured for your panel.
• Stops in the log → note the last lines and follow recovery if needed.
• No log at all → check the power supply and the serial wiring.

Use a 3.3 V USB-to-TTL adapter on the board’s debug UART: GND to GND, adapter TX to board RX, adapter RX to board TX — leave VCC unconnected.

Rockchip boards use 1,500,000 baud, 8N1, no flow control by default — not 115200, which shows garbage. Some adapters (older PL2303) cannot reach that speed; CH340-based adapters with PuTTY or picocom work well. The debug header location is on your board page.

• Connect the USB OTG / device port — USB-A host ports do not carry adb.
• Use a data cable, not a charge-only one.
• Make sure USB debugging is on: ItempApiPub.setUsbDebug(context, true), checked with getUsbDebugStatus.
• Accept the “Allow USB debugging” prompt on the screen if it appears.
• Alternatively use adb over the network.

• The firmware version: adb shell getprop ro.itemp.firmware.version.
• The app log: adb logcat -d > logcat.txt right after the problem.
• For boot or crash problems: the serial console log from power-on.
• The model, serial number and what changed before it started.

autoLogCatch(context, true) records logs continuously for problems that are hard to reproduce — switch it off afterwards, it fills storage. Send everything through Contact an engineer.

1. Check the basics: power, cables and a reflash — MaskRom recovery fixes most boot problems.
2. Send model, serial number and symptoms through the engineer form, with a photo of the label if possible.
3. Diagnosis: an engineer confirms whether it is a hardware fault and issues an RMA number.
4. Repair or replace: ship the unit with the RMA number.

Start at Warranty & RMA. Warranty terms for your order are stated in your quotation.

On the board’s page in the public developer wiki — no account, no NDA. Each page lists the SoC, Android version, I/O, connector pinouts and size. Start at Boards, or enter your model on the support page.

Our firmware supports OTA updates, so you can ship signed firmware updates to deployed devices without visiting them; for small fleets on site, an SD card or USB flash also works. For custom firmware we prepare the update packages for your build. See OTA updates, or ask us to set up an update plan for your fleet.

Run:

adb shell getprop ro.itemp.firmware.version

Quote this value in every support request. The wiki is versioned per firmware release — pick yours in the version selector. If your build number is not listed, the device runs a custom image made for your project; ask your account manager for its notes.