Not a software problem…

It must be admitted that for some types of SW development, the statement that energy consumption is not a software problem is true. By “not being a software problem” we mean that energy consumption either cannot be monitored easily, that certain methods of optimization are barely available or give low effect, or that monitoring and optimization add expenses that will never be returned. However, the statement is often mentioned where it actually is not true. There is no complete and impeccable method to determine how deep energy optimization can and should be performed for a particular product. Nevertheless, verifying your situation against the checklist below may lead to some interesting opportunities. Feedback is, as ever, greatly appreciated!

Again, software affects energy consumption, and the SW developer is as responsible for it as HW, mechanical, RF, and other engineers. So, energy optimization is on your task list IF:

1. HW is being developed within an arm’s length. If you do have access to pre-production prototypes, use them to see how your code affects system components and total consumption.
2. You have access to the configuration of the CPU and peripherals. The SW developer is then responsible for selecting appropriate power modes and timely switching between them.
3. SW architecture is designed in-house. Custom firmware, unlike a kernel or framework, does not need to be universal and can be well optimized for performance and low consumption.

If you are checking off all the criteria above, you’re most likely in a bare metal world. Welcome! Regardless, it’s time to get acquainted with benchtop multimeters, SMUs, oscilloscopes, or Otii Arc (of course)!

But even if you’re developing a custom app for a smartphone OEM (Original Equipment Manufacturer), it won’t hurt to request a breakdown board from the prototype workshop or ask for help to do this and verify your application.

Why do that? Well, not only for the obvious reasons to get happy customers, think and act sustainably, and lots of other noble ones… Do it because you can! You’re the master of the code. Do it because no one else can do it as well and as smooth as you. Simply do it!