It´s exciting to see that our friends at Sony Mobile Research and Incubation have released a desktop application called Otii, which supports our Power Profiler Kit.
The beta version of the Otii application is cross platform and runs on Windows, Linux, and macOS. It is straight forward to install and use with the Power Profiler Kit connected through a regular USB cable.
With Otii you get a nice tool for finding out what parts of your software that is the cause for certain power consumption related behaviors. Besides all the perks of customizing your PPK measurements as in nRF6707-SW, there are features such as sync between current measurements and UART debug logs from your nRF software. You can work with analysis in real time or with saved recordings, for example zooming in on certain parts of your test cycles and comparing it with previous recordings by overlaying them in the same graph. Otii complements the PC application provided by Nordic Semiconductor and is well worth a try. See some pictures of the user interfaces at the bottom of the blog post.
If you’d like to try the Otii application for Nordic Semiconductor Power Profiler Kit, you can download it from the Qoitech web site here:
More info about the power profiler kit.
Otii from Sony Mobile research.
PC application from Nordic
Thank you for your kind comments Narendra. If you have any more feedback or comments, don't hesitate to write to us on our forum accessible from the Help menu in the Otii application.
Using the RTT for the DUT would cause its debug unit to be powered on, which will cause few mA of current consumption always. In this case UART makes better sense, just need to switch off the UART peripheral after each log.
Many thanks to the developers at Sony for this multi-platform tool!!
You are of course right. I had the single Segger setup in mind.
We do not currently support the use of RTT logs in the otii application. If we see a demand we may consider introducing the feature into the application.
If someone doesn't mind a bit of development i can be done with current otii if you forward the RTT logs to a virtual serial port.
@Christer This limitation does not reside in the PPK design (firmware running on the hardware), but the software, and the usage of a single DK as communication interface. Our software does not use the multiAPI of the pynrfjprog since it didn't exist a while ago, but now that it does this should definitely be possible to support. By using the multiAPI, RTT can be utilised from several RTT sources, so if you have an external debugger you can do RTT transfers to both DUT and and the PPK.
That being said, we can also use two different RTT channels on the same RTT instance. One for current data, one for debugging.
RTT is lighter than UART on cpu and power so it may be a better option for some applications.
We can have 2 RTT interfaces one for the PPK and one for the application on the DK.
yes you do need to have a segger in addition to the segger on the DK but this should be possible.
The python interfaces on the PC allow for multiple RTTs so this is definitely in the realm of the possible. What do you feel ?