 We can now switch to the logic analyzer view application is now running. Blue LED is blinking. We now press the user button. And we start to see the expected activity on I2C bus. We see five frames. Most important one are number three and number five. On number three, we see six bytes received. And on number five, we see the final six bytes received. We now want to check if our 12 bytes were correctly received via the MA using LP Bump. So we entered in the back section and we are now comparing the first and second group of six bytes received. As we can see, these are identical. So first six bytes receiving are filling buffer temp position from zero to five. And second group of six bytes is filling buffer temp position from six to eleven. So our DMA acquisition using LP Bump is working correctly. We are now going to measure power consumption using cube monitor power. We have now switched to cube monitor power. We have connected this nuclear power shield. We reset the target. We set one kilohertz as sample frequency and we start the acquisition. Broly D is blinking fast. I press the user button and we see MCU is going in stop two for 800 millisecond, which is exactly the time needed for I2C to transfer data. Average power consumption is only five microamps. These results is truly remarkable, especially if compared with solutions that do not have a P-BOMS assist system and typically need to wake up from stop to perform this kind of transfer. So we have easily beat our first ultra low power application using cube Mx and LP Bump tool configurator. We can now add more complexity by inserting a second cube into our application. Coming back to the purpose of our hands-on, we now have to implement the low power timer free triggered by low power timer one in order to generate a PWM in GPIO with a modulated duty cycle. Technically, this will be a new cube. It will be triggered by low power timer one and we will learn in circular loop. PWM functions two and three will be used to write auto-reload register and counter register via LPDMA to update duty cycle. In addition, we will also show how to debug an LP1 scenario in stop two. It's possible to configure free power alternate function output for debug purposes using cube Mx. These pins are CL-SLEEP, CD-STOP and SRD-STOP. CL-SLEEP and CS-STOP are showing the activity on CPU domain instead SRD-STOP is showing the state on SMARTRAN domain. In stop two, we expect to see CL-SLEEP and CS-STOP high and SRD-STOP toggling and going to zero in case of LPDMA transfer activity. Let's now go through the steps we did to add the second cube. As first thing, second cube will be mapped to channel one, so we change it and configure the channel one into link at least mode. And in power state, we added the free debug pins we just mentioned. Inside LP1 scenario and configuration, a second cube was added. It includes three functions, one for the start and two for updating the PWM. And these two functions will be put in circular mode. In pinoutting configuration, we simply configure low power timer free as an output assigning pin PC free. Now let's move to the logic analyzer to see the output that we get. We have initialized the logic analyzer, we press user button and we see the expected activity on I2C signals with fireframes for TX and RX. We observe that LP team free channel keeps on being modulated in circular loop. The bank pin stays high, meaning that there is activity in SMARTRAN domain and we are in stop two. SRD stop goes low during DMA transfer operations. It's important on the line that when buffer is filled, MCU comes back to run mode as we can see from the back signals that are becoming low. And also we can see that we are in run mode from the slow blinking of our LED. Even in run mode, the LPBAM system keeps on operating, modulating the PWM output of LP team free via LPDMA. This concludes our webinar. We saw that LPBAM is a unique functionality introduced into STM42U5 to achieve ultra low power consumption. And thanks to LPBAM peripherals can operate independently from software running on MCU. There's no need for CPU while performing tasks and all is based on DMA. We experienced that our QBMX helps the developer to abstract linked at least complexity by means of a very user friendly GUI for LPBAM scenario configuration. For additional information on LPBAM, STM42U5 and QBMX, you can refer to these resources available on ST.com. Thank you very much for your attention.