 Now I'm going to provide you the demo of dual-core solutions, so STM32WL, LoraVan, and ZikVox on the same chip. So the coexistence is possible. What is skill-learning? I will show you how to cover both LoraVan and ZikVox protocol stack in one application. We'll show you the basic introduction to the software implementation and you will see the work in LoraVan and ZikVox application example in practice. This is another advantage of Sequencer, that it is really easy to combine more than one application process. So within the main loop, as you can see here, following the control variable stored in SRAM2, so the SRAM which can be preserved, the retention feature during the stop and standby mode. Following the control variable, the application can select the LoraVan process or ZikVox process. You can find the source code for this example within the folder given in the bottom of the slide. The flow is controlled by external interrupts, and we will use for that the user button. It is not reset button as you can see here. So following the button press, we are changing the control variable state, active application ZikVox, active application LoraVan. In order to place variable in SRAM2, we need to define no init variable. So here, you can see the excerpt of linker code below. It is GCC linker and here, you can see the definition of this variable within the source code. In order to show you the ZikVox activity, I will use the portable ZikVox base station only for development purpose. It is so-called SDR dongle and related to this hardware ZikVox network emulator. Regarding the resources, the memory footprint, the usage of the flash, it is a little bit higher than 50 percent. So still almost all second half to be used, and about 39 percent of the SRAM usage. Maybe I will show you live. So I need to start Qube IDE, then open projects from file system. You have this source code within your repository. So STM32WLWS, demo, LoraVan ZikVox projects, workload WL applications, LoraVan ZikVox sent on timer, and Qube ID subfolder. So finish and product is here. So applications for this, I will open the main.c. So here is the switch, following the control variable in main loop. I will build the application. So the application is flashed, and I will open terminal. Okay. Setup serial port 115 and reset. So now by default, ZikVox application is ready, and I will open ZikVox network emulator. It looks like this. So messages, this is the menu. You can see the messages. So the data are sent every 15 seconds from the board, and here are the data. So I received value 15 in hex, so it means 16 plus 521 Celsius degrees. And now I'm pressing the user button one, and now LoraVan application is ready. So it is joining to the network, and this application is already well known to you, because it sends, okay, the temperature is the same, 21 degrees. This application also shows the same temperature. And again, you can receive the downlink, increase the temperature because the threshold is 27 degrees. Then I can come back to the ZikVox by pressing user button one. So again, ZikVox application is ready, so we can follow the value on the screen here, then next frame is here. And again, 16 plus 5 gives us 21 degrees. This is a very simple example, because the context is not stored. So after switching back to the LoraVan, the node needs to rejoin to the network. Of course, it is possible to save the context of the session within the RAM memory. The purpose of this demo is more to show you that in terms of resources, in terms of the transceiver capability, it is possible to cover dual protocol use case in single core solution. So it means very low cost of the application. Of course, we can combine LoraVan and wireless Mbass, we can combine ZikVox and wireless Mbass. I cannot see an obstacle to combine two different protocols. The only condition for that is modulation must be supported by transceiver. That's all for today. Thank you.