Home
last modified time | relevance | path

Searched refs:memory (Results 1 – 25 of 52) sorted by relevance

123

/Renode-v1.15.3-c57714d/tests/platforms/systemc/dma/
Ddma.robot5 ... memory: Memory.MappedMemory @ sysbus 0x20000000 ${\n}
30 # Initialize memory
31 Execute Command sysbus.memory WriteString 0 "Hello"
33 # Make sure memory destination is initialized to 0
49 # Start memory-to-memory transfer in dma_systemc
55 # Verify the memory was copied correctly.
/Renode-v1.15.3-c57714d/tests/unit-tests/
Driscv-amo-instructions.robot44 # Place value in memory.
58 # Perform amoadd to atomically increment memory location
61 # After amoadd, rd register should have the original memory value (before the add)...
66 # Now value in memory should have been incremented.
79 # Now value in memory should have been incremented.
86 # Place value in memory.
100 # Perform amoadd to atomically increment memory location
103 # After amoadd, rd register should have the original memory value (before the add)...
108 # Now value in memory should have been incremented.
121 # Now value in memory should have been incremented.
Darray_memory.robot8 ... // Unregister mapped memory
10 ... // Register array memory and alias as ddr
38 # Overlayed mapped memory area shouldn't be loaded with code
43 # Array memory overlay should be filled with code
59 …# ensure overlayed mapped memory was not loaded with code and therefore that program executes from…
Dhooks.robot48 # executing the `ldrb` instruction followed by the memory test
70 # Empty memory acts as NOPs in ARM so not loading anything to memory isn't an issue.
Driscv-lr-sc-instructions.robot28 # Just write 5 to memory, we'll use this to check for successful and failed writes
32 # Make a0 hold the memory address
59 # Try to update memory address with number 6
/Renode-v1.15.3-c57714d/src/Plugins/CoSimulationPlugin/IntegrationLibrary/src/peripherals/
Dcpu-agent.h233 return debugProgram.memory[(addr - debugProgram.address) / 4]; in requestDoubleWordFromAgent()
238 return debugProgram.memory.back(); // CPU is prefetching debug program in requestDoubleWordFromAgent()
252 if (idx + 1 == debugProgram.memory.size()) in requestDoubleWordFromAgent()
254 return debugProgram.memory[idx]; in requestDoubleWordFromAgent()
257 …return debugProgram.memory.back(); // CPU is probably prefetching, last program instruction should… in requestDoubleWordFromAgent()
349 …return addr >= debugProgram.address && addr < debugProgram.address + debugProgram.memory.size() * … in inDebugProgramRange()
Dcpu-interface.h29 std::vector<uint64_t> memory; variable
/Renode-v1.15.3-c57714d/platforms/cpus/
Dfomu.repl28 // according to the header this memory has a size of 0x10,
29 // but it's currently not possible to allocate such a small memory in Renode
Dmicrowatt.repl8 memory: Memory.MappedMemory @ sysbus 0x0
Dtock_veer_el2_sim.repl13 // Virtual uart's memory
Dpolarfire-soc.repl186 memory: envmData
220 // The exact DDR Memory Partition depends on the amount of physically connected DDR memory.
271 // but because of Renode's memory alignment limitations they are mapped as a single memory
297 // The exact DDR Memory Partition depends on the amount of physically connected DDR memory.
Dup_squared_x86_64.repl33 # address to memory-mapped accesses, it should be the same as 'uart' point of registration
Dlitex_nexys_video_vexriscv_linux.repl55 memory: main_ram
Dvexpress.repl13 memory: Memory.MappedMemory @ {
Dat91rm9200.repl7 memory: Memory.MappedMemory @ {
Dtegra2.repl12 memory: Memory.MappedMemory @ {
163 Tag <0x7000F000,0x7000F3FF> "memory-controller"
Dnuvoton_npcx9.repl133 memory: internal_flash
230 // Mocking "Power Management Channel (PMCH) device registers", as RW memory
246 // that on hardware would be present in board's read-only memory
/Renode-v1.15.3-c57714d/tests/peripherals/
DARM_GenericInterruptController.robot77 … gic: cpu1.0.0.0 reads from 0xC (InterruptAcknowledge) register of memory-mapped CPU Interfa…
79 … gic: cpu0.0.0.0 reads from 0xC (InterruptAcknowledge) register of memory-mapped CPU Interfa…
88 … gic: cpu1.0.0.0 reads from 0xC (InterruptAcknowledge) register of memory-mapped CPU Interfa…
89 … gic: cpu0.0.0.0 reads from 0xC (InterruptAcknowledge) register of memory-mapped CPU Interfa…
/Renode-v1.15.3-c57714d/tests/peripherals/CLIC/
DCLIC-test-platform.repl19 memory: Memory.MappedMemory @ sysbus 0x80000000
/Renode-v1.15.3-c57714d/tools/metrics_analyzer/metrics_visualizer/
Dmetrics-visualizer.py13 from assets.memory import *
/Renode-v1.15.3-c57714d/tests/platforms/
DLeon3.robot40 …# Note that these writes to memory are in the emulation target's endianness (which is big-endian h…
41 …# For example, after `sysbus WriteDoubleWord 0x00000000 0x03100000`, the memory content as a byte …
Dnucleo_h753zi.robot28 # The address of the memory is mentioned in the MCU docs, when the QSPI is configured to operate in…
209 # If the LEDs turned on, it means that the code relocated to QSPI memory is being executed
213 # Get out of GPIO init functions, which are located in regular memory
214 # and step into infinite spin-loop in the QSPI memory
216 # QSPI memory starts at: 0x90000000
/Renode-v1.15.3-c57714d/tools/PeakRDL-renode/
DREADME.md142 For each memory a wrapper structure is generated. It defines read/write access methods for the
170 This structure is instantiated within the peripheral as a member named after the memory instance:
177 to the underlying memory at a given entry index and exposes the entry's fields as
178 properties that map to the memory.
/Renode-v1.15.3-c57714d/tools/guest_cache/
DREADME.md53 Total memory operations: 68952483 (read: 50861775, write 18090708)
/Renode-v1.15.3-c57714d/tools/PeakRDL-renode/src/peakrdl_renode/
Dscanner.py24 from .memory import RegArray

123