Please recommend a VGA to parallel LCD board or IC

[Tantratron]

Many many thanks @KerJoe, I've tried your code to recover the VGA after it was disconnected. It just works super good, so many thanks.

[amiq]

Perhaps this is of use

https://drive.google.com/file/d/1QIPHuwE10HqicRdAPSBfImHLHeSxzoSm/view?usp=sharing

[Tantratron]

Here is an new update where as a reminder, scaling down HORIZONTAL was always working live under ISP mode but for whatever reason, upon scaling down VERTICAL would always freeze (blue screen).

Now thanks to @KerJoe VGA restored routine, the VERTICAL scaling down just works fine with a skewed image but that is not important at this point. Of course, my panel parameters from the OEM firmware are not known for the moment (I need to do more work on this) but the key point, under ISP mode (8051 halted and VGA image displayed live) the scalers/registers can be directly manipulated via VGA-i2c arduino sketch or what other computer, processor.

I do have to investigate more why the MEASURE DIGITAL subroutine does not work upon first call when VGA input signal, I need to call twice to get proper measurements whereas MEASURE ANALOG does perfect estimation at first call when RGBs input signal.

Anyway for the record, see attached image result prior rewriting scaling DOWN factors and after, the key point now is the swiss knife routine able to recover VGA.

My next approach to say live hack or trick the OEM firmware, the RTD2660 board upon power up boots normal so I have good valid matched LCD parameters display, scalers/registers values and so. Then I enter via VGA-i2c into ISP mode to manipulate different registers/scalers via my arduino sketch. I set a 10 seconds timer wait so enough time to (1) disconnect the VGA connector from valid VGA input (2) modify scalers/registers and finally (3) connect this time my RGBs signal. After the 10 second twilight moment, I call the recover VGA routine to see the final display result.

Before this was impossible because connecting the RGBs would just have the 8051 declared NOT SUPPORT input so no proper scaler/register LCD setup.

[Tantratron]

Here is an update following a PM so I've ordered this morning to AliExpress a PCB800099-V9 board. It will serve two purposes, maybe I'll understand or isolate why my actually PCB800099-V9 does not work well (see previous pages about symptoms including denial of I2C transaction) and best platform to learn the programming of both TTL and LVDS.
For the moment, I do have one PCB800196-V6 (only LVDS) connected to G065VN01-V2 and one PCB800808 (only TTL) connected to AT056TN53-V1.
That way I'll probably go faster comparing side by side the outputs, the registers and scalers since I've few arduino DUE's board.
The working PCB800099-V9 might help since higher chance of you have the same then we could team work or find my mistakes.

Today I've received the new PCB800099-V9 ordred at AliExpress on dec. 5th then made a quick test with my setup (i.e. LCD 6.5" LVDS 6bits). It works fine, accepts the i2c transaction from the arduino, does not over-heat and offers a stable nice image which really confirms what I've told before in this thread regarding the first PCB800099-V9 purchased in France (failed). I will see if it can be repaired but my priority is really to see if possible to de-interlace my RGBs 15 KHz signal.

One simple question for @KerJoe, do you confirm that since your the ANALOG MEASURE routine works with my RGBs 15 KHz signal (correct values as predicted by my Logic Analyzer) then for sure the RTD2660 can full decode the RGBs signalling ?

Does it prove that since Hsync is XORed with Hsync so only one CompositeSync signal, the RTD2660 if properly scaler programmed (how... no idea for the moment) has enough input signal information to fully decode then LCD display the video ?

[KerJoe]

If the RTD2662 supports the YPbPr signal, which it does, then there's no reason it can't also support RGBs. Plus there are reports on the internet that say the RGBs signal at 15kHz works fine on it.

[Tantratron]

If the RTD2662 supports the YPbPr signal, which it does, then there's no reason it can't also support RGBs. Plus there are reports on the internet that say the RGBs signal at 15kHz works fine on it.

I've tried to understand the datasheet regarding how to program the scalers/registers when RGBs, it is really not easy.

One option I wonder if it could make sense and help, tell me frankly if it could work as a indirect reverse engineering. As mentioned before, we know this UK company got a firmware from russian person or company for RGBs 15 KHz to drive a 800x480 LCD display (RGB-8 bits), see again here then here and here. Now I that have a working PCB800099-V9 as JagDroid used so how about I flash the russian firmware used by JagDroid into my PCB800099-V9 then solder a 50 pin to 40 pin connector after checking where are the signals truncated to 6 bits per color, where are the DE CLK pins to be displayed through my 40 pin LCD which is slightly different (640x480 RGB-6bits) ?

If this modification or hack shows valid RGBs display then how about using ScalarReadByte different scalers registers with my arduino in order to spoof or observe or reverse engineer what values were programmed to RGBs 15 KHz de-interlace ?

[Tantratron]

Ok so now that I've a valid working PCB800099-V9, it might be easier to understand via ScalerReadByte() calls some live dynamic registers/scalers. This board has multiple firmware possibilities or scalers possibilities  (see attached document showing about 30 possibilities) so I've first tried my LVDS 640x480 RGB-6bits display through jumpers A-3, so far so good. Then I've chosen jumpers A+1 to target LVDS 6 bits 800x480 and my LCD does display the image, off course part of is lost on the right (800 versus 600). However I can probe (read) some scalers/registers by entering into ISP mode through my arduino sketch. Kind of spoofing or spying to self-learn since understanding in details the 401 datasheet is very hard for me (time, energy, knowledge).

I do have another technical question regarding the RTD2660's chip data path, see attached picture extracted from monster datasheet. About the dark green block (SCALER), am I correct this block is only to ScaleUp or ScaleDown but all the registers supposed to manage the synchronization, detection of signal type are in other blocks ?

I ask this because we talked lot of scalers but i just want to make sure my global understanding of the architecture described in this diagram versus the reality of registers/scalers/video engines which can be seen as slave or autonomous self-run once pre-programmed correctly.

Thank you in advance for any clarification and positive critic

[Tantratron]

Specific message and post for @DC1MC because i'm suddenly realizing all my posts, reports are kind of hacking or absorbing or invading your initial thread, posts. Please tell me frankly, maybe the topic and what i'm trying to do is different from your intent so I can start another thread in order to not corrupt your own thread.

Greeting from France

[KerJoe]

I do have another technical question regarding the RTD2660's chip data path, see attached picture extracted from monster datasheet. About the dark green block (SCALER), am I correct this block is only to ScaleUp or ScaleDown but all the registers supposed to manage the synchronization, detection of signal type are in other blocks ?

Yes, that block is the one that's responsible for scaling the incoming signal up/down. Referring to the whole video processor as a "Scaler" may not be technically correct, however that's the way the datasheet refers to it.

[DC1MC]

Specific message and post for @DC1MC because i'm suddenly realizing all my posts, reports are kind of hacking or absorbing or invading your initial thread, posts. Please tell me frankly, maybe the topic and what i'm trying to do is different from your intent so I can start another thread in order to not corrupt your own thread.

Greeting from France

Hello, there is no need to dilute the information and spread it all over, you can stay here as much as you wish until your issue is finished. I'm continuing to slowly walk trough the firmware and waiting to see if you'll find a set of settings suitable for your video signal. Afterwards only a firmware capable to store the registers in a place where they are retrieved at startup is needed and voila universal firmware is here. If is combined with a storage and retrieve of the LCD parameters it will be truly universal. OSD and other goodies are nice to have, but not essential for a display to be put in measurement instrument or car.

Cheers,
DC1MC

[Tantratron]

Hello, there is no need to dilute the information and spread it all over, you can stay here as much as you wish until your issue is finished. I'm continuing to slowly walk trough the firmware and waiting to see if you'll find a set of settings suitable for your video signal. Afterwards only a firmware capable to store the registers in a place where they are retrieved at startup is needed and voila universal firmware is here. If is combined with a storage and retrieve of the LCD parameters it will be truly universal. OSD and other goodies are nice to have, but not essential for a display to be put in measurement instrument or car.

Ok great and thanks, so let’s then only concentrate in your thread about past information, past knoweldge, recent testing and learning, maybe more knowledge could be provided by russian and ukrainian joining your thread. When I did look for specific thread about the very topic of RTD266x last october, it seems most of the return of experience, advanced practice (HW and SW) are found only in russian language forum so very hard to join. Maybe more russian speaking persons besides KerJoe and Postal2 would accept to join, ideally the person from ORTD2662 who provided to the JagDroid british company the unique firmware able to SCART RGBS 15 KHz decode the video then display into 800x480 panel.

You raise a point, namely there is another serious application regarding car display modification besides Arcade retro gaming or test equipment CRT to LCD retrofit. Interesting to see few russians actually made kits for Lexus or Toyota Camry, maybe other high model or brand plus this british firm doing the same for specific Jaquar model. In the mean time, I’ve now forked KerJoe’s Github repo into my account here because it seems the best the way it is structured but I’ll adapt and simplify most of its part oriented arduino sketch in the near future.

I might have to go a bit on holidays in the next 2 weeks for a break but will try do some new test tomorrow and sunday.

One thing I’m now suddenly realizing, the PCB800099-V9 board in my had offers multi-jumpers to provide about 30 different LCD’s model. Problem I did not think earlier, the JagDroid PCB800099-V1 is not exactly the same, for sure no jumpers but we do have the firmware from ORTD2662 able to decode SCAR-RGBS 15 KHz. My sudden fear, maybe you can help here, if I decide to flash the ORTD2662 firmware in my PCB800099-V9, is there a risk part of the pinout are not the same between V9 and V1, worse a risk of electrical incompatibility or shorting (blue smoking) since GPIO pins can have different mode of operation ?

If it could work, maybe I can take the risk to flash the Jagdroid-ORTD2662 firmware into my PCB800099-V9 then directly connect my 15 KHz interlaced signal to see if it works. This wil not provide any knowledge of the scalers/registers programming but would confirm it is doable and worth pursuing.

The key thing which still worries me, when looking at Realtek leaked code, KerJoe or specadmin Github, it seems only YPbPr mode can be handled. The YPbPr is not exactly as RGBS-SCART because only 3 wires versus 4 wires. The way Composite SYNC is embedded is different, separate wire as in my signal and fused in one color signal output. So yes, the Realtek datasheet says it can handle YPbPr interlaced signaling but I do not see clearly on the Data Chip flow diagram a specific RGBS block. There is an ORANGE block (VGA/YPbPr) but I see no information about CSYNC because there are different ways to compositive SYNC into the signalling system as explained in this link

Lastly about my PCB800099-V9 new testing when in LVDS mode, I’ve tried both jumpers A-1 (800x480 LVDS) and A-3 (640x480 LVDS) with the same screen 640x480 from AUO then modified my arduino sketch to directly change the caler values. Prior to this, I did ScalerReadByte these scalers both for HOR and VER, which means after I can dynamically arduino write the scalers to virtually change A-1 to A-3 resolution. As long as I do not change any value in VERTICAL scalers, everything works when I only change HORIZONTAL but any attempt to change VERTICAL fails.

I’m still on my learning curve with video 2D processing, my background is only digital signal 1D processing so I must miss a point. Why changing VERTICAL scalers requires to modify or re-compute other scalers to work whereas directly changing HORIZONTAL scalers really does not screw the display except truncating on the right ?

[DC1MC]

Regarding the compatibility in between versions 0.9 and 1.0, I don't think there's any chance of destructive malfunction.
The power, inputs and LCD outputs, as well as flash interface are immutable, the rest are GPIO pins that are current limited from design, so, IMHO, there is no harm in testing the firmware, it may not work, but the board will survive.

 Cheers,
 DC1MC

[Tantratron]

I've looked on the DIY details instructions from JagDroid to find out the datasheet of his LCD display, we see here the model model YX070TN94-VL800 by SEBO.

Unfortunately I cannot find its datasheet on the web, maybe my google search key words are not the best so do you know this panel or its datasheet or an equivalent display with same pins ?

The reason being that I want to save time when building the 50 pins to 40 pins TTL adapter so I could try the Jagdroid firmware made by ORTD2662 with my 40 pins LCD display under TTL mode.

N.B. My LCD are RGB 6 bits so I'd only use 6/8 bits generated by the Jagdroid firmware

Thank you, Albert

[DC1MC]

I generally don't like to be someone's "google bitch"  , but in the interest of science    the datasheet of this panel is in the Jaguar forum:
https://www.jaguarforum.com/threads/android-upgrade-to-jaguar-touchscreen-for-xj-x350-x358-s-type-and-x-type-howto.96954/page-39?post_id=1024931#post-1024931

PDF attached.

Cheers,
DC1MC

[pcprogrammer]

The reason being that I want to save time when building the 50 pins to 40 pins TTL adapter so I could try the Jagdroid firmware made by ORTD2662 with my 40 pins LCD display under TTL mode.

For what I have seen of RGB TTL based 50pins LCD panels is that the pinout is fairly standard. The FNIRSI-1013D uses a similar 800*480 LCD and when working on the reverse engineering I ordered what I thought to be also a 800*480 LCD on Aliexpress, turned out to be a 1024*600 LCD. The pinout on the cable is the same.

To test software I bought a Lichee Nano, which has the same processor (F1C100s) as the FNIRSI-1013D scope, but it uses a 40 pin connector for connecting LCD panels. To attach my 50 pin LCD I made a conversion protoboard based on a bunch of modules. 40 pin FPC to 2.54 header, 50 pin FPC to 2.54 header and a +/- boost converter to get the needed voltages for the display.

I did not read what is in this thread and what your goal is, but here is what I made.

The power module I used was bought on Aliexpress. https://www.aliexpress.com/item/1005007220441135.html

[Tantratron]

I generally don't like to be someone's "google bitch"  , but in the interest of science    the datasheet of this panel is in the Jaguar forum:
https://www.jaguarforum.com/threads/android-upgrade-to-jaguar-touchscreen-for-xj-x350-x358-s-type-and-x-type-howto.96954/page-39?post_id=1024931#post-1024931

PDF attached.

Many thanks for web google track search assistance, you are ready to be a great spy agent post with dropbox still active link

So now thanks again, the specific LCD datasheet pin used by Jagdroid is known to avoid any blue smoking when I'll proceed the HW rewiring from PCB800099-V9 towards one of my displays (40 pins or 33 pins).

For what I have seen of RGB TTL based 50pins LCD panels is that the pinout is fairly standard. The FNIRSI-1013D uses a similar 800*480 LCD and when working on the reverse engineering I ordered what I thought to be also a 800*480 LCD on Aliexpress, turned out to be a 1024*600 LCD. The pinout on the cable is the same.

To test software I bought a Lichee Nano, which has the same processor (F1C100s) as the FNIRSI-1013D scope, but it uses a 40 pin connector for connecting LCD panels. To attach my 50 pin LCD I made a conversion protoboard based on a bunch of modules. 40 pin FPC to 2.54 header, 50 pin FPC to 2.54 header and a +/- boost converter to get the needed voltages for the display.

I did not read what is in this thread and what your goal is, but here is what I made.

Thanks @pcprogrammer for joining and helping, note that 50 pins LCD are not exactly standard, for example the attached datasheet from AUO display model G070VVN01.1-V2

In a few words about this thread started wayback in december 2020 by @DC1MC. The topic is roughly on looking, choosing and hacking a LCD driver multiple format video decoder where it seems now the best candidate would be RTD2660/26662 chip. Very few documentation exist for modifying or developping new firmware compatible with this chip so it is about being autonomous.

N.B. Unless I'm wrong, it seems only in Russia and China complete development tool is mastered by experts but access to this knowledge is hidden or restricted.

Technically we find archives for some LCD models so hacking is simple, namely re-flash the firmware able to decode different video input format but no customization is possible (i.e. OSD content, LCD model, video input format).

In my project, I cannot find any firmware able to RGBS-SCART deinterlace 15 KHz video format found in old Advantest spectrum analyzer (R3x61/R3x65/R3x71) models to replace CRT by LCD kit.

The very same topic seems to interested people modifying high end display car systems like Jaguar, Lexus.

[Tantratron]

Regarding the compatibility in between versions 0.9 and 1.0, I don't think there's any chance of destructive malfunction.
The power, inputs and LCD outputs, as well as flash interface are immutable, the rest are GPIO pins that are current limited from design, so, IMHO, there is no harm in testing the firmware, it may not work, but the board will survive.

As far as I remember from your posted pictures, you only have the PCB800099-V9 old version (fixed LCD resolution by firmware) whereas the latest PCB800099-V9 which I'm using has set of addition 11 jumpers to select internally about 30 different LCD resolution wether LVDS or TTL. Maybe there is a schematics describing how these jumper pins are wired into the RTD2660 versus the actual 50 pins TTL output. I might need to DMM test and verify if actually the TTL-50 pins output from the multiple-resolution firmware board are the same physically as the single resolution as your board or the one used by Jagdroid, here Im' talking the ZIF pins verus the actual RTD2660 pins.

On a side note, I've tested this morning under LVDS output another jumper select, namely A-4 (LVDS 800x600) directly into my 640x480 display. It does work with proper Hsync and Vysnc scaling except of course my display will truncate even more the image on the right side and bottom side. All this to say that wether A-1 (800x480) A-3 (640x480) or A-4 (800x600) jumper resolution, the image is stable on my 640x480 display so I must really miss a technical programming knowledge on how to dynamically change the VERTICAL scalers under ISP. As a reminder, the HORIZONTAL live change of scaling really works under ISP with my sketch so the vertical change requires additional register/scaler software modification.

[Tantratron]

Ok here is first hope RGBS deinterlacing is doable through a quick and dirty test before engaging myself into flashing firmware from ORTD2662/Jagdroid then soldering a dedicated 50 to 40 pins adapter.

My idea is taking advantage of different resolution thanks to the 11 jumpers manipulation on the PCB800099-V9 board (see attached datasheet for jumer choice). Some of the jumper combination are for LVDS, others are for TTL then of course different resolution. Anyway I've tried jumper A alone supposed to be 800x480 (AT070TN92 display) then 2+9 for EJ50NA-8C display. They seem to be pin compatible with the YX070TN94-VL800 by SEBO where I do not care if RGB 8 bits or RGB 6 bits.

To my surprise, check attached picture where I'm using my TDS784D (with LCD retrofit) to check pin 10 (VS) and pin 11 (HS), so there seems to be coherent signalling SYNC output of 42 KHz x 80 Hz when I do aply as an input my RGBS signal 15 KHz interlaced signal. I need to refine and confirm later using my SALEAE 16ch logic analyzer but maybe the actual PCB800099-V9 board already does RGBS de-interlacing for some jumpers selection.

This would be strange because then why in the first place, the Jagdroid owner needed a specific firmware for his RGBS 15 KHz signal !

[Tantratron]

Another interesting outcome when using PCB800099-V9 board with LVDS mode (jumper A-3) connected ty the RGBS 15 KHz interlaced signal. When pressing MENU it will display NOT SUPPORT plus now an estimation what the firmware can guess, namely 61 Hz which we knew but cannot guess resolution (0x0), see attached screenshot.

Whereas using my PCB800196-V6 board (single flashed LVDS resolution) or my PCB800808 board (40 pins TTL), it would only display NOT SUPPORT without any additional information.

All this to say that MEASURE ANALOG and MEASURE DIGITAL subroutine of KerJoe works good, the challenge is really figuring out how to de-interlace.

[pcprogrammer]

Thanks @pcprogrammer for joining and helping, note that 50 pins LCD are not exactly standard, for example the attached datasheet from AUO display model G070VVN01.1-V2

Clearly you found the odd one out, and connecting that one to your controller would result in some smoke. The backlight supply would be fed into the 3.3V power supply of the one you found. 

Including the one DC1MC found, I know have six datasheets of LCD panels with 50 pin connectors that all have the same pinout.

Yesterday I received the PCB800852 RTD2660H based HDMI-mini to 50 pin RGB TTL display controller plus belonging display I ordered on Aliexpress. (https://www.aliexpress.com/item/1005005292813240.html) The 50 pin connector pinout on that board matches to what I found in all these datasheets. It does work with the 1024*600 display I mentioned in my previous post. Unfortunately the image quality is crap and might be due to the controller outputting in a 800*480 resolution instead of the needed 1024*600. See the review I wrote on the sellers page.

It is now added to my to do list to see if I can fix this. 

[Tantratron]

Ok here is first hope RGBS deinterlacing is doable through a quick and dirty test before engaging myself into flashing firmware from ORTD2662/Jagdroid then soldering a dedicated 50 to 40 pins adapter.

My idea is taking advantage of different resolution thanks to the 11 jumpers manipulation on the PCB800099-V9 board (see attached datasheet for jumer choice). Some of the jumper combination are for LVDS, others are for TTL then of course different resolution. Anyway I've tried jumper A alone supposed to be 800x480 (AT070TN92 display) then 2+9 for EJ50NA-8C display. They seem to be pin compatible with the YX070TN94-VL800 by SEBO where I do not care if RGB 8 bits or RGB 6 bits.

To my surprise, check attached picture where I'm using my TDS784D (with LCD retrofit) to check pin 10 (VS) and pin 11 (HS), so there seems to be coherent signalling SYNC output of 42 KHz x 80 Hz when I do aply as an input my RGBS signal 15 KHz interlaced signal. I need to refine and confirm later using my SALEAE 16ch logic analyzer but maybe the actual PCB800099-V9 board already does RGBS de-interlacing for some jumpers selection.

This would be strange because then why in the first place, the Jagdroid owner needed a specific firmware for his RGBS 15 KHz signal !

P.S. Additional measurement when choosing jumpers 2-9 settings on my PCB800099-V9, now probing the DE (Data Enable) and DCLK (Clock) from respective TTL output, again RGBS-SCART 15 KHz interlaced being fed as an input signal. The DCLOCK is near 35 MHz whereas DE/HS are 42 KHz with VS 80Hz.... let's hope one of my TTL-LCD (G057VN01-V1 from Innolux or AT056TN53-V1 from AUO) is able to absorb  (eat) this rescaled pixel clock of 35 MHz

[Tantratron]

I generally don't like to be someone's "google bitch"  , but in the interest of science    the datasheet of this panel is in the Jaguar forum:
https://www.jaguarforum.com/threads/android-upgrade-to-jaguar-touchscreen-for-xj-x350-x358-s-type-and-x-type-howto.96954/page-39?post_id=1024931#post-1024931

Just thought of another way to get the safe pin out of the TTL 50 pins connector, the russian website shows different documents and schematics. The schematic 6 called VS-TY2662-V1 shows on page 6-7 all the pins from the PCB800099-V9 where clearly the LCD used by Jagdroid is similar with no risk of blue smoking. However with both panel, I need to be cautious because each have an additional pin for dimming the WLED throw PWM so that section is not exactly the same in the 50 pins output connector.

I need to decide now if I try to wire and connect my AT056TN53 display or my G057VN01-V1 where both are RGB-6bits, the difference the 2nd is maybe safer because the backlight power LED have dedicated connector.

In the mean time, I'll try using again my arduino sketch to ScalerReadByte some scalers/registers to intuit or guess how the deinterlacing is done when jumper 2-9 are selected

[Postal2]

What "pin", what "diagram"... There is a ready-made connection diagram, I don't understand what you are doing.

[Tantratron]

For the moment, I've still not connected any LCD to the PCB800099-V9 output connector 50 pins TTL because I first need to solder the wires, match the pins free of error. However I've just notice something wierd unless there is an explanation.

Pin1-2 are +VLED then pin3-4 are -VLED but when measuring the voltage (open load with no WLED), I read 32 volts... is there an explanation to have such a voltage boost inside the PCB800099-V9 board because it receives +15Vdc then generate lower voltage rails 5V 3.3V and 1.8V ?

This is where I did purchase the board https://fr.aliexpress.com/item/32557356912.html

[pcprogrammer]

For the moment, I've still not connected any LCD to the PCB800099-V9 output connector 50 pins TTL because I first need to solder the wires, match the pins free of error. However I've just notice something wierd unless there is an explanation.

Pin1-2 are +VLED then pin3-4 are -VLED but when measuring the voltage (open load with no WLED), I read 32 volts... is there an explanation to have such a voltage boost inside the PCB800099-V9 board because it receives +15Vdc then generate lower voltage rails 5V 3.3V and 1.8V ?

This is where I did purchase the board https://fr.aliexpress.com/item/32557356912.html

Depends on the circuitry used of course, but the back light controller can use constant current control and without load it will output its maximum voltage.