Home
last modified time | relevance | path

Searched refs:R5 (Results 1 – 21 of 21) sorted by relevance

/Zephyr-latest/cmake/sca/eclair/ECL/
Danalysis_WP.ecl15 -enable=MC3R1.R5.9
16 -enable=MC3R1.R5.1
17 -enable=MC3R1.R5.6
18 -enable=MC3R1.R5.7
19 -enable=MC3R1.R5.8
Danalysis_STU.ecl98 -enable=MC3R1.R5.2
99 -enable=MC3R1.R5.3
100 -enable=MC3R1.R5.4
101 -enable=MC3R1.R5.5
/Zephyr-latest/boards/amd/kv260_r5/support/
Dxsdb.cfg10 targets -set -nocase -filter {name =~ "*R5*#0"}
17 targets -set -nocase -filter {name =~ "*R5*#0"}
/Zephyr-latest/boards/beagle/beaglebone_ai64/doc/
Dindex.rst13 MCU, WKUP). This document gives overview of Zephyr running on Cortex R5's
58 The J721E does not have a separate flash for the R5 cores. Because of this
59 the A72 core has to load the program for the R5 cores to the right memory
63 By default the R5's Memory Protection Unit (MPU) only allows for execution of
65 carved out for each R5 by Linux. These can be used for IPC (DDR0) and for
69 This is the memory mapping from A72 to the memory usable by the R5. Note that
70 the R5 cores always see their local ATCM at address 0x00000000 and their BTCM
116 Zephyr on BeagleBone AI-64 J721E Cortex R5 uses UART 2 (Rx p8.22, Tx p8.34)
/Zephyr-latest/boards/beagle/beagley_ai/doc/
Dindex.rst12 MCU). This document gives overview of Zephyr running on both Cortex R5.
16 BeagleY-AI defaults to single-core mode for the R5 subsystem. Changes in that
60 The AM67A does not have a separate flash for the R5 core. Because of this
61 an A53 core has to load the program for the R5 core to the right memory
65 This is the memory mapping from A53 to the memory usable by the R5. Note that
66 the R5 core always sees its local TCMA at address 0x00000000 and its TCMB0
70 the R5. The amount of the allocation can be changed in the Linux device tree.
/Zephyr-latest/include/zephyr/arch/arm/
Dgdbstub.h43 R5, enumerator
/Zephyr-latest/drivers/interrupt_controller/
DKconfig.vim14 and aggregating the interrupt sources for ARM Cortex-R5 processor cores.
/Zephyr-latest/boards/qemu/cortex_r5/
Dqemu_cortex_r5.dts12 model = "QEMU Cortex-R5";
/Zephyr-latest/boards/amd/kv260_r5/doc/
Dindex.rst8 * Two independent R5 cores with their own TCMs (tightly coupled memories)
11 This processing unit is based on an ARM Cortex-R5 CPU, it also enables the following devices:
51 * Only the first core of the R5 subsystem is supported.
53 * The Cortex-R5 and the Cortex-A53 shares the same UART controller, more details below.
138 2. Cortex-R5 and Cortex-R5F Technical Reference Manual (ARM DDI 0460C ID021511)
/Zephyr-latest/soc/ti/k3/am6x/
DKconfig.soc24 Enable support for AM6X R5 Series.
/Zephyr-latest/boards/amd/kv260_r5/
Dkv260_r5.dts12 model = "KV260 Cortex-R5";
/Zephyr-latest/boards/qemu/cortex_r5/doc/
Dindex.rst9 This configuration provides support for an ARM Cortex-R5 CPU and these devices:
102 2. Cortex-R5 and Cortex-R5F Technical Reference Manual (ARM DDI 0460C ID021511)
/Zephyr-latest/scripts/coredump/gdbstubs/arch/
Darm_cortex_m.py24 R5 = 5 variable in RegNum
76 self.registers[RegNum.R5] = tu[10]
/Zephyr-latest/cmake/compiler/iar/
Diccarm-cpu.cmake46 set(ICCARM_CPU Cortex-R5)
/Zephyr-latest/arch/arm/core/
Dgdbstub.c58 ctx.registers[R5] = esf->extra_info.callee->v2; in z_gdb_entry()
/Zephyr-latest/boards/beagle/beagleplay/doc/
Dbeagleplay_cc1352p7.rst18 * ARM Cortex-R5
/Zephyr-latest/arch/arm/core/cortex_a_r/
DKconfig88 This option signifies the use of a Cortex-R5 CPU
/Zephyr-latest/doc/hardware/arch/
Darm_cortex_m.rst377 * up to 5 arguments are placed on registers R1 - R5
/Zephyr-latest/doc/releases/
Drelease-notes-3.4.rst545 * Xilinx KV260 (Cortex-R5)
Drelease-notes-2.3.rst920 * :github:`24911` - arch: arm: aarch32: When CPU_HAS_FPU for Cortex-R5 is selected, prep_c.c uses u…
Drelease-notes-3.3.rst3551 * :github:`49413` - TI-AM62x: Add Zephyr Support for M4 and R5 cores