diff -r 578be2adaf3e -r 307f4279f433 Adaptation/GUID-C8DF0CB0-92F4-5F9E-A8F1-7DE50954C4F1.dita --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/Adaptation/GUID-C8DF0CB0-92F4-5F9E-A8F1-7DE50954C4F1.dita Fri Oct 15 14:32:18 2010 +0100 @@ -0,0 +1,37 @@ + + + + + +Debugging +the PRMThis document describes how to debug the PRM using internal macros. +
Purpose

Use the provided KTrace and BTrace macros +to debug your PRM implementation.

Introduction

These +kernel services allow you to generate and capture trace information in a manner +designed to minimise the impact on a running system.

+
Using KTrace

Use the KTRACE macro +with KRESMANAGER for debug print messages in the code.

__KTRACE_OPT(KRESMANAGER,Kern::Printf(">DH4PowerResourceController::DoInitController\n”))
+
Using the kernel +trace tool

The BTRACE category, TCategory::EResourceManager, +and a number of sub categories are defined and used to trace the progress +of all operations on the PRM. All tracing sub categories are wrapped with +a macro definition. Implement macro definitions in e32\include\drivers\rescontrol_trace.h to +replace BTrace with other tracing methods.

+ +Porting the +Power Resource Manager +Implement +the controllable power resources +Implement +the PSL for the target +Port client +drivers to use the PRM +Testing the +PRM PSL + \ No newline at end of file