AN12902

QN9090/QN9030 Power Consumption Analysis
Rev. 3 — 24 June 2022

1 Introduction
This document provides information about the power consumption of QN9090
wireless MCU, how the hardware is designed and optimized for low-power
operation, and how the software is configured to achieve the best low-power
profile. In this document, only QN9090 is mentioned but the measurements
apply to the complete family of products including QN9030, QN9090(T), and
QN9030(T). This document provides an overview and guidance on how toachieve the best low-power profile while still keeping the high performance ofthe system. The setup and the procedures to measure the current consumptionof the QN9090 chip are also described in this document.

Application Note

Contents
1
2
2.1
2.2
3

Introduction......................................1
Bluetooth Smart Power metrics.......1
Communication steps.................. 1
Bluetooth Low Energy events...... 2
Getting ready for low-power
measurement.................................. 3
3.1
Hardware configuration................3
3.2
Software configuration................. 6
4
Low-power results......................... 13
4.1
Low-Power modes..................... 13
4.2
Advertising mode....................... 14
4.3
Connect mode........................... 16
5
Conclusion.....................................20
6
Revision History............................ 20
Legal information.................................... 21

The power consumption of wireless devices is a critical requirement for the
fast-coming Internet of Things (IoT) world. As a result, the hardware has been
gradually improved and optimized from the power consumption perspective
and new communication standards have been developed. Bluetooth Smart®
also known as Bluetooth Low Energy (Bluetooth LE) is part of these new standards that have been developed for long-term
battery operation, typically years.
QN9090 is a radio wireless MCU that supports Bluetooth LE v5.0 protocol.

The prerequisites for understanding this document are that the reader has good knowledge about Bluetooth Smart protocol, as
well as basic knowledge about ARM MCU architecture, and radio communication basics.

2 Bluetooth Smart Power metrics
2.1 Communication steps
During Bluetooth Low Energy communication steps, both MCU and radio are in a different state at a different moment. They are
either in active, sleep, or deep sleep mode. The time spent in sleep/deep sleep is the longest compared to all other operation
modes as explained in the below figure.

Figure 1. Bluetooth Low Energy communication steps
1. The MCU is woken up and performs system initialization and pre-processing
2. The radio transceiver is woken up and ready to operate. The MCU may enter the STOP mode of the MCU if thesoftware allows it.
3. The radio transceiver is performing one or more RX/TX sequences

NXP Semiconductors
Bluetooth Smart Power metrics

4. The MCU is processing the received or transmitted packets
5. The radio transceiver is put back in sleep mode
6. The MCU enters low-power (sleep/deep sleep mode)

2.2 Bluetooth Low Energy events
Two events are considered during Bluetooth Low Energy (Bluetooth LE) communication. They are described in the following
sections and their power consumption is described in Advertising mode and Connect mode.

2.2.1 Advertising mode
All communications between two devices start from advertising events.
Devices can advertise for various reasons:–To broadcast promiscuously–To transmit signed data to a previously bonded device.
–To advertise their presence to a device wanting to connect.
–To reconnect asynchronously due to a local event.

Figure 2. Communication start process between two devices

2.2.2 Connect mode
Once a connection is established:• Master informs slave of hopping sequence and when to wake
• All subsequent transactions are performed in the 37 data channels (from channel 0 to channel 36)• Transactions can be encrypted• Both devices can go into deep sleep between transactions

Figure 3. Connection mode process between two devices• It occurs even when one (or both) sides have no data to send:

QN9090/QN9030 Power Consumption Analysis, Rev. 3, 24 June 2022
Application Note

2 / 23

NXP Semiconductors
Getting ready for low-power measurement— Occurs periodically— Slave devices can use slave latency, that is number of times it can ignore connection events from the master when
there is no data to transmit

3 Getting ready for low-power measurement
Specific applications software and hardware are used for the current measurements. The below sections describe how to set
the hardware and the software to set the device in different modes to perform the low-power measurement. All the low-power
measurements are done on the slave device. However, a master device will also be needed to perform measurements inconnected mode.

3.1 Hardware configuration
The power consumption is measured on an optimized DK6 board for low-power tests with the QN9090 module fitted as slave.
The master device is a DK6 board with a QN9090 module fitted. This board is available in the QN9090DK Development Kit. The
QN9090 module is plugged into the DK6 board (JM1/JM2) because of the mezzanine interface.
The slave device is a DK6 board that has been modified for low-power measurement as presented in the IoT-ZTB-DK006
Development Kit user guide UM11393. More details on the connection are described in the next chapter.
The test set-up block diagram is shown in the following figure.

Figure 4. Test setup block diagram for power profile measurement
The board configuration is as follows:
The current probe of the current analyzer (Keysight CX3322A for instance), in series with an external power supply, is connected
to J14 on pin 2.
From a supply standpoint VBAT = VDDTRGT.
A picture of the test connections is shown here:

QN9090/QN9030 Power Consumption Analysis, Rev. 3, 24 June 2022
Application Note

3 / 23

NXP Semiconductors
Getting ready for low-power measurement

Figure 5. Hardware connection for Low-power measurement (external power supply)
NOTE
Especially for the deep power-down currents, a power supply capable of measuring low currents such as Keysight
B2902A Source/Measure Unit is preferred to the current waveform analyzer. The test set-up block diagram isshown in the following figure.

Figure 6. Test setup block diagram for deep power-down currents with a Source/Measure Unit

3.1.1 QN9090 DC-DC converter modes
On both the devices, only the Buck mode is enabled.
More details can be found in the DC-DC guidelines application note AN12893.

3.1.2 QN9090 Low-Power modes
Power-Down currents from the data sheet are described below:
Table 1. Deep Power-Down and Power-Down modes
SymbolParameter

Conditions

IDD

SupplyDeep Power-Down (everything is powered off,current

wake-up on HW reset only)

Min

Typ

Max

Unit

-

250

-

nA

-

350

-

nA

-

800

-

nA

Deep Power-Down-IO (everything is powered
off, wake-up on HW reset only or an event on
any of the 22 GPIOs and NTAG interrupt)
Power-Down (wake-up on HW reset or an IO

Table continues on the next page...

QN9090/QN9030 Power Consumption Analysis, Rev. 3, 24 June 2022
Application Note

4 / 23

NXP Semiconductors
Getting ready for low-power measurement

Table 1. Deep Power-Down and Power-Down modes (continued)
SymbolParameter

Conditions

Min

Typ

Max

Unit

-

1025

-

nA

-

1120

-

nA

event, wake-up timer ON, 32 kHz FRO on, no
SRAM retention)
Power-Down-4K (wake-up on HW reset or an
IO event, wake-up timer on, 32 kHz FRO on,
with 4 KB SRAM retention)
Power-Down-8K (wake-up on HW reset or an
IO event, wake-up timer on, 32 kHz FRO on,
with 8 KB SRAM retention)
NOTE
Each additional 4 KB consumes around 105 nA.

On the slave device, the modes are selected when the User interface button (BP1) is pushed.

Figure 7. User interface button location
The user can evaluate low-power currents in the configurations described below by pressing the user interface button to navigate
from one state to the next.
Table 2. Low-power application modes
Button
press
0/

Mode

Corresponding data
sheet mode

Comments

Power-Down
mode

Power-Down (wake-up on
HW reset or an IO
event, wake-up timer ON,
32 kHz FRO on, no
SRAM retention).

Bluetooth LE device is in Power-Down mode where
all blocks are de-activated except the low-power
timer and QN9090 is waiting for an internal wake­
800 nAup event from its low-power timer or IO event (nomemory retention).

power
ON

Referencevalue @ 3 V

Table continues on the next page...
QN9090/QN9030 Power Consumption Analysis, Rev. 3, 24 June 2022
Application Note

5 / 23

NXP Semiconductors
Getting ready for low-power measurement

Table 2. Low-power application modes (continued)
Buttonpress

ModeCorresponding data
sheet mode

DPD-IO

Deep Power-Down-IO.
Everything is powered off,wake-up on HW reset onlyor an event on any of
the 22 GPIOs and NTAG
interrupt) (for QN9090(T)or QN9030(T))

1

Sleep
2

Bluetooth LE device is fully operational and able toreceive and transmit at any time.

-

Advertisingmode

4

350 nA

Device is in sleep mode where most of the blocks are 1 .9 mA
activated and SRAM content is maintained.

Rx IdleWARNING
The current
measure is
between two
advertising
eventsBluetooth LE device is in Deep Power-Down mode
where all blocks are de-activated and QN9090 is
waiting for an IO event (no memory retention).

Sleep mode Bluetooth LE
N/A

3

Referencevalue @ 3 V

Comments

Power-Down 36
KB (between
Advertising events)

2.4 mA(receiving or
ready toreceive, No TX)

Between two advertising events, the Bluetooth LE
device is in Power-Down mode where several blocks
are off except the low-power timer, and the SRAM
retention is at 36 KB to ensure a fast wake-up. Thismode can also be used between connection events.
NOTE
If time accuracy is requiredfor connection event wake up,
XTAL 32 kHz shall be usedinstead of FRO 32 kHz.

1.9 µA

3.2 Software configuration
3.2.1 Bluetooth Smart application configuration
The software is configured for two devices namely: Master and Slave. The slave is configured to advertise and then connect to themaster. The master is configured to scan and connect to the slave device. As mentioned before, all the low-power measurements
are done on the slave device. However, a master device will also be needed to achieve the measurements in connected mode.
This can be achieved in two ways:• By using a second DK6 board mounted with its corresponding QN9090 modules (available in QN9090DK) connected to
a computer.
• Or by using NXP IoT Toolbox mobile phone application.
Different configurations for the Master side will be detailed in chapter 3.2.2.2

3.2.2 Preparing the Slave software
The software can be uploaded from the SDK. The slave application is named QN9090dk6_power_profiling_bm. To upload thebin files to the master and slave devices, use a flash programmer. For the detailed instructions, see application note JN-SW-4407

QN9090/QN9030 Power Consumption Analysis, Rev. 3, 24 June 2022
Application Note

6 / 23

NXP Semiconductors
Getting ready for low-power measurementin the Tools folder of the SDK. To perform the power measurements, flash QN9090dk6_power_profiling_bm.bin must be on theslave device.

3.2.2.1 Software modification required to the power profiling projectTo achieve the power setting, the following changes are required to the power profiling project within the SDK. An explanation of
how to import the application is detailed in “Getting Started with MCUXpresso SDK for QN9090.pdf” delivered with the QN9090
SDK. Once the application is imported, the following files and changes are required prior to compiling and testing.

3.2.2.2 App_preinclude.h
Because the app only requires one button to switch from one power state to another, the following lines inside app_preinclude.hof the power profile project must be changed as follows:/* Defines the number of available keys for the keyboard module: counting buttons and TSI keys
#define gKBD_KeysCount_c
1*/

The LEDs that are detailed in this document show the mode that the device is in. The LEDs must be disabled to achieve thelow-power values detailed in this document. Therefore, the following line of code must be changed as below:/* Specifies the number of physical LEDs on the target board */#define gLEDsOnTargetBoardCnt_c0

The UART debug must be disabled and it is done by adding the following line of code:/* disable debug */#define SDK_DEBUGCONSOLE DEBUGCONSOLE_DISABLE

To prevent any compilation issue, you must remove the definition of SDK_DEBUGCONSOLE in the project settings by removing
the below preprocessor symbol:

Figure 8. Power profiling preprocessor settings

QN9090/QN9030 Power Consumption Analysis, Rev. 3, 24 June 2022
Application Note

7 / 23

NXP Semiconductors
Getting ready for low-power measurement

3.2.2.3 powerprofile.h
Average power consumption varies with the value of interval in both advertising and connection events. The less the interval is,
the higher the power consumption is. Interval tuning for a specific application is crucial to leverage between power consumption
and transaction time. Advertising interval can be adjusted by modifying the macro definition in the project file.
The advertising interval modification can be accomplished by changing values of macro definitions in file power_profiling.h ofthe power_profiling project. The default values are:#define gReducedPowerMinAdvInterval_c#define gReducedPowerMaxAdvInterval_c

1600 /* 1 s */4000 /* 2.5 s */By default, during the advertising interval, two macros do not share values, so that the Bluetooth LE controller can select a proper
one. To have a known and fixed interval, these two macros take the same value in the unit of 0.625 ms. In the case of a specified
500 ms interval, a value 800 = (500 ms / 0.625 ms) is set for the two macros. Therefore, the values must be changed to:#define gReducedPowerMinAdvInterval_c#define gReducedPowerMaxAdvInterval_c

1600 /* 1 s */1600 /* 1 s */3.2.2.4 powerprofile.c
In the file powerprofile.c of the power profile project, the following 2 lines of code must be added to confirm that the radio setting
is set to 0 dBm, as defined in board.h. The lines of code must be added after the function call to Bas_Start (&basServiceConfig).
/* Set power level - default in board.h but can be overwritten in app_preinclude.h */Gap_SetTxPowerLevel(gAdvertisingPowerLeveldBm_c, gTxPowerAdvChannel_c);
Gap_SetTxPowerLevel(gConnectPowerLeveldBm_c, gTxPowerConnChannel_c);

3.2.2.5 Gpio_pins.hChanges are only required within this file if the user is not using a DK6 board as the slave. In this example, the slave device is a
modified DK6 with a QN9090 module fitted which uses a user interface (GPIO 1) to change functionality. Therefore the following
must be changed, to represent a GPIO that is an input/button/switch on their designed board:#define BOARD_USER_BUTTON1_GPIO_PIN

1U

After all these needed modifications are done, the slave application is ready to be compiled and flash into the QN9090 module.
The next needed part is to configure the master device.

3.2.3 Preparing the Master software
As mentioned before, the master can be either a QN9090 module plugged into the DK6 board (JM1/JM2), properly configured,and connected to a laptop or a smartphone with the NXP IoT Toolbox application installed. In this chapter, we explain how to set
up and use both configurations.

3.2.3.1 QN9090 module acting as MasterTo use as QN9090 module as a master, the easiest solution is to use the QN9090dk6_ble_fsci_black_box_bm application. Thisapplication can be found in the SDK and must be flashed on the master device. It must be used with the Connectivity Qtool
application running on a laptop to control the master device. Connectivity Qtool can be downloaded from here.
1. Run Connectivity Qtool on the PC. The following screen should be displayed:

QN9090/QN9030 Power Consumption Analysis, Rev. 3, 24 June 2022
Application Note

8 / 23

NXP Semiconductors
Getting ready for low-power measurement

Figure 9. Master device communication port opening
2. Select the serial port of the master device and click Open.
3. A device address appears in the Devices window.

Figure 10. Master device address (example)
4. To start the scanning of the master device, select the device and click Start Scanning button.

QN9090/QN9030 Power Consumption Analysis, Rev. 3, 24 June 2022
Application Note

9 / 23

NXP Semiconductors
Getting ready for low-power measurement

Figure 11. Master device scanning start
5. If the slave is advertising (if not, press the user interface button on the slave device to start it), it should appear in the
Devices menu.

Figure 12. Slave device address (example)
Once the slave is scanned, scanning can be stopped with the Stop Scanning button in Qtool.
6. Select the slave device (left-click it) and set the connection parameter in the right panel. In our test, the connection interval
is set to 100 ms (80*1.25 ms)

QN9090/QN9030 Power Consumption Analysis, Rev. 3, 24 June 2022
Application Note

10 / 23

NXP Semiconductors
Getting ready for low-power measurement

Figure 13. Connection to the slave device

3.2.3.2 Smartphone acting as Master
Test set-up: A smartphone with IoT Toolbox application (available on Google® Play as well as on Apple® App Store) and the
QN9090 fitted on modified DK6 with the slave binary on the modified DK6 board as in chapters above.
The procedure is as follows:
1. Open the IoT toolbox application on your cell phone.
2. Select the Blood Pressure icon.
3. The cell phone automatically starts scanning for available slave devices.
4. On the slave device, press sequentially 4 times on the user interface button to go into advertising mode.
5. The cell phone detects the slave device. The following figure shows the cell phone app prior to connecting to the slave.

QN9090/QN9030 Power Consumption Analysis, Rev. 3, 24 June 2022
Application Note

11 / 23

NXP Semiconductors
Getting ready for low-power measurement

Figure 14. Screen capture of scanning step
The slave device is detected as ‘NXP_BPS’ in this example.
6. Click the NXP BPS device on your mobile application to connect to it.
When connected, the data is received and can be displayed as:

QN9090/QN9030 Power Consumption Analysis, Rev. 3, 24 June 2022
Application Note

12 / 23

NXP Semiconductors
Low-power results

Figure 15. Screen capture of connecting step
The measurements can be run on the slave device in the same way as with the QN9090 FSCI Black Box applicationas master.

4 Low-power results
4.1 Low-Power modes
Table 3. Low-Power modes
Button pressure #Reference values

Measurement @ 3 V

Unit

0 / power ON

800

890

nA

1

350

330

nA

2

1.90

2.201

mA

3

2.40

2.31

mA

4

1.90

1.80

µA

1. The current can be lowered a little without the Pull Up resistance (R47) and be closer to 1.90 mA

QN9090/QN9030 Power Consumption Analysis, Rev. 3, 24 June 2022
Application Note

13 / 23

NXP Semiconductors
Low-power results

4.2 Advertising mode
Device configuration:• TX output power: 0 dBm• RAM retention: 36 kB• Payload: 31 B
• Clock: 32 MHz
After pressing 4 times the user interface switch on the slave device, the advertising mode is launched as described in Table 2.
A sniffer is used to capture over-the-air communication. The following is an example:

Figure 16. Advertising sniffer log
At this point, the current can be measured. The waveform of the advertising event is as follows:

Figure 17. Advertising event

QN9090/QN9030 Power Consumption Analysis, Rev. 3, 24 June 2022
Application Note

14 / 23

NXP Semiconductors
Low-power results

The power profile is analyzed and the energy consumption can be measured at 6.288nAh under 3.0 V. The total event durationis 5.64 ms.

Figure 18. Advertising power profile
Table 4. Advertising break down table
Event

Duration

Current at 3 V-

1.80 µA

2. awakes from Power-Down mode

86.7 µs638.7 µA

3 to 6. Pre-processing

1.752 ms

311.2 µA to 3.085 mA

7. TX warm up

106.8 µs

5.561 mA

8. Active TX

314.9 µs8.750 mA

9 to 11. TX to RX

150.1 µs

4.439 mA

12. Active RX

123.0 µs

5.507 mA

13. Rx warm down

62.75 µs

3.592 mA

14. MCU STOP

572.3 µs

2.153 mA

15. TX Warm up

97.89 µs

5.620 mA

16. Active TX

316.3 μs

8.793 mA

17 to 19. TX to RX

150.6 μs

4.273 mA

20. Active RX

118.0 μs

5.565 mA

21. Rx warm down

70.28 μs

3.592 mA

1Power-Down mode[including stack and Radio initialization]

Table continues on the next page...

QN9090/QN9030 Power Consumption Analysis, Rev. 3, 24 June 2022
Application Note

15 / 23

NXP Semiconductors
Low-power results

Table 4. Advertising break down table (continued)
Event

Duration

Current at 3 V

22. MCU STOP

559.7 μs2.176 mA

23. TX Warm up

133.0 μs

5.732 mA

24. Active TX

311.2 μs

8.982 mA

25 to 27. TX to RX

150.6 µs

4.415 mA

28. Active RX

120.5 μs

5.652 mA

29. Rx warm down

52.71 µs

3.830 mA

30. Post processing

416.68 µs

2.271 mA

31. Power Down mode-

1.80 µA

NOTE
With a 48 MHz clock, the total energy is 5.603 nAh under 3.0 V.

4.3 Connect mode
Device configuration:• TX output power: 0 dBm• RAM retention: 36 kB• Payload: 0 B• Clock: 32 MHz
When the advertising is launched on the slave device, the scanning and connection on the master can be started as describedin QN9090 Low-Power modes.
The connect waveform is as follows:

Figure 19. Connect event

QN9090/QN9030 Power Consumption Analysis, Rev. 3, 24 June 2022
Application Note

16 / 23

NXP Semiconductors
Low-power results

Figure 20. Connect period 100 ms
Following is an example of a sniffer capture of a Connect event.
The first frame is a Link Layer Feature Request from the master device.

Figure 21. 1st Connect frame sniffer log

The slave corresponding packet response is as follows:

QN9090/QN9030 Power Consumption Analysis, Rev. 3, 24 June 2022
Application Note

17 / 23

NXP Semiconductors
Low-power results

Figure 22. 2nd Connect frame sniffer log
The master then responds to the slave feature request.

Figure 23. 3rd Connect frame sniffer log

And the slave responds to the master feature request.

QN9090/QN9030 Power Consumption Analysis, Rev. 3, 24 June 2022
Application Note

18 / 23

NXP Semiconductors
Low-power results

Figure 24. 4th Connect frame sniffer log
At this point, the devices are connected.
The power profile of the connect event is shown in the following figure, the total energy is 3.044 nAh under 3.0 V. The total event
duration is 3.299 ms.

Figure 25. Connect event power profile
Table 5. Connect event breakdown table
Event
1. Device in Power-Down mode
2 to 6. Pre-processing

Duration

Current at 3 V-

1.80 µA

2.019 ms

561 µA to 3.298 mA[including stack and Radio initialization]

Table continues on the next page...

QN9090/QN9030 Power Consumption Analysis, Rev. 3, 24 June 2022
Application Note

19 / 23

NXP Semiconductors
Conclusion

Table 5. Connect event breakdown table (continued)
Event

Duration

Current at 3 V

7. RX Warm up

115.1 µs

4.087 mA

8. Active RX

238.1 μs

6.269 mA

9 to 11. RX to TX transition

148.9 μs

5.468 mA

12. Active TX

48.81 μs8.310 mA

13 to 14.TX warm down

88.97 µs

4.989 mA

15 to 16. MCU Post-processing

1.061 ms

2.455 mA-

1.80 µA

17. SoC back to Power-Down mode

5 Conclusion
This application note provides an overview of how to evaluate the low-power current consumption on a QN9090 during Bluetooth
LE communication events. The measurements are done on an NXP QN9090DK development kit and can be replicated on thecustomer side. All the measurements are in line with the specification.

6 Revision History
Table 6. Revision history
Revision number

Date

Substantive changes

0

06/2020

Initial release1

07/2020

Latest NXP template2

31 May 2022

Sections 2.1, 3, 4 are updated, section 5
is removed.

3

24 June 2022

Figure 4 is updated, minor corrections

QN9090/QN9030 Power Consumption Analysis, Rev. 3, 24 June 2022
Application Note

20 / 23

NXP Semiconductors
Legal information

Legal information
Definitions

Applications — Applications that are described herein for any of these

Draft — A draft status on a document indicates that the content is still
under internal review and subject to formal approval, which may resultin modifications or additions. NXP Semiconductors does not give any
representations or warranties as to the accuracy or completeness of
information included in a draft version of a document and shall have no

products are for illustrative purposes only. NXP Semiconductors makes norepresentation or warranty that such applications will be suitable for the
specified use without further testing or modification.
Customers are responsible for the design and operation of their applications
and products using NXP Semiconductors products, and NXP Semiconductors

liability for the consequences of use of such information.

accepts no liability for any assistance with applications or customer productDisclaimers

products planned, as well as for the planned application and use of customer’s

Limited warranty and liability — Information in this document is believed

third party customer(s). Customers should provide appropriate design andto be accurate and reliable. However, NXP Semiconductors does not give

operating safeguards to minimize the risks associated with their applications

any representations or warranties, expressed or implied, as to the accuracy

and products.

or completeness of such information and shall have no liability for the

NXP Semiconductors does not accept any liability related to any default,

design. It is customer’s sole responsibility to determine whether the NXP
Semiconductors product is suitable and fit for the customer’s applications andconsequences of use of such information. NXP Semiconductors takes noresponsibility for the content in this document if provided by an information
source outside of NXP Semiconductors.

damage, costs or problem which is based on any weakness or default in thecustomer’s applications or products, or the application or use by customer’s
third party customer(s). Customer is responsible for doing all necessary testing

In no event shall NXP Semiconductors be liable for any indirect, incidental,

for the customer’s applications and products using NXP Semiconductors

punitive, special or consequential damages (including - without limitation -products in order to avoid a default of the applications and the products or of thelost profits, lost savings, business interruption, costs related to the removal orapplication or use by customer’s third party customer(s). NXP does not accept

replacement of any products or rework charges) whether or not such damages

any liability in this respect.

are based on tort (including negligence), warranty, breach of contract or any
other legal theory.
Notwithstanding any damages that customer might incur for any reason
whatsoever, NXP Semiconductors’ aggregate and cumulative liability towards
customer for the products described herein shall be limited in accordance with
the Terms and conditions of commercial sale of NXP Semiconductors.
Right to make changes — NXP Semiconductors reserves the right to makechanges to information published in this document, including without limitation
specifications and product descriptions, at any time and without notice. This
document supersedes and replaces all information supplied prior to the
publication hereof.

Terms and conditions of commercial sale — NXP Semiconductors products
are sold subject to the general terms and conditions of commercial sale,as published at http://www.nxp.com/profile/terms, unless otherwise agreed
in a valid written individual agreement. In case an individual agreement
is concluded only the terms and conditions of the respective agreement
shall apply. NXP Semiconductors hereby expressly objects to applying thecustomer’s general terms and conditions with regard to the purchase of NXP
Semiconductors products by customer.
Export control — This document as well as the item(s) described herein may besubject to export control regulations. Export might require a prior authorizationfrom competent authorities.

Suitability for use — NXP Semiconductors products are not designed,
authorized or warranted to be suitable for use in life support, life-criticalor safety-critical systems or equipment, nor in applications where failure or
malfunction of an NXP Semiconductors product can reasonably be expected
to result in personal injury, death or severe property or environmental damage.
NXP Semiconductors and its suppliers accept no liability for inclusion and/or
use of NXP Semiconductors products in such equipment or applications andtherefore such inclusion and/or use is at the customer’s own risk.

Suitability for use in non-automotive qualified products — Unless thisdata sheet expressly states that this specific NXP Semiconductors productis automotive qualified, the product is not suitable for automotive use.
It is neither qualified nor tested in accordance with automotive testingor application requirements. NXP Semiconductors accepts no liability forinclusion and/or use of non-automotive qualified products in automotive
equipment or applications.
In the event that customer uses the product for design-in and use in automotive
applications to automotive specifications and standards, customer (a) shall use
the product without NXP Semiconductors’ warranty of the product for suchautomotive applications, use and specifications, and (b) whenever customer
uses the product for automotive applications beyond NXP Semiconductors’
specifications such use shall be solely at customer’s own risk, and (c) customer
fully indemnifies NXP Semiconductors for any liability, damages or failed
product claims resulting from customer design and use of the product for
automotive applications beyond NXP Semiconductors’ standard warranty and
NXP Semiconductors’ product specifications.

QN9090/QN9030 Power Consumption Analysis, Rev. 3, 24 June 2022
Application Note

21 / 23

NXP Semiconductors
Legal information
Translations — A non-English (translated) version of a document, including
the legal information in that document, is for reference only. The English
version shall prevail in case of any discrepancy between the translated andEnglish versions.
Security — Customer understands that all NXP products may be subject tounidentified vulnerabilities or may support established security standards or
specifications with known limitations. Customer is responsible for the designand operation of its applications and products throughout their lifecycles
to reduce the effect of these vulnerabilities on customer’s applications
and products. Customer’s responsibility also extends to other open and/or
proprietary technologies supported by NXP products for use in customer’s
applications. NXP accepts no liability for any vulnerability. Customer should
regularly check security updates from NXP and follow up appropriately.
Customer shall select products with security features that best meet rules,

elQ — is a trademark of NXP B.V.
FeliCa — is a trademark of Sony Corporation.
Freescale — is a trademark of NXP B.V.
HITAG — is a trademark of NXP B.V.
ICODE and I-CODE — are trademarks of NXP B.V.
Immersiv3D — is a trademark of NXP B.V.
I2C-bus — logo is a trademark of NXP B.V.
Kinetis — is a trademark of NXP B.V.
Layerscape — is a trademark of NXP B.V.
Mantis — is a trademark of NXP B.V.
MIFARE — is a trademark of NXP B.V.

regulations, and standards of the intended application and make the

NTAG — is a trademark of NXP B.V.

ultimate design decisions regarding its products and is solely responsible

Processor Expert — is a trademark of NXP B.V.

for compliance with all legal, regulatory, and security related requirements
concerning its products, regardless of any information or support that may be

QorIQ — is a trademark of NXP B.V.

provided by NXP.

SafeAssure — is a trademark of NXP B.V.

NXP has a Product Security Incident Response Team (PSIRT) (reachable

SafeAssure — logo is a trademark of NXP B.V.

at PSIRT@nxp.com) that manages the investigation, reporting, and solution

Synopsys — Portions Copyright © 2021 Synopsys, Inc. Used with permission.

release to security vulnerabilities of NXP products.

All rights reserved.
Tower — is a trademark of NXP B.V.

Trademarks

UCODE — is a trademark of NXP B.V.

Notice: All referenced brands, product names, service names, andVortiQa — is a trademark of NXP B.V.

trademarks are the property of their respective owners.
NXP — wordmark and logo are trademarks of NXP B.V.
AMBA, Arm, Arm7, Arm7TDMI, Arm9, Arm11, Artisan, big.LITTLE, Cordio,
CoreLink, CoreSight, Cortex, DesignStart, DynamIQ, Jazelle, Keil, Mali,
Mbed, Mbed Enabled, NEON, POP, RealView, SecurCore, Socrates, Thumb,
TrustZone, ULINK, ULINK2, ULINK-ME, ULINK-PLUS, ULINKpro, μVision,
Versatile — are trademarks or registered trademarks of Arm Limited (or its
subsidiaries) in the US and/or elsewhere. The related technology may beprotected by any or all of patents, copyrights, designs and trade secrets. All
rights reserved.
Airfast — is a trademark of NXP B.V.
Bluetooth — the Bluetooth wordmark and logos are registered trademarks
owned by Bluetooth SIG, Inc. and any use of such marks by NXP
Semiconductors is under license.
Cadence — the Cadence logo, and the other Cadence marks found atwww.cadence.com/go/trademarks are trademarks or registered trademarks ofCadence Design Systems, Inc. All rights reserved worldwide.
CodeWarrior — is a trademark of NXP B.V.
ColdFire — is a trademark of NXP B.V.
ColdFire+ — is a trademark of NXP B.V.
EdgeLock — is a trademark of NXP B.V.
EdgeScale — is a trademark of NXP B.V.
EdgeVerse — is a trademark of NXP B.V.

QN9090/QN9030 Power Consumption Analysis, Rev. 3, 24 June 2022
Application Note

22 / 23

Please be aware that important notices concerning this document and the product(s) describedherein, have been included in section 'Legal information'.

© NXP B.V. 2022.

All rights reserved.

For more information, please visit: http://www.nxp.com
For sales office addresses, please send an email to: salesaddresses@nxp.com
Date of release: 24 June 2022
Document identifier: AN12902