Jump to content
OGXbox.com

Prehistoricman

Members
  • Posts

    110
  • Joined

  • Last visited

  • Days Won

    9

Everything posted by Prehistoricman

  1. Ah, but if you want the modchip to always be selected without a D0/LFRAME wire, then you should only cut the trace. Adding a resistor like I did restores the original function where a D0/LFRAME wire is required.
  2. I cut it in a specific place close to the Xyclops and put a 470 ohm resistor between the two cut ends. This lets the Xbox work as normal with and without the modchip and reduces the current greatly. I always use a blade. You can do two cuts at slightly different angles to get a bigger segment out. Yeah the 1.6 uses fewer caps, fewer chips, a more modern version of the GPU, and a less capable PSU (IIRC) all to reduce the cost.
  3. Oh, it's actually worse. Around 71mA on my box So that draws 0.071 * 3.3 = 0.23W which is enough to burn small components. The LFRAME grounding trick was another Microsoft oversight I suppose. The BIOS is in the Xyclops because it's convenient and cheap. The 1.6 is basically a cost-down Xbox and this saves them from including a flash chip like the previous models.
  4. Do you mean how much current does it take to drive LFRAME after it's cut? Grounding isn't required after it's cut. Or how much current it takes when grounded and uncut? It's about the 30mA mark from memory. No, the Xyclops is the SMC or system management controller and it contains the 1.6 BIOS. The video encoder isn't hooked up to the LPC at all so it can't possibly be used as BIOS storage.
  5. This was not the experience that I had with my non-CE X3. I measured it and it was driving LFRAME low constantly, taking 2 digit milliamps. 35uA is nothing - even the most sensitive circuits will not be damaged by such a low current. I think I saw around 30mA which is short circuit output current for that kind of IO driver. It is only 0.1 watts, but it will accelerate the lifetime of that driver in the MCPX. That led me to cut LFRAME on my 1.6 and put a resistor on it. @Bowlsnapper LFRAME is a signal on the LPC bus, the bus which the modchips use to send the BIOS data over. Holding it low on a 1.6 stops the Xyclops chip from using the bus, so the modchip can take over instead. The REAL D0 signal on a 1.6 board is unused. D0 means data bit 0, and it's part of a parallel bus up to D7. This bus is used for flash on 1.0 - 1.4 but that flash doesn't exist on 1.6. Likewise, LFRAME is unused on 1.0 - 1.4. The confusion starts when modchip instructions started calling LFRAME D0 because the user needs to wire up the modchip's D0 pin to LFRAME on 1.6. So they make a picture showing the LFRAME trace and mark it as D0.
  6. It makes sense that you could use 4 chips with the double capacity to get 128MB on 1.6. Doesn't really make sense if those bigger chips are expensive though.
  7. I have a original Samsung drive that is useless due to a dead diode. I looked several times for information online about diode replacement but struggled to find anything, especially for PC drives. The typical approach is just to replace the whole laser assembly. I'm sure the laser can be replaced with some knowledge and effort.
  8. I checked on my board and L2F1 doesn't connect to the C1F2 cap. You need to remove that connection. If that doesn't fix it, can you post pictures of your soldering?
  9. Bro... I'm talking to the OP!
  10. Test the voltage on a battery that you already know the voltage of (like a fresh PP3) to make sure your meter isn't lying to you.
  11. Holy shit what a disaster! Looks like some vias are destroyed too, so will require wires through/around the board. Cheap solder braid doesn't contain flux so it's basically useless until you add flux. You can't have too much flux.
  12. R7D10 on v1.4 is for the output enable signal on the flash. That is critical. R7R3 is a pull-up for write-enable to keep writing disabled. By shorting the link under it, you connect the MCPX to the flash to allow for write-enable to be driven dynamically and thus allow re-flashing. I think it's likely that it's required, or else the signal will be left floating and read operations may be interpreted as writes. You can place any value resistor there between 1k and 22k - it's just a digital signal pullup.
  13. This is the kernel API call for rebooting: https://xboxdevwiki.net/Kernel/HalReturnToFirmware Here's an MS implementation of changing XBE: https://github.com/xerohour/xbox_leak_may_2020/blob/master/xbox_leak_may_2020/xbox trunk/xbox/private/ntos/xapi/k32/launch.c#L183 First, it takes the XBE info, like its path and name, and writes that to a special place in RAM. Then, it calls the HAL function to quick reboot.
  14. It's theoretically possible for that to be true, but it's not how MS implemented the kernel. When the kernel loads a new xbe, it basically reboots itself. Even the debug monitor command to load an XBE is called "magicboot". It's not a full reboot, so it doesn't read the entire kernel out. I tested this and it only reads 1668 bytes from flash when you launch a new XBE. My guess is that it's reading xcodes and then a small bit of code to go back to the kernel which is still in RAM.
  15. You can swap the CPLD to find out if it's the PCB or the CPLD that's faulty.
  16. You can try booting with a real X3 into config live and then hotswap to r3dux and see if you can change any settings. Since the BIOS data can be read okay, I'm putting my money on the issue being SMBus comms. Xblast has a hacky way to detect X3, so this doesn't prove that the SMBus is working fine. Did you program anything into the EEPROM? That's a step on the installation page that you didn't mention.
  17. You can ask the seller, modzvilleusa, to help you with a replacement or something. The guy that runs it is nice.
  18. Are you measuring continuity or resistance while the Xbox is powered? It should be completely unpowered when performing resistance checks, unlike voltage tests. Most meters beep in continuity mode. You can check this by touching the probes together.
  19. It can be tricky. You can set the board vertically and probe on each side. Or use a temporary wire to whatever you want to probe. Yeah I misread your table from the start of the thread. 0V when connected is not good because LCLK should be running at all times. Can you check continuity to ground vs pin 1 with the modchip connected?
  20. Your LCLK and LRESET seem dead. In your previous results, LCLK on pin 1 was 1.7V which looks good. This indicates that there is a disconnect between the Aladdin and the LPC header. Check continuity from pin 1 to that corner hole that read 0.02V. Also check continuity of LRESET (pin 5) to the hole that reads 0.21V.
  21. That diode near it has also gotten toasty. It's on the primary side, so I'd guess that it's a PSU fault rather than too much load.
  22. When this thread first came up, I gave up on reading the post. Not a single item of punctuation! It's like listening to my drug addict neighbour.

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.