Method for interfacing a first data read / write unit with a second data read / write unit and interface module thereof - Patents.com

The method for interfacing data reading and writing units with interface modules in FPGA and SoC-FPGA systems addresses data transfer speed issues by managing FIFO memory operations, enhancing system performance through efficient data flow control.

JP2024542202APending Publication Date: 2024-11-13エラム エスアールエル
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
JP2024529518
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2021-11-24
Filing Date
2022-11-18
Publication Date
2024-11-13

AI Technical Summary

Technical Problem

Data processing and acquisition systems, such as those using FPGA and SoC-FPGA units, face issues with data transfer speed due to small storage capacity in FIFO memory modules, leading to compromised overall system performance.

Method used

Implementing a method for interfacing data reading and writing units with respective interface modules that manage data flow to prevent writing to full FIFO memory modules and reading from empty ones, using control algorithms to ensure efficient data transfer beyond the memory buffer size.

Benefits of technology

This approach enhances data transfer speed and improves the performance of data processing and acquisition systems by preventing FIFO memory module wait states, allowing for highly configurable data management.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024542202000001_ABST
    Figure 2024542202000001_ABST
Patent Text Reader

Abstract

The present invention relates to a method for interfacing a first data read unit (245) with a second data read unit (260a), said first data read unit (245) and said second data read unit (260a) being operatively connected to a data read interface module (310), said method comprising: a data read request phase, in which a data read request signal (R-Req) is received by said data read interface module (310), said data read request signal (R-Req) being asserted; a read status signaling phase, in which a data read status signal (R-Stat) is received by said data read interface module (310), said data read status signal (R-Stat) being asserted if there is no data (Q) in said second data read unit (260a); a read status verification phase, in which said data read interface module (310) is operatively connected to said data read interface module (310), a module (310) verifies whether the data read status signal (R-Stat) is asserted; if asserted, the data read request signal (R-Req) will be unasserted by the data read interface module (310) and sent to the second data read unit (260a), and a data read wait signal (R-Wait) will be asserted by the data read interface module (310) and sent to the first data read unit (245); if not, the data read interface module (310) will send the data read request signal (R-Req) to the second data read unit (260a), and the data read interface module (310) will receive the data (Q) from the second data read unit (260a) and send the data (Q) to the first data read unit (245).
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to a method for interfacing a first data reading unit with a second data reading unit according to the preamble of claim 1.

[0002] In particular, described herein are a method for interfacing a first data reading unit with a second data reading unit, and a method for interfacing a first data writing unit with a second data writing unit, as well as respective data reading and data writing interface modules.

[0003] The invention may be used in any data processing and / or acquisition system that may be configured with one or more functional modules, such as a processing system with an FPGA (Field Programmable Gate Array) unit and / or a SoC-FPGA (System on Chip FPGA) unit, etc. Several types of FPGA or SoC-FPGA units currently exist, which may be used in various data processing and / or acquisition systems, such as image and / or video acquisition and coding systems.

[0004] Such systems suffer from several drawbacks, examples of which are listed below.

[0005] A first drawback lies in the fact that such a system suffers from several critical situations in terms of data transfer speed during data read and / or write processes; such critical situations are due to the small storage capacity of memory buffers, e.g. FIFO memory modules implemented in FPGA and / or SoC-FPGA units.

[0006] A second drawback stems from the fact that the performance of the processing and / or acquisition system as a whole is compromised due to poor data transfer rates.

[0007] It is therefore an object of the present invention to solve these and other problems of the prior art, and in particular to provide a method for interfacing a first data reading unit with a second data reading unit, and a method for interfacing a first data writing unit with a second data writing unit, as well as respective data reading and data writing interface modules, which enable to reduce critical situations caused by low data transfer rates during data reading and / or writing processes.

[0008] A further object of the present invention is to provide a method for interfacing a first data read unit with a second data read unit, and a method for interfacing a first data write unit with a second data write unit, as well as respective data read and data write interface modules, which enable effectively controlling the flow of data being read and / or written in functional modules included within the FPGA and / or SoC-FPGA unit.

[0009] Briefly, the invention described herein comprises a method for interfacing two or more units, configurable as FPGA and / or SoC-FPGA units, implementing two or more functional modules, such as, for example, FIFO memories, functional modules, DMA (Direct Memory Access) functional modules, data acquisition (DAQ) functional modules, data output functional modules, data processing modules, communication modules, etc., for the purpose of reading and / or writing data.

[0010] Further advantageous features of the invention are set out in the appended claims, which form an integral part of this specification. [Brief description of the drawings]

[0011] The present invention will now be described in detail through some non-limiting exemplary embodiments thereof with particular reference to the accompanying drawings, in which: [Figure 1] 1 is a schematic diagram of a data processing and / or acquisition system according to one embodiment of the present invention. [Diagram 2] FIG. 2 is a schematic block diagram of an SoC-FPGA unit of the system of FIG. 1. [Diagram 3] 3 is a schematic diagram of a data read interface module and a data write interface module implemented in the SoC-FPGA unit of FIG. 2. [Figure 4] 4a and 4b are a first flowchart illustrating a method for interfacing a first data reading unit with a second data reading unit and a second flowchart illustrating a method for interfacing a first data writing unit with a second data writing unit, respectively, according to this embodiment of the present invention. [Diagram 5] 5a to 5d are diagrams of an example of signals exchanged with reference to the first and second flow charts of FIG. 4a and FIG. 4b. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] 1 shows diagrammatically a data processing and / or acquisition system 100 which may comprise a first processing means 110, an I / O interface means 120, a memory means 130 and a second processing means 200. These may be interconnected via a communication bus 101, such as a PCI bus.

[0013] The I / O interface means 120 is adapted to receive and transmit input / output information from the system 100 to a user, for example to enable the user to manage the system 100. The I / O interface means 120 may comprise, for example, a screen, a keyboard, a touch screen, etc. The I / O interface means 120 may also comprise a communication means adapted to establish a communication channel to a server. The communication means may comprise, for example, an interface such as USB, CANBUS, ETHERNET, WiFi, Bluetooth, GSM, etc.

[0014] The memory means 130 is adapted to store information and instructions for the system 100 according to this embodiment of the invention and may comprise, for example, a flash type solid state memory, an SDRAM memory, etc. The information may comprise, for example, data and / or parameters relating to the system 100 and necessary for its operation.

[0015] The first processing means 110 is adapted to process information and instructions stored in the memory means 130 with reference to the I / O interface means 120 and the second processing means 200 described in more detail hereinafter. The first processing means 110 may comprise, for example, a multi-core ARM processor, a multi-core x86 processor, etc.

[0016] 2, the second processing means 200 may, according to this embodiment of the present invention, comprise, for example, a SoC-FPGA unit, such as an Altera Cyclon V unit. In particular, the second processing means 200 may comprise, for example, a HPS (Hard Processor System) unit 210 and an FPGA unit 240 operatively connected to each other using a first interface 230 and a second interface 235.

[0017] The HPS unit 210 may comprise a microprocessor 215, e.g., an ARM Cortex-A9 MPCore processor, and an SDRAM controller 225, operatively connected to each other using a connection unit 220, e.g., an L3-Interconnect unit. In particular, the microprocessor 215 controls the connection unit 220, which further handles the flow of control data sent from the HPS unit 210 to the FPGA unit 240 and vice versa via a first interface 230, which may comprise, for example, a lightweight bridge bus having a 32-bit data width. Moreover, the connection unit 220 handles the flow of data from the HPS unit 210 to the FPGA unit 240 and vice versa via a second interface 235, which may comprise, for example, an HPS-to-FPGA bridge bus and an FPGA-to-HPS bridge bus having a configurable 32-bit, 64-bit, or 128-bit data width.

[0018] The FPGA unit 240 comprises a number of programmable logic elements and a number of reconfigurable interconnects that allow the logic elements to be physically connected to each other. It is therefore possible to configure the logic elements to implement simple functional modules, such as, for example, AND and / or OR logic ports. Additionally or alternatively, the logic elements may be configured to implement complex functional modules, such as, for example, a FIFO memory functional module, a DMA (Direct Memory Access) functional module, a Data Acquisition (DAQ) functional module, a data output functional module, a data processing module, a communication module, and the like. Such functional modules may be configured, i.e. implemented, in the FPGA unit 240 by VHDL (VLSI Hardware Description Language), which allows describing hardware components. Indeed, VHDL is not an executable language, and therefore it does not describe the operations that a processor needs to perform to compute the result of a processing activity; on the contrary, the VHDL language describes the logic elements that constitute a circuit capable of performing the required processing. Such functional modules implemented by VHDL may thus create interconnectable complex units, i.e. such units may comprise one or more functional modules operatively connected to each other.

[0019] In particular, according to this embodiment of the present invention, the first data read unit 245 and the second data read unit 260a, which are operably connected to the data read interface module 310, and the first data write unit 255 and the second data write unit 260b, which are operably connected to the data write interface module 320, are implemented in the FPGA unit 240 by VHDL, for example, using INTEL's Quartus-prime platform.

[0020] The first data read unit 245 may comprise a DMA module for reading data, hereafter referred to as R-DMA, the first data write unit 255 may comprise a further DMA module, hereafter referred to as W-DMA, while the second data read and write unit 260 may comprise both a second data read unit 260a and a second data write unit 260b; for example, the second data read and write unit 260 may comprise a FIFO memory module. In particular, the first data read unit 245 and the first data write unit 255 utilize a bus conforming to the Avalon standard and having a memory-mapped master / slave architecture for communicating with the second data read and write unit 260, i.e., for communicating with a FIFO memory module. Furthermore, in order to ensure highly configurable data management within the system 100, the second data read and write unit 260 may be implemented, for example, with a FIFO memory module in showahead mode, having 1024 binary words of 32 bits each as data Q. However, when implemented in this way, the second data read and write unit 260 does not comply with the Avalon standard. Indeed, although the Avalon standard guarantees bidirectional and controlled data transfer management, its characteristics cannot be fully utilized when a FIFO memory module is used. In particular, the Avalon standard requires that the data write and read request signals remain unchanged when the master receives a read or write waitrequest signal, which would result in a write operation occurring in a full FIFO memory module or a read operation occurring from an empty FIFO memory module; therefore, the FIFO memory module must not receive such data write and read request signals while a read or write waitrequest signal is active.

[0021] According to the present invention, advantageously, the data read interface module 310 and the data write interface module 320 respectively allow the first data read unit 245 to be interfaced to the second data read unit 260a and the first data write unit 255 to be interfaced to the second data write unit 260b, thereby advantageously ensuring a highly configurable management of data Q in the system 100. This advantageously allows to prevent data Q from being written to a full FIFO memory module or read from an empty FIFO memory module, thus preventing the FIFO memory module from receiving a read or write waitrequest signal while such a signal is active.

[0022] In addition to or as an alternative to this embodiment of the present invention, the second data reading unit 260a and the second data writing unit 260b may be independent: for example, the second data reading unit 260a may comprise a data acquisition (DAQ) module with a first memory buffer, while the second data writing unit 260b may comprise a data output function module with a second memory buffer, which do not comply with the Avalon standard.

[0023] Similar to the above, in accordance with the present invention, the data read interface module 310 and the data write interface module 320 respectively enable the first data read unit 245 to be interfaced to the second data read unit 260a and the first data write unit 255 to be interfaced to the second data write unit 260b, thereby advantageously ensuring highly configurable management of data Q in both the first memory buffer and the second memory buffer.

[0024] According to this embodiment of the invention, the data Q is transferred from the memory means 130, i.e. from the SDRAM memory, to the second data read and write unit 260, i.e. to the FIFO memory module, and vice versa. For example, the data Q may comprise a predefined total number of binary words, for example 10,000 binary words of 32 bits each. With reference to Fig. 2, the data Q may be read from the memory means 130 and transferred via the bus 101 to the SDRAM controller 225, which then transfers the data Q to the FPGA unit using the second interface 235 via the connection unit 220. The second interface 235 then sends the data Q to the first data write unit 255, which writes the data Q to the second data read and write unit 260, i.e. to the FIFO memory module, using the data write interface module 320. Also, the first data read unit 245 may read data Q from the second data read and write unit 260, i.e., from the FIFO memory module, using the data read interface module 310, and transmit the data Q to the SDRAM controller 225, via the connection unit 220, using the second interface 235. Thus, the data Q may be transmitted from the SDRAM controller 225 to the memory means 130, i.e., to the SDRAM memory, via the bus 101. The first data read unit 245 and the first data write unit 255 are managed by the HPS unit 210, using the first interface 230, which is operatively connected to the slave control ports 241 of both the first data read unit 245, i.e., the R-DMA module, and the first data write unit 255, i.e., the W-DMA module. For example, the first data reading unit 245 and the first data writing unit 255 may be managed by the HPS unit 210 by using a control algorithm that may be implemented as a piece of software code, for example written in the C programming language and that may be loaded from the memory means 130 via the bus 101 into the HPS unit 210.

[0025] With reference to FIG. 3, the following describes a data read interface module 310 and a data write interface module 320 implemented in the second processing means 200 previously described herein with reference to FIG.

[0026] In particular, the data read interface module 310 may be implemented as a computer program product comprising portions of software code, for example VHDL software code, that may be loaded into the FPGA unit 240 .

[0027] The data read interface module 310 (see also Fig. 5a and Fig. 5b) is adapted as follows: receiving a data read request signal R-Req, which is asserted and sent by the first data read unit 245; Receive a data read status signal R-Stat sent by the second data read unit 260a, and the data read status signal R-Stat is asserted when the second data read unit 260a has no data Q; Verify whether the data read status signal R-Stat is asserted: If asserted, the data read interface module 310 is adapted to unassert and send a data read request signal R-Req to the data read interface module 310, and assert and send a data read wait signal R-Wait to the first data read unit 245; Otherwise, the data reading interface module 310 is adapted to send a data reading request signal R-Req to the second data reading unit 260a, receive data Q from the second data reading unit 260a, and send such data Q to the first data reading unit 245.

[0028] It should be noted that, in this specification, asserting a signal means setting its logic state to "TRUE," while unasserting a signal means setting its logic state to "FALSE."

[0029] The first data read unit 245 may also comprise a first data read port 246 adapted to send a data read request signal R-Req, to ​​receive a data read wait signal R-Wait and / or to receive data Q. The second data read unit 260a may also comprise a second data read port 261 adapted to receive a data read request signal R-Req, to ​​send a data read status signal R-Stat and / or to send data Q. The data read interface module 310 may also comprise a third data read port 311 adapted to receive a data read request signal R-Req, for example at a first input IN1, to send a data read wait signal R-Wait, for example from a second output OUT2, and / or to send data Q, for example from a third output OUT3. The data read interface module 310 may also comprise a fourth data read port 312 adapted for example to send a data read request signal R-Req from the first output OUT1 and adapted for example to receive a data read status signal R-Stat at the second input IN2 and / or for example to receive data Q at the third input IN3. Also, the first data read port 246 and the fourth data read port 312 may be of the master type, while the second data read port 261 and the third data read port 311 may be of the slave type.

[0030] In addition, the second data read and write unit 260 may include a second data read unit 260a; in particular, the second data read and write unit 260 may include a FIFO memory module, and the data read status signal R-Stat includes an empty FIFO memory signal (Empty).

[0031] Also, the first data read unit 245 may include a DMA module, i.e., an R-DMA module, and the data read wait signal R-Wait includes a waitrequest signal. Similarly, the data write interface module 320 may be implemented as a computer program product including a portion of software code, for example a VHDL software code, that can be loaded into the FPGA unit 240.

[0032] The data writing interface module 320 (see also Fig. 5c and Fig. 5d) is adapted as follows: receiving a data write request signal W-Req, which is asserted and sent by the first data write unit 255; Receive a data write status signal W-Stat sent by the second data write unit 260b, and the data write status signal W-Stat is unasserted when the second data write unit 260b has no data Q; Verify whether the data write status signal W-Stat is asserted: If asserted, the data write interface module 320 is adapted to unassert and send a data write request signal W-Req, and assert and send a data write wait signal W-Wait to the first data write unit 255; Otherwise, the data writing interface module 320 is adapted to send a data writing request signal W-Req to the second data writing unit 260b, receive data Q from the first data writing unit 255, and send such data Q to the second data writing unit 260b.

[0033] For example, the first data write unit 255 may comprise a first data write port 256 adapted to send a data write request signal W-Req, to ​​receive a data write wait signal W-Wait and / or to send data Q. The second data write unit 260b may also comprise a second data write port 262 adapted to receive a data write request signal W-Req, to ​​send a data write status signal W-Stat and / or to receive data Q. The data write interface module 320 may also comprise a third data write port 321 adapted to receive a data write request signal W-Req, for example at a fourth input IN4, to send a data write wait signal W-Wait, for example from a fifth output OUT5, and / or to receive data Q, for example at a sixth input IN6. The data write interface module 320 may also comprise a fourth data write port 322 adapted to transmit a data write request signal W-Req, for example from a fourth output OUT4, receive a data write status signal W-Stat, for example at a fifth input IN5, and / or transmit data Q, for example from a sixth output OUT6.

[0034] Also, the first data write port 256 and the fourth data write port 322 may be of the master type, while the second data write port 262 and the third data write port 321 may be of the slave type.

[0035] The second data read and write unit 260 may also include a second data write unit 260b; in particular, the second data read and write unit 260 may include a FIFO memory module, and the data write status signal W-Stat includes a full FIFO memory signal (Full).

[0036] Also, the first data write unit 255 may include a DMA module, ie, a W-DMA module, and the data write wait signal W-Wait includes a waitrequest signal.

[0037] It should be noted that the R-Req, R-Stat, R-Wait, W-Req, W-Stat, and W-Wait signals may be binary signals, i.e., they may be binary electrical signals for which a high voltage value, designated as "1," and a low voltage value, designated as "0," may be determined. According to positive logic, a high value "1" is associated with a "TRUE" logic state, while a low value "0" is associated with a "FALSE" logic state.

[0038] Alternatively, according to negative logic, a high value "1" is associated with a "FALSE" logic state, while a low value "0" is associated with a "TRUE" logic state. As used herein, asserting a signal means setting its logic state to "TRUE," while unasserting a signal means setting its logic state to "FALSE."

[0039] 4a to 5d, the R-Req, R-Stat, R-Wait, W-Req, W-Stat and W-Wait signals are considered herein according to positive logic. In particular, the following table describes the above-mentioned R-Req, R-Stat, R-Wait, W-Req, W-Stat and W-Wait signals in more detail: [Table 1]

[0040] Advantageously, the data read interface module 310 and the data write interface module 320 enable controlling the flow of data Q using the R-Stat, R-Wait, W-Stat, and W-Wait signals, so that the control algorithms of the first data read unit 245 and the first data write unit 255, i.e., the R-DMA and W-DMA modules, can be programmed to enable data transfers Q that exceed the size of the FIFO memory (1,024 binary words), thus significantly improving the transfer speed of data Q in the system 100.

[0041] In particular, taking into account that the first data read unit 245 comprises an R-DMA module and the first data write unit 255 comprises a W-DMA module, it is necessary for the control algorithm in the HPS unit to know one or more of the following address values ​​so as to be able to manage the first data read unit 245 and the first data write unit 255: the address value of the second data read port 261, the address value of the second data write port 262, the address value of the control port 241 of each DMA module, and an address value corresponding to the base of the usable portion of the SDRAM memory.

[0042] Such an address can be determined as follows: a) Considering a master port in the HPD unit 210 connected to the FPGA unit 240 via the second interface 235, the address value (address) of such master port is equal to the sum of the offset value (bridge_base) of the second interface 235 and the base address value (slave_base) of the slave port of the FPGA unit 240, i.e.: address = bridge_base + slave_base; b) Considering a master port in FPGA unit 240, the address value (address) of such master port is equal to the base address value (slave_base) of the slave port of FPGA unit 240, ie: address=slave_base.

[0043] Those addresses useful for managing the R-DMA and W-DMA modules, SDRAM memory and FIFO memory are listed in the table below. [Table 2]

[0044] In Table 2, the LW_BASE value corresponds to a predefined parameter named LT_LWFPGASLVS_OFST, which can be obtained from the "hps.h" file provided by Altera in the Quartus-prime installation folder reserved for the specific library of the device used (Cyclone V in this case), while the R-DMA_BASE and W-DMA_BASE values ​​can be found in the Qsys screen of the Quartus-prime platform or in the "*.h" files generated using the sopc-create-header-files command in the Altera SoC EDS (to execute this command, it is necessary to have available the "*.sopcinfo" file for the project generated by the Quartus-prime platform during the compilation phase).

[0045] Regarding the SDRAM_BASE address, no offset is taken into account: each DMA module is connected to the HPS unit 210 via the second interface 235 (FPGA → HPS), which refers to the L3 address-space, where the first 2 GB are mapped in SDRAM; therefore, it is sufficient to define the SDRAM part reserved for data transfer. Finally, regarding the SDRAM_BASE address, no offset is taken into account: such an address can be obtained from the "*.h" file or from the Qsys screen on the Quartus-prime platform. For reading from and writing to the FIFO memory module at the same time, it is possible to define two different addresses for the data read and write ports, or to use two different FIFO memory modules. It should also be noted that in order to be able to use all the addresses described above, the memory area in which they are located must first be mapped in the user space by using the mmap command, which returns a pointer to the first address of the mapped memory area. It should also be pointed out that the Linux operating system pre-installed in the development board usually uses all of the SDRAM, and therefore it is necessary to reserve parts of the SDRAM for data transfer; this can be done for example by executing the following U-BOOT command: $ setenv mmcboot 'setenv bootargs console=ttyS0, 115200 mem=800M root=${mmcroot} rw rootwait;bootz ${loadaddr} - ${fdtaddr}' $ saveenv In this case, the SDRAM dedicated to the Linux operating system is reduced to 800MB; therefore, the SDRAM address communicated to the R-DMA and W-DMA modules is 0x32000000 (the address of the 800th MB).

[0046] In order to perform a bidirectional data transfer from memory means 130, i.e. from the SDRAM memory, to the second data read and write unit 260, i.e. the FIFO memory module, the control algorithm in HPS unit 210 must be able to write to or read one or more of the following registers of the first data read unit 245, i.e. the R-DMA module, and of the first data write unit 255, i.e. the W-DMA module: status registers, read registers, write registers, transfer length registers, and control registers. Such registers are accessible by adding further offset values ​​as detailed in the table below to the above-described LW_BASE+R-DMA_BASE and LW_BASE+W-DMA_BASE addresses for the R-DMA and W-DMA modules, respectively. [Table 3]

[0047] The following describes such registers in detail; specifically, the status register is described in the table below. [Table 4]

[0048] The read register contains the first address from which each R-DMA and W-DMA module reads the data Q to be transferred; subsequent addresses are obtained by suitably incrementing this address depending on the size of the individual elements of the transfer. If it is desired to read from a fixed address (such as when reading from a FIFO module), it is necessary to set the RCON bit in the control register to 1. The size of this register is defined when the first read unit 245 and the first write unit 255 are created, and may be large enough to identify all slave peripherals connected to the first data read port 246 of each R-DMA and W-DMA module.

[0049] The write register contains the first address to which each R-DMA and W-DMA module writes the data Q to be transferred; subsequent addresses are obtained by suitably incrementing this address depending on the size of the individual binary words of the transfer. If it is desired to write to a fixed address (such as when writing to a FIFO module), it is necessary to set the WCON bit in the control register to 1. The size of this register is defined when the system is generated and may be large enough to identify all slave peripherals connected to the first data write port 256 of each R-DMA and W-DMA module.

[0050] The length register contains the number of bytes of data Q to be transferred, and its value is progressively decremented during the transfer: when it reaches 0, the LEN bit in the status register is set to 1 and the transfer ends.

[0051] The control register consists of several single bits that specify the behavior of each R-DMA and W-DMA module according to the table below. [Table 5]

[0052] It must be pointed out that of all the bits that define the size of the binary word to be transferred, only one can be set to 1, otherwise the behavior of the DMA module is undetermined.

[0053] Referring to Figures 4a, 5a, and 5b, the following describes a method for interfacing a first data reading unit 245 with a second data reading unit 260a, both of which are operably connected to a data reading interface module 310 according to this embodiment of the present invention.

[0054] In step 410, a data read request phase is executed, in which a data read request signal R-Req is received by the data read interface module 310. The data read request signal R-Req is asserted and sent by the first data read unit 245.

[0055] In step 420, a read status signaling phase is executed, in which a data read status signal R-Stat is received by the data read interface module 310, where the data read status signal R-Stat is transmitted by the second data read unit 260a; the data read status signal R-Stat is asserted when there is no data Q in the second data read unit 260a.

[0056] In step 430, a read status verification phase is performed in which the data read interface module 310 verifies whether the data read status signal R-Stat is asserted, and if it is asserted the data read interface module 310 will perform step 435, otherwise it will perform step 440.

[0057] In step 435, a data read wait phase is executed, in which a data read request signal R-Req is unasserted by the data read interface module 310 and sent to the second data read unit 260a, and a data read wait signal R-Wait is asserted by the data read interface module 310 and sent to the first data read unit 245.

[0058] In step 440, a data read phase is executed, in which the data read interface module 310 sends a data read request signal R-Req to the second data read unit 260a, and in which the data read interface module 310 receives data Q from the second data read unit 260a and sends the data Q to the first data read unit 245.

[0059] For example, the first data read unit 245 may include a first data read port 246 that transmits a data read request signal R-Req and receives a data read wait signal R-Wait and / or receives data Q.

[0060] The second data read unit 260a may also include a second data read port 261 for receiving a data read request signal R-Req and transmitting a data read status signal R-Stat and / or transmitting data Q.

[0061] The data read interface module 310 may also include a third data read port 311 for receiving a data read request signal R-Req and transmitting a data read wait signal R-Wait and / or transmitting data Q.

[0062] Finally, the data read interface module 310 may comprise a fourth data read port 312 for transmitting a data read request signal R-Req and receiving a read status signal R-Stat and / or for receiving data Q.

[0063] For example, the first data read port 246 and the fourth data read port 312 may be of the master type, while the second data read port 261 and the third data read port 311 may be of the slave type.

[0064] For example, the second data read and write unit 260 may include a second data read unit 260a; in particular, the second data read and write unit 260 may include a FIFO memory module, and the data read status signal R-Stat includes an empty FIFO memory signal (Empty).

[0065] For example, the first data read unit 245 may include a DMA module, ie, an R-DMA module, and the data read wait signal R-Wait includes a waitrequest signal.

[0066] It will be clear to a person skilled in the art that the above described method for interfacing the first data reading unit 245 with the second data reading unit 260a may be implemented in the FPGA unit 240 using a computer program product comprising portions of software code, e.g. VHDL software code, that may be loaded into the FPGA unit 240 to implement the data reading interface module 310. This means that the system 100 may include an FPGA unit 240 adapted to implement the data reading interface module 310 according to the method for interfacing the first data reading unit 245 with the second data reading unit 260a as described above with reference to steps 410 to 440.

[0067] Similarly, with reference to Figures 4b, 5c and 5d, the following describes a method for interfacing the first data writing unit 255 with the second data writing unit 260b, both of which are operably connected to the data writing interface module 320 according to this embodiment of the present invention.

[0068] In step 450, a data write request phase is executed, in which a data write request signal W-Req is received by the data write interface module 320, where the data write request signal W-Req is asserted and transmitted by the first data write unit 255.

[0069] In step 460, a write status signaling phase is executed, in which a data write status signal W-Stat is received by the data write interface module 320, where the data write status signal W-Stat is transmitted by the second data write unit 260b; the data write status signal W-Stat is unasserted when there is no data Q in the second data write unit 260b.

[0070] In step 470, a write status verification phase is performed in which the data write interface module 320 verifies whether the data write status signal W-Stat is asserted, and if it is asserted the data write interface module 320 will perform step 475, otherwise it will perform step 480.

[0071] In step 475, a data write wait phase is executed, in which a data write request signal W-Req is unasserted by the data write interface module 320 and sent to the second data write unit 260b, and a data write wait signal W-Wait is asserted by the data write interface module 320 and sent to the first data write unit 255.

[0072] In step 480, a data write phase is executed, in which the data write interface module 320 sends a data write request signal W-Req to the second data write unit 260b, and the data write interface module 320 receives data Q from the first data write unit 255 and sends data Q to the second data write unit 260b.

[0073] For example, the first data write unit 255 may comprise a first data write port 256 for transmitting a data write request signal W-Req, receiving a data write wait signal W-Wait, and / or transmitting data Q. Also, the second data write unit 260b may comprise a second data write port 262 for receiving a data write request signal W-Req, transmitting a data write status signal W-Stat, and / or receiving data Q. Also, the data write interface module 320 may comprise a third data write port 321 for receiving a data write request signal W-Req, transmitting a data write wait signal W-Wait, and / or receiving data Q. Finally, the data write interface module 320 may comprise a fourth data write port 322 for transmitting a data write request signal W-Req, receiving a data write status signal W-Stat, and / or transmitting data Q.

[0074] For example, the first data write port 256 and the fourth data write port 322 are of the master type, while the second data write port 262 and the third data write port 321 are of the slave type.

[0075] For example, the second data read and write unit 260 may include a second data write unit 260b; in particular, the second data read and write unit 260 may include a FIFO memory module, and the data write status signal W-Stat includes a full FIFO memory signal (Full).

[0076] For example, the first data write unit 255 may include a DMA module, ie, a W-DMA module, and the data write wait signal W-Wait includes a waitrequest signal.

[0077] It will be clear to a person skilled in the art that the above described method for interfacing the first data writing unit 255 with the second data writing unit 260b may be implemented in the FPGA unit 240 using a further computer program product comprising portions of software code, e.g. VHDL software code, that may be loaded into the FPGA unit 240 to implement the data writing interface module 320. This would allow the system 100 to include an FPGA unit 240 adapted to implement the data writing interface module 320 according to the method for interfacing the first data writing unit 255 with the second data writing unit 260b as described above with reference to steps 450 to 480.

[0078] The advantages of the present invention are apparent from the above description.

[0079] Advantageously, the present invention provides a method for interfacing a first data read unit with a second data read unit and a method for interfacing a first data write unit with a second data write unit, as well as respective data read and data write interface modules, which ensure highly configurable data management for the memory buffers of the second read unit and the second write unit.

[0080] A further advantage of the present invention lies in the fact that the present invention provides a data read interface module and a data write interface module that allow for controlling the data flow by means of signals exchanged between the first data read unit and the second data read unit, and between the first data write unit and the second data write unit, so that the control algorithms of the first data read unit and the first data write unit can be programmed to allow data transfers that exceed the size of the memory buffer, thereby significantly improving the data transfer speed of the data processing and / or acquisition system.

[0081] Naturally, the embodiments and implementation details may be modified significantly from what has been described and illustrated herein merely as non-limiting examples, without prejudice to the principles of the invention, but without departing from the scope of protection of the invention as set forth in the appended claims.

Claims

1. 13. A method for interfacing a first data reading unit with a second data reading unit, the first data reading unit and the second data reading unit being operatively connected to a data reading interface module, the method comprising: a data read request phase, in which a data read request signal is received by the data read interface module, and the data read request signal is asserted and sent by the first data read unit; a read status signaling phase, in which a data read status signal is received by the data read interface module, where the data read status signal is transmitted by the second data read unit, and the data read status signal is asserted when there is no data (Q) in the second data read unit; A read status verification phase, in which the data read interface module verifies whether the data read status signal is asserted, and if it is asserted, the data read interface module will perform a data read wait phase; otherwise, it will perform a data read phase, where: In the data read waiting phase, the data read request signal is unasserted by the data read interface module and sent to the second data read unit, and a data read waiting signal is asserted by the data read interface module and sent to the first data read unit; In the data reading phase, the data reading interface module sends the data reading request signal to the second data reading unit, and the data reading interface module receives the data from the second data reading unit and sends the data to the first data reading unit. A method comprising:

2. the first data read unit has a first data read port for transmitting the data read request signal and receiving the data read wait signal and / or receiving the data; the second data read unit has a second data read port for receiving the data read request signal and transmitting the data read status signal and / or transmitting the data; the data read interface module has a third data read port for receiving the data read request signal and transmitting the data read wait signal and / or transmitting the data; the data read interface module has a fourth data read port for transmitting the data read request signal and receiving the read status signal and / or receiving the data; The method of claim 1.

3. 3. The method of claim 2, wherein the first data read port and the fourth data read port are of the master type, and the second data read port and the third data read port are of the slave type.

4. 4. The method of claim 1, wherein a second data read and write unit comprises the second data read unit, the second data read and write unit comprises a FIFO memory module, and the data read status signal comprises an empty FIFO memory signal.

5. The method of claim 1 , wherein the first data read unit comprises a DMA module, and the data read wait signal comprises a waitrequest signal.

6. 13. A method for interfacing a first data writing unit with a second data writing unit, the first data writing unit and the second data writing unit operatively connected to a data writing interface module, the method comprising: a data write request phase, in which a data write request signal is received by the data write interface module, and the data write request signal is asserted and sent by the first data write unit; a write status signaling phase, in which a data write status signal is received by the data write interface module, where the data write status signal is transmitted by the second data write unit, and the data write status signal is unasserted when there is no data in the second data write unit; a write status verify phase, in which the data write interface module verifies whether the data write status signal is asserted, and if it is asserted, the data write interface module will perform a data write wait phase, otherwise it will perform a data write phase, where: In the data write wait phase, the data write request signal is unasserted by the data write interface module and sent to the second data write unit, and a data write wait signal is asserted by the data write interface module and sent to the first data write unit; In the data writing phase, the data writing interface module sends the data writing request signal to the second data writing unit, and the data writing interface module receives the data from the first data writing unit and sends the data to the second data writing unit. A method comprising:

7. the first data writing unit comprises a first data writing port for sending the data writing request signal and receiving the data writing wait signal and / or for sending the data; the second data writing unit comprises a second data writing port for receiving the data writing request signal, transmitting the data writing status signal, and / or receiving the data; the data write interface module comprises a third data write port for receiving the data write request signal, transmitting the data write wait signal, and / or receiving the data; The method of claim 6 , wherein the data write interface module comprises a fourth data write port for transmitting the data write request signal, receiving the data write status signal, and / or transmitting the data.

8. 8. The method of claim 7, wherein the first data write port and the fourth data write port are of the master type, and the second data write port and the third data write port are of the slave type.

9. 9. The method of claim 6, wherein the second data read and write unit comprises the second data write unit, the second data read and write unit comprises a FIFO memory module, and the data write status signal comprises a FIFO memory full signal.

10. The method of claim 6 , wherein the first data writing unit comprises a DMA module, and the data writing wait signal comprises a waitrequest signal.

11. A computer program comprising portions of software code that can be loaded into an FPGA unit adapted to implement a data read interface module according to the method of any one of claims 1 to 3.

12. A system comprising a first processing means, an I / O interface means, a memory means, and a second processing means having an FPGA unit adapted to implement a data read interface module according to the method of any one of claims 1 to 3.

13. A computer program comprising portions of software code that can be loaded into an FPGA unit adapted to implement a data writing interface module according to the method of any one of claims 6 to 8.

14. A system comprising a first processing means, an I / O interface means, a memory means, and a second processing means having an FPGA unit adapted to implement a data writing interface module according to the method of any one of claims 6 to 8.

Citation Information

Patent Citations

  • Interface conversion bridge based on Avalon bus, interface conversion method and system

    CN109918325A

  • Multiprocessor system

    JP2009134635A

  • Memory access device, memory access system, and processing method of memory access device

    JP2010244197A

  • Memory access device, memory access system, and processing method of memory access device

    US20100257310A1