 Hi, I'm Anna Snasheff from Intel. And we hear the Zephyr booth, so what do you do with Zephyr? Yeah, well, I have been working on Zephyr for the last four years. I am dedicated to the Zephyr project. The founder of Zephyr? I'm not the founder of Zephyr, I am on the TEC, the Technical Steering Committee, involved with different members on different technologies and features that we are introducing into Zephyr. And so, what's the latest? What's happening? So the latest now is that in one month from now, if everything goes alright, we are going to be releasing Zephyr 1.14, which is going to be our long-time support release, something we are going to use also for taking Zephyr into certification, at least parts of Zephyr. And it's also a major release because there are a lot of things that happened in the last few years and most of them are being stabilized and released in this 1.14 coming up. So you call about it long-term support now? Yes. So how long? Well, since this is the first one and we are experimenting and we are thinking first about two years and basically to give us time to stabilize and also drive it to certification, once we have some level of certification probably we will reconsider and make it a little bit longer, especially for long-term products. So this is a big milestone? It is a big milestone. You've been working more than four years to get there? I would say that, yes. We are at the right point where we actually can do that, given the community growth and the membership growth that we had over the last years and the major features that we put in Zephyr. Nice. And what are you showing for example here? So here we are showing two things. This is showing two things. One is using Zephyr in a non-MCU environment, basically using it as a guest on top of an open source hypervisor. So what am I looking at here? So here we have Zephyr and Zephyr. What do you say, echo? Echo, yes. So you can show it here as Zephyr running as a guest only on top of hypervisor, side by side with Linux. And it is a use case that we use. He maybe can demonstrate. So why do you run Zephyr with a Linux? Why do we run Zephyr with a Linux? Yeah, how does it help? So it helps when you go on workload consolidation where you want to consolidate different workloads and we have different operating systems. So you may have systems that are of workloads running on Linux, it being half real-time or soft real-time or even a much more generic function like doing artificial intelligence, doing more intelligence human machine interactions. But then you may also need to consolidate the same physical platform or workload that is a bit more real-time by nature. So what we mean by that is when you have latencies requirements that are back in the microseconds or even below that. And so echo is there to help you consolidate these different requirements and platforms onto a single physical hardware. And so it creates a partition at the hardware level where you have a very isolated machine that in this example is running the Zephyr project on real-time noise to the one that guarantees you these small response times and real-time characteristics. And echo allows you to then run on the same platform just alongside a Linux virtual machine that can be doing, in this example here, we're doing object recognition on a video stream. So this is what we're showing here and all running concurrently with Zephyr. So are the both running on the same X86 chip? It's the same processor and we just partition the different cores and we partition the different resources on the machine. And so this is one of the users for Zephyr to design this direction. Yes, this is one of the new use cases for R2Cs and for open source software in general, consolidation and putting multiple workloads on the same hardware. This is very interesting for industrial and automotive and Zephyr is trying basically to fit in the space as well. And it's special or interesting to be able to run multiple OS at the same time on the same chip? Yes, because this actually gives you control and it gives you also scalability. You can just start additional guests when you need them and you have full control. It's not running on separate hardware. This is interesting in consolidation in the car, for example. ECUs, instead of having multiple ECUs you can actually do all of that on one single piece of hardware. And what is this? So this is an audio processor, audio DSP. It's code name is True Creek from Intel. And this part here is... The microphone array? The microphone, you know that very well. It's running an extensor chip from Cadence and it basically does the audio processing on Zephyr and sends that to Alexa using a Raspberry Pi. So basically the audio comes back through Zephyr as well. So it's showing here that Zephyr is not just a sensor, IoT type of application. You can also do audio processing. And this demo here has also audio processing or commercial audio processing, middleware that does eco-cancelling and a few advanced audio features. Nice. And then later in the video I'm going to introduce some of you other colleagues around here doing this, a lot of different chipset companies that are partnering this, right? Yes. So we have an XP here and they are demonstrating multi-core. So basically using, not open AB in this case but RB message light to communicate between different cores running Zephyr and showing basically the communication on the screen. So we can have a little bit more detail there. Over there we have Nordic showing their new chip NRF91 which has LTE-M chip and use for IT and has various use cases in IoT space. So we can go there if you want. They are getting... Let's jump over here. Let's go to Nordic. Nordic. So we have an interview here on the spot. Are you ready? Yeah, sure, yeah. Hi, so who are you? Hi, I'm Joel Stableton, product manager at Nordic Semiconductor but I work with the Zephyr project. I represent Nordic on the board. Here we have a gaming mouse. This is some plastics developed by one of our partners. Is it on the market? It is not on the market. It will be a reference design from Nordic. To run Zephyr in a mouse. It does run Zephyr on the mouse. This particular unit can do proprietary connections or it can do Bluetooth Low Energy standard connections to the laptop hardware here. So this is running the mouse through Bluetooth Low Energy. Or you can connect it with the USB cable. So it will switch cleanly from Bluetooth Low Energy to USB. And it's a very high resolution sensor and we can do very high report rates with this. A one millisecond report rate to a laptop and one millisecond report rates over USB. So all these stacks are from the open source project. Is it an Cortex M33? No. This is a Cortex M4F. This is our NR52 series inside this product. NR52? NR52, yeah. So it's already a huge quantity? Absolutely, yeah, yeah. Is one of your best selling parts? It is, it is. The highest running part. We have five devices in the series today ranging from small kind of low flash devices up to the higher end that run multiple protocols So what do you want to run Zephyr into mouse? What is it going to bring? So if you think about a mouse manufacturer or a hardware manufacturer doing a very wide product line then they have a challenge that these are very simple applications but they need to release maybe 15 products a year. And to develop with the on top of the RTOS services or the services offered by the RTOS they can reuse so much of their application code over and over again and they only need to test the applications as they change in between hardware. When you have to develop something bare metal without the use of an RTOS and without the services of the RTOS then doing that many products a year you can get into trouble with your re-usability of code test and quality. Alright, so but a mouse is not just pointing an error around? That's it? It is. I don't know who it is. But doing it at a high report rate with a high resolution sensor and over USB and over wireless that starts to be a real time problem. And that's why you need an RTOS? Yes. Do many mouse have RTOS? No, it would, well I don't know but I do know that a lot of the hardware will run bare metal as they say so without an RTOS. But like I said as design cycles are shortening and products are being rolled out faster it's more and more important to write less code every time you do a new product and this is the way to do it. Awesome. What is this one? So this one's the NRA of 916 that's an NB IoT and LTE M device. This is the chip here. It's actually what we call a system in package. It is power management, RF front-end for all the supported bands of LTE M and NB IoT and modem chip with an application processor. So you can do a system on chip, low power system on chip design just with this silicon here. Is it a Cortex M? This is a Cortex M33. That's one of the new ones. Yes, that's right. This is brand new silicon. This is going to production in the coming months. And so it has all the security stuff that's new in M? That's right. So how does it get into that? So there's been work recently on putting M33 or RMA support in Zephyr so it's possible to do secure and non-secure callable functions. And the device or the implementation of the M33 actually requires you to do a what we call a security unit which is more than an MPU. It actually secures memory and peripherals. So we've got that implementation there and when you boot into this device that security peripheral will verify the images on the device and also configure the non-secure regions for the non-secure application. So you have this separation between secure region and non-secure. The crypto libraries, for example, run in the secure region and talk to the crypto accelerator hardware from the secure region. So is Nordic one of the first to run M33? We were actually, I think the first to announce publicly that we were doing an M33 but we weren't the first to put it into production. But those products were without a radio. So this is a much more complex product. Can I get my control of SAC? Yes, it is. Can you call it? SAC, you call it? Assistive in package. But it does have an application processor so you do not need to add another chip. You only need this chip that will run both the application and the modem and everything you need is in package apart from the SIM card which is over here and the antenna. So this is the antenna here? Yes. And where is it along with this? Basically being able to have debug headers and the debugger is so good here. So how much is this coming soon? It's available now from distribution, the exact price tag, I can't tell you right now. It is shipping, this kit is shipping. And this is production silicon. Production silicon shipping, NRF 9160 was Zephyr. And Zephyr is just the best to use on this, right? Absolutely. We really believe in the project. It's multi-architecture, it's multiple platforms built on Linux, Windows and Mac. It's very scalable. So this is another thing. These products, there's going to be more complex applications on these types of products. So this is a bigger flash memory device, a lot more RAM. But you can run a, this one has a mega flash. Yep, and 256k of RAM. And this mouse product can run as low as 192k of flash and 24k of RAM. So the scalability that Zephyr allows you can use more of the out source or less of the out source based on the complexity of the application. So you can choose and build how big the Zephyr you want. Yes, it goes as shown here. Also like the micro bit for example running Zephyr with Bluetooth mesh with 16k of RAM. This guy here also running Zephyr. This is a badge that is running on Nordic NRF 52. That's Bluetooth and it has Bluetooth mesh. It was produced for the Zephyr project by Phytic. And it has our software running fully supported with Zephyr. And there are plans actually to add expansion guards, you know, for different technologies, being able to have different chips here. So actually I don't have it right now but you can have an NXP module or an NRF or SD micro. And, sorry? How can you put the modules? I don't have it here right now. Does it go under here? What's his name? Johan. Johan. Let's go to Johan. He's added most of them. Johan. What is the other one? With the NXP? I don't have one. It doesn't have it. What is the other latest stuff maybe he can talk about? He's our Bluetooth expert. You interviewed him last year as well. So what's the latest with Bluetooth? Is it like even better than last year? Of course, it's getting better every year. So what's happening? Well, we are improving the existing Bluetooth Mesh Support that we have. We have added new features from Bluetooth 5. The Bluetooth 5.1 specification was released just very recently, I think in the past month or so. 5.1 specification? Yeah, yeah. What's new with 5.1? There's something called the direction finding. So you can figure out which direction the signal comes from and you can do, for example, implement some massive tracking use cases like that. So it says Bluetooth Mesh Badge. Yes. Is that what you have? It does mesh. Yeah, so we have all of these badges in the same Bluetooth Mesh network. And a little battery kind of runs the thing? There's a AAA battery at the back of it, yeah. And then it meshes around to do it? If I press a button, let's see. On us, is your badge enabled? If I press that button here, then you can see it. Oh, you're pinging everybody else? We can say it. Okay, you press the button now. All right. And everybody who has it would have it. And I'll press the button. I see you also linking. Nice. That's really cool. So it works, it's stable. The whole mesh is not, it's complicated to do good mesh, no? So the main thing people are talking about also? Sure. Bluetooth Mesh is quite different from that. But yeah, it's stable. We've had it available ever since the specification came public. So that was one and a half years ago. So we've had also lots of time since then to improve it and to make it stable. So it should be pretty good by now. Cool. All right, that's awesome. And it's working super stable with the Zephyr. Yes, yes it is. Is Zephyr the best way to do it? Well, we were the first open source implementation of Bluetooth Mesh. There are actually not that many around. I can't say if it's the best one since I haven't actively tried many, many others. But there are many people using it and we've had lots of time to make it good and stabilize. Cool. Well, what else is happening here? Is it an XP? Are you filming now or are you telling when the light is on? Yeah, it's still filming. Cool. So I'll try to add some more just later.