Home
last modified time | relevance | path

Searched refs:real (Results 76 – 100 of 235) sorted by relevance

12345678910

/Zephyr-latest/samples/bluetooth/bap_unicast_client/
DREADME.rst66 Similarly to how you would for real HW, you can do:
/Zephyr-latest/samples/bluetooth/bap_unicast_server/
DREADME.rst66 Similarly to how you would for real HW, you can do:
/Zephyr-latest/samples/bluetooth/cap_acceptor/
DREADME.rst57 Similarly to how you would for real HW, you can do:
/Zephyr-latest/samples/bluetooth/cap_initiator/
DREADME.rst57 Similarly to how you would for real HW, you can do:
/Zephyr-latest/samples/bluetooth/pbp_public_broadcast_sink/
DREADME.rst59 Similarly to how you would for real HW, you can do:
/Zephyr-latest/samples/bluetooth/pbp_public_broadcast_source/
DREADME.rst59 Similarly to how you would for real HW, you can do:
/Zephyr-latest/boards/native/nrf_bsim/doc/
Dnrf5340bsim.rst53 Note that unlike a real nrf5340 device, the nrf5340bsim boards have unlimited RAM and flash for
77 Unlike in real HW, the net core MCU is set-up to automatically boot at start, to facilitate
/Zephyr-latest/boards/toradex/verdin_imx8mp/doc/
Dindex.rst38 cores support both real-time trace through the ETM system and static debugging via JTAG.
39 Furthermore, the platform features support for real-time trace capabilities, achieved through ARM's
274 https://developer.toradex.com/software/real-time/cortex-m/how-to-load-binaries
277 https://developer.toradex.com/software/real-time/cortex-m/cortexm-jtag-debugging/
/Zephyr-latest/boards/native/nrf_bsim/
Dnrf5340bsim_nrf5340_cpuapp.dts132 /* We re-use the IPC shared buffer definition from the real HW. But note the start address of the
/Zephyr-latest/boards/renesas/rcar_spider_s4/doc/
Drcar_spider_a55.rst12 The software package supports the real-time cores with various drivers and basic software
/Zephyr-latest/samples/net/sockets/dumb_http_server_mt/src/
Dresponse_big.html.bin27 …eaders from across the industry to build a best-in-breed small, scalable, real-time operating syst…
/Zephyr-latest/samples/net/sockets/dumb_http_server/src/
Dresponse_big.html.bin27 …eaders from across the industry to build a best-in-breed small, scalable, real-time operating syst…
/Zephyr-latest/samples/bluetooth/bap_broadcast_sink/
DREADME.rst62 Similarly to how you would for real HW, you can do:
/Zephyr-latest/samples/bluetooth/bap_broadcast_source/
DREADME.rst63 Similarly to how you would for real HW, you can do:
/Zephyr-latest/samples/bluetooth/ccp_call_control_client/
DREADME.rst60 Similarly to how you would for real HW, you can do:
/Zephyr-latest/samples/bluetooth/ccp_call_control_server/
DREADME.rst59 Similarly to how you would for real HW, you can do:
/Zephyr-latest/tests/drivers/build_all/adc/boards/
Dnative_sim.overlay9 * with real-world devicetree nodes, to allow these tests to run on
10 * (and be extended to test) real hardware.
/Zephyr-latest/samples/subsys/usb/midi/
DREADME.rst19 would provide. The loopback acts as if a real MIDI cable was connected between
/Zephyr-latest/doc/kernel/services/threads/
Dsystem_threads.rst59 The function used by a real application can be as complex as needed.
/Zephyr-latest/doc/connectivity/usb/host/
Dusbip.rst66 :ref:`native_sim <native_sim>`. Use on real hardware is not really tested yet.
/Zephyr-latest/samples/drivers/ipm/ipm_imx/
DREADME.rst24 would not be appropriate for a real world application.
/Zephyr-latest/doc/connectivity/bluetooth/
Dfeatures.rst47 real-time specifics so that they can be encapsulated in a hardware-specific
/Zephyr-latest/subsys/net/lib/capture/
DKconfig58 is used instead of real network link header.
/Zephyr-latest/samples/subsys/usb/webusb/
DREADME.rst20 real usecase, implement applications based on the WebUSB API.
/Zephyr-latest/boards/renesas/rzt2l_rsk/doc/
Dindex.rst110 …z-mpus/rzt2l-high-performance-mpu-realizing-high-speed-and-high-precision-real-time-control-etherc…

12345678910