# Venus 3.62, Pi 4, GX Touch 50

**URL:** <https://community.victronenergy.com/t/venus-3-62-pi-4-gx-touch-50/38159>\
**Category:** Modifications\
**Tags:** rpi, venus\_os\
**Created:** [2 July 2025 23:19 UTC](https://community.victronenergy.com/t/venus-3-62-pi-4-gx-touch-50/38159 "2025-07-02T23:19:34Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![BenH5](https://avatars.discourse-cdn.com/v4/letter/b/ad7895/32.png) [@BenH5](https://community.victronenergy.com/u/BenH5)\
**Post date:** [2 July 2025 23:19 UTC](https://community.victronenergy.com/t/venus-3-62-pi-4-gx-touch-50/38159/1 "2025-07-02T23:19:34Z")

</div>

I have been attempting to get a GX TOUCH 50 working as the primary display (NOT HEADLESS) in VENUS on my Rasberry PI4 8GB. Initially I tried installing on an SSD (ARGON ONE case), however found out the hard way that VENUS does not support booting from USB devices. I reverted to a 256GB SDHXC card I had laying around. I have attempted using [GitHub - lpopescu-victron/ft5316-touchscreen: Victron 7 inch touch HDMI I2C](https://github.com/lpopescu-victron/ft5316-touchscreen), however the latest version of VENUS is using DAEMONTOOLS for services and not SYSTEMD. I have built my own CMAKE for VENUS, enabled I2C with changes to u-boot/config.txt, and I have also been able to build ydotool. I only see one device at 0x1A with the GX TOUCH 50 plugged in and the interface does display after changes to u-boot/config.txt and disabling the default headless. I can use a mouse to control the display on the GX TOUCH 50.

DISABLE HEADLESS

sudo mv /etc/venus/headless /etc/venus/headless.off

/u-boot/config.txt

 ![image](https://europe1.discourse-cdn.com/victron/original/3X/7/e/7e1298f9fd985b0043a7c37d01d19dcb97477efd.png)

INSTALL PYTHON3

opkg install python3  
opkg install python3-pip  
opkg install python3-smbus

ft5316\_touch.py now executes…  
 ![2025-07-05 10_15_33-PuTTY](https://europe1.discourse-cdn.com/victron/original/3X/7/9/79c331fb08d8d0ba7c61de289cd251150621dfe5.png)

ONLY I2C-1 IN VENUS OS 3.62 ☹  
 ![image](https://europe1.discourse-cdn.com/victron/original/3X/6/9/69a4bfe7b46d447e3ffed41a13e22d4d65bf4904.png)

 ![2025_07_04_15_09_04_192.168.0.118_PuTTY](https://europe1.discourse-cdn.com/victron/original/3X/a/0/a00b68e056bfe544ce8930e98b1c7b6db684660e.png)

DDC AVAILABLE IN RASPBERY PI OS (BOOKWORM)  
 ![image](https://europe1.discourse-cdn.com/victron/original/3X/9/5/95bb4a8f3efc258b521a05c9bbce1e54934f9e7e.png)

Next step is enabling the i2c/DDC channel on the HDMI port which I am currently stuck…

Check your PI4 Firmware…my eeprom was dated 2021 on my PI4. 😃

DDC is suppose to be available on i2c20/21 and enumerates with Raspberry Pi OS (Debian Bookworm, 2025-05-13) as seen above.

My current Venus 3.62 does not enumerate the DDC channels for i2c  
dtoverlay=vc4-kms-v3d is suppose to enable this and does not.

With dtoverlay=vc4-fkms-v3d  
 ![image](https://europe1.discourse-cdn.com/victron/original/3X/8/f/8fa95433cfa853fb0e44092e9f1a3b921448199b.png)  
Does look like FKMS is enabled

With dtoverlay=vc4-kms-v3d  
 ![image](https://europe1.discourse-cdn.com/victron/original/3X/8/f/8fa95433cfa853fb0e44092e9f1a3b921448199b.png)  
Strange, FKMS still shows enabled…  
So does VenusOS support KMS or just FKMS (FAKE)?

 ![image](https://europe1.discourse-cdn.com/victron/original/3X/3/0/3087019c39d0fc1587830a5d063d8db1513c3dd5.png)  
No overlays for KMS in Venus OS 3.62…

Overlays in Raspberry Pi OS (BOOKWORM)

 ![20250707_BOOKWORM_OVERLAYS](https://europe1.discourse-cdn.com/victron/original/3X/8/7/875a8dad09924ee9320620445d285c618e4fa6a7.png)

And surprise, Venus OS 3.62 DOES NOT HAVE AND FTP CLIENT!

wget ftp://anonymous@\<host_\>/_