Dell S5148F-ON Open Networking Hardware Diagnostic Guide September 2017 - Page 49

read Output, write Output, Constraints, Data flow, Configuration file format, flow, Configuration

Get Dell S5148F-ON PDF manuals and user guides View all Dell S5148F-ON manuals
Add to My Manuals
Save this manual to your list of manuals

Page 49 highlights

read Output root@dell-diag-os:~# memtool --read --addr=200 [00000200]: 0x00 || . write Output root@dell-diag-os:~# memtool --write --addr=200 --val=0x50 Constraints You cannot perform memory tests while other tests that allocate and use memory within the region are performing. However, you can perform the Read tests concurrently with other processes. You cannot run multiple memory tests at the same time as they may collide within the memory spaces. Memory tests cannot test all the memory, and without cache flushes, memory tests may not get out of the caches. The SDI must ensure the memory accessed is accessing the physical memory. This check slows down the tests. Data flow The memtool is not part of the data path and does not participate in the data flow. Configuration file format The configuration file for the memtool is a list of memory segments separated by a ==== divider. Each entry describes the memory in a system that is accessible. This list allows you to review memory in RAMs, FPGAs, and RAM in a memory-mapped PCI BAR. Each parameter is on a separate line and consists of: • Name-The name of the memory region. • Start Address-The address that the memory starts with. If this address is system memory, use a '-' to request the system to get a location from the OS Heap. • Size-The size of the memory. If this size is system memory, use a '-' to request the system to get a location from the OS Heap • Access Mode-How you access the memory; through (b)yte, (h)alfword, or (w)ord. • Increment-The byte address increment for each successive memory location. • Ecc-checks if ECC is available. • Max Chunk-Memory is tested in chunks in which the available memory is divided into. This number is the maximum size of a chunk. • Max Cache-The size of the cache-not currently used. Ensures that caches are fully tested. • Cache Line-The size of a cache line-not currently used. • Iterations-How many times to run the tests on this region. • Tests-lists the tests to perform. Tests are specified in a comma-separated list. Available tests are: • ALL_TESTS-All the following tests, except for DATA_CACHE, which must be run separately. • ADDRESS_READ-Read test of the address lines. Dell EMC DiagOS tools 49

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
read Output
root@dell-diag-os:~# memtool --read --addr=200
[00000200]: 0x00
|| .
write Output
root@dell-diag-os:~# memtool --write --addr=200 --val=0x50
Constraints
You cannot perform memory tests while other tests that allocate and use memory within the region are performing. However, you can
perform the Read tests concurrently with other processes. You cannot run multiple memory tests at the same time as they may collide
within the memory spaces.
Memory tests cannot test all the memory, and without cache
flushes,
memory tests may not get out of the caches. The SDI must ensure
the memory accessed is accessing the physical memory. This check slows down the tests.
Data
flow
The
memtool
is not part of the data path and does not participate in the data
flow.
Configuration
file
format
The
configuration
file
for the
memtool
is a list of memory segments separated by a ==== divider. Each entry describes the memory in a
system that is accessible. This list allows you to review memory in RAMs, FPGAs, and RAM in a memory-mapped PCI BAR. Each parameter
is on a separate line and consists of:
•
Name
—The name of the memory region.
•
Start Address
—The address that the memory starts with. If this address is system memory, use a '-' to request the system to get
a location from the OS Heap.
•
Size
—The size of the memory. If this size is system memory, use a '-' to request the system to get a location from the OS Heap
•
Access Mode
—How you access the memory; through (b)yte, (h)alfword, or (w)ord.
•
Increment
—The byte address increment for each successive memory location.
•
Ecc
—checks if ECC is available.
•
Max Chunk
—Memory is tested in chunks in which the available memory is divided into. This number is the maximum size of a chunk.
•
Max Cache
—The size of the cache—not currently used. Ensures that caches are fully tested.
•
Cache Line
—The size of a cache line—not currently used.
•
Iterations
—How many times to run the tests on this region.
•
Tests
—lists the tests to perform. Tests are
specified
in a comma-separated list.
Available tests are:
•
ALL_TESTS
—All the following tests, except for
DATA_CACHE
, which must be run separately.
•
ADDRESS_READ
—Read test of the address lines.
Dell EMC DiagOS tools
49