 Before starting to play and to build a Bluetooth low-energy application on the WBA55 Nuclear Board, let's take the opportunity to have a look about the product capabilities, the main asset and the associated ecosystem. So in this section, we'll go through the main product capabilities. So first of all, the Bluetooth low-energy features, the power and radio performances of the product, the extensive security feature set inherited from the powerful STM32 U5 series, as well as some hardware consideration demonstrating the boom flexibility and efficiency and of course going through the ecosystem which is there to leverage your software and hardware design. So first of all, let's have a look about the product ID card and the associated Bluetooth low-energy features. First of all, we are dealing here with a series, the STM32 WA5X series. The focus of the end zone and playing session will be based on the STM32 WA5 series, a chipset series which is SEMPS-based, which is power efficiency oriented. In the meantime, there is existing the STM32 WA52, which is LDO-based, which is a trade-off between power efficiency versus boom efficiency. Product are system-on-ship based on the single core M33 where you will run your application and the Bluetooth low-energy stack. The BLE stack is compliant to Bluetooth low-energy 5.4. So that means the product has been qualified, Bluetooth low-energy 5.4. On top of BLE, the product is capable to support other protocols such as ZigBee, Thread. Device is getting quite outstanding output power up to 10 dBm and some very good and aggressive figures in terms of power efficiency, 5.4 mA at 0 dBm typically. But we'll see later on in coming slides the result considering this in an overall use case. So device is targeting BLE, we are compliant 5.4, but we are supporting as well other protocol. Device is indeed certified 5.3, but features are, but device is full feature of 5.3. So this is always a trade-off and compromise in BLE landscape. You will get some chipset which are compliant to specification and so certified to the 5.4 while they are supporting only some feature of 5.3. House, STM32WBA, support the full feature of 5.3. So that means on top of the legacy 1 mA, we are supporting first long-range Coded Fee in order to increase the range. We are supporting the advertising extension feature with as well the periodic advertising. Device is capable to support the new coming audio use cases such as AuraCast and so we are supporting at stack level and at silicon level the Osochronous Channel. Of course our device is capable to work as a master and slave in the same time being able to sustain up to 20 link in the same time. And of course we are supporting some more let's say with an exotic feature from the BLE such as the gut caching and the power control which is quite a nice and efficient feature that allows to reduce dynamically the output power versus the quality link and so at the end it's a compromise to get a very good power efficiency. And of course our stack is always under let's say improvement on top of maturity we are adding features. New one coming will be periodic advertising with response that should let's say allow to cut the market of electronic shift level. For the one being in the past playing with our first BLE STM32, the STM32WB just a bit of word about the BLE API. Of course the STM32WB is a dual core. The STM32WBA is a single core with a new RFIP so an improvement of the existing WB. Both devices are so based on a differently clear. But at all stack level, at all BLE stack level the stack is the same. Of course the one on the WBA is getting more featured. But at the end the software API remains the same. So migrating from one to another one it's pretty efficient and flexible. So if you want to start from the dual core and migrate to the single core from BLE software application it's pretty efficient because the software API are almost the same. As we are dealing with a wireless product we have to consider two very strong features which are the radio performances and the power performances. First, RF performances. Our device STM32WBA45 is capable to get an output per up to 10 dBm. The RF sensitivity. The RF sensitivity is at minus 97 dBm at 1 Mbps. And so at the end this allows to get a quite outstanding dynamic range of 106 dB. So an overall budget link of 106 dB which is quite strong and that allows to get a very strong and robust connectivity. Now what I can achieve with 106 dB this is a good question and there is no magic answer. It really depends on the overall environment. So here I will really encourage you to go to the BLE web alliance website. Link is there. Open the Bluetooth range estimator tool. That will give you some, let's say, approximative range pending to your application constraints outdoor or indoor. And this is pretty nice in order to fill the things and to understand up to 10 dBm outdoor at 1 Mbps what is the range I can achieve. So RF performance is pretty aggressive with a budget link of 106 dB. This is maybe a chart you are familiar with if you are familiar with our STM32 product. As you can see our STM32 WBA5 X series and so the WBA55 is offering as well a wide range of power consumption scheme. And this is very efficient to really consume what application is really demanding. So for sure if you look at the chart and the figures extract from datasheet the STM32 WBA55 which is SMPS based will give some better performances. As we are dealing with Bluetooth low energies there is one key figures which is important. What is the sleep or let's say standby current that I am able to sustain while the RF operation is still ongoing? On WBA55 I would be able to sustain RF operation while my sleep current in between such RF operation will be 1.25 mAh. And so if we consider this standby current in an overall real application use case such as a beacon I would get some very quite good and aggressive figures. Let's consider a device which is advertising every 2 seconds 11 bytes at 0 dBm. In between those 2 seconds period I will so under into the standby mode at 1.25 mAh. In such use case my device will consume 5.5 mAh and so I will be able to get a beacon application running from years over basic salecon battery. So just keep in mind that on top of wide range of power scheme the standby current that allowed to sustain RF application is really key and efficient and at the end you will get very nice figures and being able to design peripheral application running on salecon battery for years. Okay power and RF which are some key features. The other key features of the STM32WBA series is the security features. Device has been built to design wireless application to design to build a secured application. Our product is so based on quite extensive functionality to protect your asset to protect your software IP to protect your hardware and at the end to protect your overall design. Device integrates the trustdom and we'll see later on which is a must to have and a key asset to be able to easily the secure part to the non-secure part. Some cryptographic accelerator in order to secure the link to secure your data. Active tamper with six active pairs of tamper pins to protect your hardware design and one of the most key element is the security assurance level. Our solution, our STM32WBA5 is CZIP level 335 and this is now not just a nice to have but will become almost a must to have looking at the ongoing and coming new regional certification. So our device has been certified CZIP level 3 and this is one of the strong feature of the product on top of the BLE capability. So it has been certified CZIP level 3 so this is mainly something that you will have to potentially reuse in front of certification lab but in regard of your application what you can do is our security built in let's say application. The trust zone, our device, our STM32WBA integrates the trust zone which is there to easily the trust to the untrust. Of course the RF stack will remain on the untrust part and you cannot move it to the trust part but you can easily move and put your code into the trust zone. How to do this? There is a dedicated wiki page where you will find a lot of input in order to be able to enable over STM32WBA or a BLE code example to trust zone. So already in phases how STM32 wiki page integrates a lot of input and part of it there is this powerful trust zone enabling over a BLE code example. Let's consider now some other features of the product more hardware oriented. First the flash access improvement. The STM32WBA integrates a flash manager in order to ensure synchronization between flash access request and RF activity. Access to the flash is always a constraint so let's say compromise when you have to deal with RF activity getting highest priority and your own application needs. Thanks to the flash manager your application just need to ask and request an access to the flash and the flash manager will give you access if there is no RF constraints on viewing. So this is efficient and transparent for your application. Just use it as it is and it will definitely ease your software design. Just a word in general and this was the case of our past series STM32WB time to erase a sector of 8 kilobytes is around 22 milliseconds and even more on some other competitors. Thanks to the flash technology integrated over the STM32WF5 time to erase is only 3.4 milliseconds. So at the end you can still for sure use the flash manager but we do not foresee any constraints in terms of flash application access and RF constraints and on top of the flash efficiency again the flash manager will ease the overall flash access synchronization and will ensure no RF links issue when your application will ask to erase a sector typically. So please use this flash manager in your application reuse our code example it will definitely ease and secure your application. Still on our side now let's have a look about the bomb cutter flexibility. Thanks to WBA5 series flexibility and integration you can reduce your overall PCB bomb. In first one of the critical pass and important parameter when dealing with RF devices is the filtering and matching. The WBA5x integrates a balloon offering at the end a single-ended RF output so you reduce the bomb. It also required a very limited number of matching and filtering components to ensure optimum performances but this will be detailed later on in the journey and you will see that you can still even improve. The STM32WBA series also includes HAC internal programmable capacitance so that's a low first during design phase to ease the overall HAC centering so the HAC which is needed to get and to make RF so it will allow and ease the HAC centering and tuning and of course as we are dealing with software load cap it will allow to reduce the bomb without the need to put some physical external load caps but again this is something that will be and phases and details in the hardware chapter. Another quite good important feature in regard of bomb cutter is the number of limited decoupling caps required. The number of decoupling caps required is also very limited making STM32WBA very efficient in terms of size and bomb. For example with the STM32WBA55 in QFN package it will just require 100 nanofarad for each supply pin so typical sticks and 3 bigger values so 4.7 micro farad on dedicated supply chain so at the end few decoupling caps again reducing the overall bomb. Finally the STM32WBA is providing a lot of flexibility so thanks to large package scalability but as well to the flexibility pending to your real focus power versus bomb you can use an external STM32K or use the internal one, the LSE as on phases at the beginning you can use a variant with SNPS if you want to achieve power efficiency or the LDU base and of course the device integrates a lot of peripherals. Ecosystem and we'll conclude with this as you know the STM32Ecosystem is quite strong powerful in order to design and this ecosystem has been enriched in order to design an RF application so first of all I assume you are all familiar with the powerful STM32Ecosystem the Qubemix that allow in few clicks to make the pinning and to enable and draft the initial skeleton code the QubedID to build and compile your application and the QubedProgramming on top of those ecosystem and we'll play with this ecosystem later on in the journey some dedicated tool has been enabled the Qubemix or RF which is here for hardware guys in order to make in few clicks some tests in order to check if the matching is a good one if the output power is a good one some nice and very good application at smartphone and now the capability to be able to do some air trace over the air so first of all the STM32Q monitor RF which is a nice tool that you just plug to your board or to your PCB over your art and that allow to directly send some command from your PC to your device so that allow to emulate some Bluetooth low energy application from your laptop so first it's really educative because you can play with the API without building, compiling, testing you just open the tool, test it, send the command and see how the device react so this is more than useful during design to understand the BLE features but for hardware guys to start to make some initial tests to understand if the PCB is behaving as expected in terms of sensitivity and in terms of power efficiency some smartphone apps which are more than useful and will play with so first of all the ST2 box which is a debug app and ok I will not comment here we will play with later on but this is something that is more than useful and allow to display all device around data coming allow to connect to ST device to enable the bonding to make some data rate test to enable the thermal grid over the air and we have as well some custom app which are more considered as demo app ok with some nice logo display in your cube moving and so on some temperature and so on typically this one might be a good starting point for you to start your own design because this one is available as Android and iOS in source code a new tool which has been let's say in the past months and which is available as well on the STM32 wiki page is the BLE sniffer this sniffer is based on the formal and old STM32WU55 which is a dual core solution that allow with specific firmware to make some air logs using Wireshark plugin you just need to get an STM32WU55 board for the link go to STM32 MC wiki page look at BLE sniffer you will find all the right instructions step by step to guide you to install first the Wireshark plugin and then to start to play and to see air logs and being able to debug some BLE communication ok what to keep in mind so first our STM32WU55 is full feature of BLE 5.3 is getting some very efficient power consumption especially when the BLE Bluetooth application is running some security add-on which is no more a nice to have but will become a must to have so trust on and the secure CCIP level 3 certification and then of course on top the whole ecosystem that will play with in the coming session in order to build a basic application but just before playing just remaining 5-10 minutes with my colleague Sébastien that will show you the way you can evaluate start to prototype your own application based on STM32WU55