 Ac mae'n wneud yn ymddi'r rhaglion i gael y rhan oherwydd rydyn ni'n gael y cyffredinol gwahanol a'r pethau gwahanol ddim yn defnyddio'r portfolio a bod yn gweithio'r ddechrau cynnig. Rydyn ni'n gofio'n amser ar y SRM32 yn y pastor a'r ysgrifennu yn y website yma. SRM32 yn dweud yn dweud yn ddechrau'n gweithio. Mae'n dweud yn dweud ar 12 oed, felly rhan oedd yn 2007 yn y Corthex M3'r SRM32 F1. Rwy'n dod o'r unrhyw o'r ddweud, ac mae'n swyddwyr ar gyfer y porfolaidd a bwysig hon i'rdym ni. Mae'r ddweud yn hynny o gwisio'r adeiladau ar gyfer y ddweud. Rwy'n mynd i'r cyfwyr gyda gennym o'r productau maen nhw, mae'r F0 a'r F3 o'r ddweud. Mae'r U4 cyfrydy o'r grannu ar gyfer ddweud, sydd mae'n gwybod ar gyfer ddweud o'r ddweud o'r cyfwyr, felly yw eu cael am llawer. Os y gynllun o gwaith rhai wahanol herfodd, wyrda i'n gyfynifig yn cynllun. Dwi'n rhai dwi'n ddweud o'r F2 o'r F4, o'r F7, o'r H7 o'r fain yma fel yn cael yma. Ac mae'r ddaf yn cheif. Mae eich ddaf yn hollisio'r M1 o rhai, fel mae'n gwybod hwn am hyn, gwyddoedd masnig ar y Duxfyrd Gyllidrach, a'r M4 o los. Felly mae'n ddweud arall o'r cyflau. Yn nol y byd yw, all y SAG-32's general purpose a not application specific, we've got with the exception of a couple of parts which are dedicated towards particular applications, generally speaking they're application agnostics of the general purpose design to fit to be able to feel to be able to find the right device regardless of what your application is. One of the key things about the SAG-32 is if you design it in today oherwydd, rydw i, yn y ddechrau, gydyn nhw'n fawr, oherwydd, gydyn nhw'n fawr, y wnaethef, mae'r ysgol yn fawr ar hyn, oherwydd y gallwch yn cael bwysig, y same board yn 5 yma, 8 yma, 10 yma, etc.. Felly mae'n ymwysig yn y ddweud. Felly mae'r 32 gennych cyfresol, yn ffwrdd, mae'r prolt yma o'r proladıon yng Nghymru a'r 10 yma. Mae'r glwn yn nid oed yn rhan y 10, y gallwn y cyfresol o'r bron, it's not from the day we launched the product, it's 10 years. A roll-in commitment that we refresh January every single year. So, when you take the product, the F1 that we launched in 2007, we're still offering 10 year longevity commitment on that today. So, eventually that means a minimum of 22 years commitment to that product. So, if you design it in, it's going to be around for a considerable period of time. And that includes the MP1 that we're launching. oherwydd wysnowogaethau. inspiration in terms of where it fits on where the MP1 comes from. Yei. The key thing is, is the re-use of the STM32 ecosystem and infrastructure making it familiar to anybody that is already using the STM32. So from that point of view if you consider this innerbox here as standard STM32. Any other microcontroller that you might have used gyda'r M4, ystafell SGM32, yn y cyffredinol iawn, a'r ystafell ECO systemau sy'n mynd i'r cyffredinol i'r mwyaf ar y Cortex M. Felly, mae'r cyllid o'r Arhau Arhau Arhau, o'r cyffredinol sy'n cyfrannu sy'n gyfrannu sy'n gyfrannu cyfrannu, mae'r cyfrannu cyfrannu sy'n gyfrannu cyfrannu, mae'r cyfrannu cyfrannu sy'n gyfrannu cyfrannu. Nid oesマel gennym些au o'r ystafell. Ond nid oes trefŷ rud, aenderfwm ddedwed o uneg robusteb cyfle ph�m Mer pickwch eu byd yn y gweith f wrth gwrdd dda, sgwyd haes gwyd da. Felly ei wneud ar comprominio, drafod d многiau'n argylchedd trwy y d oldadyd cwrdd ddwyn pisoed mwy mae'r mwyaf i'n ag i mewn enfyn. Diolch i 찾ogi я le o'r pryd na Felly mae'n cwrtech gyda 7 yw'r product. Mae'r 3D graffix wedi ychydig. Mae'r ddoran ffasgau, os ydych yn gallu ddoran ffasgau, ac mae'r Linnx ecosystem, sy'n gael y cyfnod i'r opa, ynbeddau a'u yw'r yw'r yw'r yw. Yn ymweld yw'r yw'r yw'r yw'r product, yw'r product, a'r yw'r market. Mae'r Cyfnod Llinx yn ymweld, a'r cyd-dynai yn gwybod gennych, ac mae nid o bwysig edrych yn gwybod mewn cyfnod. Felly yw'r ddwy darllen ymweld, yn ymweld yw'r yw'r yw'r yw'r cyfnod, mae'n ddod i'r fwyf yn ymwyf yn gweithio'r cyflwyngau. A oes chi'n gwybod y fflexiwn i'r yw yw'r yw'r yw'r Linnx-based product, felly mae'r adnod i'r gwaith i'r adnod i'r diwrnod a'r ddweud yn gwybod ein cyfweld rydyn ni'n ddoedd. Rydyn ni'n byw'r cyd-gorydd cychwynol hynny a'r adnod i'r adnod i'r adnod i'r cyd-gorydd cyfan. A dyna'r adnod i'r cyd-gorydd cyfan, yn ddod i'r cynnwys mewn gwahanol, a'r adnod i'r cyd-gorydd cyfan, roeddwn ni'n meddwl am gyfer y cyfweld, bwysig i'r cyfweld, ond yr adnod i'r cyfweld, ac rydyn ni'n cael cyfeiriad Llin X. Rydyn ni'n cael f assistance lle gyda hunain a rydyn ni'n cael meddwl am y Llin X oherwydd na'r gennydd byddwn ni'n colli arweithio aros Ymgrifiwr ac mae'r meddwl yn cael meddwl, mae'n meddwl yn meddwl. Mae'r meddwl onf, mae'n meddwl am y cyflawn, yn cyflawn, achos y dyfodol. A gael lle hanesent hwnnw, mae'n meddwl i fi ar hyd yn cael meddwl a'u meddwl goryn am yr Un Efo Llin. Mae'r meddwl am ffyrdd ymddag yma'r periforol yn ei wneud. Felly, felly mae'n gynnau'r Corthex M a mae'n gynnau'r Corthex A, ond mae'n ddyn ni'n gwybod fel Llinix a'r Alun, mae'r periforol yn ni, o'n ddod, yn ei ddweud wrth dod i'r periforol yn maen i chi'n gyd, ond mae'n gwybod, yn fwy o'r hynny. Mae'n gwybod i'r periforol yn ôl i gynnig oherwydd sy'n cael ei gynnau. Felly, ychydig i'r ethynedd o'r Corthex A, sy'n ddysgu fydd yn llawer cael ei awn yn SNF4. Yr Rhwng ymddwr i'w fwylch, am y digwydd fylau'r ysgr Zhang, gyda ni'n ddysgiliau, oedd yn dod, oedd yna'r ystafell yn ddysgiliau. Mae gweithgelf am ar y MYW, ac mae'r ddweud o'r hyn yn gwneud amser i gyrsedd C0 OX i gynnwys i fynd i gyd â ffyrddau C0 OX. Gwadau'r derbyn yng ngryffwys. Ydwodysg LPR Ynws, mae'n ddysgiliau LPR 3, LPR LPDDR. Dyna dwi'n wych. Gwybod yosingwch â 16-bit a 32-bit fi... ...diwrnod gwybod fynd ar yr oradau'r gwain. Felly mae'r gweithio sy'n plesio. Mae gennym gan rhai ddauau mae gwaith. Mae gwaith i fy nifer ysg Jones-Boot cy synthetic. Byddai bod hwnnw i'r gweithio, cyffeithio fi'n ystod ddysgu hynny. Rwy'n cael ei wneud o'r disblwyr. Yn y cyfle hwnnw, mae'r hirendygoet. Mae'r mipidys wnghwyl, mae'r disblwyr. a y 3D GPU sy'n cael ei gael i gael y rhan oherwydd ymlaentym ar gyfer y broses. A dyna, wrth gwrs, fel yw'r SGM32, mae'r anolog yn cael ei ddefnyddio cyntafol. Mae'r AdC, Dychysl, ac os ymlaen i chi, mae'n cael ei ddefnyddio. Mae'n cael ei gweithio, mae'r gwybwyng yn dod o'r ddiolch yn cael ei ddefnyddio. Rwy'n cael ei ddefnyddio gydag ymlaen, dylau'r ddechrau ei ddefnyddio ar yr ymlwg cyfiol. a ti tyw'r gwahanol ar gyfer gyda pariforol. Felly yn wneud sy'n fawr'u ddr. Felly yn wneud fawr i'r WSP, i wneud fawr i'r eithanat, ffaith, felly mae'n fawr ar gyfer, mae'n fawr o'r lathau. Mae'r rechel yn ddiweddol, mae'r pariforol ystod o'r microproces mae'r cyfrwysau ac i'r cyfrwysau ymlaen i'r cyfrwysau ac rhaid i'r cyfrwysau i'r cyfrwysau. Mae'r cyfrwysau i'r pariforol a yw'n dweud gyda'r un iawn, yn ddefnyddio'r dweud o'r dweud i gael'r dweud i ddweud'r dweud i gael dweud. Dwi'n mynd i fyddiad o gweithio diwyddiad. A dyna dweud yn rharffwyr ac o dweud i'r dweud o gweithio ar gyfer Dos, felly mae'r dweud yw'n mynd i ei wneud. Roedd yno o'r graffics. Graffics yn y cyhoeddiant yn y MP1. Mae'r dweud o'ch walty i dda'r graffics. Mae nhw gan y ddyn nhw'n gael unig 3D graffics o'r graffics, Felly, rydym yn ganunio Fivanti IP ac yn gwasanaeth, ac yn gwasanaeth i GLES2 ac yn GVG. Rhyw bwysig ar y cyfnod, mae'n gwneud yn cael ei ddweud am hynny. Felly, rydym yn cyfnod yn lluniau i'r ddweud ac yn cael ei ddweud. Felly, mae'n gwasanaeth ar y cyfnod. Mae'n ddweud ar gweithio'r gwneud yn gweithio. Felly, mae'n gweithio'r gweithio cyfnod ar gyfer y solwysiad. Mae'n gweithio'r ddweud. Well, in terms of resolution we're talking about WXGA up to 60 frames per second. So a reasonable quality for an embedded processor. And then you have a MiPDSI, if you want to use a MiPDSI as your interface for the displays. So the displays you've got on those boards are MiPDSI based. Ecosystem wise, I mentioned already, it uses the same ecosystem, or certainly for the Cortex-M it uses the same ecosystem as all the other SGM32s. So that's STM32Cube with Cubamex and Cubeprogrammer. And then hardware-wise, so from an SC point of view the ecosystem is the software, the hardware and the support infrastructure that we put in place for an STM32. So hardware-wise we've got the discovery board, so you've got the board you have which is the DK2. On your board so that's got the graphics, it's got the combination of BLE and Wi-Fi module, and the SGM32MP1 on there has the hardware cryptography enabled on it. There is also another board which is the DK1, which I have over on the demo table, which is the same base board, it just doesn't have the display, it doesn't have the Wi-Fi module, and it doesn't have the hardware crypto enabled part fitted, so it's a slightly cheaper option. Then we have the eval board which is somewhat bigger. Lots of connectors on it for connecting stuff. Not quite as flexible for prototyping, so I would recommend if you want to prototype really the DK1 or DK2s are the way to go, but that is an option if you need either the bigger display or you need just to be able to easily plug various things into the peripherals. Then on the customer side support, so the information side, the MP1 is supported by the same global support network that the SGM32 already is. So that's our online support, the STEs community for STM32, our FAEs worldwide, our distributor FAEs as well. And then we also have a partner programme, and now the partner programme becomes more important for the MP1 because obviously with it being at Linux there's a whole load more, it's not just about consultancy for hardware design or low level drivers design. You've got lots more layers to consider, so we have many partners associated with the hardware design, with low level driver software design, middleware design, application level design, that kind of thing. And also partners that produce things like SOMS, so if you don't want to do your own design you can take someone else's design and drop those into your product, so I pretty much summarised what I've already said to be honest. So the eval board, the big board, is probably the most expensive option to consider for your development. Two flavours of it again, one with and one without the hardware cryptographic engine enabled in the device. A couple of options on the discovery board, which I've talked about, and then SOMS, another board, so you've got manufacturers making SOMS, but also other reference designs of development boards. So for example the Lanara specification for 96 boards, there's a number of third parties actually developing boards based on that spec, whether it's the IoT spec or any of the others. So you can go out and pick up those boards as well to do development with. You'll notice on the slide that the pricing for the discovery boards have an agreement with our colleagues at Avnet to allow you to actually purchase the board at a discounted price. So if you follow the link that's in the slide or even just use this search number or this part number on Avnet's website, you can get a decent discount off the price of the board. MP1 development tools, what we changed in terms of the existing tool set. Cubomex is our configuration tool for those that don't know. So it allows you to do the alternate function mapping of the device, set up the PLLs or the clocks, generate the initialisation code for the boards or for the firmware. We've enhanced it to allow you to map the peripherals between the cortex A and the cortex M. So that's the first step, so you can choose where you want the peripherals to be connected. But we've also added in, as part of that, device tree generation. So for Linux, you need a device tree to configure the peripherals and map them. So Cubomex will generate the device tree for you so that you can just import that into your projects. Also, another important part is the DRAM tuning. So obviously DDR, high-speed interface needs some critical tuning in order to function at its best. Cubomex has a facility in there to allow you to do that tuning to get the best performance out of it and then save the configuration to load into the device. Tools-wise or compiler-wise, et cetera. For cortex M, it's exactly the same. So you use the same tools as you already have done. So whether that's IAR, Kyle, on the paid solutions, the free solutions from System Workbench or other eclipse-based tools, et cetera. So AC6, System Workbench, eclipse-based tools as well, generally. Or even just command line GCC-based tools, you can use those. When it comes to the Linux side, for this workshop, we're using the AC6 tool to do all the compilation. Then Cube Programmer, we have Cube Programmer, which we've enhanced to support MP1. So we're adding in OTP, it has OTP programming based in. So there's a lot of OTP available to put your own parameters in within the device. So any MAC addresses, that kind of thing, programming into them. So you can do that from Cube Programmer. If you have a situation where you want to sign binaries and encrypt them, Cube Programmer can do that for you and create those signed images as well. I'll skip that slide pretty much. It covers what I've pretty much said. So in terms of simplifying your Linux development, obviously there's a whole lot out there. It's a complex package to be involved with and to use. There's lots of different drivers, lots of different combinations of things. So we've tried to simplify it by one, pushing everything up into the community. So we've upstreamed pretty much all the software. So you can go out there and just find it. You don't need to come to us. You can download it from kernel.org. You can download it from our open GitHub repository and pull all the code down. So that's the first thing. So all the code is supported by the community as well as us. We've tried to, where possible, in fact, pretty much we have to if we're going to put it out into the community. So we're fully compliant with all the open source standards where we need to be. So we've uploaded to the Linux Foundation. We're covered by the Yocto project. So we're part of the Yocto project. On the secure side, we use OPE. So again, another community-based secure solution. So not something specific to ST, not something proprietary. Pretty much we've gone with open source solutions for everything. So just a reminder, I think we've said this a number of times. The key benefit on the Cortex-M side is the reuse. So you benefit from using everything that's already out there. If you have code already written for the STM32, you can recompile that and run it on the MP1 on the Cortex-M. So you don't need to redesign from scratch. So you can use the APIs to access the peripherals. So that whether that's the STM32 KUPE HAL or the low layer, which many of you may be used already, you can reuse those. Middleware components that we already showed for the Cortex-M, again, reusable. You can learn from many of the examples that we have already in the packages. So when you download the firmware package for, say, the M4, there's loads and loads of examples in there on how to use the peripherals. So they're all still very relevant. And we go through a continuous cycle all the time for quality. So taking in field reports, bug fixing, adding features, recycling the firmware and making sure we're constantly updating. And the final point on their business-friendly licence as well. From our point of view of the Cortex-M, everything we give out on our website has always been free of charge. We are STs in the business of selling chips, not software or anything like that. So the drivers are all free of charge. The middleware source code that we provide is all free of charge. The schematics and the Gerbers, we provide those. You can free to copy them. You can copy and use pretty much as you like. And that now extends onto the Linux side because everything is covered by standard Linux-type licences. So whether that's GPL or various flavours, BSD, et cetera. And again, Chris has got a slide on what the licensing terms mean. So which types of MP1 being if you've looked at the STM32 portfolio, you'll know we have 100. So from a few different product lines, we have thousands of partners because we can take something like the MP1 and in this case, as a headline product, we have right now 24 different products. In production because we do different flavours of it to suit different customers needs. So starting at the top, we have the MP157, which is the device on here. So you've got the dual Cortex-A7s with the Cortex-M4 with the 3D graphics and CanFD and the Mipi DSi as well. Then we step down to the 153, which again has the dual Cortex-A7 and the M4 with CanFD. This time we don't have the graphics. So if you've got a product that needs the performance but doesn't need the graphics, then you can drop down to the 153. And then the lower end, if you're looking for a Linux infrastructure, an application type product but don't necessarily need all the performance of the dual Cortex-A, then you can go down to a single Cortex-A with the M4 still. So the M4 is still there giving you the real time sign. So that gives you three product lines. For those, you can have hardware cryptography within the product. So you can have variant with and without hardware cryptography. And then finally, we do all those products. So the six different products in four different packages to suit your design requirements. So whether it's four layers, boards, six layer boards, whether you support laser vires, plate through hole, et cetera on the PCP, you need to be able to do 0.8 pitch or 0.5 pitch on the VGAs. So you've got all the options. And as a note, the 10x10 is currently the smallest dual Cortex-A based product on the market. So we talked about, I mentioned partners, how they're important now to the P1. This is just a small subset, a snapshot of when we made these slides right back at the start of the year, February. It's growing all the time. But the key is you can see we have partners available for training, for the embedded software, for the high level software and engineering surfaces, actually for the software development tools, hardware design, and then SOMs and SIPs. So we have a number of partners producing MP1-based SOMs and SIPs. As I say, that's growing all the time, but if you need help of any particular partners or indeed if you're a consultant yourself and want to be involved in supporting people using our products, then you can go to our partner programme either to find a partner or to request registration if you want to become a partner, best tea for this product. MP1 is the start. It's at first entry for the micros division of ST into microprocessors in terms of mass market microprocessors. Obviously it won't be the last because you've seen how the roadmap grows. We will be continuously implementing new products. So whether that's an increase in performance features or security or even products to reduce the cost and reduce the power consumption of the device. So we're currently focused on two different avenues for the next generation of products.