vol.2
Posts: 26
Joined: Tue Dec 13, 2016 5:17 pm

Re: STICKY: Using a Gert VGA 666 adapter - [HOWTO]

Tue Nov 26, 2019 5:03 am

Gert van Loo wrote:
Tue Oct 08, 2019 6:25 pm
If this is a hardware-related problem, why does it happen only on Raspbian Buster and/or RPi 4, and not on Raspbian Stretch / RPi 3?
I don't know. Maybe they use a different drive strength for the GPIO or the Pi4 PCB has the tracks thinner and closer together. It can also be that there is more or different frequency noise on the supply. To trace things like this I would connect my spectrum analyzer to the signal and see if that show up anything different between the builds & PCB's.
Hi Gert, I wanted to report that I am getting zero visible dot crawl using this timing on a Pi4 with a 15kHz Sony CRT monitor:
320 1 16 30 34 240 1 2 3 22 0 0 0 60 0 6400000 1

I was playing around with timings because I'm trying to get various old dos programs to work in dosbox, but other timings showed dotcrawl. I think it may be a sweet-spot kind of situation with the pulse width and placement and not necessarily an issue with the sync voltage level. But, hey, I could be wrong.

kevinfishburne
Posts: 3
Joined: Sat Oct 12, 2019 12:33 am

Re: STICKY: Using a Gert VGA 666 adapter - [HOWTO]

Mon Jan 13, 2020 10:37 am

I was struggling for a while to get a super resolution working on a RPi4 with the RetroTINK (like a VGA666 but 24-bit/888). I finally got it working with these settings:

Code: Select all

# Turn off conflicting peripheral overlays using GPIO pins.
dtparam=i2c_arm=off
dtparam=spi=off
dtparam=i2s=off
dtparam=audio=off
enable_uart=0

# Generic 24-bit DPI display.
dtoverlay=dpi24
dpi_output_format=7

# Set default display.
enable_dpi_lcd=1
display_default_lcd=1

# Disable overscan.
disable_overscan=1

# Enable custom dpi timings.
dpi_group=2
dpi_mode=87

# Set custom dpi timings.
dpi_timings=3840 1 109 343 343 240 1 3 5 14 0 0 0 60 0 72925291 1 # 3840x240
#dpi_timings=320 1 9 29 29 224 1 21 3 14 0 0 0 60 0 6077108 1	# 320x224
I was connecting to a Sylvania CRT television over S-Video and noticed no dot crawl or artifacts in either of the above modes using both Lakka's November 4th nightly image and the latest Raspbian Buster Lite. Sadly I'm not sure if what fixed the initial issue was the above settings being correct or a firmware update.

Also of note here is that the holy grail of super resolutions, 3840x240, now works. Previously it would fail with a segfault on the RPi3. You may also find this spreadsheet useful for calculating dpi timings:

http://eightvirtues.com/lakka/hat/RPi%2 ... 20Docs.ods

antiriad
Posts: 161
Joined: Sun Nov 17, 2013 7:38 pm
Location: Italy
Contact: Twitter

Re: STICKY: Using a Gert VGA 666 adapter - [HOWTO]

Mon Jan 13, 2020 11:00 am

kevinfishburne wrote:
Mon Jan 13, 2020 10:37 am
I was struggling for a while to get a super resolution working on a RPi4 with the RetroTINK (like a VGA666 but 24-bit/888). I finally got it working with these settings:
...
Hello Kevin,
may I ask if you are currently using this super-resolution with the CRT Switchres feature in LAKKA?

Thank you

kevinfishburne
Posts: 3
Joined: Sat Oct 12, 2019 12:33 am

Re: STICKY: Using a Gert VGA 666 adapter - [HOWTO]

Mon Jan 13, 2020 11:21 am

may I ask if you are currently using this super-resolution with the CRT Switchres feature in LAKKA?
I haven't played with that yet. I assume it changes the dpi timings to match the native output of systems without having to reboot. So far I've just been manually setting core overrides. My adventures with integer scaling haven't worked too well, as I still often have to set it manually and half the time it doesn't even integer scale properly on some game resolutions. You'd think integer scaling would just scale the whole thing to maximally fit within the "desktop resolution" / screen mode without clipping unless one resolution axis is larger than the screen mode axis (in which case it should center-clip), but it doesn't.

antiriad
Posts: 161
Joined: Sun Nov 17, 2013 7:38 pm
Location: Italy
Contact: Twitter

Re: STICKY: Using a Gert VGA 666 adapter - [HOWTO]

Mon Jan 13, 2020 11:31 am

It seems that we are trying to achieve the same objective (but with not so good results by my side, with RPi4 and VGA 666)
Maybe you'll find interesting this thread on LAKKA forums:

https://forums.libretro.com/t/new-crtsw ... arch/20513

rememberizer
Posts: 8
Joined: Fri Oct 18, 2019 1:58 am

Re: STICKY: Using a Gert VGA 666 adapter - [HOWTO]

Thu Mar 05, 2020 10:44 am

I just tested with the latest Lakka Nightly and the firmware update. Pixel crawl on the pi4 is gone!!! The image is perfect now!

However, there's a problem with the Frame Throttle option - it doesn't work very well. I get choppiness when 3rd Strike is set to run at native refresh, but when it's at 60hz everything seems smooth. This isn't a VGA666 issue though!

allpass
Posts: 16
Joined: Sat Oct 26, 2019 3:10 pm

Re: STICKY: Using a Gert VGA 666 adapter - [HOWTO]

Sun Mar 08, 2020 5:09 am

Thanks for this thread. I'm wondering if anyone has experienced problems starting up Xorg on HDMI + DPI outputs on raspbian? My setup uses the CM3+ compute module driving HDMI and an LCD on the DPI pins at 320x480. (18 bit mode) Everything is great except on approx. 20% of boots X doesn't fully start. (log below) It's far enough along to actually accept X connections but clients block waiting forever to initialize graphics forever. Killing (even -9) doesn't stop Xorg and I have to power cycle the machine.

I've tried new firmware, built the latest kernel sources, tried with and without an xorg.conf. I'm using the fake kms driver in config.txt... I tried the real kms driver (vc4-kms-v3d) which outputs only on HDMI, but can't seem to configure xorg.conf in a way that makes target both screens. The rest of the system is stable and working fine so I'm 99.9% sure my hardware is okay.

I'm starting Xorg from a systemd service like this:

Code: Select all

/usr/bin/Xorg :0 -nolisten tcp -noreset -verbose 2
My xorg.conf looks like this:

Code: Select all

Section "Device"
    Identifier      "VideoCore4-DPI"
    Driver          "modesetting"
    # this allows the HDMI device to get page flipping priority over DPI.
    # Without this option, you will experience tearing on every HDMI frame
    # plus a stuttering update cadence on HDMI leading to a very unstable
    # frame rate.
    Option "PageFlip" "false"
    Screen          0
EndSection

Section "Device"
    Identifier      "VideoCore4-HDMI"
    Driver          "modesetting"
    Option "PageFlip" "true"
    Screen          1
EndSection

Section "Monitor"
    Identifier      "HDMI-1"
    Option          "Primary" "true"
EndSection

Section "Monitor"
    Identifier      "DPI-1"
    Option          "Primary" "false"
    Option          "Rotate" "normal"
EndSection

Section "Screen"
    Identifier      "DPI Screen"
    Device          "VideoCore4-DPI"
    Monitor         "DPI-1"
    DefaultDepth    24
        SubSection "Display"
            Depth       24
            Modes       "FIXED_MODE"
    EndSubSection
EndSection

Section "Screen"
    Identifier      "HDMI Screen"
    Device          "VideoCore4-HDMI"
    Monitor         "HDMI-1"
    DefaultDepth    24
        SubSection "Display"
            Depth   24
            Modes   "1920x1080"
        EndSubSection
EndSection

Section "ServerLayout"
    Identifier      "SeparateScreens"
    Screen 0        "DPI Screen"
    Screen 1        "HDMI Screen" RightOf "DPI Screen"
EndSection

Section "ServerFlags"
    # These options disable screen blanking, which is important for embedded systems
    Option "BlankTime"    "0"
    Option "StandbyTime"  "0"
    Option "SuspendTime"  "0"
    Option "OffTime"      "0"
    Option "AllowMouseOpenFail"     "true"
EndSection
The log file is below from a successful run. I indicated the point where startup fails:

Code: Select all

Xorg.0.log:
[     7.600] xorg-server 2:1.20.4-1+rpt1 (https://www.debian.org/support) 
[     7.600] Current version of pixman: 0.36.0
[     7.600] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[     7.600] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[     7.600] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Mar  8 04:42:26 2020
[     7.606] (==) Using config file: "/etc/X11/xorg.conf"
[     7.606] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[     7.624] (==) ServerLayout "SeparateScreens"
[     7.624] (**) |-->Screen "DPI Screen" (0)
[     7.624] (**) |   |-->Monitor "DPI-1"
[     7.634] (**) |   |-->Device "VideoCore4-DPI"
[     7.634] (**) |-->Screen "HDMI Screen" (1)
[     7.634] (**) |   |-->Monitor "HDMI-1"
[     7.637] (**) |   |-->Device "VideoCore4-HDMI"
[     7.637] (**) Option "AllowMouseOpenFail" "true"
[     7.637] (**) Option "BlankTime" "0"
[     7.637] (**) Option "StandbyTime" "0"
[     7.637] (**) Option "SuspendTime" "0"
[     7.637] (**) Option "OffTime" "0"
[     7.638] (==) Automatically adding devices
[     7.638] (==) Automatically enabling devices
[     7.638] (==) Automatically adding GPU devices
[     7.638] (==) Max clients allowed: 256, resource mask: 0x1fffff
[     7.685] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[     7.685] 	Entry deleted from font path.
[     7.685] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[     7.685] 	Entry deleted from font path.
[     7.685] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[     7.685] 	Entry deleted from font path.
[     7.685] (WW) The directory "/usr/share/fonts/X11/Type1" does not exist.
[     7.685] 	Entry deleted from font path.
[     7.685] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[     7.685] 	Entry deleted from font path.
[     7.685] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[     7.685] 	Entry deleted from font path.
[     7.685] (==) FontPath set to:
	/usr/share/fonts/X11/misc,
	built-ins
[     7.685] (==) ModulePath set to "/usr/lib/xorg/modules"
[     7.685] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[     7.685] (II) Loader magic: 0x1fcf80
[     7.685] (II) Module ABI versions:
[     7.685] 	X.Org ANSI C Emulation: 0.4
[     7.686] 	X.Org Video Driver: 24.0
[     7.686] 	X.Org XInput driver : 24.1
[     7.686] 	X.Org Server Extension : 10.0
[     7.689] (--) using VT number 2

[     7.689] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[     7.691] (II) xfree86: Adding drm device (/dev/dri/card0)
[     7.692] (II) no primary bus or device found
[     7.692] 	falling back to /sys/devices/platform/soc/soc:gpu/drm/card0
[     7.692] (II) LoadModule: "glx"
[     7.696] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[     7.744] (II) Module glx: vendor="X.Org Foundation"
[     7.744] 	compiled for 1.20.4, module version = 1.0.0
[     7.744] 	ABI class: X.Org Server Extension, version 10.0
[     7.744] (II) LoadModule: "modesetting"
[     7.744] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[     7.749] (II) Module modesetting: vendor="X.Org Foundation"
[     7.749] 	compiled for 1.20.4, module version = 1.20.4
[     7.749] 	Module class: X.Org Video Driver
[     7.749] 	ABI class: X.Org Video Driver, version 24.0
[     7.750] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[     7.750] (WW) xf86OpenConsole: setpgid failed: Operation not permitted
[     7.750] (WW) xf86OpenConsole: setsid failed: Operation not permitted
[     7.750] (II) modeset(0): using drv /dev/dri/card0
[     7.751] (II) modeset(1): using drv /dev/dri/card0
[     7.751] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[     7.751] (**) modeset(0): Depth 24, (--) framebuffer bpp 32
[     7.751] (**) modeset(0): Option "PageFlip" "false"
[     7.751] (==) modeset(0): RGB weight 888
[     7.752] (==) modeset(0): Default visual is TrueColor
[     7.752] (II) Loading sub module "glamoregl"
[     7.752] (II) LoadModule: "glamoregl"
[     7.753] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
[     7.836] (II) Module glamoregl: vendor="X.Org Foundation"
[     7.836] 	compiled for 1.20.4, module version = 1.0.1
[     7.836] 	ABI class: X.Org ANSI C Emulation, version 0.4
[     9.402] (II) modeset(0): glamor X acceleration enabled on VC4 V3D 2.1
[     9.402] (II) modeset(0): glamor initialized
[     9.403] (II) modeset(0): Output DSI-1 using monitor section DPI-1
[     9.403] (**) modeset(0): Option "Rotate" "normal"
[     9.403] (**) modeset(0): Option "Primary" "false"
[     9.417] (II) modeset(0): EDID for output DSI-1
[     9.418] (II) modeset(0): Printing probed modes for output DSI-1
[     9.418] (II) modeset(0): Modeline "FIXED_MODE"x60.0   19.20  320 475 485 640  480 488 492 500 +hsync +vsync (30.0 kHz UeP)
[     9.418] (II) modeset(0): Output DSI-1 connected
[     9.418] (II) modeset(0): Using user preference for initial modes
[     9.418] (II) modeset(0): Output DSI-1 using initial mode FIXED_MODE +0+0
[     9.418] (==) modeset(0): Using gamma correction (1.0, 1.0, 1.0)
[     9.418] (==) modeset(0): DPI set to (96, 96)
[     9.418] (II) Loading sub module "fb"
[     9.418] (II) LoadModule: "fb"
[     9.419] (II) Loading /usr/lib/xorg/modules/libfb.so
[     9.424] (II) Module fb: vendor="X.Org Foundation"
[     9.424] 	compiled for 1.20.4, module version = 1.0.0
[     9.424] 	ABI class: X.Org ANSI C Emulation, version 0.4
[     9.425] (II) modeset(1):  reusing fd for second head
[     9.425] (**) modeset(1): Depth 24, (--) framebuffer bpp 32
[     9.426] (**) modeset(1): Option "PageFlip" "true"
[     9.426] (==) modeset(1): RGB weight 888
[     9.426] (==) modeset(1): Default visual is TrueColor
[     9.426] (II) Loading sub module "glamoregl"
[     9.426] (II) LoadModule: "glamoregl"
[     9.427] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
[     9.427] (II) Module glamoregl: vendor="X.Org Foundation"
[     9.427] 	compiled for 1.20.4, module version = 1.0.1
[     9.427] 	ABI class: X.Org ANSI C Emulation, version 0.4
[     9.444] (II) modeset(1): glamor X acceleration enabled on VC4 V3D 2.1
[     9.444] (II) modeset(1): glamor initialized

*************** gets stuck here *********************

[     9.459] (II) modeset(1): Output HDMI-1 using monitor section HDMI-1
[     9.459] (**) modeset(1): Option "Primary" "true"
[     9.473] (II) modeset(1): EDID for output HDMI-1
[     9.474] (II) modeset(1): Printing probed modes for output HDMI-1
[     9.474] (II) modeset(1): Modeline "1024x768"x60.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[     9.474] (II) modeset(1): Modeline "800x600"x60.3   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
[     9.474] (II) modeset(1): Modeline "800x600"x56.2   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync (35.2 kHz e)
[     9.475] (II) modeset(1): Modeline "848x480"x60.0   33.75  848 864 976 1088  480 486 494 517 +hsync +vsync (31.0 kHz e)
[     9.475] (II) modeset(1): Modeline "640x480"x59.9   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
[     9.475] (II) modeset(1): Output HDMI-1 connected
[     9.475] (II) modeset(1): Using exact sizes for initial modes
[     9.475] (II) modeset(1): Output HDMI-1 using initial mode 1024x768 +0+0
[     9.475] (==) modeset(1): Using gamma correction (1.0, 1.0, 1.0)
[     9.476] (==) modeset(1): DPI set to (96, 96)
[     9.476] (II) Loading sub module "fb"
[     9.476] (II) LoadModule: "fb"
[     9.477] (II) Loading /usr/lib/xorg/modules/libfb.so
[     9.477] (II) Module fb: vendor="X.Org Foundation"
[     9.477] 	compiled for 1.20.4, module version = 1.0.0
[     9.478] 	ABI class: X.Org ANSI C Emulation, version 0.4
[     9.776] (==) modeset(0): Backing store enabled
[     9.776] (==) modeset(0): Silken mouse enabled
[     9.785] (II) modeset(0): Initializing kms color map for depth 24, 8 bpc.
[     9.785] (==) modeset(0): DPMS enabled
[     9.786] (WW) modeset(0): Option "Primary" is not used
[     9.786] (WW) modeset(0): Option "Rotate" is not used
[     9.787] (II) modeset(0): [DRI2] Setup complete
[     9.787] (II) modeset(0): [DRI2]   DRI driver: vc4
[     9.787] (II) modeset(0): [DRI2]   VDPAU driver: vc4
[     9.919] (==) modeset(1): Backing store enabled
[     9.919] (==) modeset(1): Silken mouse enabled
[     9.920] (II) modeset(1): Initializing kms color map for depth 24, 8 bpc.
[     9.920] (==) modeset(1): DPMS enabled
[     9.920] (WW) modeset(1): Option "Primary" is not used
[     9.921] (II) modeset(1): [DRI2] Setup complete
[     9.921] (II) modeset(1): [DRI2]   DRI driver: vc4
[     9.921] (II) modeset(1): [DRI2]   VDPAU driver: vc4
[     9.921] (II) Initializing extension Generic Event Extension
[     9.922] (II) Initializing extension SHAPE
[     9.923] (II) Initializing extension MIT-SHM
[     9.924] (II) Initializing extension XInputExtension
[     9.931] (II) Initializing extension XTEST
[     9.932] (II) Initializing extension BIG-REQUESTS
[     9.933] (II) Initializing extension SYNC
[     9.934] (II) Initializing extension XKEYBOARD
[     9.935] (II) Initializing extension XC-MISC
[     9.936] (II) Initializing extension SECURITY
[     9.936] (II) Initializing extension XFIXES
[     9.937] (II) Initializing extension RENDER
[     9.938] (II) Initializing extension RANDR
[     9.939] (II) Initializing extension COMPOSITE
[     9.940] (II) Initializing extension DAMAGE
[     9.941] (II) Initializing extension MIT-SCREEN-SAVER
[     9.942] (II) Initializing extension DOUBLE-BUFFER
[     9.943] (II) Initializing extension RECORD
[     9.944] (II) Initializing extension DPMS
[     9.945] (II) Initializing extension Present
[     9.946] (II) Initializing extension DRI3
[     9.947] (II) Initializing extension X-Resource
[     9.948] (II) Initializing extension XVideo
[     9.949] (II) Initializing extension XVideo-MotionCompensation
[     9.949] (II) Initializing extension SELinux
[     9.949] (II) SELinux: Disabled on system
[     9.949] (II) Initializing extension GLX
[     9.966] (II) AIGLX: Loaded and initialized vc4
[     9.966] (II) GLX: Initialized DRI2 GL provider for screen 0
[     9.981] (II) AIGLX: Loaded and initialized vc4
[     9.981] (II) GLX: Initialized DRI2 GL provider for screen 1
[     9.981] (II) Initializing extension XFree86-VidModeExtension
[     9.982] (II) Initializing extension XFree86-DGA
[     9.983] (II) Initializing extension XFree86-DRI
[     9.985] (II) Initializing extension DRI2
[     9.992] (II) modeset(0): Damage tracking initialized
[     9.992] (II) modeset(0): Setting screen physical size to 84 x 127
[     9.996] (II) modeset(1): Damage tracking initialized
[     9.997] (II) modeset(1): Setting screen physical size to 270 x 203
[    10.257] (EE) modeset(1): failed to set mode: Invalid argument
[    11.030] (II) modeset(0): Disabling kernel dirty updates, not required.
[    13.007] (II) modeset(1): Disabling kernel dirty updates, not required.

gizmo1990
Posts: 12
Joined: Sat Nov 17, 2018 5:08 pm

Re: STICKY: Using a Gert VGA 666 adapter - [HOWTO]

Wed Mar 11, 2020 10:58 pm

I'm not having any joy getting my VGA 666 to work. I've followed the OPs instructions but upon a reboot I just get the pi's multi coloured square test screen, via hdmi. Nothing from the VGA side.

I'm probably missing something but I can't think what. Could the place in the config.txt where you place the 3 lines of code be important perhaps? I presume you can just enter it anywere as long as it's not hashed out.

I've also noticed that The SPI and I2C are not disabled from the Advanced Options menu but rather the Interfacing Options one instead. Unless I've missed something else?

Any advice much appreciated.

EDIT: I got this working so all is good. The only change I made was to specify the resolution? The instructions seem to suggest that this isn't necessary on first reboot, but it wouldn't work for me without them added.

littleshiro
Posts: 1
Joined: Thu Apr 09, 2020 2:48 pm

Re: STICKY: Using a Gert VGA 666 adapter - [HOWTO]

Thu Apr 09, 2020 2:55 pm

Recently I have bought a VGA 666 to attach to my old Raspberry pi 2B 1.1. I have followed the OPs instructions to set it up and I achieved only to enable the VGA video output. The HDMI only shows a rainbow.

My target is to connect 2 monitors to the raspberry to try to connect via remote desktop with my office PC that also have 2 monitors.

Has somebody achieved this scenario or a similar one?

User avatar
mahjongg
Forum Moderator
Forum Moderator
Posts: 14218
Joined: Sun Mar 11, 2012 12:19 am
Location: South Holland, The Netherlands

Re: STICKY: Using a Gert VGA 666 adapter - [HOWTO]

Mon Apr 20, 2020 2:54 pm

littleshiro wrote:
Thu Apr 09, 2020 2:55 pm
Recently I have bought a VGA 666 to attach to my old Raspberry pi 2B 1.1. I have followed the OPs instructions to set it up and I achieved only to enable the VGA video output. The HDMI only shows a rainbow.

My target is to connect 2 monitors to the raspberry to try to connect via remote desktop with my office PC that also have 2 monitors.

Has somebody achieved this scenario or a similar one?
AFAIK both VGA666 and HDMI have always used the exact same framebuffer, so that meant that they could not be used simultaneously.

Perhaps now the RPI4 supports two HDMI screens, and there is more (video) RAM that might have changed, but I doubt a RPI2 can support two screens at the same time.

User avatar
rpdom
Posts: 19260
Joined: Sun May 06, 2012 5:17 am
Location: Chelmsford, Essex, UK

Re: STICKY: Using a Gert VGA 666 adapter - [HOWTO]

Mon Apr 20, 2020 4:20 pm

mahjongg wrote:
Mon Apr 20, 2020 2:54 pm
AFAIK both VGA666 and HDMI have always used the exact same framebuffer, so that meant that they could not be used simultaneously.
I'm not sure about that. I know I did have two screens attached to my Pi 1B at one point. One of them was on the VGA666. But I can't remember if the other was composite or HDMI (DVI-D). I used omxplayer to play different videos on each screen.
Unreadable squiggle

6by9
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 12084
Joined: Wed Dec 04, 2013 11:27 am
Location: ZZ9 Plural Z Alpha, aka just outside Cambridge.

Re: STICKY: Using a Gert VGA 666 adapter - [HOWTO]

Mon Apr 20, 2020 4:54 pm

rpdom wrote:
Mon Apr 20, 2020 4:20 pm
mahjongg wrote:
Mon Apr 20, 2020 2:54 pm
AFAIK both VGA666 and HDMI have always used the exact same framebuffer, so that meant that they could not be used simultaneously.
I'm not sure about that. I know I did have two screens attached to my Pi 1B at one point. One of them was on the VGA666. But I can't remember if the other was composite or HDMI (DVI-D). I used omxplayer to play different videos on each screen.
Yes, you can have simultaneous HDMI and DPI running together.

Looking up the potential options from last time
https://github.com/raspberrypi/firmware ... -455556619
DSI0+DSI1+HDMI
DPI+DSI1+HDMI
DSI0+DSI1+SDTV
DPI+DSI1+SDTV
But software only allows 2 displays at once.
Software Engineer at Raspberry Pi Trading. Views expressed are still personal views.
I'm not interested in doing contracts for bespoke functionality - please don't ask.

loscanones
Posts: 7
Joined: Sun May 17, 2020 5:12 pm

Re: STICKY: Using a Gert VGA 666 adapter - [HOWTO]

Sun May 17, 2020 5:22 pm

I`ve already spent many hours with configuration-tests and reading forums. VGA output is NOT working at all.
Unit is a PI 3 Model B with VGA666 adapter. No matter what settings i choose, there is no output on VGA port.
Monitor is a New Net City Toshiba with 15 or 31 Khz, running fine on 640x40 or 800x600 resolution with other machines.

Pi is running a raspbian stretch lite -used to play a short video.
I finally delete all and clean install a fresh copy of latest raspbian, update everything, configure in all possible ways found on forums. Still nothing (HDMI is fine).

Any ideas will be greatly appreciated!

EDIT: Tested with a plasma tv with PC port and it`s working. This is more confusing now...my arcade monitor works fine with a pc on 640x480.
What can be wrong?? Refresh?

rememberizer
Posts: 8
Joined: Fri Oct 18, 2019 1:58 am

Re: STICKY: Using a Gert VGA 666 adapter - [HOWTO]

Thu Jul 02, 2020 5:00 pm

If you are using it for emulation only (because you're using an arcade cabinet), try the CRT-PI Project images. There's a build for VGA output. It should work right out of the box.

loscanones
Posts: 7
Joined: Sun May 17, 2020 5:12 pm

Re: STICKY: Using a Gert VGA 666 adapter - [HOWTO]

Fri Jul 03, 2020 10:47 am

If you are using it for emulation only (because you're using an arcade cabinet), try the CRT-PI Project images. There's a build for VGA output. It should work right out of the box.
I`m not using it for emulation - this is already mentioned for people who bothered to read.
It`s used to play a short intro video and should run FAST (4 seconds after boot). This was achieved with Raspbian Lite.

However, problem was already solved - without any help from this forum...àu contraire...
Link to details:
viewtopic.php?f=29&t=24679&p=1662968#p1662968

james-at-lo-tech
Posts: 46
Joined: Sat Oct 04, 2014 1:07 pm

Re: STICKY: Using a Gert VGA 666 adapter - [HOWTO]

Tue Aug 04, 2020 6:42 am

6by9 wrote:
Mon Apr 20, 2020 4:54 pm

Yes, you can have simultaneous HDMI and DPI running together.

Looking up the potential options from last time
https://github.com/raspberrypi/firmware ... -455556619
DSI0+DSI1+HDMI
DPI+DSI1+HDMI
DSI0+DSI1+SDTV
DPI+DSI1+SDTV
But software only allows 2 displays at once.
@6by9 - is there any way to have framebuffers for both displays, so the machine can use VGA and HDMI(s) concurrently for normal OS tasks?

6by9
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 12084
Joined: Wed Dec 04, 2013 11:27 am
Location: ZZ9 Plural Z Alpha, aka just outside Cambridge.

Re: STICKY: Using a Gert VGA 666 adapter - [HOWTO]

Tue Aug 04, 2020 7:37 am

james-at-lo-tech wrote:
Tue Aug 04, 2020 6:42 am
6by9 wrote:
Mon Apr 20, 2020 4:54 pm

Yes, you can have simultaneous HDMI and DPI running together.

Looking up the potential options from last time
https://github.com/raspberrypi/firmware ... -455556619
DSI0+DSI1+HDMI
DPI+DSI1+HDMI
DSI0+DSI1+SDTV
DPI+DSI1+SDTV
But software only allows 2 displays at once.
@6by9 - is there any way to have framebuffers for both displays, so the machine can use VGA and HDMI(s) concurrently for normal OS tasks?
Not when using DRM/KMS. If you disable that (and lose 3D acceleration) then bcm2708_fb will create 2 frame buffer devices, but you now can't easily stretch X over both displays. On a Pi0-3 you'll also need to add max_framebuffers=2 to config.txt.
Software Engineer at Raspberry Pi Trading. Views expressed are still personal views.
I'm not interested in doing contracts for bespoke functionality - please don't ask.

slikvik
Posts: 3
Joined: Mon Mar 14, 2016 9:25 am

Re: STICKY: Using a Gert VGA 666 adapter - [HOWTO]

Sun Nov 08, 2020 3:53 pm

Hi,

I would like to run a VGA 2 SCART adapter on this but the adapter states that:

"The board gets power from VGA pin 9, please ensure your input device outputs +5V on pin 9."

Does the Gert output +5V on pin 9?

User avatar
rpdom
Posts: 19260
Joined: Sun May 06, 2012 5:17 am
Location: Chelmsford, Essex, UK

Re: STICKY: Using a Gert VGA 666 adapter - [HOWTO]

Sun Nov 08, 2020 4:06 pm

slikvik wrote:
Sun Nov 08, 2020 3:53 pm
Does the Gert output +5V on pin 9?
No. Pin 9 on the VGA socket is not connected.
Unreadable squiggle

jgilroy
Posts: 2
Joined: Tue Jan 19, 2021 1:42 am

Re: STICKY: Using a Gert VGA 666 adapter - [HOWTO]

Thu Jan 21, 2021 4:13 pm

I got a vga666 and was able to get it running with my Pi4 and an old monochrome VGA monitor I had lying around. I decided that ultimately, I wanted to use the vga666 with a Pi Zero, so I built a new raspbian image, added the same config.txt parameters I added for the Pi4 (including disabling i2c and spi), and fired up my Pi Zero W. Unfortunately, it just hangs at the rainbow splash screen. Thinking there might be a problem with my Pi Zero, I tried another one I have laying around - same result. In the case of a hang, the activity light continues to be sporadically active; not a steady "error code" flash.

Through trial and error I was able to determine that both Pi Zeros hang if enable_dpi_lcd=1 is present; if this line is commented out then both Pi's will boot successfully (using the HDMI port, of course, the vga666 isn't active.). This is true whether the vga666 is connected to the Pi Zero's or not.

Again - no problem at all with the Pi4 - and each device is using its own Raspbian image freshly built using the Raspberry Pi Imager (MacOS).

/boot/config.txt from my Pi Zero W:

Code: Select all

# For more options and information see
# http://rpf.io/configtxt
# Some settings may impact device functionality. See link above for details

# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1

# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
#disable_overscan=1

# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16

# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720

# uncomment if hdmi display is not detected and composite is being output
#hdmi_force_hotplug=1

# uncomment to force a specific HDMI mode (this will force VGA)
#hdmi_group=1
#hdmi_mode=1

# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
#hdmi_drive=2

# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
#config_hdmi_boost=4

# uncomment for composite PAL
#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800

# Uncomment some or all of these to enable the optional hardware interfaces
dtparam=i2c_arm=off
#dtparam=i2s=on
dtparam=spi=off

# Uncomment this to enable infrared communication.
#dtoverlay=gpio-ir,gpio_pin=17
#dtoverlay=gpio-ir-tx,gpio_pin=18

# Additional overlays and parameters are documented /boot/overlays/README

# Enable audio (loads snd_bcm2835)
dtparam=audio=off

[pi4]
# Enable DRM VC4 V3D driver on top of the dispmanx display stack
dtoverlay=vc4-fkms-v3d
max_framebuffers=2

[all]
dtoverlay=vc4-fkms-v3d

dtoverlay=vga666
enable_dpi_lcd=1
display_default_lcd=1

dpi_group=2
dpi_mode=87

hdmi_timings=640 1 8 96 40 400 0 5 2 28 0 0 0 70 0 25175000 1
I don't see anything especially useful in /var/log but I'm not sure exactly what I'm looking for. Any ideas what might be wrong or how to further debug?

Thanks!

jonnyapps
Posts: 1
Joined: Thu Apr 15, 2021 4:21 pm

Re: STICKY: Using a Gert VGA 666 adapter - [HOWTO]

Thu Apr 15, 2021 4:28 pm

Hello!

Is it possible to deliver the 1-3v needed to tell a CRT TV to set RGB mode, using this adapter? I'm using it for VGA-SCART. I've looked at the pinout/schematics and don't think it's possible, but I am a complete novice at anything like this.

Thanks in advance

Return to “Beginners”