|
  |
Full VGA Support For Modchips! |
|
|
| pimpysmurf |
Apr 12 2007, 09:25 PM
|
X-S Enthusiast
Group: Members
Posts: 5
Joined: 4-April 07
Member No.: 337031

|
QUOTE(FrostyTheSnowman @ Apr 5 2007, 10:09 PM)  Yes, the resistor is what decides the 'compatibility' of the generated VGA sync signals, so changing it could very well fix the problem. The most common resistors used are 320k, 470k, 570k, and 680k. I would try the 680k first, and then if that doesn't work try the 320k. Also note though that you can actually use any resistor you like between 320k and 680k. (I usually use 470k resistors.)  I finally got around to trying the other resistors and had some unexpected results, first I tried a 680k and had the same results, then I dropped to a 320k and once again the same results, I tried a couple of resistors in the middle and still had the same results, I would of expected something different. I even removed the resistor completely and had the same result. (I think it is an issue with the evo projector). one thing that is a little weird is that on first boot the screen brightness would flash from bright to dim rapidly, if I unplug the vga connection and then plug it back in, the monitor would readjust and be fine (well all except the top fifth which would quiver like before.). I am not sure where to go from here, maybe softmod the box, I have heard it has better vga output still. any opinions or suggestions frosty? thanks
|
|
|
|
| |
| pimpysmurf |
Apr 12 2007, 10:41 PM
|
X-S Enthusiast
Group: Members
Posts: 5
Joined: 4-April 07
Member No.: 337031

|
ok, thanks for all the help frosty!
|
|
|
|
| |
| PunMaster |
Apr 30 2007, 08:32 PM
|
X-S Young Member

Group: Members
Posts: 30
Joined: 30-April 07
Member No.: 340530

|
Hi. This VGA BIOS mod looks really cool! Unfortunately, it's not going as well for me as it is for everyone else. First of all, I have a v1.1 Xbox (Conexant encoder). I applied the patch to the newest release of iND-BiOS (iND-BiOS.5003.06.bin) and flashed it to my TSOP. I am using EvolutionX as my dashboard with an unlocked hard drive and no Microsoft dashboard installed. My monitor is an IBM LCD which supports sync-on-green beautifully. I know my port is wired correctly because I tested it with an older VGA BIOS mod (which worked on mode 1+3). Anyway, after flashing my BIOS, I got some interesting results which varied with mode settings. I tested each mode individually, with my Xbox connected to both a composite TV (NTSC) and my VGA LCD.The following table outlines my experience:
Mode 1 ----- TV: green tinted video - VGA: no video Mode 2 ----- TV: no video ----------- VGA: no video Mode 1+2 --- TV: green tinted video - VGA: no video Mode 3 ----- TV: green tinted video - VGA: no video Mode 1+3 --- *See Below* -------------------------- Mode 2+3 --- TV: no video ----------- VGA: no video Mode 1+2+3 - TV: normal video ------- VGA: no video
* Mode 1+3 was the most interesting. When I first turned my Xbox on I got a correctly colored "LOADING iND-BiOS" message on my VGA monitor. Then, after a few seconds, the message disappeared, my VGA display went blank, and my TV filled with green lines and other indistinguishable garbage.
Has anyone else had these problems? Am I missing something obvious? Thanks!
|
|
|
|
| |
| Risca |
May 6 2007, 10:31 AM
|
X-S Enthusiast
Group: Members
Posts: 16
Joined: 30-December 03
From: Sweden
Member No.: 87195
Xbox Version: v1.0
360 version: none

|
How about the Cromwell BIOS? Are these patches already integrated in the Cromwell BIOS? I shure hope so, because xbTool won't let me unpack it I'm working on the cable right now, but it would be rather useless if I can't use it for my Linux box. My specifications: Xbox 1.0 Conexant encoder of course 128mb ram GentooX installed as native OS (no FATX here) SmartXX v2 (it have som weird "Linux" menu in it's OS, but I don't know exactly what it does, other than boot Linux) These specs makes it impossible for me to use an ordinary BIOS, unless I would boot with a CD each time, and that's just a pain. And one more thing, you still need a patched BIOS for proper VGA even though you're running Linux, right? Linux don't have any magic ability to patch the encoder once booted? Keep up the good work, frosty  Note: Won't mode 2+3 signal the xbox that a HD cable is connected, and fool Microsoft dashboard in believing that there is a HDTV cable inserted. I mean, 2+3 is HDTV-mode, right? This post has been edited by Risca: May 6 2007, 10:35 AM
|
|
|
|
| |
| FrostyTheSnowman |
May 7 2007, 06:11 AM
|

X-S Freak
    
Group: Members
Posts: 1673
Joined: 29-June 06
From: Utah
Member No.: 288078
Xbox Version: v1.0
360 version: v1 (xenon)

|
Actually, yes, Linux does magically patch the encoder for VGA once booted.  Linux already has full support for VGA. Just make your cable a 1+3 cable (NOT 2+3, Linux is different) and Linux will fully support it, no patching needed. However, if you are going to use this cable for actual XBOX gaming, then you need to patch a BIOS with my VGA patcher, and make your cable a 2+3 cable. (HDTV) And yes, by having your cable in 2+3 mode, the XBOX does indeed think it is an HDTV cable, and this allows you to use HD resolutions over a VGA cable. This post has been edited by FrostyTheSnowman: May 7 2007, 06:12 AM
|
|
|
|
| |
| g-rasshopper |
May 7 2007, 11:38 AM
|
X-S Enthusiast
Group: Members
Posts: 9
Joined: 7-May 07
Member No.: 341220

|
Hi Frosty,
Firstly, thanks for all the work you've done on this. I can't understand why M$ didn't build VGA support into the Xbox as a standard feature. It would after all have cost them practically nothing. It's frustrating that my Dreamcast currently produces a far better picture (through VGA) than my Xbox.
I've got a question regarding the Xcalibur encoder.
My understanding is that European Xboxes can output an RGB scart signal, and RGB scart signals treat colours in the same way as VGA. So would it be possible to find out how a European BIOS programs the Xcalibur to produce an RGB scart signal? You could then just copy the code, without having to understand how it works, to add Xcalibur support to your patch.
Just a thought.
This post has been edited by g-rasshopper: May 7 2007, 11:41 AM
|
|
|
|
| |
| The Zep Man |
May 7 2007, 12:52 PM
|
X-S Freak
    
Group: XS-BANNED
Posts: 1833
Joined: 14-January 04
Member No.: 91914
Xbox Version: unk
360 version: unknown

|
QUOTE(g-rasshopper @ May 7 2007, 01:14 PM)  My understanding is that European Xboxes can output an RGB scart signal, and RGB scart signals treat colours in the same way as VGA. So would it be possible to find out how a European BIOS programs the Xcalibur to produce an RGB scart signal? You could then just copy the code, without having to understand how it works, to add Xcalibur support to your patch.
The use of RGB is the same, the use of sync signals is not. RGB SCART still uses 480i/576i (whether PAL60/NTSC or PAL is used) as it's resolution, while you probably want a progressive mode (480p) for VGA. Also, VGA uses two separate sync signals which differ a lot compared to those of RGB SCART. By the way, there is no 'European BIOS'. The BIOS is the same in each region. Regional settings are written into the EEPROM. Reverse engineering the Xcalibur is possible (hell, ANYTHING is possible)) , but I think it's a hell of a job.
|
|
|
|
| |
| FrostyTheSnowman |
May 7 2007, 01:57 PM
|

X-S Freak
    
Group: Members
Posts: 1673
Joined: 29-June 06
From: Utah
Member No.: 288078
Xbox Version: v1.0
360 version: v1 (xenon)

|
Well, i'm not sure if that would work or not, but it's definately an idea... The only thing is that the registers table for the Xcalibur encoder (and also the Conexant and Focus encoders) has a totally different layout for each output type, meaning it has a differently formatted table for Composite/S-Video, SCART, HDTV, etc... I have already located the HDTV registers table for the Xcalibur encoder, but i'm totally lost as to what to actually change... Everytime I attempt to reverse-engineer the HDTV encoder table on the Xcalibur encoder, I spend hours thinking of logical ways to do it, but every attempt so far just ends up in a FRAG. Then, at which point I will get frustrated and just give up, which has been the on-going cycle for months now... If anyone out there has better hex-editting skills than I do, or feels confident, please feel free to improve upon my work. Xcalibur support would be a great thing to see in the future. 
|
|
|
|
| |
| g-rasshopper |
May 7 2007, 05:31 PM
|
X-S Enthusiast
Group: Members
Posts: 9
Joined: 7-May 07
Member No.: 341220

|
I'm very new to the Xbox modding scene so I could be talking complete nonsense. But from my Amiga days, I always got the impression that, if you ignore the sync signals (which are of course a different issue), then the only substantial difference between an RGB scart signal and VGA is the refresh rate (~15.5 khz vs ~31.5khz). QUOTE(FrostyTheSnowman @ May 7 2007, 02:33 PM)  The only thing is that the registers table for the Xcalibur encoder (and also the Conexant and Focus encoders) has a totally different layout for each output type, meaning it has a differently formatted table for Composite/S-Video, SCART, HDTV, etc...
So are you saying that the Xcalibur/Conexant/Focus encoders have to be programmed differently depending upon the refresh rate? If you are then that would of course massively complicate matters.
|
|
|
|
| |
| FrostyTheSnowman |
May 8 2007, 08:56 PM
|

X-S Freak
    
Group: Members
Posts: 1673
Joined: 29-June 06
From: Utah
Member No.: 288078
Xbox Version: v1.0
360 version: v1 (xenon)

|
Well, the refresh rate is not too important, because progressive video signals already produce a compatible sync signal right from the get-go. (480p, 720p, and 1080i all produce a 31khz signal natively.) However, the register tables for the colors are different for each cable type. Meaning that HDTV and SCART have their own individual hex code, and that code is only used if that particular type of cable is used. I have not experimented with the *possible* similarities in the code for HDTV and SCART, because I am still somewhat lost as to what code actually applies to what cable, because of the fact that the Xcalibur encoder is so largely undocumented... However, it *might* be possible to use a SCART cable to produce a VGA compliant signal by use of a sync-doubler, but I have not tried this myself...
|
|
|
|
| |
| g-rasshopper |
May 8 2007, 10:11 PM
|
X-S Enthusiast
Group: Members
Posts: 9
Joined: 7-May 07
Member No.: 341220

|
I wonder how hard it would be to write a little program that allowed you to tweak the various registers to see what the effect was on the display in real time. I remember many years ago there was a program like that for the Amiga.
Incidentally, how many registers in total are there?
|
|
|
|
| |
| g-rasshopper |
May 9 2007, 06:22 PM
|
X-S Enthusiast
Group: Members
Posts: 9
Joined: 7-May 07
Member No.: 341220

|
Wow, it's more complicated than I realised. But I'm a bit confused. Is that just the actual data that goes into the registers, or the program code that sets the registers?
If it's the latter, then someone ought to run it through a disassembler. If it's the former, then I'm astonished that so much data is needed, unless M$ deliberately made the chip hard to program in an attempt to thwart hackers.
|
|
|
|
| |
|
  |
|