Home›Industry News›GOWIN GW5AT Single Chip Bridges GEV/U3V/HSB Vision Links
← Back to Industry News
Domestic FPGA

GOWIN GW5AT Single Chip Bridges GEV/U3V/HSB Vision Links

Domestic FPGAGOWIN GW5AT SingleChip BridgesGEV/U3V/HSB Vision…fpga.love
Illustration

Vision bridging has long meant three protocols, three boards, and three firmware builds. DepEye's solution folds GigE Vision, USB3 Vision, and NVIDIA Holoscan Sensor Bridge protocol encapsulation into a single GW5AT, eliminating the need for an on-board CPU. For camera makers delivering to multiple host platforms, this changes the BOM structure rather than being a mere IP license.

The cost of developing three links twice over

Host links in industrial vision and robot perception have long split three ways: GigE Vision over Ethernet, balancing distance and multi-camera deployment; USB3 Vision over USB 3, with low integration cost; and NVIDIA's Holoscan Sensor Bridge on the edge AI side, connecting directly over 10GbE. The three are mutually incompatible in transmission medium, bandwidth ceiling, control protocol (GVCP, GenCP, and ECB register access), and host driver, so the same sensor often requires repeated board designs, rebuilt timing logic, and multiple firmware and parameter configurations for different host platforms. DepEye's approach makes the protocol bridging layer a reusable component, so the front end is designed once and delivered per output protocol. The real question is that the bridging layer is provided by a solution vendor rather than the chip maker, and who bears long-term maintenance responsibility is not addressed in the source material.

Protocol encapsulation and frame scheduling on chip

The solution uses the GW5AT series as the core for protocol processing and link output. Video sources enter via LVDS or MIPI DPHY/CPHY, pass through flow control and frame boundary handling into the FPGA, where on-chip GEV/U3V/HSB IP performs standard protocol encapsulation and control; on the output side, GEV 2.5G/10G goes out via external PHY or SFP+ optical port and DAC, U3V 5G/10G via USB 3.1, and HSB 10G via SFP+ optical port or DAC. Parameters such as exposure, gain, and resolution are sent back from the host via the corresponding protocol. The solution states three characteristics: no on-board CPU, with protocol encapsulation, buffer scheduling, and register access all completed inside the FPGA, so the board no longer carries a separate processor, memory, or operating system; on-chip storage absorbs bursts and inter-frame jitter; and no local interactive interface is provided on the device side. For board design, what is saved is the cost of processor, memory, and operating system; the constraint in return is that logic resources must accommodate both the protocol stack and the buffer.

ArchitectureProcessEcosystem
Illustration

Measured figures and supply format

The solution brief provides real-board measurements: GEV 10G achieves 9.785 Gb/s image transmission payload, HSB single-channel CoE image payload reaches 9.483 Gb/s, both close to 10GbE line rate; U3V 10G delivers 8.270 Gb/s pixel throughput at 4K resolution; GEV 2.5G shows 2.497 Gb/s at the NIC side. The four figures are respectively NIC traffic, transmission payload, pixel throughput, and single-channel payload—different measures that cannot be added together or converted into one another. On supply, GEV 1G is pure IP, allowing camera makers with existing FPGAs to integrate it themselves; the three high-speed links—2.5G/10G Ethernet, USB 3.1, and HSB—are delivered as "GW5AT chip plus corresponding IP" combinations. The solution supports the GW5AT15 and GW5AT60 devices, selected by logic resources and interface count. On the control path, GEV and U3V use GenICam XML to describe device capabilities, so hosts can continue using standard camera tools; HSB uses ECB for register-level configuration and is recognized natively by the Holoscan platform.

Three takeaways
  • Three protocols folded into one GW5AT, removing CPU, memory, and OS from the board
  • 10G measured payloads approach line rate, but the four figures use different measures and are not convertible
  • GEV 1G is offered as IP alone; high-speed links are delivered as chip plus IP combinations

What it means for us

For teams building industrial cameras and multi-camera robot接入, the value of this solution lies in BOM and firmware maintenance: one board covers three types of host interface, line switching and remote deployment parameter delivery both go through the host side, and the device side no longer maintains an operating system. Adoption depends on two points: first, whether the logic resources of the GW5AT15/60 can simultaneously accommodate the selected protocol stack and on-chip buffer—the solution provides no resource utilization data; second, GEV 1G is IP-only, meaning vendors with existing FPGAs can buy just the protocol layer without changing the main chip. On the supply chain, the solution vendor provides IP and chip combinations, and the toolchain still follows GOWIN's existing EDA flow, introducing no new development environment. For teams using NVIDIA Holoscan for edge AI, the zero-copy connection at the HSB output is a ready path, but the ECB configuration method differs from the GenICam toolchain, requiring adjustments to debugging habits.

vision bridgingGW5ATGigE VisionUSB3 VisionHoloscan
fpga.love

Subscribe to fpga.love

Daily Briefing · Weekly Digest · Monthly Deep Dive