Dell PowerSwitch S4112F-ON Open Networking Hardware Diagnostic Guide April 201 - Page 48

OutputRead output, Write output, memtool, Tests, Output, Read output

Page 48 highlights

Write data at the specified address:= lpctool --write --addr=address --val=data [--size=b,w or l] lpctool -w -a -V [-z ] Execute repeatedly command by count:= lpctool --iteration=max/ [option1] [option2]... lpctool -I max/ [option1] [option2]... Usage:= -h, --h Show the help text -w, --write Write operation -r, --read Read operation -z, --size= Size -I, --iteration= Iteration command execution -C, --count= Count -a, --addr= Address Output (or) (or) Read output root@dell-diag-os:/opt/dellemc/diag/bin# ./lpctool --read --addr=102 Byte Port 0x102 : 0xde Write output root@dell-diag-os:/opt/dellemc/diag/bin# ./lpctool --write --addr=102 --val=10 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. 48 Dell EMC DAIG-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
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88

Write data at the specified address:=
lpctool --write --addr=address --val=data [--size=b,w or l]
(or)
lpctool -w -a <address> -V <data> [-z <b,w or l>]
Execute repeatedly command by count:=
lpctool --iteration=max/<count> [option1] [option2]...
(or)
lpctool -I max/<count> [option1] [option2]...
Usage:=
-h, --h
Show the help text
-w, --write
Write operation
-r, --read
Read operation
-z, --size=
Size
-I, --iteration=
Iteration command execution
-C, --count=
Count
-a, --addr=
Address
Output
Read output
root@dell-diag-os:/opt/dellemc/diag/bin# ./lpctool --read --addr=102
Byte Port 0x102 : 0xde
Write output
root@dell-diag-os:/opt/dellemc/diag/bin# ./lpctool --write --addr=102 --val=10
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.
48
Dell EMC DAIG-OS tools