Jump to content
OGXbox.com

Prehistoricman

Members
  • Posts

    110
  • Joined

  • Last visited

  • Days Won

    9

Posts posted by Prehistoricman

  1. I have been looking and thinking about this topic @sweetdarkdestiny

    I basically repeated what others have done with PC drives and got some random LG drive to load DVDs and game copies but not original discs. I took a brief look at the original and hacked drive firmware images and decided to save myself the pain of looking at it further.

    The problem for me, someone who doesn't have experience with drive firmware, is that the system is totally unknown and hard to probe. The main DVD drive chip from MediaTek doesn't have public documentation. I don't think we've had any source code leaks related to the Xbox DVD drives so that's a dead end too. It's possible to reverse-engineer almost anything but the effort that takes on this level could be hundreds of hours depending on the hacker's experience.

    A close example to me is the TMS57070, a digital audio processor chip from the 90s that was also 100% undocumented. I spent around 400 hours investigating and got a very good understanding of it over a span of 3 or 4 years https://github.com/Prehistoricman/TMS57070. If I could be sufficiently motivated, then I suppose I could do the same for the DVD drives.

    There are still people in the scene with a decent base knowledge of the drives, so not all hope is lost. But screaming into the void YEAH LET'S DO THIS won't get the hard work done. Sorry to be a pessimist :(

    • Like 1
  2. That kind of boot loop usually happens when booting Xblast with some RAM soldering mistake. It occurs because the xblast bootloader fails to load the main xblast image correctly. The bootloader has already passed the SMC check (so it will not FRAG) but due to the check fail, xblast requests a reboot.

    • Like 1
  3. 7 hours ago, sweetdarkdestiny said:

    Hot glue on a, more or less, hot surfice? You could use a old chewing gum which would give it more strength. If glue, then 2k epoxy or better a cyanoacrylate based glue.

    I made that mistake when I was a kid. I hot glued a fan to a heatsink in my PC and a few weeks later it fell off 😅

    • Haha 1
  4. 1 hour ago, prtscn said:

    Probably was plugged in the wrong way, this is what i did, and actel chip got REKT. My chip heats up as well.

    Possible solution would be to replace actel chip, since you have working one. I bet there is a way to dump data from working chip if needed, not sure.

    If the CPLD is replaced, the new one would need programming with the open-source R3DUX code at https://github.com/ChimericSystems/R3DUX

    The original Xecuter code isn't available for extraction from the device, nor available online.

    • Like 1
  5. Every multimeter model will have a different threshold for continuity and a different current/voltage to probe the resistance. Getting the beep doesn't mean it's a short circuit.

    Use resistance mode and see if the value is near SS_Dave's result.

  6. I believe you two are talking about different things. Hastings is talking about the LCD contrast (or backlight?) and the control pot on the X3 chip. Bowlsnapper is talking about the X3 switches and status LEDs which are unaffected by the potentiometer.

    I also have a stability issue with the X3 controls, but it's with the small black one that you stick to the front of a normal panel, not the whole custom front panel. I believe it's the wires breaking after too many stresses and bends. Mine has flickery or dim LEDs very often but rarely boots from the wrong bank.

    • Like 1
  7. 34 minutes ago, Bowlsnapper said:

    Testing bioses seems like exactly the kind of thing you would NOT want to pull the chip out of the box for. YIKES. You are a glutton for torture. :) 

    I once did a bad flash to the TSOP. So I desoldered it, wrote an arduino programmer and soldered it back in. Then I fucked up the flash again to see what went wrong the first time :)

    • Haha 2
  8. 24 minutes ago, Bowlsnapper said:

    Please forgive my stupidity, but could you clarify that a bit? I'm not as knowledgeable as I would like to be. If RAM speed becomes an issue when slowing down? I actually wasn't aware that you could control memory and CPU speeds independently from one another. Is this an option in XBOverclock? By divider, do you mean multiplier? JESUS I'm retarded.

    dust08 has it right: if RAM speed becomes an issue when increasing the FSB too much, you can reduce the memory clock independently.

    XBOverclock can be modified to do this. Go to its main.c file and after line 93 put bios_data[i+6] = 0x33; to reduce the memory clock by 33%.

Board Life Status


Board startup date: April 23, 2017 12:45:48
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.