![[Main Page]](http://www.eurasia.nu/images/svico_t.gif)
Xbox v1.6 Event log
Links:
Xbox v1.6 was discovered in the month of May 2004.
booyeah @ forums.xbox-scene.com found a new xbox version.
Named Xbox v1.6.
ModRobert @ EurAsia
There are some changes, the main difference seems to be the "missing" onboard TSOP and a new 'Xyclops' labeled chip. It's unknown at this moment if there is extra or new security.
Clear hi-res pictures of the motherboard from xbox-scene:
XanTium @ xbox-scene:
Here an overview of what various people have been discussing in the xbox-scene.com forums since the last newspost. - Xboxes with a manufacture date of 2004-03-22 are v1.6. 2004-03-11 are still v1.4. So far these very recently produced xboxes are only found in US stores ... but it's only a matter of time before they come everywhere (when old stock clears). - We now saw pictures (by pROvIs - see below) of the backside of the board. There's no TSOP there either - so bios/kernel (firmware) must be on another chip. First guess is still that new "Xyclops" labeled chip above the LPC. It's unknown yet if the onboard bios/kernel will be flashable or not. Will have to be researched by HW teams. MS might have permanently strap "d0" on the "TSOP bus" (on MCPX) to "0", and build-in an LPC boot ROM instead (oz_paulb). - We do NOT know yet if it's still possible to force boot from (external) LPC. Neither do we know yet if the LPC bus changed (apart from the visual difference that there is a LPC point #4 now - this point was not on older xbox versions). So it's also unknown yet if the current modchip hardware will be compatible with the v1.6 - The 5530 and 5713 retail kernel (seen in xbox v1.4/v1.5) has already support for the new xcalibur chip. There's is no hacked bios/kernel yet based on these builds. Yoshihiro (GueuX'NeT Team) said these builds would require a new init table. - The audiochip is also gone. The new videochip (labeled xcalibur) is bigger then the one used before (conexant/focus) so it's possible audio and videochip are now combined in this new xcalibur chip (the joker). - The new 'xyclops' and 'xcalibur' have not been identified yet as any known chips. These might be custom chips made by/for MS or maybe these are just relabeled/renamed chips. - Modchip teams are showing interest for this new v1.6 xbox and will probably start research as soon as they manage to get one of these v1.6 xboxes.
ModRobert @ EurAsia
Updated the xbox-scene version table at EurAsia to reflect xbox v1.6:
Evobex @ xbox-scene
I hope this is of use. I sanded down the V1.0 MCPX PCB, then traced as many points as I could back to the LPC bus and flash chip. Maybe someone can check the same points on a V1.6 MCPX and see where they all go? Might help:- 1) Determining the true identity of the mysterious Xyclops chip 2) Locating flash-enable jumpers, if any 3) Mapping out the new LPC bus
My apologies if there are any mistakes. This was done with no magnifying glass, no desk lamp (only had the "big light" on ) and with standard Fluke test meter probes. In particular the LPC connections are vague, but they appear in that order as you move the probe across the traces.
Picture here:
The_Mad_Maragan @ ozxodus.com
Due to booyeah's recent discovery of the much anticipated V1.6 motherboard it appears that things are about to get a little bit more interesting for the Xbox community.
OzXodus have been fortunate enough to aquire booyeah's V1.6 console for our research into what changes have been made to the console's motherboard. As many have already speculated it appears that major changes to the LPC have been made, our initial findings are indicating a redundant LPC with all 4 LAD lines no longer present.
We have found that the d0 point is in the general area of the d0 found in previous motherboard revisions.
We call on the other teams to confirm these initial results when they are able to aquire V1.6 motherboards for their own testing.
We would like to take this opportunity to thank booyeah and kris for their assistance in obtaining these motherboards for our testing, we will keep you updated on developments via our website as they become available.
But it's not all bad news, we are very confident that we will have a Xenium with Xenium-OS V2.0 booting on a V1.6 in the very near future (72 hours???). ;-)
hamtitampti @ smartxx.com
After working little bit, now little help for the Xenium's & others if you "dump" the bios, the MD5 of Retail (256) 5838.01 is = C5 90 7D 24 1D E3 7C 22 B0 83 B6 E3 0F A9 34 B0
good luck guys and continue with these fake news
Btw: the Power connector has changed. Normal Power supply's will not work anymore (have to find out why)
BIOS dump here:
ed2k://||file||original_5838.zip||241379||97B1F31D23E15BB1A6C0C21F62540445||/
hamtitampti @ smartxx.com - more infos
today, i played with the I2C bus.
the I2C temperatue Sensor dissapeared. or i have false adress, who knows.
i attached a dump of a startup of the I2C codes.
btw: Interesting new findinds in the new Bios already. and it looks so, that there will be no "universal" bios now, which works on all boxes. 1.6 will need seperate Bioses.
THE PIC is here the Video encoder moved to 0x70 Temperature gone no 10 (or 20) seconds Temperature askings from PIC anymore (logically) The Video Encoder Traffic is "bulk" and not BYTE/WORD anymore.
and from my feeling: it looks like "encrypted"
EEprom hdd key also changed, but already idendified and found.
xcalibur-I2C-Startup.txt (17 KB) http://www.smartxx.com/forum/attachment.php?attachmentid=66&sidd645342279e7a89e7f6d173aec02849f
Team Gueux.Net
As you know, we're a french Team and actually it's very difficult for us to help and work on the new Xbox v1.6 (we're trying to bring back one in France). However, as kernel 5838 is already released we're working on it.
The result is that we have integrated Xcalibur support in a flashable 512k debug bios. We need help from other team to test it, if they have the possibility : - This bios is forced for Xcalibur so don't try it on other versions (v.1.4/v1.5 and less). - Kernel number implemented : 1.00.1600.01 - Do not split it in 256k - You can launch unsigned XBE.
We hope that the other teams will want to give us the result of their tests with this bios. Thanks Team Gueux.Net
Team OzXodus proudly announces another groundbreaking achievement for the Xenium.
In less than a week from the first sighting of the new Version 1.6 motherboard, we have worked round the clock and now have our premium product, the Xenium, up and running. Once our new OS2 is inline and updated, the Xenium will truly live up to its billing as the premium chip on the market.
For the meantime, Xenium solder less will not work as there is need to solder five jumpers under the mother board.
For those of you who are interested, we have posted a picture showing clearly where the D0 is located. (Although it is no longer needed in the 1.6, it can still be used to toggle between LPC and standard flash bus interface).
We have also included a video showing version 1.6 controlling the Xenium debug LED.
We would like to take this opportunity to invite all of you over to our forums at www.ozXodus.com , where we will be discussing and working on all development and release issues exclusively. So if you want to hear news first , join us there==
Xenium. Discover a whole new Xperience==
Picture link here:
Download Video: http://66.111.59.177/pictures/testvid.AVI
team-xecuter.com
Finally got our hands on a v1.6 yesterday - just waiting for another 5 for our other coders. The technical data needed was pretty much discovered in the first couple of hours, we simply wait for the other boxes to arrive at the workbenches of our colleagues then we will have a release for you - modchip info including an X2 / X3 bios with xcalibur video & audio support. Good to see the whole scene pull together for a change on this one - even though much mis-information has been spread around.
Will be interesting to see how long it takes to add support to any Linux bios. Focus took around 3 months - and this is far more complicated - good luck to those coders.
XanTium @ xbox-scene.com
Xbox v1.6 update: manufacturer date
From ealier news we already knew xbox consoles made on and after 2004-03-22 were v1.6 but today lookformeb informed us (also added some nice new pictures) on the xbox-scene v1.6 research thread that his Xbox with a manufacturer date of 2004-03-19 is also an Xbox v1.6 already. From earlier news we know 2004-03-11 xboxes are still v1.4 - so between 2004-03-11 and 2004-03-19 it is still unknown at this time. That is of course considering all production lines changed to v1.6 at the same time (if not you can have different versions produced on the same day).
Artifex @ ozx forums
Hello everyone==
As I'm sure you've all noticed by now, we have succeeded in modifying the v1.6 such that the Xenium is fully functional. Within just a few minutes of posting this video, several people came to me with the same questions, so we at OzXodus thought it would be a good idea to answer some of the inquiries as to the technical details by starting a thread in which to share our findings with you, our friends, customers, and even the competition.
To answer some of the common questions:
- How much modification was done to the board? Is it a difficult modification? 5 jumpers were soldered on the underside of the board. I did these solders myself, and I am by no means an expert with an iron. The modification was not difficult, anyone who can manage a d0 will have no problem.
- Will a solderless be available? That is yet to be determined.
- What are the actual modifications? Previously it had been said that the LPC bus was no longer functional, and that the LADs were missing, yet the chip appears to be on the LPC bus. Is it, or isn't it? The LAD lines are not routed to the LPC bus, but they still exist. In fact, the onboard firmware is no longer a parallel device, but an LPC slave device. In other words, Microsoft's firmware is now the same type of hardware used for contemporary modchips. The modifications made to the board re-route the LAD lines to the debug header, for use by a chip.
-If both the mod and the onboard firmware are LPC slaves, doesn't that create bus contention? YES= However, interestingly enough, Microsoft's onboard flash makes use of the LFrame, which has been brought back in this new revision! It is believed that microsoft previously removed the Lframe to thwart people wishing to modify their xbox for running linux, and similar "homebrew" projects. One of the OzXodus team members, in fact, was the first to discover the "missing LFrame" and the modding community was quick to react. Now, modchips such as the Xenium, no longer have any need for the LFrame. The common LPC Flash component chosen by microsoft for the v1.6 does, however, hence it being brought back.= We simply disable the LFrame signal, causing the onboard bios to cease functioning, and allowing the Xenium to take control. You could say that Microsoft's own solution to modchips came back to bite them==
- I heard mention of differences in the power supply between this and previous revisions. Can you elaborate? Previous revisions used a standby voltage of 3.3v, where this new revision uses a standby of 5v. Power supplies from earlier revisions will not work with the new revision.
- I heard mention of the smbus being "encrypted." Is it? No. The new video encoder (Xcalibur) found in the v1.6 appears to use a rather complicated method of table lookups for initialization. Compared to the straightforward table lookups used for previous encoders, it is easy to see how, at an uneducated glance, it would appear that some form of cipher is occuring. This is not the case, it is simply complicated code.
- Are you tired? You have no idea.
- Is that your hand? Yes.
More to follow..... Keep an eye on http://www.OzXodus.com/ for the latest Xenium and Xbox v1.6 news==
--Artifex
Michael Steil @ xbox-linux.sf.net
Updated entry submission form with new Xbox version: http://www.xbox-linux.org/docs/versionsentry.html
xbill @ forums.xbox-scene.com
source: http://forums.xbox-scene.com/index.php?showtopic=209029&st435
I put a meter on a 1.6 power supply. As mentioned earlier by walabie (page 19) who was quoting hamptitampti over on the SmartXX board, the power supply has changed.
Xbox 1.6 Power Supply Pinouts
Pin Signal Color Notes --- ------ ----- ----- 1 +5VSB Orange 2 +5VSB Orange 3 +5VSB Orange 4 GND Black 5 GND Black 6 GND Black 7 NC 8 NC 9 GND Black 10 PWR OK Blue Labeled:PWRPK, +3.3VSB, +3.3V when power is on 11 PS ON White Labeled:DRV_PWR_ENABLE, +3.3V when power is on 12 GND Black 13 NC 14 NC 15 GND Black 16 +5V Red 17 GND Black 18 +5VSB Orange 19 GND Black 20 +12V Yellow
Anyone else confirm these?
Also, the new pin #4 on the LPC has +3.3v in standby. When shorted to ground it powers up the xbox. edit: it's tied to the power button Is #6 (VCC5) supposed to have +5v in standby?
hsdemonz - v1.6 pictures
http://hsdemonz.left-click.org/xbox_1_6_Motherboard
SmartXX Team - XBoX 1.6 LPC Port Recovery
Source: http://www.smartxx.com/forum/thread.php?threadid=751&sid
DMS X-B.I.T @ http://www.dms3.com/cgi-bin/xbit/site.pl?page=news
_We have received our XBX V1.6 consoles. Thanks to Ryan for shipping them so quickly. We're now working on a solution._
OzXodus Team @ http://www.ozxodus.com/
Resurrecting a damaged V1.6 Motherboard
We have seen quite a few posts on message forums from concerned people who have "damaged" their 1.6 xboxes whilst trying to probe their new mobo. As we have first hand experience with this (during the first hour of receiving our new unit :-) ), we have decided to put together this small tutorial as a way to assist anyone who may have had the same misfortune.
Download the V1.6 Resurrection Guide here:
http://downloads.ozxodus.com/Guides/Xbox_v1.6_Resurrection.pdf
hamtitampti (franz) @ http://www.smartxx.com/forum/thread.php?threadid=703
GUYS, the first BETA = YUHUU=
Please only people who have an 1.6 box or 1.6 Box devs should install it.
I decided to release, as it looks like, the Xenium just startet there Box the first time and almost killed it. (Why the hell did i write, that power supply changed ???) Also, maybe we see in Additional ??? 72 hours an Update from there side.
So , download it from here:
http://www.smartxx.com/download/beta_3313.zip (Relase and update notes and diagramms included inside the zip)
sorry, the Website had a 200k limit (and somewhere i lost the pw for smartxx - website. ..) , i released it on tripod. (note, tripod does not allow refers, so you have to type the URL manually into your browser)
So People, i think, it is time for you, to decide what you want to buy.
- -)
Note to Xbins / Xbox-Scene & others: Do not upload this bios to Xbins / Xbox-scene , as this is a really hard core beta. Also, you can expect very soon new betas/finals, and this would only confuse the normal people (they sure will try it to install too) thx. I will release them here in this channel.
franz
hamtitampti (franz) @ http://www.smartxx.com/forum/thread.php?threadid=703
Final Beta.
SmartXX Team is proud to announce: The Final Beta for 1.x boxes.
Standby for a release in the very near future (72 hours???). ;-)
(Copyright Note: Parts of the text taken from Xenium posting )
SmartXX Team changes back to normal Development again, as the "1.6 issue" is over
Download : http://www.smartxx.com/download/beta_3315.zip
franz
news @ http://www.smartxx.com
3315 Final Beta for 1.x boxes SmartXX Team is proud to announce:
The Final Beta for 1.x boxes.
Beta Log for 3315 - Same things as 3313
Fixes: - EEprom Section fixed, works now flawlessly - PAL / NTSC works - Video modes now support all modes - Fan Confusion Fixed
hamtitampti (Franz) @ http://www.smartxx.com/forum/thread.php?threadid=703
Some nice install pictures
NOTE English:
These are lacquer insulated(coated) copper wires. You find them in every magnetic or similar coil. It is best to ask a TV Repair or other electronic repair shop, they have these wires. DO NOT USE NORMAL BARE COPPER WIRE.
NOTE German:
Das sind L�tlackdr�hte. Keine Blanken Kupferdr�hte
Beim Conrad zb. gibts sowas. Artikel nummer: 607568-14 , Drahtst�rke 0.2mm
AUF KEINEN FALL BLANKE DRAEHTE BENUTZEN = -> SONST Kurzschluss=
Before install:
full size image here: 
In theory:
After install:
full size image here: 
Smartxx leaked m8 bios(beta) ! @ http://evox.xboxhackz.net/nonflash/
Franz, from smartxx, decided to release OUR bios without our acknowledgement.
This bios was being tested, and there are many known bugs in this build.
PLEASE DO NOT USE THIS BIOS.
PLEASE DO NOT DOWNLOAD IT.
THIS BIOS WILL MOST LIKELY KILL YOUR XBOX !!!!!!!!!!!
[[hamtitampti]] i have already a dead box
[[hamtitampti]] i not said it will not boot
[[hamtitampti]] i said we should not do it
[[XXXXX]] but m8 boots 1.0-1.6..
[[hamtitampti]] but it kills the box
YES, you read it. He said that the m8 build he released kills 1.6 xbox's but he has decided
to release it anyway. Franz was not even given the bios to test, and he does/did NOT work on
this bios and just decided to release it as his.
How can a modchip maker do that ? ask them yourself.
While they are answering why they leaked our bios, maybe they can answer questions
about their "Live Detection Prevention with Crypt-Stealth Technology" that we are all
waiting on. And also about MS banning users based on their hard drive.
Mirrored
From this page : (in case they delete it)
------------------------------------------
As evox still not willing to release there ready bios.
Here the M8 bios.
Works on all Xboxes.
Attachment:
m8bios.zip (228 KB, 15 downloads)
------------------------------------------
Notice the illegal link to a Copyrighted binaries...
If it destroys your xbox, please ask the Smartxx team for a new one.
Team Evolutionx.
Bios for 1.6 @ http://www.smartxx.com/forum/thread.php?threadid=703
As evox still not willing to release there ready bios. Here the M8 bios. Works on all Xboxes. Edit .. M8 bios removed As with some speaking now with Team evox, i deleted it. I will give a statement why i released it later.
You can find more posts on the "m8 bios debate" here:
http://www.smartxx.com/forum/thread.php?threadid=755
SmartXX updated Cromwell Xcalibur V @ http://www.smartxx.com/forum/thread.php?threadid=911
SmartXX has updated Cromwell to support Xcalibur Video encoder. Download from [Xbox-linux CVS server]. NOTE: SF CVS still sometimes very confused.
It is still not ready, As I didn't want to work in the new written Video Encoder Libs, as I have no clue how they work. (I am afraid, if I screw it up Oliver or David try to kill me...)
For All developers:
As we not had the time to 100% implement, it is implemented for the Developers /( in comments) , there is sure some additional Work to do. Also note, the I2C routines in drivers/pci/~BootPerformPicChallengeResponseAction.c is compleate changed.
Video codes in xcalibur.h and ~BootVgaInitialization.c
Also give the File a deep look : boot_rom/2bBootStartup.S
#ifndef MCPXREVD5 ...
in there. 2 compile processes and so.
good luck
franz
New HK xbox v1.6?
A friend in Hong Kong informed me that a HK xbox version with Xyclops and without TSOP flash has been released. He will send pictures of the motherboard asap. It will be interesting to see if there is any diff compared with the previously released US xbox v1.6.
ModRobert
A few X3 updates... @ http://www.team-xecuter.com/modules.php?name=News&file=article&sid=55
The first release may not include v1.6 support - the priority right now is to get everything working nicely - be assured that we will be finishing work on the v1.6 either on release or shortly after (a simple bios update - mod hardware will be compatible).
SmartXX Quick Installation Manual for Xbox v1.6 @ http://www.smartxx.com/forum/thread.php?threadid=1061
More and more 1.6 XBoX units arrive in the stores. So its time for the worlds first 1.6 Installation Manual.
Detailed image: 
First working bios for Xbox 1.6 @ http://www.gueux.net
Yoshihiro, our developer, succeeded in making the first bios for Xbox 1.6. It is for the moment only a BFM version. Here is a [video] of this bios. Yoshihiro thanks ~NghtShd for xbtools, paulb for xbflash, Hampti and TEAM Evox for the M8 bios.
Evox M8 BIOS released= @ http://evox.xboxhackz.net/nonflash/=
Due to the latest confusions, leaks etc. we have decided to make an official M8 release.
There are still some unsolved matters, so we will release it in two different versions:
m8.bin:
Is a new BIOS based on the latest 5838 kernel, and has the same features as M7, it will work on XBOX versions (1.0, 1.1, 1.2, 1.3, 1.4, 1.5)
m8_16.bin:
Is also based on the 5838 kernel and has the same features as M7. It will ONLY work on XBOX version 1.6
X2.3B v1.6 Diagram @ http://www.team-xecuter.com/index.php?name=News&file=article&sid=68
Most of our users have bene using the Smartxx or Xenium diagrams to convert their v1.6 boxes. However 3.3v is not required so as promised we made our own to help you out. I think you'll find these are very high quality.
Detailed image: 
Alternate 5v for v1.6 @ http://www.team-xecuter.com/index.php?name=News&file=article&sid=69
Here's a nice spot we found. Outputs a perfect 5v only when the Xbox is powered on, gives 0v when powered off (no standby).
Currently working on v1.5 PSU to v1.6 conversion also - will post instructions as soon as everything is tested.
Avalaunch: Another Alternate D0 (LFRAME) for 1.6 Motherboards
This is an alternative LFRAME (D0) point on the backside of a v1.6 motherboard that's a lot easier to solder then the one on top (a 'via') near the Xyclops chip.
Detailed image: 
Team Xecuter @ http://www.team-xecuter.com/index.php?name=News&file=article&sid=107
v1.6B - New Xbox Causing Lockups ?
It seems there is a new Xbox that is crashing randomly when booting to the dashboard. This box has been labelled as v1.6B (the power/eject cable is brown instead of yellow - however there are many that of Xbox's with the Brown cable that work just fine - except for FlashBIOS booting to a black screen, but still functions correctly for flashing from http, hdd or disc - we found the manufacture date of these was 2004-9-13)
The manufacturing date of the boxes that seem to be affected is 2004-9-16.
The Dashboard version is 5960 and the kernel version is 5838 (kernel seems the same as v1.6)
We are in the process of updating FlashBIOS to support video on v1.6b and will be working on the X3 bios (also a new X2 bios as the Evox M8 just doesnt work at all with this Xbox.)
We would appreciate input from the scene. Please post Manufacture Date, Region of Xbox, Country bought, Dashboard/Kernel versions, Lockup reports/workarounds etc. - Please post in this new dedicated forum:
http://www.team-xecuter.com/index.php?name=Forums&fileviewforum&f=48
Note: The X2.6 and X3 mod hardware is fully functional with these versions. This is a hacked Bios issue.
Team Xecuter @ http://www.team-xecuter.com/index.php?name=News&file=article&sid=109
It seems there is some fool spreading rumours that we are telling lies about v1.6B to cover up issues with alleged faulty Xecuter chips. Well done to the nameless moron who continues her crusade in slandering Xecuter's efforts. Here is some follow up discoveries since we asked for input for the general public.
We have confirmed feedback from a number of people using v1.6B - using X2.6, X3, Xenium, Smartxx, Aladdin and DUOX2 so far. I am sure Xodus and the other makers will confirm this too in the next day or so. All chips had EvoX_M8 v16 flashed (X3 was tested with X3 bios and Evox M8 16) All same results of locking up and freezing at flubber or freezing in games.
All mods work perfect when flashed with MS 5838 Bios (Originals of course) demonstrating that the mod hardware is fine.
So far we have found the "v1.6B" to be very random indeed - results in 3 areas.
1. Xbox Freezes during flubber sequence.
2. Xbox boots fine but freezes during games.
3. Absolutley no problems whatsoever.
We have 6 of these boxes so far in our hands that are confirmed crashing at flubber (6 faulty out of a batch of 20 with the same date - the 14 were perfectly fine as normal). All dates range between 13-09 and 17-09. The strange anomoly is in the process of being investigated.
franz (aka hamtitampti) @ http://www.smartxx.com/forum/thread.php?sid=&postid15794#post15794
To end the controversy from the last few days. Some facts: Team SmartXX knew about a "1.6b"(Improper terminology) for a long time, but nobody wanted to listen. Initially, the Xbox PCB was designed for Samsung and Micron SD-Ram chips. However, MS was mainly using Samsung Memory. When the first 1.6 boxes came, we saw a different RAM pad, which made it possible to change the RAM and use even other vendors. After a quick analysis, I found out, that this was more of a Signal HF termination issue rather than an "anti-Ram upgrade".
After analyzing the 5838 bios, I saw, that the memory timing table had more entries.
What are these entries?
1: to use RAM from different Vendors
2: to use buggier ram
If you have a PC, you can change Ram timings, from Fast, to slow or failsafe.
I personally have had this issue in Cromwell already, when we had "crazy boxes." After searching for weeks I found out, when we took timing dumps from an "optimistic" box.
?
The box has a table with ram timings. During the startup period, Ram is in fail-safe mode and very slow. To get optimum performance, MS makes a small memory diagnostic and then decides which mode they will set the ram to based upon this diagnostic. Strangely, this was only in the beginning of the bios and in another occurrence later in the BIOS this "choice" was not included and they simply used static values.
MS has basically used "high quality" ram so far.
But to lower the costs, MS is now buying everything, even class B and C ram. These parts are outside tolerances. Every production of eg. CPU is the same. If you buy eg. a 2.4 Ghz CPU, it is essentially the same as a 2Ghz CPU. But after the production, you see some CPUs failing at higher rates, so they are reconfigured and sold as a slower CPU.
For example:
Same production
10% = 3.0 Ghz Cpu
50% = 2.5 Ghz Cpu
40% = 2.0 Ghz Cpu
This is why overlocking sometimes works and sometimes doesn't.
The same process applies to RAM. The Startup diagnostic diagnoses the ram, and then looks at which timing is best, and then they dump this information into the chipset. Like a Bios on the PC.
As this wasn't enough on xbox 1.6, MS also changed the layout of the EEProm and the Xcodes during Startup read from the EEprom. The last 0x20 (or 0x30 I not remember for sure) are then read out by the X-codes and the values dumped into the chipset.
These values are very likely to be the "vendor specific" inits for the RAM to put it into failsafe mode. They are created during Xbox Testing (memory testing) at MS Fabrication.
They have 3 main advantages:
- Use any ram they find - Buy cheaper ram (Ram is a very expensive product) - Have optimum performance on the system
Why is this so important? Those of you who know anything about PC architecture can tell you the random bugs that invalid memory timings can cause. If you configure your Ram too fast or outside parameters, your Ram might not store information correctly or loose information. So during operation, and temperature changes, the ram looses information or might not even works correctly from beginning and it leads to sporadic symptoms like: crashs, hangs, boot deny, working/nonworking, freezing after a little while, freezing after a long time, and all kinds of various effects.
If you take a modern PC Ram module, you will find a small SPI/I2C EEprom called the SPD. If the SPD falls off or ceases to function your system still runs but not as stable. Since the Xbox does not have an SPD EEprom they store the information inside Kernel and the central system EEprom. --- The M8 BIOS uses a self written 2bl loader, and I think, and not the full ram timing table. Evox M8 bios, uses the same table(offset 0x1c00) as 5713 bios(and others). But in 5838 this table was dramatically expanded. (surprise=)= So M8 Bios simply used the timing table which they had from history and ignored the possible appearance of lesser, different, cheaper Ram.
This is possible to fix, and I think this will be done very soon. I hope they will, because the Ram settings are completely false and can lead to permanent RAM damage.
"M8 can kill your Xbox ..."
(sorry for english, i have tooth-ace and i already wantet to go home since 2 hours)
franz
Yoshihiro released a modified Beta4 version of the EvoX M8 1.6 BIOS for xbox 1.6 with Hynix RAM circuits. Includes LBA48-06 (big hdd support) and IGR (In Game Reset). Also fix for Evolution-X dashboard temp display but CPU and motherboard values are wrong while HDD temperature is correct. NOTE: This BIOS can be flashed with any xbox 1.6 regardless of memory brand used.
EvolutionX released Evox M8+ BIOS featuring added support for xbox 1.6 with Hynix RAM circuits (aka xbox 1.6B). M8plus.bin is a new BIOS based on the latest 5838 kernel, and has the same features as M7, it will work on XBOX versions (1.0, 1.1, 1.2, 1.3, 1.4, 1.5). M8plus_16.bin is also based on the 5838 kernel and has the same features as M7. It will ONLY work on XBOX version 1.6 and 1.6B. EvolutionX thanks Team Xecuter for bringing attention to this issue and Franz of Team SmartXX for uncovering the problem.
The v1.6b xbox motherboard have RAM circuit labeled Hynix.
