How to debug power consumption (i)

How to debug power consumption (i)

Navigation Guidance and Control laboratory

January 01, 2015

This article begins to discuss the debugging steps and methods of power consumption.

The main contents of this article are as follows:

First, the goal of clear debugging

Second, clearly debug the content

Third, refer to the circuit diagram to find the output we need to detect

Iv. identifying or eliciting the output to be tested

Five, the Power test step flowchart

First, the goal of clear debugging

The goal of clear debugging, that is to meet the current requirements, the maximum possible to reduce the various states, the power consumption of each module. In general, the lower the power consumption requirements will be more stringent. For example: The battery of a device is 300mAh, Suppose a situation under the sleep power battery end is 0.8mA, another situation under the power of the battery is 1mA, obviously only a difference of 200uA (this state of the situation is more, it is possible that the state of the Gpio port is not correct, there may be peripheral leakage caused, there may be a problem with the power management configuration. The calculation can calculate the 0.8mA standby 375 hours, and 1mA standby 300 hours, the difference of 75 hours, which is very important for a device.

Second, clearly debug the content

In order to better debug the power consumption, we must make a concise and clear table to record our measurement results, in general, the content of the test table is almost the content of our testing;

Overview, including the need to debug 6 states and 5 circuit module power consumption, where

6 states are defined as:

First, the idle state after the boot (on the screen state, no operation, that is, the background almost no high CPU resource utilization process);

Second, turn off the display, but not the state of hibernation;

Thirdly, the state of entering the dormant process (early_suspend);

Third, completely into the state of hibernation;

Four, the completion of the state of the shutdown;

The other state (such as video playback, Bluetooth communication, WiFi connection, game running, etc.), this state is only used to evaluate the internal CPU module, or a specific peripheral operating power consumption.

5 circuit modules refer to the following:

Battery (battery-powered circuitry, which is the total power consumption of the device);

Cpu_core (circuitry powering the logic circuitry inside the processor);

Cpu_memory (circuitry powering the SDRAM (DDR) and the processor DDR PHY);

Vddio (for the processing of the Vddio and some processor internal peripheral controller, external peripheral power supply circuit);

Other peripherals, including all other peripherals, such as WiFi, Bluetooth, TP, and LCD, can be used to list a variety of debug conditions.

The content of the test can of course be based on the current situation for purposeful testing, for example, I am in the test is to do the table:

Note: If the data value of the test is correct, we also need to record the code version used in the test, the software resources used, the test time, the tester, and the frequency, FSB and so on.

Third, refer to the circuit diagram to find the output we need to detect

The framework diagram of Newton:

(1) Cpu_core Powered by OUT1 (1.2V);

(2) Cpu_mem powered by OUT2 (1.8V);

(4) OUT6 (3.3V) power supply to EVG;

(5) OUT9 (3.3V) and OUT17 (1.8V) power supply TP;

(6) OUT10 (1.8V) power supply to the mic;

(7) OUT11 (3.3V) power supply to sensor;

(8) OUT12 (3.3V) power supply to motor;

(9) OUT13 (3.3V) and OUT14 (1.8V) power the LCD;

(Ten) OUT16 (3.3V) power supply to sensors;

(one) OUT19 (1.8V) to power WiFi;

Then we understand the basic power supply of the whole board, thus measuring the current situation of each module.

Here we use regulator, but a lot of development boards or devices do not have regulator, then we have to get each module in the circuit diagram of the power supply situation.

Note: Like June Zheng's Newton Development Board is a regulator, in the board level we can see the simple configuration of regulator, there are some basic configuration, regulator parameter debugging is also a power consumption debugging, if the wood has, even if.

Iv. identifying or eliciting the output to be tested

1, the power side is relatively easy to measure;

2, other test points: we need to use Altium Designer, 99SE, DXP, pads and other tools to find easy to measure the point or the fly line, here is the way to save how to find the steps;

Let's start with the next step of testing.

How to debug power consumption (i)