Recalbox sur TV CRT en RGB

[Scandy]

@archimage said in Recalbox sur TV CRT en RGB:

@haricot voici un extrait de mon tuto express :

dans config.txt vérifie que tu as bien ces lignes

hdmi_cvt=1920 240 60 1 1 0 0
hdmi_disable_edid=0xa5000080
hdmi_pixel_encoding=2
avoid_safe_mode=1
disable_overscan=0
hdmi_drive=2
hdmi_group=1
hdmi_mode=6
hdmi_force=1

le mode 6 doit être activé pour emulationstation, non le mode 8 ensuite il faut que le mode 87 soit défini dans la résolution de Retroarch comme écrit plus haut...

Ces paramètres ont résolu mon problème, merci beaucoup!!!
Mais ils ont augmenté mes doutes.

Pourquoi spécifier hdmi_cvt=1920 240 60 1 1 0 0 si après vous définissez hdmi_mode=6? il est vrai qu'ils sont deux paramètres équivalents et exclusifs (l'une avec l'autre)?

Merci

[haricot]

Hi Scandy,

With Archimage Parameters , ES Station start in MODE=6 ( 480i 60hz)
see Config.txt detail

The Hdmi_cvt used here set the free MODE ( aka Mode 87)

you have to configure your recalbox.conf in recalbox (or es_systems.cfg in retropie) for the emulators to use MODE=87
for recalbox it's : global.videomode=DMT 87 HDMI
like this the ES gui use 480i ( mode 6 ) and emulators use the mode you have set in config.txt ( the Hdmi_cvt= )

hope it's help.

Stéphane.

[Scandy]

@haricot thank you for your answer but still it's not clear to me this: in config.txt it is like setting first hdmi_mode=87 and then hdmi_mode=6, right?
So shouldn't the latter declaration (mode 6) disable the first (mode 87)? Or can I set multiple hdmi_modes at once?

[archimage]

@Scandy It's quite simple :

In config.txt there's only one mode activated by default HDMI_MODE=6 there's no HDMI_MODE=87 in this file.

You create hdmi_cvt=1920 240 60 to recall it later with global.videmode=DMT 87 HDMI in the recalbox.conf file, it turns on the custom mode only when Retroarch launches. When Retroarch shuts down, it comes back to the default mode which is HDMI_MODE=6

[haricot]

when you use Hdmi_cvt , you create an new mode
Note that this simply creates the mode :group 2 mode 87.
and when you use hdmi_mode , you select the mode.
so in the config.txt from archimage when hdmi_cvt is used , it directly goes at 87 , but it use Mode 6 to start the frontend.
only retroarch and so use the mode 87 we have created in config.txt.

in conclusion
HDMI_MODE select the current mode to display when hdmi_cvt create it at bottom , but don't use it.

[haricot]

Re ,
aprés foules de test , c'est au final bien mon adaptateur HDMI/VGA qui fige sur certains Timming , vous auriez pas le lien d'un produit qui passe les réso exotique ( genre sur amazon , ca serait parfait^^ ) ?

merci d'avance.

Stéphane.

[Substring]

@haricot haha la ca va etre compliqué lol

[Scandy]

@haricot Cela pourrait être bon?

[aTg]

You are complicating life with the HDMI converter, I have already finished 10 cables if you want some. With the cable there is no problem with the hdmi_timings

[Substring]

@aTg some people have wired their sticks on GPIO, so it's easier for them this way. We should find a way to use i2c with DPI

[aTg]

I2c with DPI is not possible, but SPI with DPI yes:

I would very much help a programmer who made the soft with UINPUT and SPIDEV

[Substring]

@aTg i'll ask another way : can you free the i2c bus and still enable your gpio2scart ?

[aTg]

@Substring No, are incompatible in many pins and not possible to move.
But with SPI is possible moving CS pin, RPi in last firmwares accepts any gpio to get CS and the other pins is posible integrate in hdmi_mode=3

[haricot]

That was the start of my problem ...
I use the GPIO for input two Nintendo SNES PAD. I was commit to HDMI->VGA for the Display.

Solutions exist that can use SPI and input on the GPIO.
pi 2 jamma
but that cost a lot...

If we find cheaper hardware , it will be the perfect solution for many of use ....

Stéphane.

[Substring]

@aTg Can't reach 60fps with SPI, so we can't go that way. I had hoped that you only needed as many GPIO as the total number of bits, but looks like this is not possible

[aTg]

@Substring SPI for input buttons at 10Mhz and DPI for video output at the same time.

It is totally possible with rgb565 mode3.

[Substring]

@aTg so it means we can combine GPIO video DPI + a i2c MPC23017 ?

[aTg]

@Substring MCP23S17 is a SPI version, tomorrow i can upload a preliminar schematic to work, today i finish the last revision of rgb-pi with all improvements i can do and finally pass to the next project.

[haricot]

@aTg , You made me curious

I'm more comfortable with code than electronic but may be i can be of some help.
I found a lot of doc on SPI , but UINPUT is less common...

somes questions :

-MCP23S17 is a 16 bits inputs , using 2 Joystick and 6 buttons each will use more than 16 bits . does your schematic use two of them ?
-Are you using INT or going on a read loop ?

I take a look at Controlblock sourcecode , Adding a SPI input will not ask for tons of labor.

waiting for your schematics and will make a prototype.

Stéphane.

[Substring]

@haricot We have the mk_gpio_arcade kernel module that is supposed to handle the MPC23017, so no need of any programming, it should already be implemented. Consider 1 MPC23017 per player.

if you want some uinput examples, the easiest I know of is xarcade2jstick that we use for keyboard encoders : https://github.com/petrockblog/Xarcade2Jstick (and i'd love to make it a real configurable thing with ini file support for multiple encoders ... if you ever wanna contribute ...