https://toorun.dev/tags/diagnostics/Recent content in diagnostics on toorun.devHugo -- gohugo.ioen-usWed, 26 Aug 2026 08:00:00 +0000https://toorun.dev/posts/retrieve-hardware-specs-linux-embedded-systems/Wed, 26 Aug 2026 08:00:00 +0000https://toorun.dev/posts/retrieve-hardware-specs-linux-embedded-systems/How to Retrieve Hardware Specifications on Linux and Embedded Systems When debugging, deploying, or documenting an embedded system or Linux machine, you need to know what hardware you are working with: CPU type and speed, available memory, storage capacity, connected peripherals, and kernel configuration. This guide provides practical commands and file locations to retrieve all critical hardware information on Linux-based systems, from servers to embedded devices. 1. CPU Information Basic CPU Info # Detailed CPU information lscpu # Raw CPU data cat /proc/cpuinfo # CPU architecture uname -m What you get: CPU model, cores, threads, architecture (ARM, x86_64, RISC-V), frequency, cache sizes, flags (NEON, AVX, FPU).https://toorun.dev/posts/obd2-protocol-explained/Wed, 12 Aug 2026 10:00:00 +0000https://toorun.dev/posts/obd2-protocol-explained/What is OBD2? On-Board Diagnostics 2 (OBD2) is a standardized automotive diagnostic protocol that allows external devices to query and monitor the status of a vehicle’s engine control unit (ECU) and other subsystems. Every vehicle sold in the United States since 1996, and in the European Union since 2001, must have an OBD2 interface. Historical Context 1980s: Original OBD (OBD1) introduced with limited diagnostics and proprietary implementations per manufacturer 1996: U.