 So, we're here at the Embedded World and who are you? My name is Jack O'Gawa, I'm the Senior Director of Marketing for our Microcontroller Business Unit. And here at the Embedded World, you announced something in partnership with ARM? What are you working on with them? So indeed, so we had a release on Monday that talked about how PSOCK 6, our secure microcontroller, supports the highest level of security that's been defined by the Platform Security Architecture Initiative from ARM. Highest level. Highest level. So, we provide three levels of isolation within the microcontroller. The first level is an isolated execution environment for secure processes. The second level is an isolated area for a route of trust. And then the third level is being able to isolate the trusted applications within that. So, providing those three levels allows us to achieve that highest level for PSA. Because the PSOCK 6 is an ARM Cortex M4 based solution, right? Right. So, with the fact that you do PSOCK, you have all kinds of periphery or designs that you do security. You've been doing before. That's right. Now, this is the next level or? That's right. So, we have some unique capability in the architecture, starting with the fact that there are two cores in the part. We also have utilized memory and peripheral protection units that are fully configurable. So now I can control access to the resources in the part, creating the isolation that we just talked about. Which are the two cores? You have the Cortex M4? We have a Cortex M4 and a Cortex M0 Plus in the part. And the M0 Plus is kind of like the security core or no? That's right. So, in a typical application, we would dedicate the M0 Plus to security functions. And those security functions can be firmware update applications, as well as perhaps, for example, a TLS stack or some other things that you can imagine. So is it correct to say that ARM has suggested last year, maybe a little bit before they started launching, announcing the ARM V8M, which has some security inside of it, and you are working with ARM to make it work on the ARM V7? That's right. So, initially the PSA effort was centered around V8M, and that was the first implementation of TrustZone M. What we've done with PSLock 6, since it predates that activity, we actually have used V7M core, obviously, with some unique configuration around in the architecture to implement the security. Now what we're doing is we're taking Trusted Firmware M, which is the open source firmware that's available from PSA, and we're taking that and implementing it on PSock 6 on the M4, which is obviously a V7M core. You said the open source security firmware, what's the name? It's called Trusted Firmware M. So it's not the TrustZone, it's an open source security. That's correct. So TrustZone is actually in the silicon, Trusted Firmware M is then the firmware that runs the silicon. So in our case, rather than having a TrustZone capable core, we have an M4 core and an M0 core. We're able to provide the security that's achieved by a V8M architecture, but we've done it with our cores, and so therefore we can take that firmware and put it into PSock 6 and achieve the same security level. And so is that a new announcement for the new firmware, is like the new generation of firmware or something that all the PSocks can just use? Yeah, so that firmware would be usable by all of our PSock 6 devices that have secure capability. For free, they can just opt into that if they want? That's right, and that's the philosophy of PSA is they want to broaden the ability for people to implement security, and their strategy is to make threat models available for everybody, firmware through open source available, and then of course proliferate the marketplace with products that use ARM core technologies. So I would imagine that maybe the ARM V8M, which hasn't shipped kind of not yet, but when it's hardware security is the best way, and you have hardware security because you have those two cores, so does that mean you are as secure as whatever is going to come out with ARM V8M? That's an excellent question. So by analysis, TrustZone has two levels of protection that are implemented. Because of our architecture, not only can we cover those two levels, but we also had that third level that I mentioned, which is being able to isolate the root of trust. So if you had a single core V8M implementation using TrustZone, typically what you might have to do is to add a secure element to host the root of trust. In PSOCK 6, we actually integrate that secure element capability inside of the part, and so that's how we're able to achieve the three areas. So you have at least as much security, you have actually even more. That's correct. Like in terms of both hardware and self-care security. And so you have partners working on this? That's right, because you're talking about partners here. That's actually right. So we deliver the silicon, but we know that we need partners, for example, to implement provisioning. So we work with a company called DataIO and secure things to provide the provisioning as well as secure boot firmware capability. We also have a partner called Trust Azure, which is providing some application-specific capability in a secure application capability as well. Can we check a demo here or two here? Absolutely. Let's take a look. Great. So one of our partners is a company called OneThings, and they're implementing a LoRaWAN module using PSOCK 6. They're also working with a company called eScrip, which is a Bosch company, to provide a secure capability on top of the LoRaWAN connection. All right. So I'll have Rolf here go through the demo for you and introduce the solution. All right. Thanks a lot. All right. So hello. This is Rolf from OneThings. I want to show you a module. This is our new module. It's a very tiny module. It has LoRaWAN inside, and it has the Cypress PSOCK 6. So it has a dual-core M0 Plus and an M4 core, and it's really ultimate for doing IoT things. Do you build this board? Yes, we build this board. And you call it OneThings. Where are you based? Yeah, we're based in the Netherlands. Is this about LoRaWAN? Yes. So it's long-range, low-powered data. So if you can jump in here, so what's the demo about this board? You have the board right here. We have the board right here. So this is the board. This is with the old module. So we have keys in there. Over here. The Bosch SDK. It's a multi-sensor development kit, which we connected with our module. And when we press the button, we can see the data coming over there on our dashboard. So is this 100% security? Yes, this is 100% security. It is? This is hardware, software, everything secure? Yeah, we have a secure element inside PSOCK 6. So the secure element does do the control of the flash. And once the flash is secure, it will boot. And it will start the LoRaWAN functionality. So it will start the LoRaWAN radio. Once it compromised, the secure boot recognized that the keys are not correct. So it won't start the LoRaWAN radio. Is this using the PSA? Is this using the latest secure element? Yes, it uses. The PSOCK 6 has integrated hardware into a secure element. And it also uses the hardware acceleration, the encryption acceleration to do all those functions in the hardware and they can be compromised. Is this the optimal LoRaWAN solution in the world? Is that what you say? From a security perspective, it is. So do you have customers on it? We have a lot of requests here and we're definitely going to make some customers. And we already have some customers in the Netherlands. So we are launching our module at this demo and we are sure going to roll it out as soon as possible. Alright, awesome. Thank you. Thanks a lot. I'll put the video right here. Okay. Thank you. No, it's less than a second. It's microseconds. That's exactly right. Let's hear it for Air Doctor, whatever his name is. Egan Dorf. Is that close? Egan Dorf. I should be German. I like beer and I like sausage. So that makes me at least honorary German, right? So it takes microseconds for the CPU. Now here's the next question. How long does it take logic gates to respond to signal changes? Not a second. What's less? Not a second. Nanoseconds. Give some dev kits over here, my friend. It takes nanoseconds. And now I ask you this deep and philosophical question. How much faster is a nanosecond than a microsecond? It's three zeros. That's right. That is a long damn time. Three zeros. One thousand times faster. So the bottom line is, if you've got some safety critical thing or something, you should put it in our PLD. The other thing that you've got going on is when you have an MCU, you have software. And when you have software, you have a human being. And another name for a human being is a bug-making machine, right? So, that's exactly right. So if you make a bug in your software code, and your software code is off doing whatever it's doing, it sure as hell isn't turning off the robot arm from beating itself into oblivion. And that's no bueno, as they say, someplace. All right. Some of the other stuff are appearing. Clipping back and forth.