Dell S5212F-ON Open Networking Hardware Diagnostic Guide December 2021 - Page 36

Output, scan Output, 70 -- -- -- -- -- -- -- RR RR RR RR RR RR RR RR

Page 36 highlights

i2ctool -w -b /dev/i2c- -a -R -W -V Write(16 bit addressing):= i2ctool --write --bus=/dev/i2c- --addr= -- reg16= [--reg_le] --val= (or) i2ctool -w -b /dev/i2c- -a -o [-L] -V Usage: -h, --h -n, --scan -t, --test -r, --read -w, --write -f, --config= -C, --count= -R, --reg= -o, --reg16= -V, --val= -W, --width= -b, --buspath= -a, --addr= -D, --display_size= -I, --iteration= Show the help text Scan operation Test using the pre-programmed configuration or use supplied config Read operation Write operation To specify the location of the config file e.g. /etc/dn/diag/ Count Register Register(16 bit addressing) Value to be set Width {8,16} To specify the i2c bus e.g.: /dev/i2c- Address Display size, {1,2,4} of bytesDisplay size, {1,2,4} of bytes Iteration command execution Output NOTE: The i2ctool does not automatically scan multiple MUXed segments. Before scanning, you MUST set the MUXes to select the devices you want to see on the busses. By default, the i2ctool scans the i2c devices from the root MUX where it sees the list of devices directly connected to the CPU MUX. The default scan function scans all connected busses. By specifying a bus, you can limit the scan to one bus. In the scan data, RR indicates a reserved address which is not used for any devices and UU indicates that the device is busy or mapped to the OS. scan Output root@dell-diag-os:/etc/dn/diag# i2ctool --scan 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: RR RR RR RR RR RR RR RR 10 18 -- 1a 20 2e -30: 30 -- 32 40 50: 50 -- 52 60 69 70 RR RR RR RR RR RR RR RR 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: RR RR RR RR RR RR RR RR 10 20 30 3e -40 50: 50 51 52 53 54 55 56 57 60 70: 70 RR RR RR RR RR RR RR RR I2C devices found on bus #0: 8 0x18 0x1a 0x2e 0x30 0x32 0x50 0x52 0x69 I2C devices found on bus #1: 10 0x3e 0x50 0x51 0x52 0x53 0x54 0x55 0x56 0x57 0x70 root@dell-diag-os:/etc/dn/diag# 36 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

i2ctool -w -b /dev/i2c-<bus_number> -a <address> -R <register> -W <width> -V
<value>
Write(16 bit addressing):=
i2ctool --write --bus=/dev/i2c-<bus_number> --addr=<address> --
reg16=<register(16bit)> [--reg_le] --val=<value>
(or)
i2ctool -w -b /dev/i2c-<bus_number> -a <address> -o <register(16bit)> [-L] -V
<value>
Usage:
-h, --h
Show the help text
-n, --scan
Scan operation
-t, --test
Test using the pre-programmed configuration or use supplied config
-r, --read
Read operation
-w, --write
Write operation
-f, --config=
To specify the location of the config file e.g. /etc/dn/diag/
<file_name>
-C, --count=
Count
-R, --reg=
Register
-o, --reg16=
Register(16 bit addressing)
-V, --val=
Value to be set
-W, --width=
Width {8,16}
-b, --buspath=
To specify the i2c bus
e.g.: /dev/i2c-<bus number>
-a, --addr=
Address
-D, --display_size=
Display size, {1,2,4} of bytesDisplay size, {1,2,4} of bytes
-I, --iteration=
Iteration command execution
Output
NOTE:
The
i2ctool
does not automatically scan multiple MUXed segments. Before scanning, you MUST set the MUXes
to select the devices you want to see on the busses. By default, the
i2ctool
scans the
i2c
devices from the root MUX
where it sees the list of devices directly connected to the CPU MUX. The default scan function scans all connected busses.
By specifying a bus, you can limit the scan to one bus. In the scan data,
RR
indicates a reserved address which is not used
for any devices and
UU
indicates that the device is busy or mapped to the OS.
scan Output
root@dell-diag-os:/etc/dn/diag# i2ctool --scan
0
1
2
3
4
5
6
7
8
9
a
b
c
d
e
f
00: RR RR RR RR RR RR RR RR -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- 18 -- 1a -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- 2e --
30: 30 -- 32 -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: 50 -- 52 -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- 69 -- -- -- -- -- --
70: -- -- -- -- -- -- -- -- RR RR RR RR RR RR RR RR
0
1
2
3
4
5
6
7
8
9
a
b
c
d
e
f
00: RR RR RR RR RR RR RR RR -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- 3e --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: 50 51 52 53 54 55 56 57 -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: 70 -- -- -- -- -- -- -- RR RR RR RR RR RR RR RR
I2C devices found on bus #0: 8
0x18
0x1a
0x2e
0x30
0x32
0x50
0x52
0x69
I2C devices found on bus #1: 10
0x3e
0x50
0x51
0x52
0x53
0x54
0x55
0x56
0x57
0x70
root@dell-diag-os:/etc/dn/diag#
36
Dell EMC DAIG-OS tools