 And here's a question from Cuba 667. Does the involvement in the Octo project will result in a new product line where a double MCU will be used in a single package? Where's the first MCU more powerful can run Linux and the second one RTOS? Real-time operations are still critical in some cases but the standard Linux kernel can't deliver the hard real-time capabilities that are a large number of embedded systems demand or maybe there is something much bigger planned like QNX. Hello, so I'm Gerard Baizard. I am the STM32MP1 software architect. So thanks for your question. This is a very good question with very pertinent assumption inside. So when this question was raised, you were not already aware that we were about to announce the STM32MP1. You can move on. So the STM32MP1 is the first MPU that extends the original non-STM32MCU family. In this processor, it is a heterogeneous architecture so you will find on the right Cortex-M4 running STM32Q. So this one can be dedicated to run some real-time applications. For instance, in this demo, it is used to control the water. We have all the external memories. The good thing is you have a Raspberry Pi on the left. On the diagram, you can see that this MPU embed also a dual Cortex-A7 that is running Linux. Our Linux distribution is called Poplan-STL Linux distribution and indeed, as you noticed, it is based on your project. So that is for the demonstration. If you want more information, you can use STM32MP1. So it would be easy to develop this? Yes. And it sounds that it could be complicated. There's two things going on at the same time. You have to manage, how do you manage? Yes, so we try to make it easy extending the STM32Q by mixed tool. Maybe we can have a look on it. So you do a mixed tool. There is now a panel with several contexts. And you can easily select to which execution context you want. You just say I want an A7 or I want an Cortex-M4. Exactly. And what's the one in the middle there? What is the difference between those two? A7NS is for A7 secure. Let's say it runs on. A7NS is for A7 non-secure. That is running Linux. And the Cortex-M4, of course, is for STM32Q. And is this thing you just choose? Yes, you choose and after you can generate the initialization code. So it will generate the STM32Q firmware as it used to do with the MCU. And for Linux side, we generate the device tree that is used for the product configuration. What is this? This is a pinout. So this is directly inherited from what we had in the past already in STM32Q by mixed. This way, the customer can easily choose a pinout and assign each pin to the function he wants on his product. Define each pin? Yeah. That's a deep level control. Yes. All right. You're welcome. Bye.