 So now we will measure the consumption while running the core mark. I will run the core mark at 24 MHz because this is the sweet spot of the microcontroller, where it performs best in terms of computational workload per unit of energy. And we'll also try to measure the consumed energy per one core mark iterations. And we'll do that thanks to the integrated power shield on the discovery board and cube monitor power running on a PC. You might be already aware of standalone power shield, which is an ST board that works as a power supply that also measures the current consumption dynamically. Now the power shield was integrated on the STM32L5 discovery, so we do not need any external components. The supply voltage can range from 1.8 to 3.3 volts. The measurement has a huge dynamic range from 300 nanoamps up to 150 milliamps, and it measures with sampling rate of 100 kHz. Before we start the measurement we need to do some adjustments on the board. Let's start by connecting a second USB cable to the connector on the left, which belongs to the power shield. Then we need to put the switch in the middle of the board to the left position in the position power shield measure. The last thing we need to change the jumper and put it in the position second from the left, the one with the label 5 volt PM underscore USB. In this configuration the target MCU is supplied by the power shield. So now I can go to cube monitor power and connect. I see the configuration tab, here I can set the sampling rate, so let's put it to the maximum 100 kHz. I set the acquisition time to infinity, so it will keep measuring until I press stop button. And let's supply the target with 3 volts voltage. So once I press the start acquisition, the target will be supplied and the microcontroller will start to execute. We still have the binary with the core mark running at 24 MHz. So let me start the acquisition. You see there was a short current peak to charge the decoupling capacitors that is now offsetting the y-axis. So let me stop the acquisition and start again. So you see the core mark finished just after I started the acquisition. So now the consumption is about half a milliamp. If I press the reset button and release, it will start to execute core mark and after about 11 seconds it will finish. It will reconfigure the clock to 4 MHz and that's why you see this sharp drop in consumption. So now what we can do is to show all the measurements and you clearly see this portion of the graph that is the microcontroller executing core mark. So what I can do, I can zoom in just approximately into this interval and I see here in the selected time frame there was 61 mJ consumed during this time. And we also know from the traces that the microcontroller executed 1100 iterations of core mark. So from that we can calculate the energy required per one core mark iteration or its inverse which is in fact the ULP mark CM score. If we plug in the numbers we get a ULP mark CM score of about 18 which is close enough to what we publish at the embassy website. Of course the accuracy of this measurement depends on how closely we can zoom in into the actual core mark execution. So this is only an approximate result. Here is another comparison of STM32 L5 and one of our competitor that is also based on Cortex M33. The conditions are the same, both microcontrollers are executing 1500 iterations of core mark. The VDD voltage is 3 volts and the code runs from flash. L5 runs at 80 MHz and the other device at 150 and as you remember from before they have the same performance level at those frequencies. From the ULP mark CM score it turns out that L5 is 16.9% more efficient.