Jump to content
OGXbox.com

Prehistoricman

Members
  • Posts

    110
  • Joined

  • Last visited

  • Days Won

    9

Posts posted by Prehistoricman

  1. 49 minutes ago, Bowlsnapper said:

    That's good advice! I actually have a 470 ohm resistor so I'll go ahead and use it for that... I'd rather have the chip be wireless if I can get away with it instead of hooking up D0.

    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. 5 hours ago, SakisTheDrifter said:

    Cut the Lframe and add a switch between the 2 cuted terminals. That way you can disable\enable it as you wish

    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.

    1 hour ago, Bowlsnapper said:

    Oh my FUCK... Okay. Thank you. I'll get it dealt with... If D0 on the chip is fuxored, what's the best way to cut a trace? I've done it with a blade, but I never been sure that it's been cut since the slice is so narrow... 

    I didn't know they were trying to save with that hardware revision... They fucked off the LPC though, so I KNOW that was intentional. Lol

    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.

    • Thanks 1
  3. Oh, it's actually worse. Around 71mA on my box

    image.thumb.png.06cabc326d185fec87852a3fd4ec0a5f.png

    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. 1 hour ago, Bowlsnapper said:

    Thank you for basically erasing my confusion about this. Right on. The only other thing I'm wondering about this is: should I go ahead and use the chip D0 or leave Lframe grounded to the pad I have it to? What is typically the current that a 1.6 drives on that circuit? Micro, or milli?

    Also, I've heard the bios is stored on the video encoder chip on a 1.6. Is that true? 

    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.

    • Thanks 1
  5. On 6/15/2023 at 9:46 AM, SS_Dave said:

    I tested the current of the D0 on 1.0-1.4 and it's in the vicinity of single digit micro amps (from memory 7 or 8 micro amps) and a 1.6 is in the  high 2  digit micro amps ( around 35 micro amps from memory) I know it doesn't sound a lot but why stress the components if it's not needed

    Chips like the X3, Open Xenium, Xenium only ground the D0 just long enough to make the Xbox load from the LPC and the rest of the time it's floating.

    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.

    • Like 1
    • Thanks 1
  6. 16 hours ago, Dtomcat18 said:

    Sorry.  Late….  Found this that refers to what I saw… not sure where I seen it though

     

    IMG_6690.jpeg

    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. On 3/30/2023 at 4:58 PM, Mattia99 said:

    The same guy said that in order to repair the traces I had to connect the positives of C1F2 and C1G10 toghether an then to one of the legs of the coil above (L2F1); the negative of C1G10 to ground an finally the positive of C6G3 to the positive of the cap next to it (C6G2).

    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?

  8. 19 hours ago, SS_Dave said:

    It's not a flat battery and the meter is not lying!!

    This meter is around $1100Aud

    PXL-20230331-011102899.jpg

     

    And the Oscilloscope still fetches $600 to 800Usd

    PXL-20230331-010858297.jpg

     

     

    Cheers

    SS Dave


    Soft modding is like masturbating, It gets the job done but it's nothing like the real thing.
     

    Bro... I'm talking to the OP!

  9. 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.

    • Like 2
  10. 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.

    • Like 1
  11. On 3/3/2023 at 3:31 AM, KaosEngineer said:

    I've not tested this procedure.  But, I always thought that once the BIOS was loaded from the modchip's flash, the chip could be removed without causing a problem.  The kernel gets loaded into RAM and runs from there. No need for the modchip anymore until the console is rebooted/power cycled which loads the BIOS/kernel again across the LPC bus. 

    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.

    • Like 1
    • Thanks 1
  12. 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.

  13. 28 minutes ago, Hispano said:

    Dead in motherboard? 😳 i got 1.7V on pin 1 measuring the voltage without my chip connected but when i connected it i always got +-0V

    How can i check continuity with the modchip connected? I checked it with my motherboard disconnected against the points in the bottom from barnito's guide

    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?

  14. 4 hours ago, Hispano said:

    Hi Dave! Do you have any idea what might be wrong? All voltages seems right except 3 points in the chip. Here are my voltages:

    IMG_20230217_203545.jpg.364fe20524f2e4d04d6fdefa6a943c0b.jpg

    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.

  15. 16 hours ago, Bowlsnapper said:

    Dang man. I don't think there was a single period in that entire post. I was sitting here for 3 minutes trying to decipher what you said. HAHA. Gotta watch your caffeine intake, friend... But, Cornholio does not exist without caffiene, so , you know.

    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.

    • Haha 1

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.