Dell N3200-ON Open Networking Hardware Diagnostic Guide July 2022 - Page 42

memtool, Show the Help-text

Page 42 highlights

memtool The memtool tests the physical memories in the system. The memtool performs address bus and data tests that moves 1s or 0s through the bus lines to detect stuck, missing, bridged, or other issues found during board tests. The tool also places hamming values or addresses into memory to test and report failing bits. All tests are similar to the memtest86 application but are available through the CLI. In addition, the memtool reads the types and locations of memory in the system. The memory may be physical RAMs connected to the CPU covered by caches, or memory attached or embedded in other devices or across buses. The tool must know the addressable location of the memory, the memory address, data bus sizes, and any addressing constraints; for example, byte or word addressable boundaries. The memtool allocates a memory region to tests in, which is either malloc space or opens a memory map to the memory, and passes the pointer to access the memory. Tests ● Address Read-Causes read transactions on the memory bus. Address read can loop for several iterations, checking for any changes in the data between iterations. You can specify patterns on the address bus for the bits to allow the testing for stuck address bits. ● Address Write-Creates write transactions on the memory bus. Address writes can loop for several iterations, and works similar to the Address Read test. ● Address Walking 1-Walks a 1 though the provided address space in memory for the available address bits. Address Walking 1 writes the address of the cell in the location it is referencing. After it completes writing all the locations, it walks back through and verifies that the data is correct. ● Address Walking 0-Walks a 0 address bit through the memory area available to it. Address walking 0 writes the additive inverse of the address to the location. After writing all addressed locations, it walks back through and verifies the locations data. ● Data Read-Reads transactions similar to the Address Read test, but focuses on the data bits. Patterns are placed on the data bus to test for stuck data bits. ● Data Write-Places data patterns on the bus for testing the bus and looks for stuck data bits. ● Data Walking 1-Walks a 1 through the data bits within an address location and verifies that the values are valid before overwriting. ● Data Walking 0-Walks a 0 through the data bits and verifies the value as it is testing. ● Data Sliding 1-Slides a 1 through the data testing for stuck bits. By xor of each shift to the data, when complete, the cell holds all the 1s. ● Data Sliding 0-Slides a 0 through the data bits set to 1. By xor of each shift of the data, when complete, the cell holds all the 1s. ● Data Pattern-Writes four different patterns to memory locations within the specified region. The patterns are 0xFFFF, 0xFF00, 0xF0F0, 0xAAAA, 0xAA55 and 0x5555. The patterns are written as repeated portions of these patterns in the memory to fill the memory and as Hamming patterns (such as Hamming [8,4], Hamming[16,11], Hamming[32,26] or Hamming[64,57]) encoding with the additional most significant byte (MSB) parity bit to cover the parity bits in the Hamming code. This pattern allows for detecting multiple bit errors. ● Data Cache-Performs a rotation of a 16MB array in four clockwise rotations for 16 iterations of the complete rotation. The 16MB size ensures that memory is not within the cache lines and causes cache ejections through each of the rotations. CLI options root@dellemc-diag-os:~# memtool DellEmc Diag - Memory Tool version 2.0, x.xx.x.x-x build, 2019/07/03, Syntax: memtool Show the Help-text:= memtool --h memtool -h Display the configuration info of the device:= memtool --info (or) (or) 42 Dell DIAG-OS tools

  • 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

memtool
The
memtool
tests the physical memories in the system.
The
memtool
performs address bus and data tests that moves 1s or 0s through the bus lines to detect stuck, missing, bridged,
or other issues found during board tests. The tool also places hamming values or addresses into memory to test and report
failing bits. All tests are similar to the
memtest86
application but are available through the CLI.
In addition, the
memtool
reads the types and locations of memory in the system. The memory may be physical RAMs
connected to the CPU covered by caches, or memory attached or embedded in other devices or across buses. The tool must
know the addressable location of the memory, the memory address, data bus sizes, and any addressing constraints; for example,
byte or word addressable boundaries.
The
memtool
allocates a memory region to tests in, which is either
malloc
space or opens a memory map to the memory, and
passes the pointer to access the memory.
Tests
Address Read
—Causes read transactions on the memory bus. Address read can loop for several iterations, checking for
any changes in the data between iterations. You can specify patterns on the address bus for the bits to allow the testing for
stuck address bits.
Address Write
—Creates write transactions on the memory bus. Address writes can loop for several iterations, and works
similar to the Address Read test.
Address Walking 1
—Walks a 1 though the provided address space in memory for the available address bits. Address
Walking 1 writes the address of the cell in the location it is referencing. After it completes writing all the locations, it walks
back through and verifies that the data is correct.
Address Walking 0
—Walks a 0 address bit through the memory area available to it. Address walking 0 writes the
additive inverse of the address to the location. After writing all addressed locations, it walks back through and verifies the
locations data.
Data Read
—Reads transactions similar to the Address Read test, but focuses on the data bits. Patterns are placed on the
data bus to test for stuck data bits.
Data Write
—Places data patterns on the bus for testing the bus and looks for stuck data bits.
Data Walking 1
—Walks a 1 through the data bits within an address location and verifies that the values are valid before
overwriting.
Data Walking 0
—Walks a 0 through the data bits and verifies the value as it is testing.
Data Sliding 1
—Slides a 1 through the data testing for stuck bits. By
xor
of each shift to the data, when complete,
the cell holds all the 1s.
Data Sliding 0
—Slides a 0 through the data bits set to 1. By
xor
of each shift of the data, when complete, the cell
holds all the 1s.
Data Pattern
—Writes four different patterns to memory locations within the specified region. The patterns are 0xFFFF,
0xFF00, 0xF0F0, 0xAAAA, 0xAA55 and 0x5555. The patterns are written as repeated portions of these patterns in
the memory to fill the memory and as Hamming patterns (such as Hamming [8,4], Hamming[16,11], Hamming[32,26] or
Hamming[64,57]) encoding with the additional most significant byte (MSB) parity bit to cover the parity bits in the Hamming
code. This pattern allows for detecting multiple bit errors.
Data Cache
—Performs a rotation of a 16MB array in four clockwise rotations for 16 iterations of the complete rotation.
The 16MB size ensures that memory is not within the cache lines and causes cache ejections through each of the rotations.
CLI options
root@dellemc-diag-os:~# memtool
DellEmc Diag - Memory Tool
version 2.0, x.xx.x.x-x
build, 2019/07/03,
Syntax: memtool <option>
Show the Help-text:=
memtool --h
(or)
memtool -h
Display the configuration info of the device:=
memtool --info
(or)
42
Dell DIAG-OS tools