Home
last modified time | relevance | path

Searched refs:core (Results 226 – 250 of 877) sorted by relevance

12345678910>>...36

/Zephyr-latest/cmake/ide/
Declipse_cdt4_generator_amendment.cmake122 …file(APPEND ${OUTPUT_FILE} "\t<configuration id=\"org.eclipse.cdt.core.default.config.1\" name=\"C…
123 …file(APPEND ${OUTPUT_FILE} "\t\t<extension point=\"org.eclipse.cdt.core.LanguageSettingsProvider\"…
125 …file(APPEND ${OUTPUT_FILE} "\t\t\t<provider-reference id=\"org.eclipse.cdt.core.ReferencedProjects…
126 …file(APPEND ${OUTPUT_FILE} "\t\t\t<provider-reference id=\"org.eclipse.cdt.core.PathEntryScannerIn…
128 …ltinSpecsDetector\" console=\"false\" id=\"org.eclipse.cdt.managedbuilder.core.GCCBuiltinSpecsDete…
130 …ltinSpecsDetector\" console=\"false\" id=\"org.eclipse.cdt.managedbuilder.core.GCCBuiltinSpecsDete…
132 file(APPEND ${OUTPUT_FILE} "\t\t\t\t<language-scope id=\"org.eclipse.cdt.core.gcc\"/>\n")
133 file(APPEND ${OUTPUT_FILE} "\t\t\t\t<language-scope id=\"org.eclipse.cdt.core.g++\"/>\n")
/Zephyr-latest/boards/96boards/avenger96/doc/
Dindex.rst10 multi-core processor, composed of a dual Cortex®-A7 and a single Cortex®-M4
11 core. Zephyr OS is ported to run on the Cortex®-M4 core.
58 - 32-bit dual-core Arm® Cortex®-A7
60 - L1 32-Kbyte I / 32-Kbyte D for each core
194 on Cortex®-A7 core. Alternatively, Zephyr console output can be assigned to
204 started by the Cortex®-A7 core. The Cortex®-A7 core is responsible to load the
/Zephyr-latest/boards/native/nrf_bsim/
DKconfig22 Simulated NRF53 Network core
33 Simulated NRF53 Application core
44 Simulated NRF54L15 Application core
/Zephyr-latest/snippets/nordic-ppr-xip/
DREADME.rst10 (Peripheral Processor) from another core. PPR code is to be executed from MRAM,
/Zephyr-latest/soc/lowrisc/opentitan/
DKconfig20 # OpenTitan Ibex core mtvec mode is read-only / forced to vectored mode.
/Zephyr-latest/soc/nordic/common/vpr/
DKconfig24 Enable support for the RISC-V Nordic VPR core.
/Zephyr-latest/snippets/nordic-flpr/soc/
Dnrf54l15_cpuapp.overlay12 /* FLPR core code partition */
/Zephyr-latest/snippets/nordic-flpr-xip/
DREADME.rst10 (Fast Lightweight Peripheral Processor) from application core.
/Zephyr-latest/soc/snps/nsim/arc_classic/hs/
DKconfig.defconfig.hs6x_smp18 # SMP simulation is slower than single core, 1 Mhz seems reasonable match with wallclock
/Zephyr-latest/samples/drivers/mbox/
DKconfig8 bool "Include remote core header directory"
/Zephyr-latest/soc/intel/intel_adsp/
DKconfig27 bool "No secondary core flow."
29 Select if simulator doesn't use the normal secondary core flow
122 bool "Saves FW context into IMR before core is shut down"
145 HW configuration of a DSP. Evry time core goes to the WAITI state
/Zephyr-latest/boards/snps/hsdk/
DKconfig.hsdk11 supports single- and multi-core ARC HS34, HS36 and HS38 processors
/Zephyr-latest/drivers/coredump/
DKconfig8 desired data into core dumps.
/Zephyr-latest/soc/nxp/imxrt/imxrt11xx/
DKconfig.defconfig30 # RT Boot header is only needed on primary core
/Zephyr-latest/tests/bsim/bluetooth/
Dtests.nrf54l15bsim_nrf54l15_cpuapp.txt1 # Search paths(s) for tests which will be run in the nrf54l15 app core
/Zephyr-latest/boards/phytec/phyboard_nash/doc/
Dindex.rst16 Cortex-M33 core. Zephyr OS is ported to run on one of the Cortex-A55 core as
17 well as the Cortex-M33 core.
104 CPU's UART2 for A55 core and M33 core. The u-boot bootloader or Linux use the
/Zephyr-latest/scripts/west_commands/runners/
Decpprog.py8 from runners.core import BuildConfiguration, RunnerCaps, ZephyrBinaryRunner
/Zephyr-latest/samples/subsys/ipc/openamp/
Dsysbuild.cmake14 # remote core's build, such as the output image's LMA
/Zephyr-latest/drivers/mbox/
DKconfig.nrf_vevif_event16 Mailbox driver for transmitting events from VPR to a remote core
/Zephyr-latest/samples/drivers/ipm/ipm_mcux/
Dsysbuild.cmake14 # remote core's build, such as the output image's LMA
/Zephyr-latest/samples/bluetooth/direction_finding_central/
DREADME.rst41 also run on the network core. The :zephyr:code-sample:`bluetooth_hci_ipc` sample
73 network core application. When :zephyr:code-sample:`bluetooth_hci_ipc` is used as the
74 network core application, the antenna matrix configuration should be stored in
/Zephyr-latest/samples/drivers/ipm/ipm_imx/
DREADME.rst29 The sample requires that data are being sent by the remote core so it can echo
30 it back. The other core is usually not running Zephyr but Linux on i.MX
43 for how to load the Zephyr binary to the desired core and execute it.
/Zephyr-latest/samples/bluetooth/direction_finding_peripheral/
DREADME.rst40 also run on the network core. The :zephyr:code-sample:`bluetooth_hci_ipc` sample
72 network core application. When :zephyr:code-sample:`bluetooth_hci_ipc` is used as the
73 network core application, the antenna matrix configuration should be stored in
/Zephyr-latest/boards/toradex/colibri_imx7d/doc/
Dindex.rst6 The i.MX7 SoC is a Hybrid multi-core processor composed by Single/Dual Cortex A7
7 core and Single Cortex M4 core.
8 Zephyr was ported to run on the M4 core. In a later release, it will also
9 communicate with the A7 core (running Linux) via RPmsg.
14 - i.MX7 Single/Dual Cortex A7 (800MHz/1.0GHz) core and Single Cortex M4 (200MHz) core
129 the A7 core. The A7 core is responsible to load the M4 binary application into the
223 The boot process of the M4 core is handled solely by the Linux kernel using the RPROC
373 the drivers and start the M4 core.
443 1. Put the M4 core in reset
447 5. Get the M4 core out of reset
/Zephyr-latest/soc/nxp/imx/imx7d/
DKconfig.soc1 # iMX7D core series

12345678910>>...36