Raspberry PI 4b composite isn't working, please help

SolidShook

Pi Model or other hardware: 4B+
Power Supply used: official DC5.1V

I'm using a PAL CRT, which is capable of using 60hz. I've tested the same CRT port using a gamecube, which worked perfectly.

Here's my config.txt, I really can't see what I might be missing.

# 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=2000
#over_voltage=6
#gpu_freq=700

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

# 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=on

[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
overscan_scale=1
enable_tvout=1

If the config seems ok, does anyone know of any way I can troubleshoot this?

I've realised after making this post that it is possible that the case I'm using may be effecting this, the Argon One V2, as it's got an extension on the 3.5mm port.
I'll test it without the case tomorrow and see if there is a difference.

Is it possible I may need to do something for 240i output?

mitu

You need to add

enable_tvout=1

to enable the composite video output, on the Pi4 is not automatically enabled. See more details at https://www.raspberrypi.org/documentation/configuration/config-txt/video.md.

SolidShook

@mitu hi, thanks for responding

I have that line added at the bottom, it was added by the system's own setting selection thing.
There's no output however

Do you know of any ways of trouble shooting?

mitu

Make sure you're using a correct composite cable for the Pi - did you use the same cable with the Gamecube ?

See, for instance:

https://pinouts.ru/HeadsetsHeadphones/Raspberry_pi_composite_vi_pinout.shtml

SolidShook

@mitu Hi Mitu

Thanks for your replies

It may well be the cable, I'm using this specifically

https://www.amazon.co.uk/gp/product/B07DYF432Q/ref=ppx_yo_dt_b_asin_title_o09_s00?ie=UTF8&psc=1

Some of the reviews mention it might not actually be what I'm looking for, I may return it.

I tried without the case and going directly to the motherboard, still no luck

SolidShook

@mitu Sorry for the double post

I have found that the cable was sending the video to the red one, rather than the yellow one

What kinda monster made this

Thanks so much for your help. Sorry to be a bother <3

Beldar

@solidshook I've found that camcorder cables usually output video to the red cable. I have to reverse the red and yellow cables.

SolidShook

@beldar I think it's something where the cable probably shouldn't be working, but does.

I mentioned here I was using an Argon One V2 case, that case didn't work with the same cable.

However I just purchased an official cable, and it works fine.

False positives everywhere