Difference between revisions of "Elgato CAM LINK 4K"
| Line 1: | Line 1: | ||
This PCB is relevant to the project because [[AXIOM Beta]] generates HDMI content inside its [[Beta Main Board]] FPGA and therefore almost any data can be sent over an HDMI connection. This provides a potential solution to not having control at the HDMI receiver side (recorder manufacturers do all kinds of strange things with the image, e.g. sharpening, colour conversions, etc... and in general only support very specific resolutions/frame-rates. Coincidentally there are also no standards for HDMI. | This PCB is relevant to the project because [[AXIOM Beta]] generates HDMI content inside its [[Beta Main Board]] FPGA and therefore almost any data can be sent over an HDMI connection. This provides a potential solution to not having control at the HDMI receiver side (recorder manufacturers do all kinds of strange things with the image, e.g. sharpening, colour conversions, etc... and in general only support very specific resolutions/frame-rates). Coincidentally there are also no standards for HDMI. | ||
With the Elgato CAM Link 4k it could now become possible to take over control of the receiver side. This opens up a whole world of possibilities with regards to what data could be packed into the HDMI "frame" if it were to be used as a data container. | With the Elgato CAM Link 4k it could now become possible to take over control of the receiver side. This opens up a whole world of possibilities with regards to what data could be packed into the HDMI "frame" if it were to be used as a data container. | ||
Revision as of 18:59, 15 April 2020
This PCB is relevant to the project because AXIOM Beta generates HDMI content inside its Beta Main Board FPGA and therefore almost any data can be sent over an HDMI connection. This provides a potential solution to not having control at the HDMI receiver side (recorder manufacturers do all kinds of strange things with the image, e.g. sharpening, colour conversions, etc... and in general only support very specific resolutions/frame-rates). Coincidentally there are also no standards for HDMI.
With the Elgato CAM Link 4k it could now become possible to take over control of the receiver side. This opens up a whole world of possibilities with regards to what data could be packed into the HDMI "frame" if it were to be used as a data container.
The device can be purchased from here
1 PCB
PCB Side 1.
PCB Side 2 (mirrored).
It is reported to be an 8 layer PCB. Probably atleast a 2-3+ HDI.
PCB Side View
PCB Layer 1/8
PCB Layer 2/8
PCB Layer 3/8
PCB Layer 4/8 (Now from the back, flipped for ease of alignment.) Another solid ground plane.
PCB Layer 5/8 (flipped) Power planes.
PCB Layer 6/8 (flipped) Two sneaky DDR memory pairs routed on this layer.
PCB Layer 7/8 (flipped) ground plane - Note: 2 cutouts in this plane, that seem to correspond to SW signals of DCDC buck converters. I've never seen that before? Maybe to reduce capacitance on the SW pin?
PCB Layer 8/8 (flipped) bottom layer
Exploring Elgato CamLink4K via oscilloscope. Image from Assorted Hacking article on getting the device to play nicer on Linux.
Pinout Mapping (WIP):
2 Firmware
a dump of the SPI communication (and the decoded flash data) can be found here:
- http://vserver.13thfloor.at/Stuff/ELGATO/boot_decode.txt
- http://vserver.13thfloor.at/Stuff/ELGATO/boot.vcd.xz
3 Further files/links
- http://vserver.13thfloor.at/Stuff/ELGATO/
- https://github.com/ktemkin/camlink-re
- Patching my Cam Link 4K to play nicer on Linux - https://assortedhackery.com/patching-cam-link-to-play-nicer-on-linux/