This disclosure is related to integrated circuits and more specifically to the development of products using integrated circuits.
In general, engineers use development tools to design and test applications of integrated circuits in new products. For example, a typical development toolkit for wireless applications, e.g., Internet of Things (IoT) applications, includes hardware and software for configuring a target device and debugging software or firmware executing on the target device. The development toolkit includes a development board having a footprint for electrically and mechanically coupling to a target device under development. The footprint may provide electrical and communications interfaces directly to a target device held by the development board or indirectly to the target device via a separate printed circuit board that hosts the target device. An exemplary target device includes a System-on-a-Chip (SoC) having a radio frequency transceiver circuit, a simple, ultra low power microcontroller, and analog or digital peripherals. Separate printed circuit boards that are compatible with development hardware have the same footprint and couple to the development board at the same location but may include different components and different target devices for different products. The development board communicates with a host computing system (e.g., a laptop) using a conventional interface (e.g., USB interface). Software executing on the host computing system is available for configuration of the target device, downloading application code (e.g., firmware) to the target device, and debugging execution of the application software by the target device.
A conventional development system requires use of expensive stand-alone energy analyzers or lab bench instruments that measure current and voltage and compute power and energy consumption for analysis and provides little or no information regarding correlation of software events or execution steps with power consumption. Other conventional development systems include conventional energy profiler tools that execute software on a host computing system of a development toolkit and display energy consumption of the target device when powered based on a DC voltage received from a conventional interface (e.g., 5 V power supplied by USB connection). A conventional energy profiler integrated in a development kit improves correlation of software events or execution steps with power consumption as compared to energy profilers using external battery simulators or external current meters. The voltage provided to the target device by the development kit is a regulated DC voltage, i.e., a voltage provided by a low-dropout regulator or other voltage regulator that is interposed between a conventional power interface (e.g., USB) and the target device. However, the target device may be intended for a low power wireless application that sources energy from a battery (e.g., a coin cell battery that has a nominal voltage of 3 V) having performance characteristics that are different from the characteristics of a DC power supply. For example, a battery powered supply voltage signal includes variations (i.e., disturbances) due to ripple currents flowing through the equivalent series resistance (ESR) of the battery. Those variations are not considered when using a regulated voltage derived from a conventional power interface. Determining the power consumption of the target device when operating under conditions in a target application (e.g., battery-powered) is useful for determining battery life associated with a product including the target device and to determine how the target device behaves in response to the State Of Charge (SOC). The battery ESR and cell voltage vary and deviate from nominal values according to the SOC. Conventional development kits that use regulated voltages typically do not consider those variations in ESR and voltage. Accordingly, improved techniques for monitoring energy consumption of an integrated circuit device under development are desired.
In at least one embodiment, a method for developing a battery-powered integrated circuit product using a development system includes providing power to a load device from a battery using a first conductive node coupled to a first power supply terminal of the load device and a second conductive node coupled to a second power supply terminal of the load device. The method includes providing an indicator of power consumption of the load device while the power is being provided to the load device using a voltage across the first power supply terminal and the second power supply terminal equal to a voltage equivalent to a battery voltage of the battery coupled to a third conductive node and a fourth conductive node. Providing the indicator may include providing a bias voltage to the fourth conductive node and regulating a first voltage on the first conductive node according to the indicator and the bias voltage. The providing may include compensating for a voltage drop resulting from sensing the power consumption of the load device by regulating a voltage on the fourth conductive node based on the indicator.
In at least one embodiment, a development system includes a printed circuit board having a sensing circuit coupled to a first conductive node, a second conductive node, a third conductive node, and a fourth conductive node. The sensing circuit is configured to provide an indication of power consumed by a target device. The first conductive node is configured as a positive power supply terminal for the load device and the second conductive node is configured as a negative power supply terminal for the load device. The first conductive node and the second conductive node are configured to provide power to the load device from a battery. A voltage across the first conductive node and the second conductive node is equal to a voltage equivalent to a battery voltage of the battery. The sensing circuit may include a resistor having a first resistance, a first terminal, and a second terminal. The resistor may be coupled between the first conductive node and the third conductive node. The sensing circuit may further include an amplifier circuit having a non-inverting terminal coupled to the first terminal and an inverting terminal coupled to the second terminal.
In at least one embodiment, a development system includes a circuit configured to provide power sourced from a battery to a load device. The circuit is configured to provide an indication of a level of the power sourced from the battery to the load device using a voltage across the load device equal to a voltage equivalent to a battery voltage of the battery. The circuit may include a sensing element and an amplifier circuit. The sensing element may have a first resistance and may be coupled to a first battery terminal of the battery and a first load terminal of the load device. The amplifier circuit may have a non-inverting terminal coupled to a first sensing terminal of the sensing element and an inverting terminal coupled to a second sensing terminal of the sensing element. The circuit may include an additional resistor and a voltage regulator circuit. The additional resistor may have a second resistance coupled to a second battery terminal of the battery and a second load terminal of the load device. The second resistance may be equal to the first resistance. The voltage regulator circuit may be coupled to the second battery terminal of the battery and the second load terminal of the load device. The voltage regulator circuit and the additional resistor may be coupled in parallel. An output of the amplifier circuit may control the voltage regulator circuit.
The present invention may be better understood, and its numerous objects, features, and advantages made apparent to those skilled in the art by referencing the accompanying drawings.
The use of the same reference symbols in different drawings indicates similar or identical items.
Techniques for measuring energy consumption of a load device configured to source power from a battery in a target application are described. The techniques use a development board including sensing circuitry that compensates for a voltage drop caused by the sensing circuitry, thereby causing application of the battery voltage or a voltage equivalent to the battery voltage to the load device. The techniques provide application developers with information useful for developing software that reduces power consumption and extends battery life of the load device in a target application. Extension of battery life of the load device in the target application reduces waste and expenses associated with replacing batteries during the lifetime of the load device in the target application.
Referring to
In an embodiment, board controller 120 writes configuration information and firmware to target device 126 to configure target device 126 for a target application. In an embodiment, a user manually configures select circuit 122 to select between a power supply voltage regulated based on a DC power supply voltage provided by USB interface 130 or a voltage provided by battery 114. In other embodiments, board controller 120 configures select circuit 122 to select between a power supply voltage regulated based on a DC power supply voltage or a voltage provided by battery 114. In an embodiment of development system 100, board controller 120 programs current measurement and voltage regulation circuit 118 to change voltage VREG to a constant level in a predetermined range (e.g., 1.8 V-3.6 V) for powering target device 126 when select circuit 122 provides voltage VREG as voltage VMCU. When select circuit 122 is configured to provide power from battery 114 to target device 126, the power supplied to other circuits of development board 112 is unaffected. In at least one embodiment, board controller 120 executes firmware for use in debugging target device 126.
Development board 112 includes a printed circuit board having lands, i.e., conductive pads or conductive patterns to which components are attached, or other conductive structure to receive terminals of devices and a radio board, which holds a target device for development and associated circuitry, and couples those terminals to traces on the printed circuit board. In an embodiment, radio board 124 includes target device 126 that supports one or more wireless protocols (e.g., Bluetooth®, Matter, Zigbee, Thread, etc.) and is configured for an IoT application. Therefore, firmware executing on target device 126 should have very low-power operation (e.g., operation with an average current in a micro-Ampere range), which would allow target device 126 to operate using only power received from a coin cell battery for a substantial amount of time (e.g., years, in some applications).
In an exemplary application, target device 126 is configured as a door sensor in a burglar alarm and is powered by a coin cell battery. Development board 112 is used to develop firmware for target device 126 that causes target device 126 to have long battery life in the burglar alarm application, requiring infrequent or no maintenance. Therefore, target device 126 should be evaluated when sourcing power from the coin cell battery to determine battery life in that application and under each mode of operation associated with that application since different modes may consume different levels of operating current.
Referring to
Referring to
In
Referring to
Referring to
In another embodiment of a current-balanced battery current measurement, the current drawn by target device 126 is sensed at the negative terminal of battery 114, as illustrated in
Referring to
Thus, development system techniques for providing power information for a target device configured for a target application when the target device receives power sourced from a battery instead of a line power source are described. The techniques enable use of existing energy profiler tools operating on a host system to evaluate power consumption of the target device under all modes of the target application. The techniques improve battery life estimates used to develop low power configurations of target device 126 and reduce or eliminate the need for users to purchase expensive power analysis tools or bench-top lab instruments which do not communicate with the board controller or debugger.
The description of the invention set forth herein is illustrative and is not intended to limit the scope of the invention as set forth in the following claims. The terms “first,” “second,” “third,” and so forth, as used in the claims, unless otherwise clear by context, is to distinguish between different items in the claims and does not otherwise indicate or imply any order in time, location or quality. For example, “a first received signal,” “a second received signal,” does not indicate or imply that the first received signal occurs in time before the second received signal. Variations and modifications of the embodiments disclosed herein may be made based on the description set forth herein, without departing from the scope of the invention as set forth in the following claims.