Lines Matching full:embedded

324     Zephyr layering when built against an embedded target (left), and targeting a native_simulator
334 When building targeting Zephyr's :ref:`native_sim<native_sim>` board, we build our embedded SW,
339 embedded SW.
341 And after both the "embedded SW" and the runner will be linked together to form the final Linux
358 embedded Zephyr image can be build for each MCU, and all MCU images and the runner are assembled
361 Native simulator runner context and the embedded context
364 It is worth noting that the embedded SW library is first pre-linked. That is that all symbols which
368 neither from the runner itself or from other CPUs embedded SW libraries.
370 linker script in that first embedded SW library link.
372 When the embedded SW is built, one has the option of linking an embedded C standard library with it,
377 One is the embedded/Zephyr context, in which we build the Zephyr OS, an application for a given MCU,
378 and which may be built with an embedded C library.
380 limited visibility into the embedded context.
382 From the embedded context we can easily call into the runner context: All runner context symbols
383 will be linkable in the final link stage unless another embedded symbol with the same name was
385 But from the runner context only the symbols from the embedded context annotated with the
446 You can find information about how the native simulator runs the embedded SW in its
479 These allow registering (at build/link time) embedded context functions which will be called