Supported On This Version Top Portable - Platform Mt68 Not
The error message "platform mt68 not supported on this version top"
typically indicates a compatibility issue between a system-monitoring utility (like
or a variant) and the hardware architecture it is trying to run on. Based on technical documentation, this often refers to the MediaTek MT68 series or similar embedded architectures (like the
) where standard Linux binaries may lack specific support for the hardware's performance monitoring counters or instruction sets. Error Summary : The version of the
command being executed does not have the necessary drivers or compilation flags to interface with the MediaTek MT68 (or similar) platform's kernel metrics. Common Platforms : This is frequently seen on ARM-based embedded systems
, smart displays, or industrial IoT devices using MediaTek or Texas Instruments chipsets. Potential Fixes : Many users find that
offers better cross-platform compatibility for ARM architectures and may bypass the specific platform check that causes Update the utility is part of the platform mt68 not supported on this version top
package. Updating this to the latest version via your package manager (e.g., sudo apt update && sudo apt install procps ) can resolve support gaps for newer SoCs. Check for Aliases : Sometimes a custom script or alias for 'top'
is configured in your shell profile that adds unsupported flags. Run to verify there are no hidden parameters causing the crash. Firmware/Kernel Mismatch
: Ensure your Linux kernel version supports your specific hardware revision. On platforms like ODROID or similar boards
, an "Unsupported platform" error often requires a kernel update or a specific board-support-package (BSP) from the manufacturer. Unix & Linux Stack Exchange Are you seeing this error on a mobile device embedded IoT board virtual machine top command not working - Unix & Linux Stack Exchange 3 Nov 2017 —
The error message "platform mt68 not supported on this version top" typically indicates a compatibility mismatch between your hardware platform (specifically the MediaTek MT68xx series chipset) and the software environment or kernel version you are trying to run. Root Cause
This error usually surfaces in mobile development or custom ROM flashing (like Android/LineageOS) when: The error message "platform mt68 not supported on
MediaTek Dimensity Chipsets: The mt68 prefix refers to MediaTek Dimensity 5G platforms (e.g., MT6833, MT6877).
Kernel Mismatch: The pre-built kernel or boot image you are using does not contain the definitions or drivers for that specific chipset revision.
Tooling Limitations: High-level system monitoring tools like top or specialized profiling tools may fail to initialize if they cannot find the specific CPU topology or frequency scaling drivers for the MT68 platform. How to Resolve It
Update Your Toolchain: If you are seeing this while developing, ensure your Android NDK, build tools, or the specific library (like a performance monitoring library) is updated to a version that explicitly supports newer MediaTek 5G chips.
Verify Kernel Source: If you are building a system image, check that your BoardConfig.mk or kernel defconfig includes the correct CONFIG_ARCH_MT68XX flags.
Check for Proprietary Blobs: MediaTek platforms heavily rely on proprietary vendor blobs. Ensure that the vendor partition matches the specific SoC version (e.g., a "top" or "plus" variant of the MT6877). The Issue: Newer Dimensity chips (MT68 series) utilize
Hardware Identification: In some cases, the system incorrectly identifies the chip. You can verify your exact hardware ID by running: cat /proc/cpuinfo getprop ro.board.platform
A. The SP Flash Tool Version Mismatch (Most Common)
MediaTek devices are flashed using the SP Flash Tool. However, MTK frequently updates their Host-to-Target protocol.
- The Issue: Newer Dimensity chips (MT68 series) utilize newer "DA" (Download Agent) files and newer "Auth" files. If you are using an older version of SP Flash Tool (e.g., v5.1912) on a phone released in 2023, the tool's internal library does not contain the
MT68...TOPdefinition. - The Mechanism: The tool enters "Brom Mode" (Preloader mode). It queries the hardware. The hardware responds with an ID. The tool looks up that ID in its internal
top.xmlor database. If the ID is missing, the tool aborts the connection to prevent bricking the device, resulting in this error.
4. Driver or VCOM Issues
Improperly installed MediaTek USB VCOM drivers can cause the tool to misidentify the chip, defaulting to an unsupported platform error.
Why Does This Error Happen?
The root causes are technical but easy to understand:
Q: Can I ignore this error and continue?
A: No. Flashing without proper platform support can corrupt bootloaders. Never bypass it.
Troubleshooting steps (for developers and advanced users)
- Reproduce and collect details:
- Capture the full error output, logs, and the exact environment (OS version, kernel, CPU architecture, device model).
- Verify the target:
- Confirm the intended platform for the software build. Check build/configuration files, cross-compiler target triplets, and CI build logs.
- Check version compatibility:
- Consult release notes or compatibility matrices for the software and the runtime/OS to see whether mt68 is supported in this version.
- Inspect package metadata:
- For installers or package managers, examine manifest files (e.g., package.json, control files, RPM/DEB metadata) to see supported platforms.
- Search for naming mismatches:
- Normalize platform identifiers and search build scripts for alternative names (mt68, mt-68, MT68).
- Ensure drivers and device-tree entries:
- On embedded systems, confirm that device trees, firmware blobs, and kernel drivers for mt68 are present and loaded.
- Rebuild for the correct target:
- If the binary was built for mt68 but the device differs, rebuild or obtain a build for the actual target.
- Update or downgrade runtime:
- If the runtime lacks support, either update it to a version that includes mt68 or obtain a version of the software compatible with the installed runtime.
- Contact vendor or maintainers:
- When builds are vendor-restricted or officially supported platforms are unclear, open a support ticket or issue with full environment details.
- Workarounds:
- Emulation: Use a compatible emulator or container that presents the expected platform.
- Compatibility shims: Sometimes lightweight compatibility layers or symbolic platform mappings can be introduced, but these carry risk.