CN107957969B - Method for judging device connection state and device type - Google Patents
Method for judging device connection state and device type Download PDFInfo
- Publication number
- CN107957969B CN107957969B CN201610901247.XA CN201610901247A CN107957969B CN 107957969 B CN107957969 B CN 107957969B CN 201610901247 A CN201610901247 A CN 201610901247A CN 107957969 B CN107957969 B CN 107957969B
- Authority
- CN
- China
- Prior art keywords
- equipment
- type
- address
- data
- device type
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/38—Information transfer, e.g. on bus
- G06F13/42—Bus transfer protocol, e.g. handshake; Synchronisation
- G06F13/4282—Bus transfer protocol, e.g. handshake; Synchronisation on a serial bus, e.g. I2C bus, SPI bus
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2213/00—Indexing scheme relating to interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F2213/0016—Inter-integrated circuit (I2C)
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Small-Scale Networks (AREA)
- Debugging And Monitoring (AREA)
Abstract
A method for determining device connection status and device type, implemented by a processing unit, comprising the steps of: (A) respectively transmitting a plurality of inquiry requests to a plurality of addresses of an integrated circuit bus to confirm whether any equipment is connected to each address; and (B) when a reply message from at least one device corresponding to at least one of the addresses is received, comparing the at least one address corresponding to the reply message of the at least one device and the corresponding device type according to a lookup table to obtain the device type of the at least one device corresponding to the at least one address, wherein the lookup table comprises a plurality of device types respectively corresponding to a plurality of address sets consisting of at least one reference address.
Description
Technical Field
The present invention relates to a method for determining a device connection status and a device type, and more particularly, to a method for determining a device connection status and a device type for an integrated circuit bus.
Background
An Inter-Integrated Circuit (I2C) bus is a serial bus composed of a Data line sda (serial Data line) and a Clock scl (serial Clock line) and can transmit and receive Data. The various module circuits are connected in parallel on the bus, each circuit and module has a unique address, and only the address can communicate with the specific module circuit. During the transmission of information, each module circuit connected in parallel on the I2C bus is both a master (or slave) and a transmitter (or receiver), depending on the function it is to perform. Generally speaking, the control signal sent by the processing unit is divided into two parts, namely an address code and a control quantity, wherein the address code is used for selecting an address, namely, a module circuit needing to be controlled is switched on, and the type of control is determined; the control amount determines the type of adjustment (e.g., contrast, brightness, etc.) and the amount of adjustment required. However, if it is desired to know which devices are connected to the I2C bus, the conventional method needs to obtain a circuit diagram to know which devices are connected to the I2C bus.
However, the circuit diagram is often planned before the devices are actually connected to the I2C bus, but the devices actually connected to the I2C bus are not necessarily planned according to the original circuit diagram, so after the circuit diagram is obtained, it is necessary to confirm whether the I2C bus address indicated by the circuit diagram to which a device is connected is actually connected with a device, for example, in the case that the circuit diagram indicates that the I2C bus address 0x 010 xa0 is connected with an EEPROM (Electrically Erasable Programmable Read Only Memory) device. To confirm whether a device is actually connected to an address such as 0x 010 xa0 (i.e., address 0xa0 of bus 1), a query request including an Intelligent Platform Management Interface (Intelligent Platform Management Interface) command such as ipmitool raw 0x 060 x 520 x 010 xa 00 x 010 x00 may be sent by a processing unit to the device connected to the I2C bus address 0x 010 xa 0. If the processing unit receives a reply message from the I2C bus address 0x 010 xa0 corresponding to a device connected to the I2C bus address 0x 010 xa0, the processing unit determines that the I2C bus address 0x 010 xa0 is indeed connected to a device. If the processing unit does not receive any reply message from the I2C bus address 0x 010 xa0, the processing unit determines that the I2C bus address 0x 010 xa0 is not connected with any device.
However, the above-mentioned method for confirming by using the intelligent platform management interface command can only confirm whether the I2C bus address indicated by the circuit diagram with a device connected thereto is actually connected with a device, but cannot confirm whether the I2C bus address indicated by the circuit diagram without a device connected thereto is actually not connected with a device. Therefore, in order to make the actual connection state of the circuit diagram and the subsequent I2C bus consistent, the devices have to be connected to the I2C bus completely according to the specification of the original circuit diagram, which results in the connection of the subsequent devices losing more flexibility and being inconvenient. In addition, the SMI command for confirming whether the I2C bus address of a device indicated by the circuit diagram is actually connected with a device not only includes a read/write command type (e.g., 0x 060 x52), a query address (e.g., 0x 010 xa0) and a reply request (e.g., 0x01), but also includes a command set (e.g., 0x00) of the device connected with the query address. That is, the user must first use the circuit diagram to know a device type of the device connected to the inquiry address, and then use the processing unit to transmit the intelligent platform management interface command including the command set corresponding to the device type according to the device type, so as to confirm whether the inquiry address is actually connected to a device.
Disclosure of Invention
Accordingly, it is an object of the present invention to provide a method for determining a device connection status and a device type that improves flexibility of device connection.
Thus, the method for determining the connection status and the type of the device according to the present invention is implemented by a processing unit, and comprises the following steps:
(A) respectively transmitting a plurality of inquiry requests to a plurality of addresses of an integrated circuit bus to confirm whether any equipment is connected to each address; and
(B) when a reply message from at least one device corresponding to at least one of the addresses is received, the at least one address corresponding to the reply message of the at least one device and the corresponding device type are compared according to a lookup table to find out the device type of the at least one device corresponding to the at least one address, wherein the lookup table comprises a plurality of device types respectively corresponding to a plurality of address sets consisting of at least one reference address.
The invention has the following effects: the processing unit determines the device type of the devices connected to the integrated circuit bus by sending a plurality of inquiry requests to the addresses of the integrated circuit bus after the devices have been connected to the integrated circuit bus, whereby the connection of the subsequent devices does not have to be completely connected according to the specification of the current circuit diagram, thereby improving the flexibility of the connection of the subsequent devices.
[ description of the drawings ]
FIG. 1 is a flowchart illustrating a device type comparison procedure in an embodiment of the method of determining device connection status and device type of the present invention; and
fig. 2, 3 and 4 cooperatively illustrate a device type verification procedure in an embodiment of the method of determining device connection status and device type according to the present invention.
[ detailed description ] embodiments
The following describes an embodiment of a method for determining a device connection status and a device type according to the present invention with reference to the accompanying drawings, which is implemented by a processing unit (not shown) and sequentially includes a device type comparison procedure and a device type verification procedure.
Referring to fig. 1, the processing unit implements a device type comparison procedure of the method for determining a device connection status and a device type according to the present invention. The device type comparison program of the method for determining the device connection state and the device type shows how to obtain the device type of the device connected to an integrated circuit bus, and comprises the following steps.
In step 11, the processing unit sends a plurality of inquiry requests to a plurality of addresses of the integrated circuit bus respectively to determine whether any device is connected to each address. If an address is connected to a device, the device transmits a reply message in response to a query request to the processing unit. The addresses are, for example, all addresses of the bus (i.e., address 0x00 to address 0xfe of bus 1), so that the processing unit can confirm the connection status of all addresses of the bus. Each query request contains an Intelligent Platform Management Interface (Intelligent Platform Management Interface) instruction, such as ipmitool raw 0x 060 x 520 x 010 xa 00 x 01. Each intelligent platform management interface command includes a read/write command type (e.g., 0x 060 x52), a query address (e.g., one of addresses 0x 010 x 00-0 x 010 xfe), and a return request (e.g., 0x01), without including a command set for the device connected to the query address.
In step 12, when the processing unit receives a reply message from at least one device corresponding to at least one of the addresses, the processing unit compares the at least one address corresponding to the reply message of the at least one device and the corresponding device type according to a lookup table to determine the device type of the at least one device corresponding to the at least one address, wherein the lookup table comprises a plurality of device types respectively corresponding to a plurality of address sets consisting of at least one reference address. Each reply message in response to the query request contains only 1byte of data. Table 1 is an example lookup table.
| Address set | Type of device |
| 0x36、0x66、0xa6 | Peripheral component interconnect (Peripheral component interconnect express solid state drive, PCIe SSD for short) |
| 0xa0、0xb0 | Power supply unit (Power supply unit, PSU for short) |
| 0xa0 | Field replaceable unit (Field replacement unit, FRU for short) |
| 0xb0 | Power Supply Unit (PSU) |
| 0x98 | Temperature sensor |
| 0xE0 | Multiplexer (MUX for short) |
TABLE 1
It is worth mentioning that all the at least one address corresponding to the reply message of the at least one device is compared with the lookup table. In this embodiment, the address set corresponding to the most reference addresses has the highest comparison order, and the address set corresponding to the least reference addresses has the lowest comparison order. For example, if the at least one address is 0xa0, 0xb0, 0x36, 0x66, 0xa6, the processing unit compares 0x36, 0x66, 0xa6 as PCIe SSD and compares 0xa0, 0xb0 as PSU according to the at least one address (0xa0, 0xb0, 0x36, 0x66, 0xa6) and the lookup table (table 1), so that the device type of the at least one device corresponding to the at least one address (0xa0, 0xb0, 0x36, 0x66, 0xa6) is PCIe, PSU. When comparing 0xa0 and 0xb0, the processing unit compares the comparison result of the device type with PSU 0xa0 and 0xb0 because the address set with the most reference addresses has the highest comparison order, so the processing unit compares the address sets 0xa0 and 0xb0 with 2 reference addresses preferentially, but does not compare 0xa0 and 0xb0 with the address set 0xa0 and 0xb0 with only 1 reference address.
Referring to fig. 2, 3 and 4, the processing unit implements the device verification procedure of the method for determining the device connection status and the device type according to the present invention to verify whether the device type compared by the device type comparison procedure is correct, and includes the following steps. It should be noted that the device type compared by the device type comparison program is determined by mistake, and therefore, the device type of the at least one device connected to the at least one address and compared by the device type comparison program is verified by the device verification program to be correct, so that the processing unit can determine whether the device types of all the devices connected to the at least one address of the devices and compared by the device type comparison program are correct.
In step 201, for each of the at least one device connected to the at least one address, the processing unit determines whether the device type of the device belongs to a first device class. When it is determined that the device type of the device belongs to the first device class, step 202 is performed. Otherwise, the flow proceeds to step 208. In the present embodiment, the first device type includes a device type of a Power Supply Unit (PSU), but is not limited thereto.
In step 202, the processing unit sends a device data request to each address to which the device is connected.
In step 203, when the processing unit receives the device data from each address connected to the device, the processing unit determines whether the device data corresponding to each address matches the first predetermined data associated with the device type in the first device type that is the same as the device type of the device. When the equipment data is determined to be consistent with the first predetermined data, step 204 is performed. Otherwise, the flow proceeds to step 205.
It should be noted that the processing unit verifies whether the equipment type compared in step 12 is correct by determining whether the equipment data of each address connected to the equipment all matches the first preset data. When the equipment data corresponding to each address is determined to be matched with the preset data, the equipment is verified to be correct in the equipment type compared in the step 12; otherwise, the device type compared by the device at step 12 is verified as not being completely correct.
In step 204, the processing unit stores the device type and the corresponding address set compared in step 12 in a device lookup table electrically connected to the storage unit of the processing unit.
In step 205, the processing unit determines whether the device data that does not match the first default data both match second default data associated with a device type of a Field Replaceable Unit (FRU). When it is determined that the device data not corresponding to the first default data all correspond to the second default data, proceed to step 206. Otherwise, the flow proceeds to step 207.
It should be noted that the processing unit verifies whether the device type of the device connected to the address corresponding to the device data not corresponding to the first predetermined data is the device type of the field replaceable unit by determining whether the device data not corresponding to the first predetermined data matches the second predetermined data. When the equipment data which does not accord with the first preset data is judged to accord with the second preset data, the equipment type of the equipment connected with the address corresponding to the equipment data which does not accord with the first preset data is verified as the equipment type of the field replaceable unit; otherwise, the device type of the device connected to the address corresponding to the device data not corresponding to the first predetermined data is verified as not being the device type of the field replaceable unit or the device type compared in step 12. Continuing with the previous example, the at least one address (0xa0, 0xb0, 0x36, 0x66, 0xa6) compared in step 12 results in 0x36, 0x66, 0xa6 being PCIe SSD and 0xa0, 0xb0 being PSU. Generally, 0xa0 and 0xb0 have a high probability of connecting to the PSU, but it is also possible that 0xa0 connects to the FRU and 0xb0 connects to the PSU, so that it can be verified whether 0xa0 and 0xb0 are both actually connected to the PSU by determining whether the device data of each address, e.g., 0xa0 and 0xb0, to which the device is connected matches the first predetermined data. If it is determined that the device data of the address 0xa0 matches the second preset data and the device data of the address 0xb0 matches the first preset data, the device type of the device connected to the address 0xa0 is FRU and the device type of the device connected to the address 0xb0 is PSU.
In step 206, the processing unit stores the device type compared in step 12 for the device connected to the address corresponding to the device data corresponding to the first predetermined data, and the device connected to the address corresponding to the device data corresponding to the second predetermined data, which are verified as the device type of the field replaceable unit, and the address corresponding to the device data corresponding to the second predetermined data in the device lookup table.
In step 207, the processing unit stores the device type compared in step 12 by the device connected to the address corresponding to the device data corresponding to the first predetermined data, and the address corresponding to the device data corresponding to the second predetermined data, and verifies that the device connected to the address corresponding to the device data corresponding to the second predetermined data is the device type of the field replaceable unit and the address corresponding to the device data corresponding to the second predetermined data, instead of storing the device type compared in step 12 by the device connected to the address corresponding to the device data not corresponding to the first predetermined data and the second predetermined data and the address corresponding thereto in the device comparison table.
In step 208, the processing unit determines whether the device type of the device belongs to a second device class. When it is determined that the device type of the device belongs to the second device class, step 209 is performed. Otherwise, the flow proceeds to step 213. In the present embodiment, the second device category includes at least one of a peripheral component interconnect express solid state disk (PCIe SSD) device type and a Field Replaceable Unit (FRU) device type, but is not limited thereto.
In step 209, the processing unit sends a device data request to the device.
In step 210, when the processing unit receives the device data from the device, the processing unit determines whether the device data matches third predetermined data associated with a device type in the second device type that is the same as the device type of the device. When it is determined that the equipment data matches the third predetermined data, proceed to step 211. Otherwise, the flow proceeds to step 212.
It should be noted that the processing unit verifies whether the device type compared in step 12 is correct by determining whether the device data matches the third predetermined data. When the equipment data is determined to match the third predetermined data, the equipment is verified as correct in the equipment type compared in step 12; otherwise, the device is verified as incorrect for the device type compared at step 12.
In step 211, the processing unit stores the device type and the corresponding address set of the device compared in step 12 in the device lookup table.
In step 212, the processing unit does not store the device type and its corresponding address set compared in step 12 in the device lookup table.
In step 213, the processing unit determines whether the device type of the device belongs to a third device class. When it is determined that the device type of the device belongs to the third device class, step 214 is performed. Otherwise, flow proceeds to step 218. In the present embodiment, the third equipment category includes, but is not limited to, the type of equipment of a temperature sensing unit.
In step 214, the processing unit transmits a device data request to the device.
In step 215, when the processing unit receives the device data from the device, the processing unit determines whether the device data conforms to a predetermined data format. When it is determined that the equipment data conforms to the predetermined data format, proceed to step 216. Otherwise, the flow proceeds to step 217.
It should be noted that the processing unit verifies whether the device type compared in step 12 is correct by determining whether the data format of the device data matches the predetermined data format. When it is determined that the data format of the device data conforms to the predetermined data format, the device is verified as correct for the device type compared in step 12; otherwise, the device is verified as incorrect for the device type compared at step 12.
In step 216, the processing unit stores the device type and the corresponding address set of the device compared in step 12 in the device lookup table.
In step 217, the processing unit does not store the device type and its corresponding address set compared in step 12 in the device lookup table.
In step 218, the processing unit determines whether the device type of the device belongs to a fourth device class. When it is determined that the device type of the device belongs to the fourth device class, step 219 is performed. Otherwise, the flow proceeds to step 222. In the present embodiment, the fourth device class includes a device type of a Multiplexer (MUX), but is not limited thereto.
In step 219, the processing unit determines whether any device is connected to one of the plurality of output ports of the apparatus. When it is determined that any one of the devices is connected to one of the output ports, step 220 is performed. Otherwise, the flow proceeds to step 221.
It is worth mentioning that the processing unit verifies whether the equipment type compared in step 12 is correct by determining whether any device is connected to one of the output ports. When it is determined that any one of the output ports is connected to any device, the equipment is verified as correct in the equipment type compared in step 12; otherwise, the device is verified as incorrect for the device type compared at step 12.
In step 220, the processing unit stores the device type and its corresponding address set compared in step 12 in the device lookup table.
In step 221, the processing unit does not store the device type and its corresponding address set compared in step 12 in the device lookup table.
In step 222, the processing unit does not store the device types and the corresponding address sets of the devices not belonging to the first device type, the second device type, the third device type and the fourth device type compared in step 12 in the device comparison table.
In summary, the method for determining the connection status and the device type of the present invention determines the device type of the device connected to the integrated circuit bus by the processing unit transmitting a plurality of inquiry requests to the addresses of the integrated circuit bus after the device is connected to the integrated circuit bus, so that the connection of the subsequent device does not need to be completely connected according to the specification of the current circuit diagram, thereby improving the flexibility of the connection of the subsequent device, and in addition, the processing unit does not need to know a device type of the device connected to the inquiry address in advance when transmitting the inquiry request including the command of the management interface of the intelligent platform to each address of the integrated circuit bus, and furthermore, the processing unit can also verify whether the device type compared according to the at least one address and the lookup table is correct by executing the verification procedure, thereby obtaining the device comparison table with high accuracy, therefore, the object of the present invention can be achieved.
The detailed description and examples of the present invention are given above with reference to the accompanying drawings, but the scope of the present invention is not limited thereto, and the equivalent modifications and variations within the scope of the claims of the present invention should be considered as falling within the scope of the present invention.
Claims (9)
1. A method for determining device connection status and device type, implemented by a processing unit, comprising: comprises the following steps:
(A) respectively transmitting a plurality of inquiry requests to a plurality of addresses of an integrated circuit bus to confirm whether any equipment is connected to each address; and
(B) when receiving a reply message from at least one device corresponding to at least one of the addresses, comparing the at least one address corresponding to the reply message of the at least one device and the corresponding device type according to a lookup table to compare the device type of the at least one device corresponding to the at least one address, wherein the lookup table comprises a plurality of device types respectively corresponding to a plurality of address sets consisting of at least one reference address;
(C) for each of the at least one device, determining whether a device type of the device belongs to a first device class, the first device class including a device type of a power supply unit;
(D) when the equipment type of the equipment is judged to belong to the first equipment type, transmitting an equipment data request to each address connected with the equipment; and
(E) when receiving the equipment data from each address connected with the equipment, determining whether the equipment data corresponding to each address are all consistent with first preset data related to the equipment type in the first equipment type, which is the same as the equipment type of the equipment;
wherein, when the equipment data corresponding to each address is determined to be consistent with the first preset data, the equipment type compared in the step (B) is verified to be correct.
2. The method of determining device connection status and device type according to claim 1, wherein: in step (B), the address set corresponding to the most reference addresses has the highest comparison order, and the address set corresponding to the least reference addresses has the lowest comparison order.
3. The method of determining device connection status and device type according to claim 1, wherein: in step (a), each query request includes an intelligent platform management interface command.
4. The method of claim 3, wherein the method further comprises: in step (A), the intelligent platform management interface command includes a read/write command type, a query address and a reply request, but does not include an instruction set of the device connected to the query address.
5. The method of determining device connection status and device type according to claim 1, wherein: after the step (E), further comprising the steps of:
(F) when the equipment data corresponding to each address are judged not to be consistent with the first preset data, judging whether the equipment data which are not consistent with the first preset data are consistent with second preset data which are related to the equipment type of a field replaceable unit or not; and
(G) when the device data not in accordance with the first predetermined data is determined to be in accordance with the second predetermined data, the device type of the device connected to the address corresponding to the device data not in accordance with the first predetermined data is verified as the device type of the field replaceable unit.
6. The method of determining device connection status and device type according to claim 1, wherein: after the step (B), further comprising the steps of:
(H) for each of the at least one device, determining whether the device type of the device belongs to a second device class, the second device class including at least one of a device type of a PCI solid state disk and a device type of a field replaceable unit;
(I) when the equipment type of the equipment is judged to belong to the second equipment type, transmitting an equipment data request to the equipment; and
(J) when receiving the device data from the device, determining whether the device data matches third predetermined data associated with a device type in the second device class that is the same as the device type of the device;
wherein, when the equipment data is determined to be consistent with the third preset data, the equipment type compared in the step (B) is verified to be correct.
7. The method of determining device connection status and device type according to claim 1, wherein: after the step (B), further comprising the steps of:
(K) for each of the at least one device, determining whether a device type of the device belongs to a third device class, the third device class including a device type of a temperature sensing unit;
(L) transmitting an equipment data request to the equipment when it is determined that the equipment type of the equipment belongs to the third equipment type; and
(M) upon receiving device data from the device, determining whether the device data conforms to a predetermined data format associated with a device type in the third device type that is the same as the device type of the device;
wherein, when the equipment data is determined to conform to the predetermined data format, the equipment type compared in step (B) is verified as correct.
8. The method of determining device connection status and device type according to claim 1, wherein: after the step (B), further comprising the steps of:
(N) for each of the at least one device, determining whether the device type of the device belongs to a fourth device class, the fourth device class comprising a device type of a multiplexer; and
(O) when it is determined that the equipment type of the equipment belongs to the fourth equipment type, determining whether any device is connected to one of the plurality of output ports of the equipment;
wherein, when it is determined that any one of the output ports is connected to any device, the equipment is verified to be correct in the equipment type compared in the step (B).
9. The method of determining device connection status and device type according to claim 1, wherein: in step (B), each reply message in response to the inquiry request contains only 1byte of data.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610901247.XA CN107957969B (en) | 2016-10-17 | 2016-10-17 | Method for judging device connection state and device type |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610901247.XA CN107957969B (en) | 2016-10-17 | 2016-10-17 | Method for judging device connection state and device type |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107957969A CN107957969A (en) | 2018-04-24 |
| CN107957969B true CN107957969B (en) | 2021-11-16 |
Family
ID=61953328
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610901247.XA Active CN107957969B (en) | 2016-10-17 | 2016-10-17 | Method for judging device connection state and device type |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107957969B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112579116B (en) * | 2019-09-29 | 2023-07-18 | 佛山市顺德区顺达电脑厂有限公司 | Control method for remote updating firmware |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1585127A (en) * | 2003-08-21 | 2005-02-23 | 松下电器产业株式会社 | Semiconductor integrated circuit device |
| CN201141902Y (en) * | 2007-09-28 | 2008-10-29 | 德律科技股份有限公司 | Detection system of electronic element |
| CN101411136A (en) * | 2006-04-03 | 2009-04-15 | 极进网络股份有限公司 | Method of performing table lookup operation with table index that exceeds CAM key size |
| CN101414175A (en) * | 2008-11-21 | 2009-04-22 | 浙江中控技术股份有限公司 | Method, apparatus and system for equipment interconnection |
| CN101604277A (en) * | 2008-06-11 | 2009-12-16 | 比亚迪股份有限公司 | I 2C bus verification system and method |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7499438B2 (en) * | 2005-01-13 | 2009-03-03 | 2Wire, Inc. | Controlling wireless access to a network |
| US7743179B2 (en) * | 2007-03-30 | 2010-06-22 | Via Technologies, Inc. | Data transmission methods |
-
2016
- 2016-10-17 CN CN201610901247.XA patent/CN107957969B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1585127A (en) * | 2003-08-21 | 2005-02-23 | 松下电器产业株式会社 | Semiconductor integrated circuit device |
| CN101411136A (en) * | 2006-04-03 | 2009-04-15 | 极进网络股份有限公司 | Method of performing table lookup operation with table index that exceeds CAM key size |
| CN201141902Y (en) * | 2007-09-28 | 2008-10-29 | 德律科技股份有限公司 | Detection system of electronic element |
| CN101604277A (en) * | 2008-06-11 | 2009-12-16 | 比亚迪股份有限公司 | I 2C bus verification system and method |
| CN101414175A (en) * | 2008-11-21 | 2009-04-22 | 浙江中控技术股份有限公司 | Method, apparatus and system for equipment interconnection |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107957969A (en) | 2018-04-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11953981B2 (en) | Memory module register access | |
| US7979597B2 (en) | Programming parallel I2C slave devices from a single I2C data stream | |
| EP1877914B1 (en) | Device identification coding of inter-integrated circuit slave devices | |
| US20230004331A1 (en) | Nand raid controller | |
| CN111295710B (en) | Apparatus and method for identifying memory devices of semiconductor devices sharing external resistance | |
| US20100217903A1 (en) | Simultaneous control of multiple i/o banks in an i2c slave device | |
| CN111488304A (en) | Interface switching circuit | |
| US20080215779A1 (en) | Slave Device with Latched Request for Service | |
| US10387361B2 (en) | Serial device with configuration mode for changing device behavior | |
| CN107957969B (en) | Method for judging device connection state and device type | |
| US11237954B2 (en) | Controller and data storage system having the same | |
| CN108920299B (en) | Storage medium | |
| US20160018866A1 (en) | System And Method For Storing Manufacturing Information And Lifetime Usage History Of A Power Module For A Memory System | |
| US20160291987A1 (en) | Programmable cable and programming method thereof | |
| US20150019772A1 (en) | Signal processing apparatus | |
| TWI607315B (en) | Method of determining connection states and device types of devices | |
| EP2782013A2 (en) | Fault-spot locating method, switching apparatus, fault-spot locating apparatus, and information processing apparatus | |
| JP2019215662A (en) | Nonvolatile memory device and interface setting method | |
| CN110362524B (en) | Time sequence signal generation method and device, logic circuit board and storage medium | |
| US20230244624A1 (en) | Methods and apparatus to preform inter-integrated circuit address modification | |
| CN118613790A (en) | Method and apparatus for address modification between preformed integrated circuits | |
| CN106548311A (en) | Stock control initialization system | |
| CN107544931B (en) | Computer system with PCI-E intensifier and setting method of PCI-E intensifier | |
| CN115185478A (en) | Audio control circuit, main device and related control method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |