 Good afternoon and welcome everyone. We are happy you were able to join us for this webinar on STM32, plus Type-C port protection for safe low-cost USB Type-C applications. During this one-hour webinar, you will learn how our STM32 and TCPP protection products make USB Type-C applications more robust and cost effective. In addition to offering many benefits such as reversibility, higher data rates and fast charging, USB Type-C connectors are being adopted to help meet environmental objectives through the reuse cables and adapters, thus reducing electronic waste while taking advantage of new use cases such as dual-role data DRD or dual-role power DRT. USB Type-C applications require careful power management designs safely comply with the latest USB-C power delivered 3.1 specification without compromising overall system cost. You will also discover how to design a cost-effective hardware application based on STM32G0, the first MCU in the world to integrate a power delivery controller associated with the Type-C port protection. TCPP device designed in ST's IEE milestone award winning bipolar CMOS BCD technology. My name is Adela and I will be the moderator for today's events. There will also be a live Q&A session at the end of the webinar where ST experts will be available to answer your questions. Now, before we start, I would like to go to some housekeeping information. You can expand your slide or maximize it to full screen by clicking on the top right corner. For the best-doing experience, we recommend using a wired internet connection and closing any programs or browser sessions that are running in the background. As webinars are bandwidth-intensive, closing any unnecessary browser tabs will help conserve your bandwidth. This webcast is being streamed to your computer, so there is no dial-in number. And for the best audio quality, please make sure your computer speakers or headset are turned on and the volume is up so you can hear the speakers. As some networks or slides advance for slower than others, turning off your VPN is recommended. And if your slides run behind, pushing a 5 on your keyboard will refresh the page. Additional answers to some common technical issues can be found under the health widget. And now, without further delay, I'll hand it over to our speaker. Hello, and welcome to STM32 plus TCPP protection for SAFE, low-cost USB Type-C applications webinar. My name is Mohammed Saadna. I am technical marketing for protection devices at ST Microelectronics and I am based in Tour France. And I am with Mathieu Ruvier from ST Microelectronics, System Engineering and Application Engineering, also based in Tour France. In this webinar, you will learn about how STM32 MCUs and TCPP protections are making your USB-C application more robust and cost-effective. Also, we will present hardware and software tools to help you kickstart your USB Type-C application. So let's have a look at the agenda for our webinar today. I will firstly present why STM32 plus TCPP is a perfect combo for USB-C applications in terms of cost. Then we will review the protection requirements for USB-C that are either required by the USB-C specification or by regulations or by experience. Mathieu will then introduce the different use cases that can be implemented and the corresponding hardware and software tools we have developed for you. We will end this webinar by our summary of online resources and examples so that you can easily start implementing your USB Type-C application. Let us start with the first part of our webinar related to the USB Type-C system partitioning. When designing an embedded application featuring USB Type-C connector, you would need basically a microcontroller as a core component to manage the digital and analog interfaces. Also, you will need an external USB Type-C controller to execute both the USB-C protocol and the associated high-voltage controls. These high-voltage controls are used to manage the load switch on the Vbus or Vicon power path. And finally, there are the required protections such as overvoltage, overcurrent or ESD protection. But that was before 2019. Since then, ST Microelectronics has introduced the STM32G0, the first MCU integrating the USB-C and power delivery protocol among other features. This means that you don't need anymore an external USB Type-C controller. And to make the system partitioning complete, ST has developed a new family of protection devices, the Type-C port protection or TCPP. The TCPP integrates the high-voltage controls and the protections in the same silicon die using a high-voltage technology called BCD technology. In the end, this system partitioning requires only two chips, and this is why STM32 plus TCPP enables cost-effective USB Type-C solutions. At ST Microelectronics, we have defined three TCPP products, each one corresponding to a major use case of the USB-C specification, sync, source and dual-rule power. Each of these TCPP provides a required protection feature set depending on the use case to allow a precise cost control of your USB-C implementation. Let's start on the right with the TCPP01M12 dedicated to sync applications. This is typically the protection for USB charging devices. TCPP01M12 is in mass production and widely available from ST Microelectronics official distributors worldwide. On the left, we have the TCPP02M18 dedicated for source applications, such as power adapters or USB hubs. It contains more features and high-voltage controls as defined in the USB-C power delivery. Finally, in the middle, the TCPP03M20 is tailored for high-voltage controls and protections of dual-rule power applications that use STM32 with built-in USB-C controllers, such as STM32G0, G4, L5 or U5. Dual-rule means that the application uses the same USB-C connector to act as a sync or as a source depending on the application that connects to it. Let's take the example of a power bank that would feature a unique USB-C connector that is DRP enabled here represented in the middle in blue. When nothing is connected to it and the system is active, the USB-C connector is acting as a DRP and is toggling between sync and source state. When the power bank is connected to a wall adapter to charge the battery, the USB-C connector of the power bank is then acting as a sync. Now, let's unplug the wall adapter and charge a smart speaker from the power bank. Now, the power bank is charging the smart speaker, so acting as a source. Here, we have all three TCPPs that are compliant with the latest USB-C power delivery specification 3.1 for standard power range and they are able to manage up to 100W contract negotiation. They are also compliant with the voltage levels of the programmable power supply feature to enable fast charging. TCPPO2 and TCPPO3 will be available from ST distributors in September. And now, Mathieu will present us the development tools. Thanks Manuel for this product introduction. Let me complete it with development tools on the STM32 ecosystem. Each STM32 family has a N64 board. These highly affordable STM32 nuclear boards allow anyone to try out new ideas and to quickly create prototypes with any STM32 MCU. On the left, you can see a nuclear board with a white screen. On top of the nuclear board, X nuclear boards can be plugged to extend the application hardware. Based on this principle, 3x nuclear boards can be plugged on top of any nuclear hiding type C connector and also green screw connector for power pass. One 2 SIM power and device data with TCPP01 and M12. One 2 source power and host data with TCPP02 and M18. One 4 dual roll power and dual roll data with TCPP03 and M20. Each board can be used according to the type C configuration. XNUCLEO SNK1 M1 and XNUCLEO SRC1 M1 can be used with any NUCLEO 64 boards for 5 volts up to 3 amps. NUCLEO with UCPD peripherals on STM32 allow power delivery feature up to 20 volts with 5 amps and programmable power supply PPS. Please note that power delivery is mandatory for dual roll power. Software is available on XCube TCPP package and also on GitHub. Now let's start the story from the beginning, the connector itself. We all observed that USB type C connector is gradually replacing all the legacy USB connectors. Indeed, USB type C connector is slim and slink tailored and is reversible plug orientation and cable direction. It's a convergence on a single connector. As example, power or data roll was previously defined by Mechanic. Type A for source, type B for sink. The design USB type C connector is much more complex because we are moving from legacy connector to 24 pin connector. It's simplifying the user experience, that's the challenge for the engineer. Previously, the power bus also named VABAS was always 5 volts on type A connectors. On type C connector, it's 0 volts before connection and it can rise up to 20 volts with USB power delivery protocol. Let's see how cable detection and orientation works in the USB type C. This electrical block diagram represents source to sink connection with the type C cable. On the cable, four lines are used in this process, the power bus, VABAS, the configuration channel, CC lines, array indicates to the source to turn on vacant voltage, effective cable and ground. By default, the bus is not powered, it's a cold plug. At connection, the configuration channel is used to solve plug orientation using CC1 or CC2 lines of the connector. It's highlighted in yellow. Source is identified by pull up resistor and voltage source on its CC pins. Sink is identified by pull down resistor on CC pins. To rephrase, a CC line voltage change due to pull down resistor connection to pull up resistor indicates source to sink connection. VABAS is then turned on at 5 volts, as well as VCON 1 array is connected to the other CC pins. Source also indicates its 5 volt current capability. Legacy 0.5 amps with 56 kilo ohm resistor, 1.5 amps with 22 kilo ohm resistor and 3 amps with 10 kilo ohm resistors. Then, voltage on 5.1 kilo ohm pull down resistor of sink CC lines gives the current source capability at 5 volts to the sink. When the cable is removed from the receptacle, the source must activate a discharge pass for the VABAS and on VCON in order to ensure a cold plug. We've just seen how a detach orientation sink and source detection is done, but only at 5 volts up to 3 amps. That limits the power to 15 watts. Thanks to the USB power delivery protocol with a numerical communication on CC lines, it is possible to increase power up to 100 watts with a negotiation between sink and source. Before showing the capabilities of the USB-C power delivery, let's place on the source power rating graphics the 5 volt red line with USB 2.5 watts, USB 3.4.5 watts for adapter. This power can be increased to 7.5 watts by shorting data lines. It's USB BC or battery charging 1.2. On USB-C only, 1.5 amps and 3 amps source capability indicated by pull down resistors are also reported in gray on the 5 volt red line. USB power delivery allows voltage increase with 4 fixed power data objects, PDOs, 5 volts, 9 volts, 15 volts and 20 volts. For current lower than 3 amps, standard cable can be used, while an electronically marked cable is mandatory between 3 and 5 amps. I'll let Mohammed present you protection and system recommend for USB-C. Thank you, Mathieu. So now let's review USB Type-C protection requirements. Here are the three main hazards that can damage your USB-C device. First, an ESD event that can destroy integrated circuits. Second, a defective adapter that can provide a DC voltage higher than the one negotiated with the sink. Or a defective load that can sink a higher current than expected. And finally, a short circuit can happen between Vbus and adjacent pins. First, let's review the electrostatic discharge also known as ESD. The metallic pins of the USB-C connector are an entry path to ESD. And this can cause reliability issues or even destroy ICs in your system. This picture on the right shows one of the potential consequences of an ESD event called a melting flash. The most reliable way to protect against ESD is to implement an ESD protection rated for IEC 61000-4-2 standard. Our three TCPPs are compliant with this IEC 61000-4-2 standard, integrating ESD protections up to plus or minus 8 kV contact discharge, which complies with the highest level of protection, the level 4 of the standard IEC 61000-4-2. Second danger is defective source. Let's take an example of defective charger. If this charger has been used at 20V and now due to software or defective hardware, Vbus is now stuck at 20V. When you connect this defective charger to a sink, even if the sink requests 5V, the charger will deliver 20V without negotiation with the sink. It will damage the power management circuit of the sink application. Many examples of VCU are available online, especially due to poor quality cables or adapters. This highlights the requirement for protecting USB-C applications. On the right, for instance, there is a story where the security researchers were able to infect a variety of fast chargers with malicious code to deliver more voltage than the connected device could handle. This caused the components inside the affected electronics to spark and finally melt. A protection is also required against defective sink. Indeed, an overcurrent protection is required for any source application. For example, if a short circuit happens on a power sinking device, this will generate an overcurrent on Vbus. And this is clearly specified in the USB Type-C specification, saying that a source shall protect itself from a sink that draws current in excess. Finally, an overvoltage protection is required on CC lines to protect against a short to Vbus event. This may occur when a user plugs or unplugged the USB-C cable. For instance, as shown on this picture, Vbus could get shorted to those adjacent pins such as CC or SBU pins. And even though the USB-C cable is more reliable than the previous micro USB connector, it can still be twisted, which might generate a short circuit, especially if it is a low quality cable or connector. On top of protection features, you have to consider specific features of the USB Type-C specification. First one is a control drive time on the load switch. For this, you will need a gate driver for N-Channel MOSFETs. N-Channel MOSFETs are usually preferred over PMOS thanks to their lower DRS on and they are also cheaper and smaller, but they require a charge pump for their control. Also, the USB-C is a cold socket, meaning that Vbus and Vcon must be discharged when the USB-C connection is lost. The Vcon pin being the CC pin that is not used for communication, you must integrate a switch matrix for this purpose. And finally, the programmable power supply requires current monitoring, so an analog current sense must be implemented. All these features are making the development of USB-C applications quite complex. However, the STM32 plus TCP-P approach is simplifying the USB-C implementation, because the STM32 with built-in UCPD takes care of the USB-C protocol and the software of your application, and on the other hand, the TCP-P integrates all these required high voltage features and protections. On top of STM32-G0, UCPD is now proliferating into other STM32 series such as STM32-J4, STM32-L5, and now STM32-U5. So you can select your USB Type-C power delivery MCU within a list of 332 part numbers, depending on the required peripherals of your application. Here is the table summarizing the TCP-P product features according to their use case. For a sync application, the features and protections are plus or minus 8 kV contact discharge ESD protection on CC lines, as well as OVP on CC lines. On VBus, a gate driver with charge pump for N and channel MOSFET is integrated to enable the overvoltage protection. When a protection is triggered on the TCP-P1, an open drain flag is activated. For source applications, the TCP-P02 re-use TCP-P01 features and adds an overcurrent protection as well as an analog current sense and discharge path for VBus and VCON. The communication with the MCU is done via an I2C interface. Please note that a source shall not present dead batteries resistors. Then, for dual role power applications, the TCP-P03-M20 uses features that are common to both source and sync. Now, Matcher will present you the hardware tools associated with these free use cases. In this section, I will present you application cases with associated development tools. The first development tool is for sync, with X-Nucleo SNK1-M1 plugged on top of N64 board. It can offer USB-C power delivery sync up to 100W and it has been certified by USB IF. With an STM32 with UCPD peripheral on N64 board, it is possible to realize USB PD sync up to 20V, 5A and programmable power supply. USB data 2.0 are also supported. All protection features are realized on the X-Nucleo SNK1-M1, an all-use line of the USB-C connector. VBus surges and overvoltage protection, CC lines ESD and overvoltage protection, D-plus and D-minus data lines, ESD and EMI filtering. TCPP-01 M12 also embed an over-temperature protection. Dead batteries are managed to start when battery is empty and the power consumption is optimized according to the use case. There is no consumption when unattached. With an STM32 without UCPD peripheral on N64 board, it is possible to realize USB sync up to 5V, 3A. USB data 2.0 are also supported. Like previously, all protection and specific features are realized on the X-Nucleo SNK1-M1 on all-use lines of the USB-C connector. To change X-Nucleo SNK1-M1 configuration from 5V only to power delivery, only two jumper positions must be changed. To supply the whole system by VBus coming from the Type-C connector, only two jumper positions must be changed. The over-betrigger voltage can be adjusted with a solder bridge table according to the consumer pass absolute max rating connecting the green screw connector. The second development tool is for source, with X-Nucleo SRC1-M1 plugged on top of N64 board. It can offer USB-C power delivery source up to 100W and it will be available on Q4 2021. With an STM32 that embeds UCPD peripheral on N64 board, it is possible to realize a USB PD source up to 20V, 5A and programmable power supply. USB data 2.0 are also supported. All protection features are realized on the X-Nucleo SRC1-M1 on all-use lines of the USB-C connector. VBus searches and overcurrent protection. CC lines is the overvoltage and overcurrent protection. D-plus and D-minus data lines is the NEMI filtering. DCP-P02-M18 also embeds over-temperature protection. Specific overvoltage features for VBus are NMOS gate driver for load switch, discharge pass and analog current sensor. V-con switch matrix and discharge pass are also available. The power consumption is optimized according to the use case with less than 11 microamps when unattached. With an STM32 without UCPD peripheral on N64 board, it is possible to realize a USB source up to 5V, 3A. USB data 2.0 are also supported. Like previously, all protections and specific features are realized on X-Nucleo SRC1-M1 on all-use lines of the USB-C connector. To change X-Nucleo SRC1-M1 configuration from 5V only to power delivery only to jumper positions must be changed. To supply the whole system by source-connected green screw connector only to jumpers to add. The 5V current source capability can be adjusted with a solid bridge table. The last development tool is for USB dual-role power with X-Nucleo DRP1-M1 plugged on top of N64 board. It can offer USB-C power delivery DRP up to 100W. Certification has been submitted to USB IF. A STM32 that embeds UCPD peripheral on N64 board is required to manage power delivery. The solution offers USB PDDRP up to 20V, 5A and programmable power supply. USB data 2.0 are also supported. All protections and specific features presented on X-Nucleo SNK1-M1 and X-Nucleo SRC1-M1 are present on X-Nucleo DRP1-M1. Indeed, there is a toggling between zinc and source when the DRP is used. To supply the whole system by V-Bus coming from the Type-C connector or by source voltage coming from the green screw connector, only two jumpers need to be added. The OVP trigger voltage can be adjusted with a solid bridge table according to the consumer pass absolute maximum rating connected to the green screw connector. These three X-Nucleo boards are a part of STM32 USB-C development ecosystem. They can be plugged on top of any N64 boards for 5V zinc and source. If power delivery is required for higher voltage, PPS or DRP, then UCPD peripheral is required on the STM32 of the N64 board. STM32 G071B Disco board is a complete USB-C sniffer. It is intended for discovery and display of USB-C port characteristics such as data roll, power roll, V-Bus, voltage and current monitoring. STM32 Cubemix and also STM32 Cubideo are free and integrated development environment for STM32. They can be used for STM32 configuration and programming. To finish, STM32 Q-Monitor UCPD is a software tool to configure and monitor the USB Type-C power delivery boards on equipped STM32 boards. The configuring part allows the modification of the USB Type-C power delivery port default configuration. Check of power delivery contract establishment and activity are possible with the monitoring tool. We have summarized in this slide all the resources and tools to help you kickstart your USB Type-C application with STM32 and TCPP. You may start with video tutorials on YouTube and then look for advanced informations in our application notes or web pages. To easily start your project, I invite you to check the exNucleo SNK1M1 page and download the associated software on Xcube TCPP web page. At any time in your project development, we can support you on the ST Community Forum. In conclusion, taking advantage of STM32 and TCPP offers cost efficient systems with optimized power consumption, a wide offer of STM32 MCUs expanding with more UCPD based STM32 in the future and a safe and easy way to add innovative USB Type-C and power delivery features thanks to TCPP Nucleo expansion boards within STM32 development ecosystems. Thank you. Great presentation. We are now ready for our Q&A session. So let's begin with the first question for today. And our first question is, do I need TCPP 01M12 if I use USB Type-C at 5 volts only? As we are speaking, I am an application engineer on protection. Thank you for this question. Yes, because even if you are at 5 on only, you can be faced to a defective adapter as presented by Mohamed in the presentation. And if you defective adapter presents higher voltage on your absolute maximum rating of your power line, you will have a defective system. So for sure, you need a PPO1 on your SYN path even if it's at 5 volts. Thank you. Thank you, Mathieu. Let's move on to our next question which says, what is the best PCB placement for TCPP? Okay, I will also answer. As TCPP embeds easy protection for CC LANs, it needs to be placed as close as possible from the connector in order to remove as quickly as possible from the search from the PCB, out from the PCB. So the best placement is close to the connector, Type-C connector. Thank you. Thank you, Mathieu. Let's move on to our next question which is coming from France. And France is asking us, how can the provided source current be limited? Is this possible with TCPP 03M20? If yes, would the source current limit be different than the SYNC one? Great question. The current is sent with a shunt resistor, and this is the same for SYNC and source. As consequence, the current protection level is the same for both cases. If you have two levels, we recommend to use a shunt resistance for the highest one. And for the lowest one, I recommend to use a software comparator on STM32 connected to TCPP 03M20 analog output current. And of course, a dedicated software interrupt to turn on the power pass. Thank you. Thank you, Mathieu. Let's move on to our next question from Arturo. Arturo is asking us, which STM32G0 MCU is ready for UCPD? Is it difficult for me to sort them by this feature on product selection? Okay, I will take this one. I am Mohamed Sadna, Product Marketing for Protection Devices. So on the product selector, STM32G0 MCUs that are ready for UCPD are mainly STM32G071, STM32G0B1. But we can also use STM32Cube MX to check this feature. And finally, also in the smartphone application, on the Android version, on the product finder, the UCPD feature is listed in the parametric search. Thank you for this question. You can move to the next one. Thank you, Mohamed. Let's move on to our next question, which is coming from Theo. And Theo is asking us, what if I need to use a type C connector without using power delivery, only using data lines? Do I still need to add protection circuits described today? Could I get away with just leaving all pins unconnected and just connecting the data lines as a micro-B connector? This is a similar answer than I've done previously. Even if you are close to your own legacy cases, that means five volts only, you can be faced to a defective adapter. So based on that, you need to protect your power pass if your power pass is not able to sustain a voltage of 22 volts. Thank you. Thank you. Let's move on to our next question, which is coming from Max Millian. And he's asking us, is there an advantage of USB CPD over traditional USB for five volts, 1.6A applications? Frankly speaking, I don't think so. I think technically there is no direct advantages because you have the same power capability. But of course, if you develop your application with power delivery, you will be able to move easier to higher voltage and higher power rates. But technically at the beginning, there is no real advantage in terms of features of your system. Thank you. Let's move on to our next question, which is coming from Peter. And Peter is asking us, on every slide I see USB 2.0, is USB 3.0 not possible? You're right. Usually we are companionship of STM32 and today STM32 embeds USB 3.0, so we don't focus on that. First thing, there is no limitation, but for source and TRP, as USB 3.0 required higher weekend current, our switches embedded in TCP P02 and O03 are a bit too small, so I think maybe that's something on the roadmap. Thank you. Thank you. Let's move on to our next question, and our next question says, can I use other protection than TCPP for my USB type C using STM32? Why not? For sure, why not? But keep in mind that this product has been developed in order to ensure the highest quality in terms of protection and also optimize the bond content of your system. So you can use something else. You have competitors on the place, of course, but this solution has been optimized. So you can do that, but I think there is no game to do that. Thank you. Let's move on to our next question, which is coming from Stefan. Stefan is asking us, can TCPP01 and M12 take care of inrush current limiting for VBUS? Great question. Unfortunately, TCPP01 does not take care of inrush current limiting for VBUS because it's not required by the standard, and as explained previously, it has tailored the product in order to fit to the best requirement, but no more. If you want to do that, and we've got some development on that way, you can use the TCPP03 and M12 on a synchrony mode, and there you will have overcurrent protection and also current sensing, allowing you to perform a nice application. Thank you. Thank you. Let's move on to our next question from James, and James is asking us, do we need a TCPP chip to design a basic 5V USB OTG application with Type C connectors? Okay, I can take this one, Mohamed. So of course, yes, it depends on the absolute maximum rating of the input pin of your power management where VBUS will connect to. If this power management pin, absolute max rating is higher than 20V, you may not need an overvoltage protection on this line. But if this absolute max rating is below 20V, then you will need an overvoltage protection that is integrated in the TCPP01, and also you will need to take care of the ESD protection of the CC lines that is also integrated in the TCPP01. So if your AMR of the power management is higher than 20V, then you don't need an OVP on VBUS, and you can add external ESD protection on the CC lines. Thank you. Thank you, Mohamed. Let's move on to our next question from James, and James is asking us, can I also use the TCPP with your L4MCUs? Okay, Mathieu speaking. Yes, you can use them with your L4MCUs, adding a Type C connector to your system. But keep in mind that L4 does not have a UCPD peripheral embedded. Never mind, you can use it only at 5V on legacy gauges for sync and source. Thank you. Thank you, Mathieu. Let's move on to our next question from Stéphane, Stéphane is asking us, is overvoltage protection required by the USB standard or just good design? It's not required by the USB standard, just for good design or a light design, that depends, but overcurrent protection is required by the standard, but overvoltage protection is not required yet. But keep in mind that as soon as the mechanical drawing of the connector has been done and tested on first interconnection events, this weakness has been identified and has been treated. And for sure it's something quite inherent of the mechanical drawing and the Type C overall system. But it's not writing down on the paper. Thank you. Let's move on to our next question, now next question, Stéphane, why need several STM32 for a multi-port USB-C power delivery application? Okay, Mohammed, I can take this one. So on STM32G0, UCPD version, there are, in some versions, there are two UCPD controllers that are able to manage dual port solution. It means that with one STM32G0 having two UCPD, you have control for two ports and on each of these ports, you will need to place one TCPP device. Thank you. Thank you, Mohammed. Let's move on to our next question. And our next question, Stéphane, when do I need one or two MOSFETs for my load switch on VBUS? Okay, Mohammed speaking, it's based on the voltage present on both parts of your system. Let me rephrase. As example, on provider pass, that means when you are on source, on a DRP connector, you can have voltage on VBUS of the type connector. So you need a MOSFET on one way to block it. And you can also have voltage on the power source of your power pass. So you need two MOSFETs because due to the body diode of your MOSFET, you have a leakage from one to another one. So you, using two MOSFETs front to front, you are blocking that. On SYNC case, on SYNC case only, you only need to block the voltage coming from the type connector in case of overvoltage. Then only a single MOSFET can be used. But if you have a voltage on both parts of your SYNC pass, you can use a dual MOSFET. So that is more application already seen. So the solution proposed are the most common ones. But if you have a specific one, don't care. Adapt your layout and your design to your application. Thank you. Thank you. Let's move on to our next question with space. Can we use STM32 plus 3CTP with USB 2.0 cable application? OK, much speaking. To rephrase, I think USB 2.0 cable application is type A to type B connector. TCPP are not dedicated to this kind of application. As example, you don't have any overvoltage risk because it's 5-round only. You don't need to send CC lines. No, TCPP is only designed for type C application. I'm not going to use one. Thank you, Mathieu. Let's move on to our next question from Johann. Johann is asking, do you have any solutions to take the USB-C power supply against lightning from the DO-160? OK, much speaking, I don't know DO-160, but on the reference design proposed around the 3 TCPPs, we all embed on the PCB a dedicated CVS, ESDA 25-piece certified 1U1M. This is a very small CVS that removes surges coming from the lab. It is mandatory as you can have some surges on your system and coming from your adapter. But of course, if you have higher current surges, you will need to adapt your CVS. This CVS is not embedded on the TCPP because it's a power device. And of course, power device might be fitted according to the system requirement. And you cannot use a generic part. We prefer to let you the possibility to adjust your CVS to your system and your requirement. Thank you. Thank you. Let's move on to our next question. Can DRP support sync and source concurrently? Mohamed speaking, so DRP, your role power is a mode where the collector will be acting either as a source or a sync, but it cannot act in the same time into both roles. So the role of the connector will be defined according to the role of the device that connects to this port as per the negotiation and pull-down position on the CC lines. Thank you. Just one comment. TCPP03, it can be used on a DRP port, cannot close consumer and provider paths together. This is hardware locked in order to avoid any bad issues while debugging the software. So for sure it's not possible to close that two paths together. Thank you. Thank you, Mohamed and Matthew. Let's move on to our next question, which states, why does TCPP do not integrate ESD protection for high-speed data lines? Yes. So as we have explained during the presentation, we have defined TCPP to be the most cost-effective for USB-C application and as not all applications require USB high-speed data lines, we prefer to keep this function for ESD protection of high-speed data lines externally that can be added on top of the minimum features that are required for the USB-C standard that are integrated in the TCPP. Thank you. Just one comment. We have an easy protection EMI filter for USB-3 high-speed lines on our portfolio. Thank you. Thank you, Matthew. Thank you for your answer. Let's move on to our next question, which states, can I use TCPP protection devices with another MCU than SCM32? Mohamed. So yes, definitely you can use the TCPP device with over MCU. So if this MCU embeds USB-C controller so you will be able to run the USB-C protocol, else you can still use TCPP with another MCU at 5 volts only from 0.5 amp up to 3 amp. Thank you. Thank you. Let's take another question and another question is coming from Jan and he's asking us, which solution do you prefer for external programmable power supply, example with XNUCLEO SRC1M1 board? Do you provide C source code for voltage control? Of course, to perform a source you need to use XNUCLEO SRC1M1 board. These boards are functional, of course, but not yet released to the market. It's planned on Q4 and when they will be released, like all the boards, the source code, the C source code will be also released on GitHub and on the X-Cube TCPP package. So yes, we will provide the C source code, sorry for the typo. Thank you. Thank you. Let's move on to our next question from Marcine and he's asking us, what is the most effective OVP up to 24 volts? So as we have explained for USB-C, you need OVP on VBus and also ESD protection on the CC line. So definitely the most cost effective OVP to 24 volts would be TCPP01. And the advantage of TCPP01 is that it integrates the charge pump in the gate driver so that TCPP01 is able to drive NMOSFET, which are obviously most cost effective compared to PMOSFET. And as a designer, you don't have to add external security to drive this external NMOSFET. Thank you. Thank you. Our next question is coming from Brandon and he's asking us, how is protection of the data lines done? Okay, much speaking, on the system partitioning, if you want to use data lines, you have two solutions. You can just add classical ESD protection. We have product for that, as example USB 86 to S66 and this is what we are recommended today. And if you want also to protect against EMI, on both bonds duration and sensitivity and also aggression, you can use ECMF, that's a product that embeds a common bond filter and also ESD protection. As example, ESM ECMF 02 to HMS Mx6. You can find all these recommended products on the reference design of the X nuclear boards. But of course, yes, you need to protect the data lines of USB 2.0. Thank you. Let's move on to our next question and our next question says, CTPP here 1M12 integrates 8kV ESD protection on VBUS. Why is there an external ESD dialed on VBUS line in reference schematic? Okay. On power buses, keep in mind that ESD is no more the issue. The issue is the search. And to filter the search, ESD are not enough. You need a TVS transient voltage separator with IR, IPP capability, current capability. And then that's why we are using TVS on top of the basic ESD protection. It's mandatory when you have power bus. Of course, your size, your TVS according to your, according to the robustness required by your system. But what we are proposing into the reference design is tiny, small TVS, allowing wall fitted to this kind of mobile application. Thank you. Thank you. So I see we are nearing the top of the hour and we will be running out of time. So let's take one more question for today. And our last question is coming from Jean-Philippe who's asking us what are the packages available for TCPP products? Mohamed speaking. So all the TCPP products comes in QFN package using 0.5 millimeter pitch to allow easy integration in low cost PCB. So TCPP01 for sync has 12 leads in QFN. TCPP02 for source has 18 leads and TCPP03 for DRP has 20 leads. Thank you. Thank you. And this last question brings us to the end of the webinar. Thank you again for attending. Also, if you and one of your friends are interested or considering pursuing a career at ST Microelectronics, we are hiring at this moment and to view our current job opening, click on the call to action button at the bottom of your screen. For those of you that have questions that come up later, we encourage you to use our online support tool. A direct link to our support tool is already available at the bottom of your screen. Of course, you can also contact your sales representative. Again, we will be sending all registrants to this webinar post event email with the link to the on demand version of this webinar, as well as additional resources and the link to the community where you can find the answer to some of your questions. A PDF of the presentation of this webinar is already available under the resource widget at the bottom of your screen. So thank you again for attending our webinar on STM32 plus TCPP protection for safe low cost USB type C applications. We hope you enjoyed it and were able to take away some useful information. And also, thank you to those of you who took the time to answer our survey. We do appreciate your feedback as it will help us improve your webinar experience with us. And of course, a big thank you to our speakers for making this webinar possible. Please stay safe and we look forward to seeing you soon at one of our future events.