 ADP0.5 activation. This will protect all the secure application or the secure mode. That means you can only connect with a debugger when your core is in non-secure. That means it executed a non-secure application. So what should you ensure before going in ADP0.5? To have a non-secure application that is executed. That means you need to have a secure application that lotion non-secure application. And in that way, the cortex will be in a non-secure mode and then you will be able to connect. So please double check with the return, press the reset button of your target and check the traces to ensure that you've got a non-secure application that's running before continuing. On that stone, we will activate ADP0.5, just one option byte, and you've got the step 8 batch to do it. And then we will see how we can configure in QBID the connection to debug the non-secure application. So first, I will press my reset button. Everything is fine. We can see that I've got a non-secure application running. So I activate ADP0.5, which has a reset. And if I press a reset button, nothing has changed. It's still working. So now we switch to QBID. I select the GFMApply non-secure and I will create a debug configuration for it. So debug as stm32.com.txtmccplaceplaceapplication. You can disable the order build. It's prevent trying to rebuild each time you want to debug. So we will save time to do this. It's not in the slide, but it's the tips. For the debugger tabs, we have to change the reset behavior because by default, the debugger connect under reset. That means you have a reset and then connect. But if it resets, by default, the Cortex-M33 with the zone enable we put in is secure mode. So you won't be able to connect. So we have to remove this parameter and set it to noun. That means we do some kind of auto-attach. If you don't do any reset, we just connect while the non-secure application is executing. In the startup tab, we have to remove the download and just load the symbol. Okay. If I apply and you hook it, so here it will directly load the debugging perspective. Now the debugger is connected. Nothing happened. We have to suspend to see where we are because we have not connected under reset. So we don't start at the main. Okay. And you can see we are in the non-secure application. If I resume and if I press the reset button of my board, we are just stop at the beginning of the secure application, the non-secure application, sorry, and then we can debug it. Just a little things to show you. If I try to check the SBSFU memory again, you can see now it's not zero, but comma, okay, question mark. And in fact, it's because we've got an additional level of protection. SBSFU is protected by the hide protect, which only shows on zero. And after we've got the HDP0.5, which protected from accessing any resources from the secure world. Okay. So just little tips. So if I come back to my presentation, so we experiment this together, please terminate your debug session and I forgot to do it. That's it. And it's okay. So what we have to do now is to remove the trace zone protection because, okay, we have finished our hands-on. Now we want to do a cleanup of the board. So the first thing will be to do a HDP regression. And we will do this by doing a trace zone regression also. That means we have to do a HDP regression to be able to do a trace zone regression. So we have a script to do this. It was a step nine. So we can say, okay, if we are doing this after it was the full cleanup of the board. In fact, no, because there is some other parameter that we can't reset right now. It was a secure boot address, but we will see after. So first let's remove the trace zone and the HDP regression, the HDP protection. So if I load the step nine, here we do a HDP regression. At the same time, we remove the trace zone. And it was the only way to remove trace zone. So now we have finished this hands-on. So we have learned how to compile and debug the TFM. We have seen how to activate and to use the HDP in the TFM context. And also we experiment how to debug a non-secure application with HDP 0.5.