Debug and Profiling Guide#

Overview#

The HVRTOS Debug and Profiling Guide provides comprehensive documentation for debugging and profiling capabilities available in the Drive OS Hypervisor (HVRTOS). This guide covers all debug interfaces, profiling tools, and debugging methodologies for troubleshooting issues across different execution contexts including kernel, sidekick, processes, VMs, and secure vs non-secure worlds.

Audience#

This guide is intended for:

  • Developers working on HVRTOS kernel, processes, and VMs

  • Test Engineers debugging test failures and system issues

  • SQA Engineers validating system behavior and performance

  • External Customers using HVRTOS in their products

Documentation Structure#

Quick Reference#

Most Common Debug Tasks:

  • View system state: Use list command in debug server

  • Check CPU usage: Use top command in debug server

  • Check memory usage: Use mem command in debug server

  • View task context: Use vcpu <task_ID> command

  • Collect event traces: Use events <trace_ID> command

  • View violations: Use proc command to see max-proc-time violations

Feature Availability:

Capability

Deployment

Target Context

Profile

Debug Server

ccplex_non_secure

HV RTOS Process, VM, Hypervisor Kernel

dev_nsr, debug_sr

Event Tracing

ccplex_non_secure, ccplex_secure

HV/RTOS Process, VM, Sidekick, Hypervisor Kernel, Secure Kernel, Secure HV/RTOS Process

dev_nsr, debug_sr

VM Profiler

ccplex_non_secure

VM

dev_nsr, debug_sr

Boot Profiler

ccplex_non_secure

HV RTOS Process, VM, Hypervisor Kernel

All profiles

JTAG

ccplex_non_secure, ccplex_secure

HV/RTOS Process, VM, Sidekick, Hypervisor Kernel, Secure Kernel, Secure HV/RTOS Process, ATF

dev_nsr, debug_sr

For detailed information on each capability, see the corresponding sections in this guide.