JP2010157819A - Encoding device of usb device - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide the encoding device of a USB device, which can transfer a large volume of encoded data with a low load on the CPU of a computer which is connected through a USB interface, and does not require to develop a private driver for each type of CPU. <P>SOLUTION: By utilizing the fact that the specification of the encoding device is determined, as the standard specification, so that a large volume of data can be transferred with a low load on the CPU in the USB storage class, the OS in a PC is made to recognize the device of the USB storage class specified by the USB specification when connection with the PC is established, and when a sector read command is transmitted from the PC, the information corresponding to the sector number contained in the sector read command, out of the information preset for each sector number interpreted as the data, is selected and sent back to the PC as the definition processing. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention is capable of transferring a large amount of encoded data with low load to a CPU of a computer connected via a USB (Universal Serial Bus) interface, and does not require development of a dedicated driver for each CPU type. Relates to the device.

  Conventionally, an encoding apparatus that can be connected to a computer via a USB (Universal Serial Bus) interface is known.

  For example, in the system described in Patent Document 1, a USB device such as an MPEG encoder is controlled from a USB host such as a PC using a USB protocol, and MPEG data is transferred to the USB host.

By the way, as this type of encoding device, a serial port type that transfers encoded data such as moving images using a serial port, or a so-called vendor-specific type in which a vendor sets its own encoding device specifications may be adopted. Many.
JP 2001-168941 A (5th and 6th pages, FIGS. 1, 4 and 5)

  However, in the encoding apparatus as described above, when the serial port type or the vendor-specific type as described above is used, the load on the CPU is increased due to the following reasons, and a large amount of data can be transferred at high speed. There was a problem that could not be transferred.

  That is, if the encoding device is a serial port type, it is software emulation of the RS-232C device, and is not suitable for high-speed data transfer from an encoding device such as an encoding device to a PC. . In general, when emulated, the data unit of the buffer is about 256 bytes. For example, if data of about 1 Mbyte / second is flowed, the CPU on the PC side is interrupted 4000 times per second. There is a problem that it is a very large processing burden for a powerless CPU. This is particularly noticeable when moving image encoded data is transferred because the amount of data is enormous.

  If the encoding device is a vendor-specific type, there is no specific format, so the CPU load on the PC depends on the vendor's specification design. In this case, the vendor is on the PC side. Since the driver is uniquely designed and the encoding apparatus is used in combination with the designed driver, it is difficult to cope with various types of CPUs. In particular, CPUs other than x86 series are often not supported. If the encoding device is a vendor-specific type, the driver is often determined according to specifications convenient on the USB device side, resulting in a high load on the PC-side CPU that is the USB host. There were many problems.

  The present invention has been made in view of such a problem, and an object of the present invention is to transfer a large amount of encoded data to a CPU of a computer connected via a USB (Universal Serial Bus) interface with a low load. Furthermore, it is an object of the present invention to provide a USB device encoding apparatus that does not require the development of a dedicated driver for each CPU type.

  The USB device encoding apparatus according to claim 1, which has been made to solve the above problem, can be connected to a computer via a USB (Universal Serial Bus) interface, and the device information output means can be connected to the computer. At the time of establishment, information for causing an OS (Operating System) included in the computer to recognize that the device is a USB storage class device (hereinafter, USB storage type) defined by the USB standard is output. Further, when a sector read command is transmitted from the computer, the control means interprets the sector number included in the sector read command as data, and executes various definition processes set in advance based on the data. The control means executes definition processing when a sector read command is transmitted from the computer. More specifically, when the sector read command is transmitted from the computer, the control means includes, in the sector read command, information set in advance for each sector number interpreted as data as a definition process. Select the information corresponding to the sector number to be sent back to the computer.

  According to the USB device encoding apparatus of the present invention configured as described above, in the USB storage class, the specification is defined as a standard so that a large amount of data can be transferred to the CPU with a low load. When establishing a connection with a computer, an OS (Operating System) provided in the computer recognizes that the device is a USB storage class device specified by the USB standard, and a sector read command is transmitted from the computer. In this case, as the definition process, the information corresponding to the sector number included in the sector read command is selected from the information set in advance for each sector number interpreted as data and returned to the computer. Universal Serial Bus) You can transfer large amounts of video encoded data with a low load to over the other CPU.

  Furthermore, according to the USB device encoding apparatus of the present invention, since existing resources can be used, it is not necessary to develop a dedicated driver for each CPU type. Further, according to the USB device encoding apparatus of the present invention, since there are many OSs corresponding to USB storage class devices, there is an advantage that there are many corresponding OSs.

  In this case, it is conceivable that the device information output means outputs information indicating that the device is a removable HD stipulated by the SCSI standard as information for causing the OS provided in the computer to recognize that it has a data storage function. Item 2).

  By the way, when the computer recognizes that the encoding apparatus is a removable HD stipulated by the SCSI standard, a partition is set in the removable HD described above according to an instruction from the OS provided in the computer. There is a possibility that writing to the removable HD may be permitted. When a partition is set, the partition “sda1” is automatically connected to the file system “/ media / usbdisk” and can be operated by the user. In this case, when the user operates “/ media / usbdisk”, access to the USB device occurs, and during encoding, there is a problem that an unnecessary burden is imposed on the device side, which causes data loss and the like. . In addition, a minimum storage capacity operable as a file system is required. In addition, when writing to the removable HD is permitted, there is a possibility that a reserved area may be incorporated into the file system area by adding or re-partitioning a partition by a user operation. . In this case, there is a problem of causing a malfunction when controlling by the read sector address.

  Therefore, it is conceivable that the above-described removable HD is recognized by the OS provided in the computer that no partition is set and writing is prohibited. Specifically, as in claim 3, the device information output means further has no partition set in the removable HD as information for allowing the OS provided in the computer to recognize that it has a data storage function, It is also possible to output information indicating that writing is prohibited.

  According to the USB device encoding apparatus of the present invention configured as described above, the encoding apparatus itself serves as a reading apparatus such as a card reader into which a medium in which a partition is not set and a write-protected state is inserted. Can be recognized by an OS provided in the computer. This eliminates the need for a capacity to operate as a disk, so that a partition need not be set and the storage capacity may be small. Further, since it is not recognized as a disk, access from the OS provided in the computer is not received, and malfunction can be prevented. In other words, since no partition is set, there is an advantage that no unnecessary load is imposed on the device side by a user operation, and a minimum storage capacity operable as a file system is not necessary. In addition, when writing to the removable HD is prohibited, the reserved area does not have to be incorporated into the file system area even if operated by the user. In addition, since partition addition or re-partitioning is writing to sector “0”, if writing to removable HD is prohibited, these will fail and there is no problem.

Embodiments of the present invention will be described below with reference to the drawings. In addition, this invention is not limited to this embodiment, It is possible to implement in various aspects.
[First embodiment]
[1. Explanation of internal structure of information processing apparatus]
FIG. 1 is a block diagram illustrating a configuration of an encoding system 100 exemplified as an embodiment, and internal structures of the information processing apparatus 1 and the encoding apparatus 27.

  The information processing apparatus 1 as a computer described below is dedicated to a specific function configured to operate a specific function of the information processing apparatus 1 by automatically executing a predetermined program group after the power is turned on. It is a device. More specifically, in the case of the present embodiment, the information processing apparatus 1 is configured as a karaoke commander, and various functions are operated as a karaoke commander by automatically executing a predetermined program group after the power is turned on. Is configured to do.

  In the following description and drawings, the information processing apparatus 1 is appropriately expressed as a personal computer (PC).

  The information processing apparatus 1 includes a CPU 11, a ROM 13, a RAM 15, a hard disk device 17, a USB interface 20, and the like. The USB interface 20 includes an external USB port 23.

  Furthermore, in order to control these hardware, the information processing apparatus 1 is equipped with an OS. In this embodiment, Linux (registered trademark) is installed as the OS. However, since only functions provided in general Linux (registered trademark) do not have sufficient functions necessary for carrying out the present invention, some unique functions are added. The specific contents of this additional function will be described in detail later, but descriptions of other functions that are not different from general Linux (registered trademark) will be omitted.

  In the present embodiment, the encoding device 27 is connected to the external USB port 23. Similarly, the encoding device 27 includes a CPU 27b, a ROM 27c, a RAM 27d, an MPEG encoder 27e, a USB interface 27a, and the like. A video camera or the like is connected to the MPEG encoder 27e, and an audio / video moving image signal is input. The moving image data stored in various recording media is input through the I / C card slot 27f or the like.

  The information processing apparatus 1 and the encoding apparatus 27 constitute an encoding system 100.

  This encoding device 27 has a function of encoding audio / video signals to generate encoded data, a function of generating encoded data from moving image data stored in various recording media, and a data storage function of storing the generated encoded data. It is a publicly known thing to have. The various functions described above are executed by the CPU 27b included in the encoding device 27. The CPU 27b included in the encoding device 27 corresponds to device information output means and control means.

[2. Processing executed when the information processing apparatus starts up]
Next, processing executed when the information processing apparatus 1 is activated will be described.

  FIG. 2 is a flowchart of processing executed when the information processing apparatus 1 is turned on.

  When the information processing apparatus 1 is turned on, the information processing apparatus 1 first loads the OS kernel into the memory of the CPU 11 (S105). The OS kernel is stored in the ROM 13, and in S105, the CPU 11 secures a part of the RAM 15 as a RAM disk and loads the kernel onto the RAM disk. As a result, the RAM disk becomes a root volume, the OS is started, and at least some of the functions of the OS start to operate.

  When at least a part of the OS starts to function in this manner, the information processing apparatus 1 recognizes the hard disk device 17 connected by the IDE method (S110). In S110, a drive name is assigned to the hard disk device 17, and in the present embodiment, the drive name of the hard disk device 17 is “hda”.

  Subsequently, the information processing apparatus 1 starts SCSI drive connection monitoring (S115). In the present embodiment, in S115, the SCSI drive connection monitoring process is started. Thereafter, the process stays resident until the information processing apparatus 1 is turned off. Connect / disconnect is monitored.

  The details of the SCSI drive connection monitoring process are as shown in FIG.

  That is, when “intra-OS SCSI drive connection monitoring” shown in FIG. 3 is started, the information processing apparatus 1 first initializes the “SCSI-I / F connection table (hereinafter referred to as SITB)” (S205). ). The SITB is a table for registering a SCSI interface (hereinafter referred to as SCSI-I / F) that is currently connected in the information processing apparatus 1. In S205, for example, when there is a SCSI-I / F mounted as hardware, processing for registering the information in the SITB is executed.

  If there is a drive connected to the I / F registered in S205, the drive is registered in the system (S210). By this S210, drive names such as “sda”, “sdb”,... Are assigned to the registered drives.

  Subsequently, the information processing apparatus 1 determines whether or not a certain time (for example, 6 seconds) has elapsed (S215). If it has not elapsed (S215: No), the process returns to S215, and the time elapses. wait. When a certain time has elapsed (S215: Yes), the currently connected SCSI-I / F is confirmed (S220).

  Thereafter, the information processing apparatus 1 determines whether or not there is a newly connected SCSI-I / F (S225). If there is no newly connected SCSI-I / F (S225: none), the currently disconnected SCSI-I The presence / absence of I / F is determined (S230). If there is no SCSI-I / F disconnected this time (S230: No), the process returns to S215. As a result, S215 to S230 are repeatedly executed approximately every 6 seconds.

  Then, when such a repetitive process of S215 to S230 is executed, if there is a newly connected SCSI-I / F (S225: present), the information processing apparatus 1 determines that the new SCSI-I / F Is registered in the above-mentioned SITB, and the drive connected to the I / F is registered in the system (S235).

  By this S235, drive names such as “sda”, “sdb”,... Are assigned to the registered drives. Further, since information on the capacity of the drive is also required at the time of registering the drive, a read capacity command, which is one type of SCSI command defined by the SCSI standard, is issued in order to acquire the information.

  At this time, in the information processing apparatus 1, the drive name for which the read capacity command is issued is stored in a storage area prepared for each SCSI-I / F. Such a process is a special process that is not performed in general Linux (registered trademark), and is a process unique to the information processing apparatus 1.

  Incidentally, when a plurality of SCSI drives are connected to one SCSI-I / F, the above-described read capacity command is sequentially issued to the plurality of SCSI drives. For this reason, the drive name for which the read capacity command is issued also changes in order, so that the drive for which the last read capacity command is issued is stored in the storage area prepared for each SCSI-I / F. The name will be stored.

  However, if one SCSI drive is connected to one SCSI-I / F, the above-described read capacity command is issued only to one SCSI drive. Therefore, the drive name for which the read capacity command is issued does not change, and the drive name connected to the SCSI-I / F is stored in the storage area prepared for each SCSI-I / F. It will be.

  When S235 is completed, the information processing apparatus 1 determines whether or not the processing of all the SCSI-I / Fs connected this time has been completed (S240), and if not completed (S240: No, the next I / F F)), returning to S235, S235 is repeated for the remaining SCSI-I / F. When all SCSI-I / F processes connected this time are completed (S240: Yes), the process proceeds to S230.

  In addition, when the SCSI-I / F that is disconnected this time is present while the repetition processing of S215 to S230 is performed (S230: Yes), the information processing apparatus 1 transmits the disconnected SCSI-I / F from SITB. The drive connected to the I / F is deleted from the system (S245). By this S245, the drive name corresponding to the deleted drive disappears from the system.

  Then, the information processing apparatus 1 determines whether or not the processing of all the SCSI-I / Fs that have been disconnected this time has ended (S250), and if it has not ended (S250: No to the next I / F), S245 By returning to step S245, S245 is repeated for the remaining SCSI-I / F. When the processing of all the SCSI-I / Fs disconnected this time is completed (S240: Yes), the process returns to S215.

  Now, the process as described above is a process started by S115, but here, returning to FIG. 2 again, the description from the point of time when S115 is completed will be continued. When S115 ends, the information processing apparatus 1 starts USB connection monitoring (S120). In the case of this embodiment, in this S120, the USB connection monitoring process is started, and after that, the process stays resident until the information processing apparatus 1 is turned off. Connect / disconnect is monitored.

  The details of the USB connection monitoring process are as shown in FIG.

  That is, when “in-OS USB connection monitoring” shown in FIG. 3 is started, the information processing apparatus 1 first initializes a “USB device connection table (hereinafter referred to as UDTB)” (S305). The UDTB is a table for registering the currently connected USB device in the information processing apparatus 1. In S305, the USB device is handled as being in a state where nothing is connected.

  Subsequently, the information processing apparatus 1 determines whether or not a certain time (for example, 100 milliseconds) has elapsed (S315). If it has not elapsed (S315: No), the process returns to S315, and the time has elapsed. Wait for. When a certain time has elapsed (S315: Yes), the currently connected USB device is confirmed (S320).

  Thereafter, the information processing apparatus 1 determines whether or not there is a newly connected USB device (S325), and if there is no newly connected USB device (S325: no), determines whether or not there is a USB device that has been disconnected this time. (S330). If there is no USB device disconnected this time (S330: No), the process returns to S315. As a result, S315 to S330 are repeatedly executed approximately every 6 seconds.

  Then, when such a repetitive process of S315 to S330 is executed, if there is a newly connected USB device (S325: present), the information processing apparatus 1 registers the new USB device in the UDTB described above. The device driver is registered in the system (S335). This S335 is a process as shown in detail in FIG.

  That is, as shown in FIG. 5, the information processing apparatus 1 first determines the type of the USB device (S405). If it is determined that the device is a USB storage class device (S405: USB storage class), a virtual SCSI-I / F (virtual SCSI host adapter) is registered in the system and a symbol of “SCSIm” is given from the system. (S410). Note that “m” in the “SCSIm” is a serial number from “0”, and is a number that is reused after disconnection.

  Further, the information processing apparatus 1 receives the information disclosure unit in “/ proc / scsi / usb-storage” as a system registration and is given the symbol “/ proc / scsi / usb-storage / n” from the system (S415). Note that “n” in the above “/ proc / scsi / usb-storage / n” is a serial number from “0”, which is a number that is not reused after cutting.

  On the other hand, if it is determined in S405 that the device is a device other than the USB storage class (S405: other than the USB storage class), the information processing apparatus 1 performs a registration process for each USB device (S420). The process of S420 can be divided into several processes depending on the type of the USB device, but the details of this process are not the main part of the present invention, and thus further explanation is omitted.

  When the processing of S405 to S420 as described above (see FIG. 5) is finished, S335 shown in FIG. 4 is finished. In this case, the information processing apparatus 1 performs processing for all the USB devices connected this time. It is determined whether or not the processing has been completed (S340).

  Here, if the processing of all the USB devices connected this time has not been completed (S340: No, to the next I / F), the process returns to S335, and S335 is repeated for the remaining USB devices. When the processing of all the USB devices connected this time is completed (S340: Yes), the process proceeds to S330.

  Further, when the USB device disconnected this time is present (S330: Yes) while the repetitive processing of S315 to S330 is performed, the information processing apparatus 1 deletes the disconnected USB device from the UDTB, and the I / O The drive connected to F is deleted from the system (S345). This S345 is a process as shown in detail in FIG.

  That is, as shown in FIG. 6, the information processing apparatus 1 first determines the type of the USB device (S505). If it is determined that the device is a USB storage class device (S505: USB storage class), the information disclosing means of “/ proc / scsi / usb-storage / n” is deleted from the system (S510). As already explained, this number “n” is never reused.

  Also, the virtual SCSI-I / F (virtual SCSI host adapter) of “SCSIm” is deleted from the system (S515). As already described, the number “m” may be reused as necessary.

  On the other hand, if it is determined in S505 that the device is a device other than the USB storage class (S505: other than the USB storage class), the information processing apparatus 1 performs a deletion process for each USB device (S520). The process of S520 is divided into several processes depending on the type of the USB device, but the details of this process are not the main part of the present invention, and thus further explanation is omitted.

  When the processes of S505 to S520 as described above (see FIG. 6) are finished, S345 shown in FIG. 4 is finished. In this case, the information processing apparatus 1 performs the process for all the USB devices that have been disconnected this time. It is determined whether or not the processing has been completed (S350). Here, if the processing of all the USB devices disconnected this time has not been completed (S350: No, to the next I / F), the process returns to S345, and S345 is repeated for the remaining USB devices. When the processing of all the USB devices disconnected this time is completed (S340: Yes), the process returns to S315.

  Now, the process as described above is a process started by S120. Here, it returns to FIG. 2 again, and the description from the time when S120 is finished is continued. When S120 ends, the information processing apparatus 1 recognizes all connected USB devices when the power is turned on (S125). This recognition is performed because the USB connection monitoring process is started in S120.

  If there is a USB storage device among the recognized USB devices, the drive existing therein is recognized as a SCSI drive (S130). Such recognition is performed because the SCSI drive connection monitoring process is started in S115.

  Subsequently, in the information processing apparatus 1, the initialization of the kernel is terminated, and the first script is executed (S135). Then, mount processing of the volume used in the main is executed (S140).

  This S140 is a process as shown in detail in FIG. That is, when the processing shown in FIG. 7 is started, the information processing apparatus 1 mounts the file system “/ dev / hda1” on a predetermined mount point “/ main” (S605). Here, the drive name “hda” and the file system name “hda1” are predetermined matters in the configuration of the information processing apparatus 1.

  When S605 is completed, it is determined whether or not the mounting is successful (S610). If the mounting is successful (S610: success), the script “/main/prog/startup.sh” in the mounted volume is executed (S615).

  On the other hand, if mounting fails in S610 (S610: success), the script “/main/prog/startup.sh” cannot be executed as it is, and the information processing apparatus 1 cannot be started normally.

  Therefore, in this case, the SCSI drive name is determined from the backup operation USB port (S620). This S620 is a process as shown in detail in FIG. That is, when the processing shown in FIG. 8 is started, the information processing apparatus 1 first searches for a file under “/ proc / scsi / usb-storage” (S705).

  Then, it is determined whether there is a file (S710). If there is a file (S710: Yes), the found file is read (S715). Here, the read target file “/ proc / scsi / usb-storage / n” is an information disclosing means for providing information on the USB storage device and the USB port.

  In S715, by reading the file, it is possible to acquire USB port information, USB storage device information, and the like. Also, such USB port information and USB storage device information are information that can be obtained by general Linux (registered trademark), but in this information processing apparatus 1, in S715, the information was assigned to the USB storage device. You can also get the drive name.

  This drive name is the drive name itself stored in the storage area prepared for each SCSI-I / F by the processing of S235. In the case of general Linux (registered trademark), when the SCSI-I / F is used, the drive name is not notified to the SCSI-I / F, so the SCSI drive connected to the SCSI-I / F is not used. However, there is no way for the SCSI-I / F side to know what drive name is assigned.

  However, in this information processing apparatus 1, as described above, every time a read capacity command is issued, the drive name to which the command is issued is transmitted to the SCSI-I / F side, and the drive name is the SCSI name. -It remains in the storage area on the I / F side.

  Therefore, by looking at the information remaining in this storage area, the SCSI-I / F side can know what drive name is assigned to the SCSI drive connected to the SCSI-I / F. it can.

  When a plurality of SCSI drives are connected to the SCSI-I / F, only the name assigned to one of the SCSI drives is left in the storage area on the SCSI-I / F side. However, in the case of a USB storage device, one virtual SCSI-I / F is generated for one USB storage device. Therefore, since only one drive name is always left in the storage area corresponding to the SCSI-I / F, the drive name assigned to the USB storage device can be specified without any problem.

  That is, by looking at the information acquired in S715, it is possible to specify which USB port the information corresponds to, as in general Linux (registered trademark). In addition, unlike general Linux (registered trademark), it is possible to specify what drive name the information corresponds to.

  Therefore, after completing S715, the information processing apparatus 1 first determines the connection port (S720), and checks whether the information corresponds to the internal USB port 21 or not. If the information does not correspond to the internal USB port 21 (S720: USB port is different), the process returns to S710. Incidentally, the process returns to S710 in this way when the USB storage device is connected to either of the external USB ports 22 and 23.

  On the other hand, if it is information corresponding to the internal USB port 21 in S720 (S720: USB port searched for), the name of the drive that executed the read capacity last is acquired (S725). That is, the drive name is extracted from the information read in S715.

  This drive name is a drive name such as “sda”, “sdb”,..., But there is no guarantee what the letters “a”, “b”,. Specifically, when the USB storage device 25 is connected to the internal USB port 21 and the USB storage device is also connected to the external USB ports 22 and 23, the drive name “sda” is included in the previously recognized device. Is granted. Further, the drive name “sdb” is given to the device recognized thereafter. However, since it is undefined which device is recognized first, for example, it is undefined whether the device to which the drive name “sda” is assigned is the USB storage device 25.

  In this regard, if the information corresponding to the internal USB port 21 is searched for in S710 to S720, and the drive name is extracted in S725, the drive name assigned to the USB storage device 25 connected to the internal USB port 21 is surely determined. You can get it.

  If there is no file to be read before the intended USB port is found in S710 (S710: No), the processing shown in FIG. 8 is terminated. This corresponds to processing when the USB storage device 25 is not connected to the internal USB port 21.

  When the process described above is completed, the process of S620 illustrated in FIG. 7 is completed. In this case, the information processing apparatus 1 sets the file system “/ dev / sdx1” to a predetermined value. Mount on the mount point “/ main” (S625). Here, “sdx” is the drive name acquired in S725. That is, a partition (file system) on the SCSI drive is specified using the drive name of the SCSI drive determined in the processing up to S725, and the partition is mounted at “/ main”.

  When S625 is completed, it is determined whether or not the mounting is successful (S630). If the mounting is successful (S630: success), the process proceeds to S615 already described, and the script “/ “main / prog / startup.sh” is executed (S615). If the mounting has failed (S630: failure), the processing shown in FIG. 7 ends.

  When the processing as described above is completed, S140 shown in FIG. 2 is completed. Subsequently, in the information processing apparatus 1, the startup program in the main volume used is activated (S145). That is, whether “hda1” or “sdx1” is mounted on “/ main” depends on the situation, but in any case, the startup program in any volume is started.

  In the information processing apparatus 1, the system operates as a dedicated device (S150), and thereafter, the operation as the dedicated device is continued until a shutdown instruction is received from the user (S155: No). On the other hand, if there is a shutdown instruction from the user (S155: Yes), a shutdown process is executed (S160), and the power is turned off.

[3. Explanation of video encoding application processing]
Next, the video encoding application process executed by the information processing apparatus 1 will be described. FIG. 9 is a flowchart of the moving image encoding application process. FIG. 13 is a time chart of processing executed by the encoding system 100.

  This process is repeatedly executed when the startup program is activated and the system starts to operate as a dedicated device (S150) until a shutdown instruction is received from the user (S155: No).

  In the information processing apparatus 1, first, processing for searching for a moving image encoding board is executed (S805). The details of the processing for searching for the moving image encoding board are as shown in FIG.

  That is, when the process for searching for the moving image encoding board shown in FIG. 10 is started, the information processing apparatus 1 first sets the target drive to “/ dev / sda” (S905). Then, the information processing apparatus 1 opens the target drive (S910). In the case of an open error, the information processing apparatus 1 proceeds to S935 described later in order to perform processing for setting to the next target drive.

  Subsequently, the information processing apparatus 1 reads sector “0” (S915). In the case of a read error, the information processing apparatus 1 proceeds to S935 described later in order to perform processing for setting the next target drive.

  Subsequently, the information processing apparatus 1 checks the partition table and determines whether the partition table has no partition (S920). If it is determined that the partition table is not a partition table without a partition, that is, a partition table with a partition (S920: No), the information processing apparatus 1 performs processing for setting the next target drive. To do so, the process proceeds to S935 described later.

  On the other hand, when it is determined that the partition table has no partition (S920: Yes), the information processing apparatus 1 reads the sector “0x00f30000” (S925). That is, the status is read.

  Subsequently, the information processing apparatus 1 determines whether the third and subsequent bytes of the sector data are check data (S930). If the third and subsequent bytes of the sector data are check data (S930: Yes), the information processing apparatus 1 determines that a moving image encode board has been found and ends this processing.

  On the other hand, if the third and subsequent bytes of the sector data are not check data (S930: No), the information processing apparatus 1 determines whether the target drive is “/ dev / sdz”. “Z” in “sdz” indicates the last drive. If the target drive is not “/ dev / sdz” (S935: No), the information processing apparatus 1 changes the target drive to the next drive (S940). For example, “/ dev / sda” is changed to “/ dev / sdb” or “/ dev / sdb” is changed to “/ dev / sdc”. Then, the information processing apparatus 1 returns to S910 to confirm whether or not the drive set as the target drive in S940 is a video encoding board.

  On the other hand, if the target drive is “/ dev / sdz” (S935: Yes), all the drives have been confirmed, but the third and subsequent bytes of the sector data are not the check data, so the information processing apparatus 1 It is determined that the encoding board has not been found, and this process is terminated.

  Now, the process as described above is a process started in S805. Here, the description returns to FIG. 9 again, and the description from the point of time when S805 is completed is continued. When S805 ends, the information processing apparatus 1 ends this process with an error if no moving image encoding board is found as a result of executing S805. On the other hand, when the moving image encoding board is found, the information processing apparatus 1 reads the encoding setting from the setting file of the moving image encoding board (S810).

  Subsequently, the information processing apparatus 1 reads the sector “0x00f4xxx” and changes the encoding setting according to the content (S815).

  Subsequently, the information processing apparatus 1 waits until there is an operation from the user (S820: No). When there is an operation from the user (S820: Yes), the content of the operation from the user is determined (S825). .

  First, when the content of the operation from the user is a request for termination (S825: termination request), this processing is terminated.

  When the content of the operation from the user is a request to change the setting (S825: setting change), the information processing apparatus 1 writes the changed content in the setting file (S830) and reads the sector “0x00f4xxx”. Then, the encoding setting is changed according to the content, and the process returns to S625.

  If the content of the operation from the user is a request to start recording (S825: start recording), the information processing apparatus 1 sets “edsec” (encoded data sector) to “0x00100000” (S840) The sector “0x00f10000” is read to instruct the start of encoding (S845). Further, it is determined whether or not there has been an operation for requesting the end of the process from the user (S850).

  When there is an operation for requesting the end of the process from the user (S850: Yes), the information processing apparatus 1 reads the sector “edsec” to read the encoding result, and the read encoding result is a file. (S870), the sector "0x00f20000" is read to instruct the end of encoding (S875), and the process returns to S820 to wait until the next user operation is performed. On the other hand, when there is no operation for requesting the end of the process from the user (S850: none), the information processing apparatus 1 reads the sector “edsec” to read the encoding result, and “ The value of “edsec” is increased, and the read encoding result is stored in the file (S855). Then, the sector “0x00f30000” is read to read the status (S860), and it is further determined whether or not an error has occurred from the read status (S865).

  If it is determined that an error has occurred (S865: yes), the information processing apparatus 1 proceeds to S875 to instruct the end of encoding. On the other hand, if it is determined that no error has occurred (S865: None), the process returns to S850 to wait for an operation requesting the end of the process from the user.

[4. Explanation of SCSI command processing]
Next, SCSI command processing executed by the encoding apparatus will be described.

  FIG. 11 is a flowchart of SCSI command processing.

  The encoding device 27 first determines whether a SCSI command has arrived from the PC (S1005). When the SCSI command has not arrived from the PC (S1005: does not come), it waits until the SCSI command arrives from the PC, and when the SCSI command from the information processing apparatus 1 has arrived (S1005: has come). The contents of the arrived command are determined (S1010).

  First, if the content of the arrived command is read capacity, it is determined that the last sector number is “0x00ffffff” and indicates that the capacity is 8 Gbytes (S1020), and the next SCSI command is The process returns to S1005 to wait for arrival.

  If the content of the arrived command is sector write, it is determined that it indicates a write prohibition error (S1025), and the process returns to S1005 to wait until the next SCSI command arrives.

  If the content of the arrived command is mode sense, it is determined that it indicates that a write prohibition error has been inserted (S1030), and waits until the next SCSI command arrives. The process returns to S1005.

  If the contents of the arrived command are other than the above contents (others), it is determined that the command is an instruction to respond to each command (S1035), and the process waits until the next SCSI command arrives. Therefore, the process returns to S1005.

  If the content of the arrived command is a sector read, the encoding apparatus determines the read address (S1015).

  First, if the read address is “0x00000000”, the encoding apparatus returns a partition table with no partition (S1040), and returns to S1005 to wait until the next SCSI command arrives.

  If the read address is “0x00100000” to “0x00effffff”, the encoding apparatus returns the encoded data as sector data (S1045), and goes to S1005 to wait until the next SCSI command arrives. Return. In this case, the upper limit of one data is 7 GB.

  If the read address is “0x00 xxxxxxxx”, the encoding apparatus operates according to the “xxxxxxxx” portion of the read address (S1050). The details of this process are as shown in FIG. That is, when the process shown in FIG. 12 is started, the encoding apparatus first determines the sector address (S1105).

  First, when the sector address is “0x00f10000”, encoding is started (S1110), and the process returns to the call source. At this time, an error code is returned in the first or second byte of the sector data.

  If the sector address is “0x00f20000”, encoding is terminated (S1115), and the process returns to the call source. At this time, an error code is returned in the first or second byte of the sector data.

  If the sector address is “0x00f30000”, the status is returned as the first or second byte of the sector data (S1120), and the process returns to the caller.

  If the sector address is “0x00f4xxxx”, the encoding setting is changed according to the “xxxxxxxx” portion of the sector address (S1125), and the process returns to the caller.

  If the sector address is other than the above (others), the sector data that is all “0x00” is returned (S1130), and the process returns to the caller.

  Now, the process as described above is a process started in S1050. Here, the description returns to FIG. 11 again, and the description from the time point when S1050 is completed is continued. After finishing S1050, the encoding apparatus returns to S1005 to wait until the next SCSI command arrives. If necessary, the execution result is returned as sector data.

  If the read address is other than the above (others), the sector data that is all “0x00” is returned (S1055), and the process returns to S1005 to wait until the next SCSI command arrives.

[5. Effects of the embodiment]
As described above, according to the encoding system 100 of the present embodiment, the USB storage class uses the fact that the specification is defined as a standard so that a large amount of data can be transferred to the CPU with a low load. 27, when establishing a connection with the information processing apparatus 1, the OS of the information processing apparatus 1 recognizes that the device is a USB storage class device defined by the USB standard, and the sector from the information processing apparatus 1 When a read command is transmitted, information processing apparatus selects information corresponding to the sector number included in the sector read command from information preset for each sector number interpreted as data as definition processing 1 to the information processing apparatus 1 connected via the USB interface 20 You can transfer large amounts of video encoded data with a low load to PU11.

  Further, according to the encoding system 100 of the present embodiment, since existing resources can be used, it is not necessary to develop a dedicated driver for each CPU type. Further, according to the encoding system 100 of the present embodiment, since there are many OSs corresponding to USB storage class devices, there is an advantage that there are many corresponding OSs.

  Also, according to the encoding system 100 of the present embodiment, the encoding device 27 is a removable HD defined by the SCSI standard as information for causing the OS provided in the information processing device 1 to recognize that it has a data storage function. Information indicating that no partition is set in the removable HD and writing is prohibited. As a result, the encoding apparatus 27 can cause the OS included in the information processing apparatus 1 to recognize itself as a reading apparatus such as a card reader in which a medium in which a partition is not set and a write-protected state is inserted. it can. This eliminates the need for a capacity to operate as a disk, so that a partition need not be set and the storage capacity may be small. Further, since it is not recognized as a disk, access from the OS provided in the information processing apparatus 1 is not received, and malfunctions can be made difficult to occur. In other words, since no partition is set, there is an advantage that no unnecessary load is imposed on the device side by a user operation, and a minimum storage capacity operable as a file system is not necessary. In addition, when writing to the removable HD is prohibited, the reserved area does not have to be incorporated into the file system area even if operated by the user. In addition, since partition addition or re-partitioning is writing to sector “0”, if writing to removable HD is prohibited, these will fail and there is no problem.

FIG. 3 is a block diagram showing a configuration of an encoding system, an information processing apparatus, and internal structures of the encoding apparatus 27. The flowchart of the process performed with the power supply ON of information processing apparatus. The flowchart of the SCSI drive connection monitoring in OS. The flowchart of USB device connection monitoring in OS. The flowchart which shows the detail of S335. The flowchart which shows the detail of S345. The flowchart which shows the detail of S140. The flowchart which shows the detail of S620. The flowchart of a moving image encoding application process. Flowchart showing details of S805 The flowchart of a SCSI command process. Flowchart showing details of S1050 A time chart of processing executed by the encoding system.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 ... Information processing apparatus, 11 ... CPU, 13 ... ROM, 15 ... RAM, 17 ... Hard disk device, 20 ... USB interface, 23 ... External USB port, 27 ... Encoding device, 27a ... USB interface, 27b ... CPU, 27c ... ROM, 27d ... RAM, 27e ... MPEG encoder, 27f ... I / C card slot, 31 ... housing, 100 ... encoding system

Claims (3)

A computer is an encoding device for a USB device that can be connected via a USB (Universal Serial Bus) interface,
Device information output means for outputting information for allowing an OS (Operating System) provided in the computer to recognize that the device is a USB storage class device defined by the USB standard when establishing a connection with the computer;
Control means for interpreting a sector number included in the sector read command as data when a sector read command is transmitted from the computer, and executing various definition processes set in advance based on the data; Prepared,
When the sector read command is transmitted from the computer, the control means includes, as the definition process, information set in advance in each sector number interpreted as the data included in the sector read command. The USB device encoding apparatus, wherein information corresponding to the sector number is selected and returned to the computer. The USB device encoding apparatus according to claim 1,
The device information output means outputs information indicating that the device is a removable HD defined by the SCSI standard as information for causing the OS provided in the computer to recognize that it has a data storage function. Encoding device. The USB device encoding apparatus according to claim 2,
The device information output means further includes information indicating that no partition is set in the removable HD and writing is prohibited as information for causing the OS provided in the computer to recognize that the device has a data storage function. An encoding device for a USB device characterized by outputting.

Images