 Hi everyone, I'm Benjamin from ST's microcontroller division and today we'll deal with our latest series, STM32WL Wireless Systemanship. As you will see, STM32WL mainly targets long-range communications. So, this presentation will be divided in four main parts. First of all, we'll deal with the general architecture of the platform and its overall integration, then we'll dive deeper in the block diagrams and even provide power data. In a third section, I will describe the advanced security features of the device and then we will conclude with a description of the protocol stacks and the whole ecosystem offer coming with STM32WL Systemanship. I hope you will enjoy this presentation, recorded from home. Let's do it! So, for more than 10 years, we've been hitting the market with our general-purpose microcontrollers portfolio, historically constituted of three main segments, virtual power MCUs, mainstream MCUs or high-performance ones. And in 2018, we released our first wireless product for 2.4 GHz application, STM32WB for Bluetooth, Thread or ZigBee, for example. And right now, we are releasing our latest STM32WL series, mainly targeting long-range communication. So, what is STM32WL series all about? Well, the first thing that you need to have in mind when talking about STM32WL is that everything is embedded on the same silicon die. That means an STM32L4 architectural basis, coming with its own ARM Cortex-M4 core and the overall peripherals, plus a second ARM Cortex-M0 core, and Lorraine-able sub-gigahertz multi-modulation radio IP. So, the fact that everything is embedded on the same silicon die makes STM32WL what we call a systemanship. So, let's review a bit the definition of a systemanship. If we have a look on what I call here the integration pyramid, well, we can figure out that up to now, all the lower implementation on the market have been done in a discrete way. For a PCB, it's quite simple. Basically, you have a standalone microcontroller and a standalone transceiver and the same piece of PCB. For a module, it's quite the same story, but everything or, I mean, these two packages are repackaged in a very tiny piece of PCB, making it a module. And for a system in package, you actually have one silicon die for the MCU and another silicon die for the standalone transceiver inside the same package. In the framework of WL, it's a totally different story because all the different parts, meaning the MCU parts, the peripherals and the transceiver part are embedded on the same silicon die. That's why STM32WL is the world's first and actually the sole Lora-enabled sub-gigards wireless systemanship on the market. So, if we have a look at the eight key points that makes a difference with WL, these are the following ones. First of all, I've already talked about the multi-modulation capability of the device, meaning that we have Lora capability, but also GFSK, GMSK and BPSK. And this is very important because that enables STM32WL to be compatible with many different protocols, such as Lora1, for example, SIGFOX, or also wireless mboos and actually many proprietary-based protocols or custom protocols. We also already talked about the massive integration that comes from the fact that it's a systemanship and such integration leads to massive cost savings for our end customers. I've described the dual core architecture of the device and you will see in this presentation that actually we have two different business lines, one which is entirely single core M4 core based and another business line, which is a dual core version. But the important point here is that it's fully open, meaning that our customers will always have the possibility to implement whatever they want inside WL in terms of firmware and protocol stack. I mentioned that it's based on the architectural basis on an L4 MCU, so that means that this platform is the ultra low power and it's actually ready for the internet of things because it comes with usual standard safety and security features, I would say, but also with advanced security features that are enabled through the dual core architecture and that I will describe also in this presentation, obviously. We have a large offer of packages from QFN up to BGE and you will see as well that we have many different part numbers depending on the number of modulation that you want to activate, for example, or depending on the flash size that you want to get. And then obviously, when we hit the market with the new silicon chip, we always provide a full ecosystem that comes with it and this will be described in this presentation too. Finally, we have our usual 10-year longevity commitment, meaning that whenever we hit the market with a part number, we commit in being able to sell the same part number for at least 10 years and usually such commitment is actually renewed every year, so it usually lasts much more than 10 years. So now that I've provided you with an overview of the architecture of the device and the main key points, let's dive deeper in the use cases and the block diagrams of the two product lines. Let's begin with the four modulation available in the device. As mentioned previously, there are LORRA, GFSK, GMSK and BPSK. So with LORRA modulation, obviously you can target LORRA1 use cases, LORRA1 being the protocol being standardized by the LORRA Alliance, but also with WL, if you want to, you can address LORRA-based proprietary protocol, okay, meaning proprietary protocols based on LORRA modulation. Also, with GFSK, GMSK and BPSK, you can target other protocols such as SICKFOX, for example. I think SICKFOX use BPSK for uplink and GFSK for downlink, or also wireless emboss. And actually, all these modulations can be used for whatever custom or proprietary protocol as well. If we have a look now at the block diagram of the first product line of STM32WL series, which is STM32WL-E, well, the first thing to say is that in that case, we have only one core TEX-M4 core inside with its own DSP instruction, and the frequency can go up to 48 megahertz. Of course, I will not detail all the blocks here, but rather highlight some of the most important ones. For example, in the red year AP, I've already expressed many times that we have four modulations available. We have a linear frequency range from 150 up to 960 megahertz, so that means that you can target whatever geographic area in the world that your use case needs or your geographic market needs. And we have as well two different output power, one which can go up to 15 dBm and another one which can go up to 22 dBm. The main difference in between these two power outputs is the power efficiency indeed. Both power outputs are programmable with 32 steps. So with 22 dBm output power, for example, you can use it at 15 dBm, but in such framework, if you want to target an application needing only 15 dBm max, then in that case, it's much better to use the 15 dBm power output because it's more power efficient. So for example, for the American power market, you will use a 22 dBm output power. Whereas for the European market, you will use the 15 dBm output power. Then also, it's good to mention that with only one external 32 megahertz crystal, you can actually synchronize both the radio part of the device and the MCU part of the device. Also, we have usual standard security features in the same way as what is available in our world general purpose microcontroller portfolio, meaning AES, True Random Number Generator, PCrup, standing here for our program called Readout Protection, or Temper Detection, for example. And as well, obviously, you have many of the peripherals that you're already very or really used to it if you are already an STM32 user. So now, if we have a look at the second product line being based on the STM32WL series, this is STM32WL5 series. And in that case, the first thing that you can observe is that here we actually have two cores, one cortex M4 core and the cortex M0 plus. So cortex M0 plus must be approached or seen as the core managing the advanced security of the device. Indeed, on such product line, there are advanced security features which are available only on this product line and which are not available on the single core architecture version, the one that I previously shown. In terms of advanced security features, then namely, we have, for example, the ability to isolate secure areas being based respectively on cortex M4 core and cortex M0 plus. We have what is called here as well key management services which enables our user to use a dedicated memory area in order to manage secure objects in a very safe and secure way. For example, you could store applicative keys, you could derivate new keys or sign and verify secure objects, for example. We have also secure firmware install or secure firmware update capability on the dual core version, secure boot as well, debug control, the ability to control your debug on cortex M4 core or cortex M0 plus. You can lock your boot in between cortex M4 or cortex M0 plus. And also we have up to six security domains. Of course, I will come back to this later on when I will describe in more details the advanced security features of the dual core product line. So if we have a look now at the portfolio of the device, we have two packages, one QFN48 pins, seven by seven millimeter and a BGS 73 pin, five by five millimeters. In the framework of QFN48 usage, then in that case, you can enable up to 29 GPIOs. But in such framework, your bill of material costs will be optimized because with QFN, you will be able to enable two layer PCBs. Whereas with BGE, you have much more flexibility because you can update or enable, sorry, up to 43 GPIOs. And the package footprint is actually more tiny. So you can observe on this diagram the two product lines that I mentioned previously. In light blue, you have the dual core version of the device. And in dark blue, you have the single core version of the device. The single core version of the device is available with three different sizes of flash for each package. And any part number that can be observed on such a block diagram is available with all the modulation activated, or you can also decide to acquire some part numbers where all the modulation are available, except lower modulation, depending on your bill of material cost targets. The STM32WL is definitely suitable to address a wide range of key vertical markets. You can actually see here a list of vertical markets as defined by the Leroy Alliance. So I talked, for example, about the multi-protocol capability for the utilities market and the linear frequency range 150 up to 960 megahertz, making this device suitable for any geographic market. For smart cities and buildings, well, the best sensitivity that can be achieved in the Lera framework with WL has been measured down to 148 dBm, which is extremely good, an excellent sensitivity for smart cities. For logistics, we have unique IDs inside this device. So 164-bit unique IDs and another 196-bit unique IDs. Very useful for traceability, for example. For industrial IoT, we have part numbers which are characterized up to 105 degrees Celsius. For smart agriculture, we guarantee that WL will be suitable for a link budget higher than 160 dB, for example, so a very long range can be achieved. And for smart homes, actually, we have features definitely improving the battery life of the device. You could see, for example, on the black diagram previously, that there's actually an embedded DC-DC inside the device. So, meaning that depending on your power consumption targets, you can decide to choose either the internal DOR, the embedded DC-DC, and also mixed signal features with ADC and DIC. Very useful for smart home use cases. So obviously, with ST-132WL, we have a massive integration, and the massive integration leads to cost savings for end users and for customers. It also simplifies and speeds up the time to market. And actually, the communication between the radio IP and the MCU is actually much less exposed, I would say, than in a standalone implementation being based on a standalone MCU plus a standalone transceiver. Obviously, the total size of the final PCB, which will be smaller as well. So all of this represents the main advantages in terms of integration related to ST-132WL series. So let's talk now about the flexible power scheme of the device. The first thing to observe on such table is the left column, where you can see a non-exhaustive list of the power modes. It's important to keep in mind that the set of peripherals and wake-up sources which are available depends on the power mode that you are currently using. For example, all the peripherals and wake-up sources will be available if you use a mode in between stop 1 up to run mode, whereas in stop 2 mode, for example, you will keep only a subset of peripherals which remains rich enough to serve your application needs. Now, in terms of RAM retention, basically it's possible to keep some RAM context or to have a RAM retention in all the modes except shutdown. And this is actually extremely important in order to keep your applicative context, for example. And the last column, the RF part, is here to show that the RF part of the device, meaning the radio part, will always be available in all the modes except shutdown. So that means that even if the MCU part of the device is in standby mode, the radio part of the device will still be able to transmit a receive protocol frame on the network of your choice. So let me provide now some more information or I would say figures about power consumption. If we assume that you are using your STM32WL in a full run mode, the first option that you can play with in order to optimize your power efficiency or your power consumption is to use either the embedded LDO or the embedded DC-DC that we saw previously on the block diagram. Then you can choose in between two voltage ranges, range one or range two, because there is actually a voltage scaling inside the device. You can also decide to stop your CPU clock and enter what is called slip mode. So in run, range one, range two and slip mode, you play basically with the performances of your device and you play also with the power efficiency and the dynamic power consumption. If now you want to optimize your static power consumption, you can enter stop one mode. For example, in stop one mode, you will actually stop the clock of the core supply of the device. If that's not enough in terms of optimization of static power consumption, you can decide to power off some support of the core supply. And in that case, you will enter stop two where, for example, you are able to achieve around one microamp as static power consumption. In standby mode and shutdown mode, you actually power off the whole core supply. The only difference in between these two modes is that in standby mode, you are still able to have RAM retention and thus applicative context if you need. And then the final mode that is mentioned here is mentioned as VBAT and it's actually how we call the backup domain where the backup domain is just a support of the circuit that can be, for example, powered with an external battery. And in such very tiny part of the device, you will keep only the RTC, real-time clock, the anti-temper detection, and finally 20 32-byte registers, for example, to keep very minor applicative context or information, for example. So if we want to compare now the differences in between all the stop modes, you can see that the wake up times in stop zero, stop one, stop two is actually very good. In stop zero, for example, we are able to achieve 2.2 microseconds. And in stop one mode, while lowering by a factor of approximately 100, the power consumption down to 4.55 microamps, we're still able to wake up the device in only 5 microseconds. If that's not enough, you can even lower down the power consumption down to 1 microamp with a stop two mode, while still being able to wake it up in 5.5 microseconds. Here it's very important to highlight that there is no impact on the wake up time from the embedded DC-DC. Usually it takes time to wake up a DC-DC, but there's a very cool architecture in STM32WL, which makes it able to wake up automatically in 5.5 microseconds, for example, in LDO mode. And whenever the DC-DC will be ready, then the device will automatically switch from LDO usage to DC-DC usage if that's what you want to do. So it's a very good way to be as power efficient as possible in a DC-DC usage framework. Also, in stop two mode, you can see here that there is only a subset of peripherals, which remains available, but it's still rich enough to serve whatever applicative needs that you might have. Now, in terms of RF performances, I want to really emphasize the fact that the RF performances will be as good as what you can get currently on the market for standalone transceivers in terms of TX, RX, in terms of sensitivity as well for both LARA and GFSK, for example. And also, let me remind that the STM32WL series is actually worldwide compatible. Indeed, there is a linear frequency range from 150 MHz up to 960 MHz, making it compatible with whatever geographic market in the world. And also, there is a dual output power that we're about to describe right now. Indeed, you can select either a low power output up to 15 dBm or a high power output up to 22 dBm. Both of these power outputs are actually programmable with 32 steps each, and the low power output is actually much more optimized in terms of power consumption. So if you target, for example, the European market, you will rather use the 15 dBm power output. For the American market or Chinese market, for example, respectively at 22 dBm or 17 dBm, then in that case, it will be necessary to use the high power output power. Also, you can decide to use the internal LDO or the internal DC-DC. If you want to optimize your power consumption and use the internal DC-DC, then you will just basically need an external self on your PCB. However, if you want to use only the internal LDO, then no external self will be needed, and then your bill of material cost will be slightly more optimized. Also, a very good piece of work from our application team is the fact that around STN32WL on your bill of material, there is no need to use a TC exhaust standing for temperature-compensated crystal oscillator in order to implement a LERA1 or SIGFOX application. Indeed, just a simple crystal oscillator will be OK, I mean a 32 MHz simple crystal oscillator will be OK, to guarantee the correct functioning of your LERA1 application or SIGFOX application, which here again lowers your bill of material cost. So very nice achievement here from our application teams. So now let's deal with advanced security features available in STN32WL series and also with STACs that will be available on ST.com. So we can have a look at the full list of safety features and security features that are available in STN32WL series. In dark blue you can see the features that are available in both the single core version of the device and the dual core version, whereas in light blue these are the features that are available only in the dual core versions. So let's focus on the light blue ones for now. First of all, we have secure hardware isolation in between the Cortex-M4 core and the Cortex-M0 plus, leading to six security domains that I will describe later on. Then we have what is called secure key management services. Also on the next slide I will describe this a bit more in details. We have also basically secure boot code protection, secure firmware installed and updates, boot selection, deeper control and also crypto libraries. So let's detail this a bit in the next slides. First of all, regarding the secure key management services, basically it's a dedicated memory area that user can use in order to store keys or objects, for example, but actually it's not only storage, it can be used for object or secure object management, meaning that users can create, update or delete secure objects, for example. SKMS benefits from AES encryption and decryption. It can also digest functions, sign or verify in an RSA framework and also obviously there is key generation possibilities and key derivations as well. Then on the right side we have secure firmware install or update. Both of them are useful when manufacturing is needed from an entrusted manufacturer, for example a subcontractor. Actually in the system flash memory of the STM32 WL there is the embedded secure firmware install and what we call the RSS standing for root security services. So this such secure firmware is programmed by ST microelectronics inside the WL during production and it's allowed the programming of the flash memory with the same interface than the one used by the embedded boot loader. So the embedded SFI and root security services can be used to load contents in secure and non-secure memory areas. Also we have what is called secure boot to ensure that our users can boot from the right memory locations and also to ensure that each application firmware can be authenticated before being executed. Finally we provide also crypto library benefiting from embedded hardware crypto accelerators inside the STM32 WL and obviously this library also provides many algorithms or cryptographic algorithms for further cryptographic needs. So basically we can say that inside STM32 WL security is present in every corner because regarding the memory for example we've already mentioned the fact that the system flash memory embeds secure firmware install firmware or root security services. Also we have up to six security domains that will be described a bit more later on through what we call memory privilege watermarking controlled by secure areas and finally we also have execution prevention regarding the SRAM. Regarding the peripherals actually some of them can be secured that's the case for AS, PKS standing for public key accelerator through random number generator. SPI 3 here stands for the SPI being used in between the cortex core and the radio part of the device so that means that the communication in between the radio of the device and the MCU part of the device can be encrypted. Also the DMA direct memory access channels can be secured as well and usually security is enabled by option bytes. Also in terms of debug we ensure that the debug for example the debug of the cortex M0 plus can be disabled by user option depending on the security needs of our customers. Also with the secure boot and the security mechanisms that I've just described we can implement what is called a chain of trust. Indeed the boot can be secured locked and protected against debug so that the next application step can be authenticated and certified then the subsequent execution steps can be trusted and this is what we call a chain of trust. Let's have a look now on an example of secure implementation. First of all here we can clearly see a secure hardware isolation in between the non-secure M4 core and the secure cortex M0 plus and then we can observe observe what is called privileged areas and unprivileged areas thanks to a mechanism called privilege is water marking. So with unprivileged non-secure privileged non-secure areas and unprivileged secure areas and finally privileged secure areas we have four security domains. Then we have hdpa standing for high protected area in sbsfu secure boot secure firmware update which could be here considered as a fifth security domain and finally you remember that in the system flash of the device we have the root security services and the secure firmware install firmware. Also here five peripherals have been secured namely the AES the true random number generator the SPI meaning that the communication in between the secure cortex M0 plus and the radio IP here is secured the channels of the DMA and the pkha here for public key accelerators. So the purpose of this slide is to provide an overview of what is feasible in terms of security settings regarding the security domain but also in terms of privileges and unprivileged settings. Okay so for example if we focus on this setting of the secure M0 plus so here the M0 plus is secure and privileged and we can see that M0 plus in such framework can access to all the memory regions that are controlled either by the M0 plus or the cortex M4 except the hide protection secure area which is the highest security domain. So now if we have a look at the for example cortex M4 non-secure privileged settings here we can see that in that way the cortex M4 can access only to the flash and RAM memory areas managed by the cortex M4 which is a big difference between because in the first case the cortex M0 plus could access to both the regions managed by the cortex M0 plus and the cortex M4 whereas the cortex M4 here can access only to the memory regions managed by the cortex M4. So of course you have many in-between configurations depending on your privileged settings and depending on your security domain and what is true for the settings of the cortex cores is also true for the configuration of the DMH channels. Here is another example of dual core firmware isolation so here the goal was to implement the wireless stack which could be Lora1 or Siegfox for example on the secure cortex M0 plus core of the STM32WL and to implement the applicative layer on the cortex M4 core. By doing so customers can actually lock their wireless stack and certify it on the cortex M0 plus core which is secured so that even if they push their devices unfilled and even if they need to update their applicative layers for example through over the update then they will be able to do so without paying for a re-certification cost because there is a total hardware isolation in between the wireless stack on the secure cortex M0 plus locked and secure and the applicative layers being updated on the non-secure cortex M4 core. So it's a very interesting feature here for customers who do not want to pay for re-certification costs each time they want to perform update of applicative layers. Just a very brief slide here to express that STM32WL customers will always keep full flexibility in their implementation meaning that the STM32WL platform is fully open the radio inside it is fully open and it's up to customers to decide whatever firmware they want to implement inside it and also to decide in between a standard implementation in terms of security or a full feature security implementation. So you have now understood that the STM32WL is fully IoT protection ready and let's review now a radio stack or application firmware update process. So first of all you need to observe the what is called here the active slot containing the current version of the firmware version 1.0 and that's this version that we want to substitute with version 2.0 through such firmware updates so let's do it. First of all we will receive a new firmware package over the air okay then this update will be launched by the Secure Cortex M0 plus then the authentication process will be done and if the signature matches the target signature then the process will be continued in case not obviously it will be aborted and the device will be reset and finally and only when the authentication has been done we can now update the firmware from the download slot to the active slot the firmware update process is now over and we are very glad to mention that in the framework of CubeWL package provided free of charge on ST.com we provide such mechanism through Secure Boot Secure firmware update and also through a source code of Lura1 firmware update over the air so it's very important for us to ensure that STM32WL is ready in front of many kinds of attacks whether there are software base or non-invasive ones and for many forms of hacking attacks or attacks we have actually counter measures that are based on many security and safety features that I've been described in the security section of this presentation so to sum up all these these security mechanisms and security features can be translated into customer benefits which are a very flexible security implementation we saw it with the dual core implementation for example but also with the single core implementation we have IP protection non-clonable device a true stability of the device and anti-hacking and finally a very trustable fleet maintenance so it's now time to talk about the different stacks that are available on ST.com first of all we have a Lura1 stack available free of charge in our firmware package called STM32 CubeWL well this Lura1 stack has been fully certified for all Lura1 regions first of all and the code is actually provided in source code format so that means that you can get this code reuse it tweak it if you need to no problem at all here again obviously up to you to implement your Lura1 stack in the single core version of STM32 WL series or in the dual core version we have also the SIGFOX stack available on ST.com as well free of charge and here again the SIGFOX stack has been fully certified for all SIGFOX radio configuration corresponding to geographic areas meaning from RC1 up to RC7 but we have also what is called the Monarch certification so in case you don't know what Monarch is basically it enables STM32 WL based devices to understand after wake-up the geographic area where they are currently based and adapt their frequency and power output to local regulations so it's a very good achievement here to have the full geographic certification and the Monarch certification for STM32 WL here again the stack is provided in an open way except the SIGFOX core library which by definition cannot be open of course but all the surrounding code is provided in an open way we also have a partnership with stack provider Stackforce who ported a wireless mbus stack on STM32 WL series so in case you have any wireless mbus need feel free to contact Stackforce and actually with their implementation you can actually be compatible with mode STCNM depending on the frequency that you need and depending on the wireless mbus mode that you actually need in your application and in stackforce implementation it's actually even cooler that just a wireless mbus implementation because you can actually replace the wireless mbus MAC and PHY by the Lura1 MAC in such framework you can get a wireless mbus implementation over Lura1 by the way before moving to the whole ecosystem presentation let me remind that in our own Lura1 stack available free of charge on st.com in our STM32 CUBE WL firmware package there is the example of a firmware update over the air implementation so such code which is actually provided in source code format is suitable for massive STM32 WL Fritz updates it's actually network server agnostic and has been demonstrated and validated on many different kind of network servers and is class B and class C compatible so feel free to enjoy this also in our firmware package STM32 CUBE WL available on ST.com let's now address the STM32 WL series whole ecosystem so maybe the first thing to mention before describing the ecosystem is that the STM32 WL series was released on the market in a mass market way in December 2020 so everything that is currently being described in this presentation is already available on the market meaning that you can already find some nuclear boards already available on various distributors websites for example but also the chips themselves I mean the STM32 WL chips are available through different pond numbers being currently sold by different distributors so let's have a look at what the STM32 WL ecosystem deals with first of all we can divide it in hardware ecosystem where we provide what we call a nuclear board for flexible prototyping then as always and in the same way as what we do with all our other general purpose microcontroller portfolio or other wireless microcontrollers we provide a set of tools that can be used concurrently with STM32 WL prototyping for example STM32 CUBE MX CUBE monitor CUBE programmer different IDEs and last but not least what we call STM32 CUBE WL which is actually a firmware package containing for example the hardware abstraction layer but also the utilities or the middleware meaning the different stacks so in STM32 CUBE WL firmware package you will find the lower one stack free of charge the sick folks types free of charge as well and basically that's it for wireless emboss as mentioned previously you need to contact Stackforce in such framework so let's assume you want to use an STM32 WL nuclear board for prototyping well in such framework you will be able to use the different tools provided in the ecosystem coming with the STM32 WL series for example STM32 CUBE MX where you will be able to configure the pinouts of your device then also you can work on the clock tree synthesis for example and CUBE MX will actually automatically generate some code for you to make your software development life much easier with STM32 CUBE programmer you will be able to flash your firmware in a very easy way in your device and with STM32 CUBE monitor you will actually be able to perform RF advanced testing I will detail this a bit more later on so what is the STM32 WL nuclear board all about well the first thing to mention is that there are actually two power number NUCLEO-WL55JC1 for high bund development and JC2 for low bund development meaning that for example with the high bund version of the NUCLEO board you can target development in Europe 868, America for example 915 or Asia 923 whereas with the low bund version of the NUCLEO board you can mainly target Chinese market 470 up to 510 megahertz actually but you can also use it with 433 megahertz development depending on the local regulations so what is that all about in terms of hardware well first of all we can observe an SMA connector when you can plug in the antenna of your choice then there are actually Arduino connectors so that you can connect shield boards or daughter boards on top of it coming from ST or from other communities then there is also obviously the STM32 WL usually under a metallic shield then through the integrated ST link you can actually flash your device in a mass storage way so very handy for your development and then you have two push buttons and two LEDs to make your developments much smoother and finally you can decide to power your board through USB or an external source so I've already mentioned when talking about lower one stack or SIGFOX stack that both of these stacks have been fully certified and actually the certification vehicle for such purpose was actually the NUCLEO board so you can be very confident in this board's ability to be used for whatever lower one development purpose or SIGFOX development purpose this board can actually be enabled on whatever lower one real network and that's also true if you want to enable it on SIGFOX network to do so on the real SIGFOX network you just need to follow the link that I provide here my.st.com slash sfxp also we passed the full commercial certification meaning C E F C C I C and type so you can be really confident that this NUCLEO board is a rock solid platform for your prototyping or development related to sub gigahertz use cases STM32 cube monitor is also a great tool in order to perform multi modulation command for example or perform different kind of sub gigahertz tests protocol tests such as lower one test CFOX tests etc and actually it can be used with the official NUCLEO boards but also with your own custom PCB through USB or your connection for example so this is a very flexible tool and useful tool to perform advanced testing of your sub gigahertz use cases so you have now understood the main software development path where you can use for example STM32 cube mix to start where you will be able to configure your pinout for example your clad tree synthesis and then you will generate code automatically you can use it concurrently with the IDE of your choice such as RAR or Armcal but also with our free of charge STM32 cube IDE software and then you can perform RF advanced testing with STM32 cube monitor to finally be able to flash your firmware in for example a NUCLEO board or also in your custom PCB if that's what you want to do so another way to sum this up is this one basically we provide tools for configuration cube mix cube IDE development STM32 cube IDE programming with a cube programmer and cube IDE again and monitoring through cube monitor the stacks as you have understood the row and stack SIGFOX stack are enabled and provided in STM32 cube WL and in the future we will also provide STM32 cube expansion for additional expansions and function packs so now that I've provided you with a full description of the chip itself and the whole ecosystem that comes with it we can have a final look at all the savings that will be triggered by the whole STM32 WL series offer first of all in terms of silicon well using an STM32 WL system and chip will mean a deep integration factor so that's actually the maximum integration that is feasible in order to have a sub gigahertz lora enable applications so in such framework instead of using two chips one for the microcontroller and another one for the intrinsiver you will be able to use only an STM32 WL and thus you will save money for this you will also be able to use less external components because we saw that for example with a single 32 megahertz crystal you can actually synchronize both the MCU part of the device but also the radio the embedded radio inside it so no more two 32 megahertz crystal on your PCB only one is enough then I also demonstrated that it's possible to use a simple 32 megahertz crystal instead of a temperature compensated crystal oscillator so that means you will save money with this as well and finally with QFN package you can enable two layers PCBs then in terms of ecosystem well it's pretty simple because first of all the two stacks that are provided on ST.com meaning Lora one stack in a source code format and sikfox stack almost fully open as well are provided free of charge both and all the tools that come with it are also provided free of charge either for configuration with kuben mix with monitoring with kubem monitor programming with kubem programmer or software development with kubed IDE everything is free of charge now one brief word about our STM32 rolling longevity commitment well basically with our 10-year longevity commitment we commit in being able to provide the same power number for at least 10 years and such commitment is actually renewed every year so it usually lasts much more than 10 years as you can see for example in this diagram with F1 which has been committed for more than 22 years now and it will be the case for WL as well at least 10 years of commitment renewed every year so let's finally review everything that we've learned through this presentation first of all STM32 WL series is a multi-modulation system and ship meaning lora gfsk gmsk and bpsk will enable you to implement whatever protocol that you want such as lora one sikfox wireless mbus for example or actually many other ones whether there are proprietary ones custom ones or standardized ones the STM32 WL series is a wireless system and ship with a maximum integration factor which will lead you to massive cost savings the platform itself is a dual core architecture with two different product lines one which is single core the other one being dual core and the device is actually fully open so it will be always up to device makers to decide whatever they want to implement inside it the device itself is a real ultra low power platform and is fully ready for the IoT thanks to different safety features security features and actually also advanced security features that we reviewed together then we saw that there are currently a qfn48 package and a bgs23 package with many different kinds of partner numbers depending on the modulation that you want to activate for example and depending on the flash size that you need then we review the whole ecosystem offer that comes with it so kube programmer for example kube monitor kube mx or kube wl firmware package all of these are great tools that will help you through your different developments and finally we just reviewed the 10-year longevity commitment for STM32 WL series so it's going to be time for me to tell you goodbye very soon but before doing so i would like to highlight some of the links provided here so first of all i would like to highlight obviously st.com slash STM32 WL well you will find many information about STM32 WL series such as the data sheets of the product the reference manuals of the two product lines single core and dual core and also many application notes that will really help you through your development so i really suggest that you have a look at the official webpage of the STM32 WL series then also i can talk briefly about the community where we have a very big STM32 users community so feel free to ask as many questions as you want here about STM32 WL or about any other STM32 devices and also of course feel free to explore all the other links provided here so thank you very much for attending this full presentation about the STM32 WL series goodbye