JP2000101611A - Equipment for interface bus - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an equipment dealing with interface bus by which a packet transmission list is automatically updated even when an interface bus configuration such as returning on a power source and adding or removing equipment is changed. SOLUTION: A packet transmission list 1a including identification codes and node ID corresponding to equipment dealing with interface bus and a node ID/equipment information correspondence list 1b are stored in a storage device 1 under the control of a controller 3, the node ID/equipment information correspondence list at the time of reconstructing an interface bus is generated and when the interface bus is reconstructed, with the identification code as a reference, any node ID on the packet transmission list stored in the storage device 1 is updated into node ID on the generated node ID/equipment information correspondence list.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

The present invention relates to a device compatible with an interface bus connected to an interface bus, and more particularly to a device compatible with an interface bus connected to an interface bus based on the IEEE 1394 standard.

[0002]

2. Description of the Related Art In an interface bus-compatible device connected to an interface bus based on the IEEE 1394 standard (hereinafter, the interface bus-compatible device is also simply referred to as a device), when the power of a device connected to the interface bus is turned on, or When a new device is additionally connected to or deleted from the device, the bus is automatically reset and a bus connection check operation is started. By this connection confirmation, devices connected to the interface bus are automatically identified, and a destination node ID and a source node ID are assigned to each device. The node ID corresponding to each device is assigned at random, and even if the power is turned on again without changing the device, the node ID for each device is not always the same.

For this reason, there has conventionally been a packet transmission method of issuing a sequence packet in which a plurality of transmission packets are stored in a list in advance, and the packets are automatically transmitted sequentially in the order of the list when executed.

[0004]

However, as described above, when the conventional packet transmission is used, the configuration of the interface bus, such as turning on the power again, connecting a new device, or removing the device, is performed. There was a problem that the packet transmission list had to be recreated every time it changed.

An object of the present invention is to provide an interface bus-compatible device that automatically updates a packet transmission list even when the interface bus configuration is changed, such as when the power is turned on again or when devices are added or deleted.

[0006]

According to the present invention, there is provided an interface bus compatible device connected to a predetermined interface bus, wherein the packet includes an identification code and a node ID corresponding to the interface bus compatible device. Storage means for storing a transmission list and a node ID-equipment information correspondence list; generation means for generating a node ID-equipment information correspondence list when an interface bus is reconstructed; and storage means based on an identification code. Generated by the generation means for the node ID in the packet transmission list stored in
Updating means for updating to a node ID in the device information correspondence list.

According to the interface bus compatible device according to the present invention, a new node ID / device information correspondence list when the interface bus is reconstructed is generated by the generation unit and stored in the storage unit based on the identification code. The node ID in the packet transmission list is updated by the updating unit to the node ID in the node ID-device information correspondence list generated by the generating unit.

Therefore, according to the interface bus-compatible device according to the present invention, even if the configuration of the interface bus changes, the packet transmission list is automatically updated, so that the packet transmission list is re-input according to the interface bus configuration. No longer needed.

[0009]

DESCRIPTION OF THE PREFERRED EMBODIMENTS An interface bus compatible device according to the present invention will be described with reference to an embodiment. FIG. 1 is a block diagram showing a configuration of an interface bus compatible device according to one embodiment of the present invention.

An interface bus compatible device according to one embodiment of the present invention includes a storage device 1. The storage device 1 stores a packet transmission list 1a and a node ID-device information correspondence list 1b. The packet transmission list 1a stores a destination node ID, a packet type, a transfer speed, a write (read) address, a data length, data to be written, and other items. Node ID-
The device information correspondence list 1b stores items of node ID and device-specific identification code.

The device has an identification code unique to the device at a specific address position in the packet transmission list 1a. Therefore, an identification code unique to the device is stored at a specific address position of the packet transmission list 1a, and the identification code at the specific address position of the packet transmission list 1a is read to determine the device, and the node ID-device information correspondence list By referring to the contents of 1b, the node ID for the device can be determined. Here, in this specification, the identification code is a node-vendor-id, chi
It means p-id-hi and chip-id-lo.

The interface bus compatible device according to one embodiment of the present invention further includes an input device 2, a controller 3, a working memory 4, and a display device 5.
The input device 2 includes a packet transmission list generation instructing unit for instructing a packet transmission list generation and a transmission start instructing unit for instructing a transmission start, and transmits a packet to the storage device 1 under the control of the controller 3 based on the packet transmission list generation instruction. The transmission list 1a is generated, and transmission of the contents of the packet transmission list is started under the control of the controller 3 based on the transmission start instruction.

The working memory 4 stores the updated node ID / device information correspondence list 1 under the control of the controller 3.
b and node ID-device information correspondence list 1 before update
b, the node ID before the update
The contents of the device information correspondence list 1b are temporarily stored, and the contents of a response from the connected device are temporarily stored.

The display device 5 displays, under the control of the controller 3, the contents of the packet transmission list 1a, the contents of the response packet after transmitting the packets described in the packet transmission list 1a, and the like.

Here, the controller 3 creates a packet transmission list 1a including an identification code and a node ID corresponding to the interface bus compatible device and a node ID-device information corresponding list 1b and stores them in the storage device 1. Generating means for generating a node ID-device information correspondence list when the interface bus is reconfigured;
The node ID in the packet transmission list stored in the storage device 1 based on the identification code is used as the node ID in the node information-device information correspondence list generated by the generation unit.
And updating means for updating the function.

The interface bus-compatible device according to the embodiment of the present invention further includes a link layer 6 for forming a physical interface with an electric signal for transmission and reception such as a transmission packet output from the controller 3. A physical layer 7 is provided.

FIG. 2 shows the operation of the interface bus compatible device according to the embodiment of the present invention configured as described above.
This will be described with reference to the flowchart of FIG.

A packet transmission list is generated based on an instruction from the input device 2 (step S1), and an inquiry about an identification code is made to each connected device (step S2). Upon receiving the inquiry about the identification code, the connection device transmits its own identification code in response (step S).
3). An identification code sent from each connected device is obtained (step S4), and a node ID-device information correspondence list is created (step S5).

The inquiry in step S2 is performed by transmitting a quadlet packet read request signal. The same applies to step S9 described later. The reception of the identification code in step S4 is performed by receiving a quadlet packet response read signal transmitted from the connected device. Step S described later
The same applies to the case of No. 11. Since the identification code is 8 bytes and the quadlet is 4 bytes, it is necessary to inquire one device twice by changing the address. Here, the reason why the block data is not used using the quadlet is that the quadlet is a packet supported by all devices.

Subsequent to step S5, the identification code of the connected device is stored at a specific address of the packet transmission list, and the packet transmission list 1a is stored in the storage device 1 (step S6). The node ID / device information correspondence list 1b created in step S5 is stored in the storage device 1 (step S7). The node ID / device information correspondence list 1b stored in step S7 is referred to as a node ID / device information correspondence list A. This is because the node ID-device information correspondence list before the bus reconfiguration.

In this state, if power is turned on again, connected equipment is added, or connected equipment is deleted, a bus reset is performed, and a bus topology is reconstructed (step S).
8). Subsequent to step S8, as in the case of steps S2 to S5, an inquiry for an identification code is made to each connected device (step S9). Upon receiving the inquiry about the identification code, the connection device transmits its own identification code in response (step S10). An identification code sent from each connected device is obtained (step S11), and a node ID-device information correspondence list is created (step S11).
12).

The node ID / device information correspondence list created in step S12 is referred to as a node ID / device information correspondence list B. This is because the node ID-device information correspondence list is obtained after the bus topology is reconstructed. Subsequent to step S12, the packet transmission list is read (step S13), and the node ID / device information correspondence list A is read (step S14).

The node ID / device information correspondence list B created in step S12 is compared with the node ID / device information correspondence list A read out in step S14.
The changed part of the node ID is extracted from D (step S15). The changed part of the extracted node ID is
This is the part changed by the bus reset.

Following step S15, step S13
Node I in the packet transmission list read in
The changed portion of D is updated (step S1)
6). The update of the node ID in step S16 is performed based on the identification code (device). That is, the node I for the identification code in the packet transmission list
When D is changed, the node ID in the node ID-device information correspondence list for the identification code is updated to the changed node ID in the packet transmission list.

Following step S16, in response to an execution instruction from the input device 2 (step S17), the packets are transmitted to the destination connection device in the order of the packet transmission list (step S19), and a response signal from the transmission destination connection device is transmitted. Then, the contents of the transmission packet and the contents of the response packet are displayed on the display-compatible device 5 (step S20).

After step S20, steps S18 to S20 are repeated until the end of the list (step S21). Step S17 may be omitted and steps S16 to S18 may be executed. Packets are transmitted according to the packet transmission list updated as described above. Therefore, even if the node ID changes due to the bus topology reconstruction, the node ID is not updated and the transmission destination is not mistaken.

Next, a specific example will be described. As illustrated in FIG. 4, the node ID of the device A (also referred to as the main unit) is set to {@}.
1}, and the identification code is {123456781234567
8}, the node ID of device B (also referred to as another device) is {0}, and the identification code is {0000000000123456}.
78} and an identification code of $ 000000012345
It is assumed that the packet transmission list including 678 # is a packet transmission list as illustrated in FIG. 5, and the node ID / device information correspondence list A is as shown in FIG.

From this state, after the bus reset,
As shown in FIG. 7 with respect to FIG.
0}, identification code is $ 00000001234567
8}, the device B node ID changes to {1}, and the identification code changes to {1234567812345678}. As a result, the node ID-device information correspondence list B
Is as shown in FIG.

Here, focusing on the identification code, the node ID of the device having the identification code {0000000000345678} changes from {0} to {1}, and the identification code {1}
234567812345678 # Node ID of device
Is changed from {1} to {0}.

Therefore, the {destination node ID for the identification code {000000000012345678} in the packet transmission list is changed from {0} to {1}. Also, the identification code $ 1234567 in the packet transmission list
Destination node ID {1} with respect to 812345678}
Is changed to the destination node ID {0}. As a result,
The packet transmission list including the identification code {00000000012345678} is as shown in FIG. 9, and the same packet can be transmitted to the same device as the first time.

[0031]

As described above, according to the interface bus compatible device according to the present invention, even if the configuration of the interface bus changes, the packet transmission list is automatically updated. There is no need to re-enter the distribution list.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a configuration of an interface bus-compatible device according to an embodiment of the present invention.

FIG. 2 is a flowchart for explaining the operation of the interface bus-compatible device according to the embodiment of the present invention;

FIG. 3 is a flowchart for explaining an operation of the interface bus-compatible device according to the embodiment of the present invention;

FIG. 4 is a schematic diagram showing a node ID and an identification code at the time of the first connection for explaining the operation of the interface bus-compatible device according to the embodiment of the present invention;

FIG. 5 is a schematic diagram showing a packet transmission list at the time of the first connection for explaining the operation of the interface bus-compatible device according to the embodiment of the present invention;

FIG. 6 is a schematic diagram showing a node-device information correspondence list at the time of first connection for explaining the operation of the interface bus-compatible device according to one embodiment of the present invention;

FIG. 7 is a schematic diagram showing a node ID and an identification code at the time of a new connection for explaining the operation of the interface bus compatible device according to one embodiment of the present invention;

FIG. 8 is a schematic diagram showing a node-device information correspondence list at the time of new connection for explaining the operation of the interface bus-compatible device according to one embodiment of the present invention;

FIG. 9 is a schematic diagram showing a packet transmission list at the time of a new connection for explaining the operation of the interface bus-compatible device according to the embodiment of the present invention;

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 1 Storage device 2 Input device 3 Controller 4 Working memory 5 Display device 6 Link layer 7 Physical layer 1a Packet transmission list 1b Node ID-device information correspondence list

Claims (2)

[Claims] 1. An interface bus-compatible device connected to a predetermined interface bus, comprising: a packet transmission list including an identification code and a node ID corresponding to the interface bus-compatible device;
Storage means for storing a device information correspondence list; generating means for generating a node ID-device information correspondence list when the interface bus is reconstructed; and packet transmission stored in the storage means based on the identification code. Updating means for updating the node IDs in the list to the node IDs in the node ID-device information correspondence list generated by the generating means. 2. An interface bus compatible device according to claim 1, wherein said updating means updates the node ID only when the node ID is different.