 and welcome back to the STM32 QBIT ADVANCE debug features video. Right now you're going to continue with our debug exploration or the serial wire debug session. So I'll just skip ahead and go to the QBIT with the very same code that we've been working so far. As you guys can see I'm back to the code editing perspective because I wanted to highlight a very unique feature that we're gonna explore on this session which is the printf. So there are a few calls throughout the code using the printf. As you guys can see I'm highlighting those right now and as I mentioned the printf is actually relying on the underscore right function and this function is using the itms and chart to actually print out the characters for us and this is going to be using the serial wire output to actually send the characters over and that's why I'm only allowed to use tx functions in this moment. So let's go ahead and enter in our debug session and now that we are back on the debug perspective I can go to window, show view, serial wire reviewer and this time I'm going to use the ITM data console. So right here is that the part that is being associated is the port zero and by entering on the settings we can actually see that the seamless port that is actually enabled is indeed the ITM port zero so that does make sense and I can just hit OK and I can start the trace. As we wouldn't expect as the code goes on for all those screens the messages are going to appear here for us but before we do that I just wanted to highlight another very useful feature which is the breakpoint. You all know that if I just add a double click here I can place a breakpoint and as the code moves into this direction the code is going to stop and I can use the breakpoint. What you may or may not know is that we can actually change the breakpoint to send us a dynamic printf as well and we can see the printf message that's going to appear. So I can just add this particular breakpoint here and instead of show the code stop through here it's going to send me information on the debugger console that this line has been achieved throughout the code execution. So I'm actually going to do both right now. I've already have my serial wire reviewer ITM data console logging information so the start trace is available and I can also see that the debugger console is also on. So by the time that I execute the code I do have this special breakpoint that I mentioned here so I expect to see a print message here and then I'll just switch to the tab. So as the code evolves I can actually see here same heatline 97 and we can see where it heated or that it is. I can actually edit the message that I want to appear when I go to the settings of this given breakpoint and I can switch then back and forth between regular breakpoint or just the dynamic printf breakpoint. So this is just a highlight information. What we are really here to validate right now is the serial wire reviewer and it's been going on for a while. We can see that our main loop is actually counting the value of our variable so we can see where we are in the values that are being plotted. I just paused the program and I also scrolled up into the very first message so we can see that even from the start along with the special breakpoint you can see both information being saved. These are two ways to use information on your debug console for printf when you don't have the serial wire reviewer at your disposal. You can use the serial wire output to just printf using the ITM. I hope you enjoyed playing with the printf's and see you guys on the next session where we are going to explore the final usage of the serial wire viewer. Thanks for watching and see you soon!