Recalbox sur TV CRT en RGB

[aTg]

Ok, let's go with the software part.

To get the audio at the same time as the video for the GPIO we need to use pins 18 and 19 which in the case of vga666 are occupied by the color red.

These two pins are the option we have to move the PWM channels from the minijack to the GPIO. So the vga666 scheme is not worth it, but the DPI output of the RPi has different configurations.

vga666 uses mode 5 that we see in the image and we need mode 6 so it is necessary to use the overlay dpi24 that supports all modes and select the 6 with dpi_output_format

The problem in recalbox is that we do not have this overlay.

Edit:
I linked a custom compilated overlay made by me to be able to use mode 6, I hope devs can include it in future versions.

rgb-pi.dtbo

[ian57]

@aTg I think we will no include the dtbo file as is. Please make a github with the sources (the dts file) and we will make a package with it for recalbox.
From http://elinux.org/RPi_BCM2835_GPIOs here is your dts file

/dts-v1/;
/plugin/;

/ {
  compatible = "brcm,bcm2708";

  fragment@0 {
    target = <&gpio>;
    __overlay__ {
      pinctrl-names = "default";
      pinctrl-0 = <&pwm_audio_pins>;

    pwm_audio_pins: pwm_audio_pins {
    brcm,pins = <18 19>;   /* gpio no ('BCM' number) */
    brcm,function = <2 2>; /* 0:in, 1:out, 2: alt5, 3: alt4, 4: alt0, 5: alt1, 6: alt2, 7: alt3 */
    brcm,pull = <0 0>;     /* 2:up 1:down 0:none */
      };
    };
  };
 };

In fact your dtbo file only moves PWM audio to pin 18-19... so the file should be named differently : rpi-audio-on-gpio.dtbo or something like that

[aTg]

@ian57 You're confused.

The audio moves with the overlay pwm-2chan that is already included do not need to rename or recompile.

The file that is required is for the video output.

Vga666.dtbo is exactly the same as dpi24.dtbo, if decompile the files you can see it, the difference is that dpi24 uses gpio pins from 4 to 27 while vga666 uses only from 4 to 21.

Rgb-pi.dtbo is another distinct compilation of dpi24 and uses pins 4 to 9, 12 to 17 and 20 to 25 to be able to use mode 6 of the DPI output as I explained above.

You could include dpi24 to use all modes, but if vga666 has its reason to exist being a custom version of dpi24 I do not understand why rgb-pi.dtbo no. This is another adapter other than vga666 and you can not use that overlay.

Here rgbi-pi-overlay.dts

/dts-v1/;

/ {
compatible = "brcm,bcm2708";

fragment@0 {
	target = <0xdeadbeef>;

	__overlay__ {
		pinctrl-names = "default";
		pinctrl-0 = <0x1>;
	};
};

fragment@1 {
	target = <0xdeadbeef>;

	__overlay__ {

		rgb-pi_pins {
			brcm,pins = <0x2 0x3 0x4 0x5 0x6 0x7 0x8 0x9 0xc 0xd 0xe 0xf 0x10 0x11 0x14 0x15 0x16 0x17 0x18 0x19>;
			brcm,function = <0x6>;
			brcm,pull = <0x0>;
			phandle = <0x1>;
		};
	};
};

__symbols__ {
	rgb-pi_pins = "/fragment@1/__overlay__/rgb-pi_pins";
};

__local_fixups__ {

	fragment@0 {

		__overlay__ {
			pinctrl-0 = <0x0>;
		};
	};
};

__fixups__ {
	leds = "/fragment@0:target:0";
	gpio = "/fragment@1:target:0";
};
};

[ian57]

So vga666 and rgb-pi are only particular case of dpi24. VGA66 is named like that according to the hardware but is making also rgb. So I still think you should rename your work rgb-scart.dtbo ( or sort of) to include the specific problem of audio + gpio pin shift due to audio ouput on scart.

but as a sum up, we can use your hardware without new dtbo with :

dtoverlay=pwm-2chan,pin=18,func=2,pin2=19,func2=2
dtparam=i2c_arm=off
dtparam=spi=off
dtoverlay=dpi24
dpi_group=2
dpi_mode=87
dpi_output_format=0x6f000 # or something like that :)

[aTg]

VGA666 is a trade name associated with the gert adapter, for the DPI port it comes out in 666 mode in other ways, my adapter is also 666, I have to put scart666&audio.dtbo? It does not seem logical to me, vga666 could perfectly use dpi24 and instead uses an overlay associated with its mark, I do not understand why it can not be the same with rgb-pi.

Rgb, evokes console video output for tv, while vga implies the use of pc monitors.

I do not want to use the term scart, because scart can also be confused with composite video.

If you mean that the same overlay includes the movement of the sound pins I think it's OK but I do not understand why I have to use a generic name.

[aTg]

@ian57 said in Recalbox sur TV CRT en RGB:

So vga666 and rgb-pi are only particular case of dpi24. VGA66 is named like that according to the hardware but is making also rgb. So I still think you should rename your work rgb-scart.dtbo ( or sort of) to include the specific problem of audio + gpio pin shift due to audio ouput on scart.

but as a sum up, we can use your hardware without new dtbo with :

dtoverlay=pwm-2chan,pin=18,func=2,pin2=19,func2=2
dtparam=i2c_arm=off
dtparam=spi=off
dtoverlay=dpi24
dpi_group=2
dpi_mode=87
dpi_output_format=0x6f000 # or something like that :)

dpi24 is still not included in recalbox.

Gert could also use this overlay and yet you are all using vga666.dtb

You going to change your settings to dpi24? Or will you continue to use the vga666 overlay?

[ian57]

I think it would be great to find a name which include audio + 666 pin shift for rgb on a scart because that is what is your project deals with. It would avoid misunderstandings....

or simply give the dpi24 config which is working well... but surely just put a dtbo file in config is simpler.

[aTg]

Look honestly, I do not care if you include dpi24 and not mention anywhere rgb-pi, that everything is done in the config.txt but it gives me a little anger that some people have an influence to give visibility to your product As is the case of vga666 and others have to carry it hidden.

When I repeat that the overlay for vga666 does nothing that does not make dpi24

[ian57]

You're misunderstanding here, recalbox would be glad to include and support your hardware, but on my side the name rgb-pi seems not to reflect all the possibilities of what you've done.
we make rgb from a hdmi-vga converter too... so... you see what I mean?

And as I say dpi24 is already included in recalbox with the standard kernel firmware.

[aTg]

Ok I will work with dpi24 but anyway the file /boot/overlays/dpi24.dts does not exist and I tried to use it in config.txt if it was included inside another file but it does not work

[ian57]

The file is included with the next release of recalbox 4.1 which embeds the 4.14 kernel. In Debian I think you already have the dpi24.dtbo file.

You work will be supported with the next release of recalbox. You only need to make it work with debian, it should also work in the next 4.1 recalbox distro.

[aTg]

The next thing I think it is necessary to work is that NOOBS start in DPI mode, so that the recalbox installation can be done integrally from the TV.

In the INSTRUCTION-README.txt says;

Your Pi will now boot into NOOBS and should display a list of operating systems that you can choose to install.
If your display remains blank, you should select the correct output mode for your display by pressing one of the following number keys    on your keyboard:
1. HDMI mode - this is the default display mode.
2. HDMI safe mode - select this mode if you are using the HDMI connector and cannot see anything on screen when the Pi has booted.
3. Composite PAL mode - select either this mode or composite NTSC mode if you are using the composite RCA video connector.
4. Composite NTSC mode

It would be nice to add option 5 to boot in a DPI mode ...

[ian57]

@aTg That's a good idea. I'm not sure but the next release on Recalbox will be released with .img file to be burned on a SD card. So Noobs will not be nacessary anymore.

[Substring]

@ian57 will ALSO be released as .img, noobs, whatever one says, is a very useful tool.
Noobs 2.0 is out btw

[aTg]

I have not understood very well, that will be released with and without NOOBS.

One of the reasons to choose recalbox for many people is NOOBS because they do not know how to burn an image on a microSD.

If you are going to continue using NOOBS I will be working on it to run in DPI mode.
Please confirm.

[ian57]

@aTg Both... Noobs and img

[r11t16]

Tout d'abord, je tiens à tous vous féliciter pour le monstrueux taf que vous accomplissez.

Je vous explique simplement ma démarche. Je débute dans le monde l'arcade et j'ai commencé à me monter une borne DIY. Pour le moment, je n'ai pas d'écran. J'ai un Rpi 3 comme système. Devant la difficulté à trouver des écrans lcd au format 4/3 de bonne dimensions (sup à 19"), je comptais me rabattre sur un TV CRT (qui a en plus l'avantage de donner de l’authenticité à l'image).
D'après ce que j'ai compris :
je recherche donc un sony trinitron (d'au moins 51) après 1994 si possible.
J'ai choisi la solution HDMI avec les deux adaptateurs (indiqués par archimage) car je veux garder le GPIO pour les sticks et boutons.
Par contre, je me perds un peu dans les différentes config en fonction de la console d'origine et la façon de gérer ça au quotidien.

Du coup : ou en êtes vous concernant le tuto "complet" que archimage devait proposer? (j'ai bien lu le tuto express).
Encore merci et bon courage pour la suite.

[Substring]

@r11t16 on a encore qq semaines/mois de travail dessus. La solution par hdmi2vga reste la plus simple à mettre en œuvre. Faut juste jouer un peu du fer à souder

[aTg]

@r11t16 Your best bet is to wire a female jamma connector and use a RPi jamma adapter, with audio, video and buttons over GPIO.

@ian57 We can use runcommands.sh to put all resolutions there.
Replace tvservices with vcgencmd and then make changes to emulatorlauncher.sh

Another thing to keep in mind is the theme that we use, for such a small resolution is not suitable, I at the moment what I do is edit and enlarge the letters, but it would be good to think of a specific one for low resolutions and with a maximum of 16 bit color.

You can change the font size by editing /recalbox/share_init/system/.emulationstation/themes/recalbox/main.xml and changing all values 0.03 by 0.09 for example.

[ian57]

@aTg for ES resolution and font size, there is an adapted theme upper in the thread which works well.