March 18, 2025 • 18 mins
This EdgeVerse Techcast episode delves into the Real-Time Edge software framework designed for industrial applications. It supports NXP i.MX and Layerscape Application Processors and i.MX RT1180 Microcontrollers. Hosts Bridgette and Kyle welcome Zbynek Fedra, an experienced technical marketing expert at NXP.
Zbynek details how Real-Time Edge helps developers:
- Enable same chip to run both high-level operating systems (Linux) and low-latency Real-Time operating systems (Zephyr, FreeRTOS)
- Use the software framework to add industrial protocols like CANopen, EtherCAT, TSN, Modbus, OPC UA
- Develop with Yocto build system environment
- Allocate resources and communicate between multiple cores and operating systems
The Real-Time Edge is ideal for applications like Factory or Building automation, Industrial Switches or even Machine vision.
To get started, developers can refer to NXP's resources at nxp.com/rtedge or email rtedge@nxp.com.
The hosts encourage listeners to like, subscribe, and set notifications for weekly updates.
(00:00) Introduction
(00:59) Meet Guest-Zbynek Fedra
(02:41) Understanding Real-Time Edge
(06:57) Software Framework
(09:27) Getting Started
(11:22) MCU and MPU Support
(13:49) Industrial Protocols
(15:30) Resources
(15:56) Wrap Up
Mark as Played
Transcript
Episode Transcript
Available transcripts are automatically generated. Complete accuracy is not guaranteed.
Bridgette Stone (00:10):
Welcome everyone to this week's episode of the NXP
EdgeVerse Techcast, where you'lllearn about NXP software, tools,
and enablement that support NXPprocessors and microcontrollers.
This is Bridgette, and we'reback again with another episode.
Kyle Dando (00:26):
Yes, we are Bridgette.
And you know what?
I think we're startingto get into a groove.
Bridgette Stone (00:31):
That we are.
Kyle Dando (00:33):
So what do you have in store for our listeners on today's Techcast?
Bridgette Stone (00:37):
Today we will introduce everyone to the Real-Time Edge.
This falls into our toolscategory that helps developers
design with NXP solutions.
Specifically, the Real-TimeEdge supports NXP's portfolio
of i.MX Applications Processors.
But, I will let our guest providea more accurate introduction.
Who is our guest today, Kyle?
Kyle Dando (00:59):
Well, he's our colleague.
Our guest today is Zbynek Fedra.
He's from NXP.
He's based in the Czech Republic.
Zbynek, you have worked at NXP inmany different areas, and I know
that this provides you a greatunderstanding of all the software
that's involved and developed by NXP.
(01:20):
Can you talk to the customers abouthow maybe your experience helps you
work with the Real-Time Edge software?
Zbynek Fedra (01:29):
Yes, definitely.
Hello, Bridgette.
Hello, Kyle.
Thank you for inviting me to your podcast.
And I am working in NXPfor quite a long time.
And I switched through multiple project.
I started on the voice assistantprojects on the MCU on the MPU.
(01:51):
We were integrating thirdparty voice assistant projects.
Then I was working a little bit with themotor control guys on the different topic.
And then I was also part ofthe SDK team working on the
drivers and audio stuff for MCUs.
And from that, I switched slightlyoff of the embedded developer.
(02:14):
And now I am a technical marketing guyand I am working with Real-Time Edge
team on this very interesting project.
Bridgette Stone (02:24):
Very cool.
And a super unique path to get towhere you are today and working on
all different types of projects.
I'm excited to hear moreabout the Real-Time Edge.
Are you ready to jumpinto our first question?
Zbynek Fedra (02:37):
Yes, let's go.
Bridgette Stone (02:39):
So I'm going to start with the easiest one.
Can you just provide us with an overviewof what the Real-Time Edge is and what
are some of the most common applications?
Zbynek Fedra (02:48):
Yeah, definitely.
In a nutshell, Real-Time Edgeis the software framework.
And it's a software framework forspecifically industrial system
designs for customers who want todevelop the versatile industrial
system based on our platforms.
It includes multiple components and It'snot only operating systems or support of
(03:13):
multiple operating systems, but we arealso introducing lots of optimizations for
latency networking protocol or industrialcommunication protocols, which are very
handy for this kind of the applications.
When you are designing yourindustrial system, you are usually
focusing on multiple criteria.
(03:34):
On the one hand, you want to havesystem which is as fast as possible.
But on the other hand, you alsowant to have the operating system
which provides you lots of tools andalready available stacks, usually
Linux operating system provides.
Then you want to optimize the ethernet orany industrial stack to the lowest level.
(04:00):
It's very tricky to get this withthe system, which is at the same
time high level and providingall the tools and like Linux is.
And that's where actually the Real-TimeEdge is helping a lot because it enables
you to have both or multiple systemsrunning on the same chip at the same time.
(04:21):
On the one hand, you may have the Linuxbased system with nice HDMI, with all
the tools and connections and stacksyou are used to and other, on the other
hand, you may have, uh, on different,uh, core running the real time operating
system like RTOS, Zephyr or even baremetal application, which is, uh, tuned
(04:46):
to best performance, very low latency,and you can use it, for example, for
controlling 64 servers from the MPU.
Real-Time Edge provides a flexibleway how to allocate resources to
different operating systems and alsohow to run side by side on single
(05:07):
chip, multiple operating systems.
So for one customer, it may be interestingto have MPU with four application cores,
where one will be running the Linuxsystem and three cores will be running
real time OS or bare metal application.
On the other hand, there are othercustomers who are more looking to
(05:31):
Linux operating systems running onmultiple cores, and they just want to
save one core for a real time operatingsystem or bare metal application.
And that's the case, the Real-Time Edgehelps you to set these resources, to
set the system according to your needs.
And this is not.
(05:51):
The only reason we are also supportingmultiple industrial protocols, multiple
networking standard, especiallylooking for low latency communications,
deterministic communicationand redundancy of the network.
Currently, the majority of the customersactually in the space of industrial
(06:12):
switches, machine vision, buildingcontrollers, or time sensitive networking.
Kyle Dando (06:19):
Okay, I get it.
So, what you describe there is alot of these higher end application
processors or these applications,they enjoy having the operating system
flexibility, but they need that, as yousaid, deterministic response time for
some of these real time applications.
So that's where, as you mentioned,these industrial switches or machine
(06:43):
vision, those types of applicationsrequire that deterministic response.
Also, the communication, all thesecomplex stacks and protocols.
So that's, in a nutshell,what you said there.
Zbynek Fedra (06:54):
Yes, you understand it very, very well.
Kyle Dando (06:56):
All right.
Well, you started by mentioningthat at the highest level, the
Real-Time Edge is software framework.
Can you talk a little bit moreabout what you mean by providing
customers a software framework?
Zbynek Fedra (07:10):
Uh, yes, we are actually starting with something
we called NXP Linux BSP.
It's the Linux board support package.
This is standard Linux package, which isavailable for our application processors.
On top of this Linux BSP, we areintroducing some patches, as I
(07:33):
mentioned, focused mainly on lowlatency and industrial applications.
And together with these patches andsome updates, we are integrating
it with the help of the Yocto.
Yocto is a build system for Linux,and it helps you to have everything
on the same place with all the tools,all the parts you need to create
(07:57):
your own system or application.
And this system with the Linux orwe are usually using a real time
patch for this Linux to have the realtime performance or closer to real
time performance on the Linux side.
So this system is then accomplished withthe add ons of FreeRTOS or Zephyr, or
(08:21):
enablement of bare metal applications.
So everything is packed in one systemin this, uh, Yocto build system.
And you don't need toleave this environment.
You can in the same environment, prepareyour system image, which will include
Linux part, RTOS part, some optimizations,stacks, bare metal part, and everything is
(08:44):
packed in this, Real-Time Edge framework.
These layers in Yocto are also expandedwith the Time Sensitive Networking
protocol, with the support of thisprotocol, with the industrial standards
stacks as the EtherCAT main device orEtherCAT subordinate device, OPC UI,
(09:06):
Modbus, Profibus, and others which areused in the industrial applications.
Sometimes it is provided aspart of the Real-Time Edge.
Sometimes you need to use theintegration only, and the stack itself
is provided as the third party component.
Bridgette Stone (09:25):
Thanks, Zbynek.
That, at least for me, provides a highlevel of understanding the framework,
an overview of the Real-Time Edge,and I guess what I'm most excited
to hear about is how do listenersget their hands on Real-Time Edge?
What platforms are supportedand is it free to use?
Zbynek Fedra (09:43):
Okay, the main target platforms are, of course, the ones
targeted by industrial use cases.
Currently, we are supportingmultiple MPUs from our portfolio.
It's, for example, i.MX 8M family.
i.MX 9 family, and we are alsoworking hard on the support of
the new i.MX 94 family, which isespecially oriented for safe and secure
(10:10):
industrial and automotive applications.
And the Real-Time Edge isnaturally the good, or very, very
good fit for these applications.
All of these platforms have thedifferences in the different hardware
resources in the different use cases anda different fit for the applications.
(10:30):
So not all options are actuallyavailable on every platform.
And we have also lots of softwarecomponents which are available as
the customers are requesting them.
So if there is some platformwhich has specific use case, we
are with the priority porting thestacks and software and specific
(10:52):
enablements for these platforms.
And this is then also shared withthe generic Real-Time Edge, and it's
available for all the customers.
The core of the Real-TimeEdge is available for free.
What may be limited is, as Imentioned, third party stacks.
Then you need to have some license fromthat third party on using that stack.
Bridgette Stone (11:14):
You mentioned the wonderful support for some of our most
popular products in our MPU portfolio.
What does the support looklike for the MCU or the
microcontroller side of the house?
Zbynek Fedra (11:27):
That's interesting topic because with the MCU portfolio, we
may actually be also talking about theApplication Processors , MPUs, which have,
as the part of the chip, also the Cortex-Mcore, which is considered to be the MCU.
So, uh, we are supporting this MCUcourse also, and you can build a
(11:51):
heterogeneous system, which is actuallyconsisting of the MPU and MCU or.
specifically Cortex-A and Cortex-Mand you can have this solution working
together, and for the next even morewe are supporting some use cases where
you are actually connecting two chips.
(12:13):
One is MPU and one is industrial MCUin our case it's currently mainly
i.MX RT1180 and you can have somebenefits from the system, which is
actually covering MPU and MCU together.
Bridgette Stone (12:29):
So to summarize, we have system ready support for
industrial applications and designs.
And I guess, continuing on, what does NXPprovide to get the developers started?
Zbynek Fedra (12:42):
Yeah, first you are starting with the development environment.
With the Yocto build system, you have thetoolchain available, you have everything
ready for building your app, and youhave also the support for different
cores and different operating systems.
Part of Real-Time Edge are also theutilities and tools which will help
(13:04):
you to build the application whichhas proper communication between
these different cores or betweenthese different operating systems.
You can use high speed data transfersand the virtual IOs to share that
data or peripheral access between thedifferent cores or different systems.
Kyle Dando (13:25):
Okay, so now you're talking about the communication.
So you have Yocto installed as a developerand now they want to explore those
industrial protocols you talked about.
So what does NXP provide to assistthose users to get started with those
complex industrial protocols thatyou mentioned earlier within the
Real-Time Edge Yocto environment?
Zbynek Fedra (13:48):
Uh, yes, a big part of Industrial Systems is
communication with external world.
In Real-Time Edge, we are supporting TimeSensitive Networking, or you can, uh, hear
about that in the abbreviation as TSN.
It's actually IEEE standard,which is extension of, uh,
standard Ethernet technology.
(14:08):
It uses combination of hardwarecapabilities and the protocol stack
to prioritize, uh, latency sensitiveworkload over non critical workloads.
Also, there are differentindustrial protocols which are
part of the Real-Time Edge.
Some of them are developed or implementedinternally, some of them are third party.
(14:29):
If we will, for example, takeEtherCAT protocol, we are supporting
EtherCAT main device stack on themultiple i.MX Application Processors
and also on Layerscape processors.
You can choose to run thisstack either on Cortex-A or
Cortex-M based on your use case.
And the Real-Time Edge also supportsthe optimized, the Linux Ethernet driver
(14:55):
that gives to this target main deviceprotocol stack, exclusive and direct
access to internet hardware and thatimproves the application performance.
This is just one example of optimizationsand options we have in our Real-Time Edge.
For other communications stacks,I should probably mention things
(15:16):
like Modbus, CANopen, or OPC UA.
Bridgette Stone (15:21):
So as a marketer, I love an easy way to communicate
to our engineers and developershow easy it is to get started.
So as we wrap up, can you let theaudience know where they should go to
get more info and quickly get started?
Zbynek Fedra (15:37):
The first point would be probably our webpage
which is on NXP.Com/RTedge . Andwe have also email you can send any
question to and it's rtedge@nxp.com.
Bridgette Stone (15:50):
Thanks Zbynek.
We'll make sure to add thoseinto our TechCasts notes.
Kyle Dando (15:55):
All right.
Well, this has been great, Zbynek.
We really appreciate you taking the time.
I know that Bridgette and I learned aton, and hopefully the listeners did.
If I can break it down, I believethat they'll find all this information
on the RT Edge website, but you guysare providing this software framework
that primarily runs on our ApplicationProcessors that are running these Linux
(16:20):
or operating systems that you mentioned.
And there's this necessarycomponent to really have responsive,
deterministic interfaces.
Whether it's between systems or withthe input coming into these products.
And so the Real-Time Edge softwarethat you and your team are providing
to customers allows that datasharing between the A cores and the
(16:45):
M cores, or even within the A cores.
It also allows those multi-chipsolutions to transfer this real time
data into these operating systems.
And so when the applications thatthese customers are trying to solve
require these Real Time stimuluses withthis reliable, dependable operating
(17:07):
system, they should definitelylook into the Real-Time Edge.
Is that safe to assume for our listeners?
Zbynek Fedra (17:14):
Definitely, Kyle.
Kyle Dando (17:16):
Okay.
Well, hopefully our listenersappreciate the time you spent.
I know we do.
I want to turn it over to you,Bridgette, so that you can wrap up.
But again, thank you Zbynekfor the time and all the extra
knowledge you shared with us.
Bridgette Stone (17:33):
Super cool to learn about.
Thank you Zbynek a lot for beinghere and sharing your wealth of
knowledge with us and to our listeners.
We ask you to like, subscribe,and set up notifications.
We're releasing weekly.
So we'll see you next Tuesday.
Kyle Dando (17:50):
All right.
And everyone, thanks for your time.
And until next time go outand enjoy the Edgeverse.
Welcome everyone to this week's episode of the NXP
EdgeVerse Techcast, where you'lllearn about NXP software, tools,
and enablement that support NXPprocessors and microcontrollers.
This is Bridgette, and we'reback again with another episode.
Kyle Dando (00:26):
Yes, we are Bridgette.
And you know what?
I think we're startingto get into a groove.
Bridgette Stone (00:31):
That we are.
Kyle Dando (00:33):
So what do you have in store for our listeners on today's Techcast?
Bridgette Stone (00:37):
Today we will introduce everyone to the Real-Time Edge.
This falls into our toolscategory that helps developers
design with NXP solutions.
Specifically, the Real-TimeEdge supports NXP's portfolio
of i.MX Applications Processors.
But, I will let our guest providea more accurate introduction.
Who is our guest today, Kyle?
Kyle Dando (00:59):
Well, he's our colleague.
Our guest today is Zbynek Fedra.
He's from NXP.
He's based in the Czech Republic.
Zbynek, you have worked at NXP inmany different areas, and I know
that this provides you a greatunderstanding of all the software
that's involved and developed by NXP.
(01:20):
Can you talk to the customers abouthow maybe your experience helps you
work with the Real-Time Edge software?
Zbynek Fedra (01:29):
Yes, definitely.
Hello, Bridgette.
Hello, Kyle.
Thank you for inviting me to your podcast.
And I am working in NXPfor quite a long time.
And I switched through multiple project.
I started on the voice assistantprojects on the MCU on the MPU.
(01:51):
We were integrating thirdparty voice assistant projects.
Then I was working a little bit with themotor control guys on the different topic.
And then I was also part ofthe SDK team working on the
drivers and audio stuff for MCUs.
And from that, I switched slightlyoff of the embedded developer.
(02:14):
And now I am a technical marketing guyand I am working with Real-Time Edge
team on this very interesting project.
Bridgette Stone (02:24):
Very cool.
And a super unique path to get towhere you are today and working on
all different types of projects.
I'm excited to hear moreabout the Real-Time Edge.
Are you ready to jumpinto our first question?
Zbynek Fedra (02:37):
Yes, let's go.
Bridgette Stone (02:39):
So I'm going to start with the easiest one.
Can you just provide us with an overviewof what the Real-Time Edge is and what
are some of the most common applications?
Zbynek Fedra (02:48):
Yeah, definitely.
In a nutshell, Real-Time Edgeis the software framework.
And it's a software framework forspecifically industrial system
designs for customers who want todevelop the versatile industrial
system based on our platforms.
It includes multiple components and It'snot only operating systems or support of
(03:13):
multiple operating systems, but we arealso introducing lots of optimizations for
latency networking protocol or industrialcommunication protocols, which are very
handy for this kind of the applications.
When you are designing yourindustrial system, you are usually
focusing on multiple criteria.
(03:34):
On the one hand, you want to havesystem which is as fast as possible.
But on the other hand, you alsowant to have the operating system
which provides you lots of tools andalready available stacks, usually
Linux operating system provides.
Then you want to optimize the ethernet orany industrial stack to the lowest level.
(04:00):
It's very tricky to get this withthe system, which is at the same
time high level and providingall the tools and like Linux is.
And that's where actually the Real-TimeEdge is helping a lot because it enables
you to have both or multiple systemsrunning on the same chip at the same time.
(04:21):
On the one hand, you may have the Linuxbased system with nice HDMI, with all
the tools and connections and stacksyou are used to and other, on the other
hand, you may have, uh, on different,uh, core running the real time operating
system like RTOS, Zephyr or even baremetal application, which is, uh, tuned
(04:46):
to best performance, very low latency,and you can use it, for example, for
controlling 64 servers from the MPU.
Real-Time Edge provides a flexibleway how to allocate resources to
different operating systems and alsohow to run side by side on single
(05:07):
chip, multiple operating systems.
So for one customer, it may be interestingto have MPU with four application cores,
where one will be running the Linuxsystem and three cores will be running
real time OS or bare metal application.
On the other hand, there are othercustomers who are more looking to
(05:31):
Linux operating systems running onmultiple cores, and they just want to
save one core for a real time operatingsystem or bare metal application.
And that's the case, the Real-Time Edgehelps you to set these resources, to
set the system according to your needs.
And this is not.
(05:51):
The only reason we are also supportingmultiple industrial protocols, multiple
networking standard, especiallylooking for low latency communications,
deterministic communicationand redundancy of the network.
Currently, the majority of the customersactually in the space of industrial
(06:12):
switches, machine vision, buildingcontrollers, or time sensitive networking.
Kyle Dando (06:19):
Okay, I get it.
So, what you describe there is alot of these higher end application
processors or these applications,they enjoy having the operating system
flexibility, but they need that, as yousaid, deterministic response time for
some of these real time applications.
So that's where, as you mentioned,these industrial switches or machine
(06:43):
vision, those types of applicationsrequire that deterministic response.
Also, the communication, all thesecomplex stacks and protocols.
So that's, in a nutshell,what you said there.
Zbynek Fedra (06:54):
Yes, you understand it very, very well.
Kyle Dando (06:56):
All right.
Well, you started by mentioningthat at the highest level, the
Real-Time Edge is software framework.
Can you talk a little bit moreabout what you mean by providing
customers a software framework?
Zbynek Fedra (07:10):
Uh, yes, we are actually starting with something
we called NXP Linux BSP.
It's the Linux board support package.
This is standard Linux package, which isavailable for our application processors.
On top of this Linux BSP, we areintroducing some patches, as I
(07:33):
mentioned, focused mainly on lowlatency and industrial applications.
And together with these patches andsome updates, we are integrating
it with the help of the Yocto.
Yocto is a build system for Linux,and it helps you to have everything
on the same place with all the tools,all the parts you need to create
(07:57):
your own system or application.
And this system with the Linux orwe are usually using a real time
patch for this Linux to have the realtime performance or closer to real
time performance on the Linux side.
So this system is then accomplished withthe add ons of FreeRTOS or Zephyr, or
(08:21):
enablement of bare metal applications.
So everything is packed in one systemin this, uh, Yocto build system.
And you don't need toleave this environment.
You can in the same environment, prepareyour system image, which will include
Linux part, RTOS part, some optimizations,stacks, bare metal part, and everything is
(08:44):
packed in this, Real-Time Edge framework.
These layers in Yocto are also expandedwith the Time Sensitive Networking
protocol, with the support of thisprotocol, with the industrial standards
stacks as the EtherCAT main device orEtherCAT subordinate device, OPC UI,
(09:06):
Modbus, Profibus, and others which areused in the industrial applications.
Sometimes it is provided aspart of the Real-Time Edge.
Sometimes you need to use theintegration only, and the stack itself
is provided as the third party component.
Bridgette Stone (09:25):
Thanks, Zbynek.
That, at least for me, provides a highlevel of understanding the framework,
an overview of the Real-Time Edge,and I guess what I'm most excited
to hear about is how do listenersget their hands on Real-Time Edge?
What platforms are supportedand is it free to use?
Zbynek Fedra (09:43):
Okay, the main target platforms are, of course, the ones
targeted by industrial use cases.
Currently, we are supportingmultiple MPUs from our portfolio.
It's, for example, i.MX 8M family.
i.MX 9 family, and we are alsoworking hard on the support of
the new i.MX 94 family, which isespecially oriented for safe and secure
(10:10):
industrial and automotive applications.
And the Real-Time Edge isnaturally the good, or very, very
good fit for these applications.
All of these platforms have thedifferences in the different hardware
resources in the different use cases anda different fit for the applications.
(10:30):
So not all options are actuallyavailable on every platform.
And we have also lots of softwarecomponents which are available as
the customers are requesting them.
So if there is some platformwhich has specific use case, we
are with the priority porting thestacks and software and specific
(10:52):
enablements for these platforms.
And this is then also shared withthe generic Real-Time Edge, and it's
available for all the customers.
The core of the Real-TimeEdge is available for free.
What may be limited is, as Imentioned, third party stacks.
Then you need to have some license fromthat third party on using that stack.
Bridgette Stone (11:14):
You mentioned the wonderful support for some of our most
popular products in our MPU portfolio.
What does the support looklike for the MCU or the
microcontroller side of the house?
Zbynek Fedra (11:27):
That's interesting topic because with the MCU portfolio, we
may actually be also talking about theApplication Processors , MPUs, which have,
as the part of the chip, also the Cortex-Mcore, which is considered to be the MCU.
So, uh, we are supporting this MCUcourse also, and you can build a
(11:51):
heterogeneous system, which is actuallyconsisting of the MPU and MCU or.
specifically Cortex-A and Cortex-Mand you can have this solution working
together, and for the next even morewe are supporting some use cases where
you are actually connecting two chips.
(12:13):
One is MPU and one is industrial MCUin our case it's currently mainly
i.MX RT1180 and you can have somebenefits from the system, which is
actually covering MPU and MCU together.
Bridgette Stone (12:29):
So to summarize, we have system ready support for
industrial applications and designs.
And I guess, continuing on, what does NXPprovide to get the developers started?
Zbynek Fedra (12:42):
Yeah, first you are starting with the development environment.
With the Yocto build system, you have thetoolchain available, you have everything
ready for building your app, and youhave also the support for different
cores and different operating systems.
Part of Real-Time Edge are also theutilities and tools which will help
(13:04):
you to build the application whichhas proper communication between
these different cores or betweenthese different operating systems.
You can use high speed data transfersand the virtual IOs to share that
data or peripheral access between thedifferent cores or different systems.
Kyle Dando (13:25):
Okay, so now you're talking about the communication.
So you have Yocto installed as a developerand now they want to explore those
industrial protocols you talked about.
So what does NXP provide to assistthose users to get started with those
complex industrial protocols thatyou mentioned earlier within the
Real-Time Edge Yocto environment?
Zbynek Fedra (13:48):
Uh, yes, a big part of Industrial Systems is
communication with external world.
In Real-Time Edge, we are supporting TimeSensitive Networking, or you can, uh, hear
about that in the abbreviation as TSN.
It's actually IEEE standard,which is extension of, uh,
standard Ethernet technology.
(14:08):
It uses combination of hardwarecapabilities and the protocol stack
to prioritize, uh, latency sensitiveworkload over non critical workloads.
Also, there are differentindustrial protocols which are
part of the Real-Time Edge.
Some of them are developed or implementedinternally, some of them are third party.
(14:29):
If we will, for example, takeEtherCAT protocol, we are supporting
EtherCAT main device stack on themultiple i.MX Application Processors
and also on Layerscape processors.
You can choose to run thisstack either on Cortex-A or
Cortex-M based on your use case.
And the Real-Time Edge also supportsthe optimized, the Linux Ethernet driver
(14:55):
that gives to this target main deviceprotocol stack, exclusive and direct
access to internet hardware and thatimproves the application performance.
This is just one example of optimizationsand options we have in our Real-Time Edge.
For other communications stacks,I should probably mention things
(15:16):
like Modbus, CANopen, or OPC UA.
Bridgette Stone (15:21):
So as a marketer, I love an easy way to communicate
to our engineers and developershow easy it is to get started.
So as we wrap up, can you let theaudience know where they should go to
get more info and quickly get started?
Zbynek Fedra (15:37):
The first point would be probably our webpage
which is on NXP.Com/RTedge . Andwe have also email you can send any
question to and it's rtedge@nxp.com.
Bridgette Stone (15:50):
Thanks Zbynek.
We'll make sure to add thoseinto our TechCasts notes.
Kyle Dando (15:55):
All right.
Well, this has been great, Zbynek.
We really appreciate you taking the time.
I know that Bridgette and I learned aton, and hopefully the listeners did.
If I can break it down, I believethat they'll find all this information
on the RT Edge website, but you guysare providing this software framework
that primarily runs on our ApplicationProcessors that are running these Linux
(16:20):
or operating systems that you mentioned.
And there's this necessarycomponent to really have responsive,
deterministic interfaces.
Whether it's between systems or withthe input coming into these products.
And so the Real-Time Edge softwarethat you and your team are providing
to customers allows that datasharing between the A cores and the
(16:45):
M cores, or even within the A cores.
It also allows those multi-chipsolutions to transfer this real time
data into these operating systems.
And so when the applications thatthese customers are trying to solve
require these Real Time stimuluses withthis reliable, dependable operating
(17:07):
system, they should definitelylook into the Real-Time Edge.
Is that safe to assume for our listeners?
Zbynek Fedra (17:14):
Definitely, Kyle.
Kyle Dando (17:16):
Okay.
Well, hopefully our listenersappreciate the time you spent.
I know we do.
I want to turn it over to you,Bridgette, so that you can wrap up.
But again, thank you Zbynekfor the time and all the extra
knowledge you shared with us.
Bridgette Stone (17:33):
Super cool to learn about.
Thank you Zbynek a lot for beinghere and sharing your wealth of
knowledge with us and to our listeners.
We ask you to like, subscribe,and set up notifications.
We're releasing weekly.
So we'll see you next Tuesday.
Kyle Dando (17:50):
All right.
And everyone, thanks for your time.
And until next time go outand enjoy the Edgeverse.
Popular Podcasts
Dateline NBC
Current and classic episodes, featuring compelling true-crime mysteries, powerful documentaries and in-depth investigations. Follow now to get the latest episodes of Dateline NBC completely free, or subscribe to Dateline Premium for ad-free listening and exclusive bonus content: DatelinePremium.com
24/7 News: The Latest
The latest news in 4 minutes updated every hour, every day.
Therapy Gecko
An unlicensed lizard psychologist travels the universe talking to strangers about absolutely nothing. TO CALL THE GECKO: follow me on https://www.twitch.tv/lyleforever to get a notification for when I am taking calls. I am usually live Mondays, Wednesdays, and Fridays but lately a lot of other times too. I am a gecko.