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

Configuration file format, i2ctool, Tests, format

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 37 highlights

Configuration file format GPIOs are separated into groups within the configuration file, such as Core GPIOs and Suspend GPIOs (if they use different power wells for sleep operations). Any line starting with a # is a comment. ===== is the separator between groups. A group starts with a header using | separators and: • # of bits defined in the GPIO interface (a hardware definition, not the number of bits being defined in the config file.) • A name for the bit group, such as Core GPIO or SUS GPIO. • Group Type - CORE. • Any bus used to access the GPIO. For the CPLD-based or FPGA-based GPIOs. • The address to use to access the GPIO. For the CPLD-based or FPGA-based GPIOs. • All the GPIOs are zero-based in a group. The 0 map is the offset to access /sys/class/gpio/gpio# in the sysfs. Each bit is then defined on its own line separated with | and includes the bit number, name, direction, active level, and default value. #bits | Name | intf | bus | addr | 0-map 60 | Core Gpio | CORE | - | - | 196 # Bit | Name | Direction | Value 15 | SATA_GP0 | IN | LOW | 0 16 | SATA_LEDN | OUT | LOW | 0 17 | SATA3_GP0 | IN | LOW | 0 19 | FLEX_CLK_SE0 | IN | LOW | 0 20 | FLEX_CLK_SE1 | IN | LOW | 0 32 | GPIO_SUS1 | IN | LOW | 0 33 | GPIO_SUS2 | OUT | LOW | 0 34 | CPU_RESET_B | OUT | LOW | 0 36 | PMU_SUSCLK | OUT | LOW | 0 37 | PMU_SLP_DDRVTT_B | IN | LOW | 0 38 | PMU_SLP_LAN_B | IN | LOW | 0 39 | PMU_WAKE_B | OUT | LOW | 0 40 | PMU_PWRBTN_B | IN | LOW | 0 49 | GBE_SDP0_1 | IN | LOW | 0 50 | GBE_LED0 | IN | LOW | 0 51 | GBE_LED1 | IN | LOW | 0 52 | GBE_LED2 | IN | LOW | 0 53 | GBE_LED3 | IN | LOW | 0 54 | NCSI_RXD1 | OUT | LOW | 0 i2ctool The i2ctool allows for scanning, reading, and writing of the I2c bus devices. To read and write to devices on the i2c bus, use the i2ctool. The i2ctool also scans the i2c busses and reports what devices are found. The scan reads address 0x0 from all the devices in the address range of 0x0 to 0x7f on all i2c busses present. The i2ctool does not automatically traverse MUXes along the i2c bus. Other tools use this tool to read i2c device information and pass the results back through a named pipe. Tests To test, the i2ctool has a configuration file that lists all the devices on the busses. The tool runs through the list and tries to reach the devices. The i2ctool reports when a device is not returning data. Dell EMC DiagOS tools 37

  • 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
Configuration
file
format
GPIOs are separated into groups within the
configuration
file,
such as Core GPIOs and Suspend GPIOs (if they use
different
power wells for
sleep operations).
Any line starting with a # is a comment. ===== is the separator between groups.
A group starts with a header using | separators and:
•
# of bits
defined
in the GPIO interface (a hardware
definition,
not the number of bits being
defined
in the
config
file.)
•
A name for the bit group, such as Core GPIO or SUS GPIO.
•
Group Type — CORE.
•
Any bus used to access the GPIO. For the CPLD-based or FPGA-based GPIOs.
•
The address to use to access the GPIO. For the CPLD-based or FPGA-based GPIOs.
•
All the GPIOs are zero-based in a group. The
0
map is the
offset
to access
/sys/class/gpio/gpio#
in the sysfs.
Each bit is then
defined
on its own line separated with | and includes the bit number, name, direction, active level, and default value.
#bits | Name | intf | bus | addr | 0-map
60 | Core Gpio | CORE | - | - | 196
# Bit | Name
| Direction
| Value
15 | SATA_GP0
| IN
| LOW
| 0
16 | SATA_LEDN
| OUT | LOW
| 0
17 | SATA3_GP0
| IN
| LOW
| 0
19 | FLEX_CLK_SE0
| IN
| LOW
| 0
20 | FLEX_CLK_SE1
| IN
| LOW
| 0
32 | GPIO_SUS1
| IN
| LOW
| 0
33 | GPIO_SUS2
| OUT | LOW
| 0
34 | CPU_RESET_B
| OUT | LOW
| 0
36 | PMU_SUSCLK
| OUT | LOW
| 0
37 | PMU_SLP_DDRVTT_B | IN
| LOW
| 0
38 | PMU_SLP_LAN_B
| IN
| LOW
| 0
39 | PMU_WAKE_B
| OUT | LOW
| 0
40 | PMU_PWRBTN_B
| IN
| LOW
| 0
49 | GBE_SDP0_1
| IN
| LOW
| 0
50 | GBE_LED0
| IN
| LOW
| 0
51 | GBE_LED1
| IN
| LOW
| 0
52 | GBE_LED2
| IN
| LOW
| 0
53 | GBE_LED3
| IN
| LOW
| 0
54 | NCSI_RXD1
| OUT | LOW
| 0
i2ctool
The
i2ctool
allows for scanning, reading, and writing of the
I2c
bus devices.
To read and write to devices on the
i2c
bus, use the
i2ctool
. The
i2ctool
also scans the
i2c
busses and reports what devices are
found. The scan reads address 0x0 from all the devices in the address range of 0x0 to 0x7f on all
i2c
busses present. The
i2ctool
does
not automatically traverse MUXes along the
i2c
bus. Other tools use this tool to read
i2c
device information and pass the results back
through a named pipe.
Tests
To test, the
i2ctool
has a
configuration
file
that lists all the devices on the busses. The tool runs through the list and tries to reach the
devices. The
i2ctool
reports when a device is not returning data.
Dell EMC DiagOS tools
37