in a real application!
> While this is exciting, I do have a question: considering an MCU with a
> Memory Protection Unit, is it possible to have some threads running
> isolated from each other? I understand that using the protected build we
> can only have two spaces: kernel and user.
I understand that using the protected build we
> > can only have two spaces: kernel and user. So if I wanted to have
> protected
> > threads running in such a system, they would have to be built as part of
> > the kernel blob and thus, would all have access to the same address
&g
> - You cannot use all normal application interfaces. You have to use
> internal OS interfaces. For example, you cannot call printf() in the OS
> but you can call syslog(). You should not use file descriptors. Instead,
> there are are special OS internal interfaces for file system access,
> net
> ... I do have a question: considering an MCU with a
> Memory Protection Unit, is it possible to have some threads running
> isolated from each other? I understand that using the protected build we
> can only have two spaces: kernel and user. So if I wanted to have
protected
> thr
other? I understand that using the protected build we
can only have two spaces: kernel and user. So if I wanted to have protected
threads running in such a system, they would have to be built as part of
the kernel blob and thus, would all have access to the same address space.
Is it possible to have
