Jump to content


Photo

Opened A Xbox To Find A Hitachi-lg Dvdrom


  • Please log in to reply
913 replies to this topic

#631 skyhi

skyhi

    X-S Enthusiast

  • Members
  • 27 posts

Posted 22 April 2005 - 05:49 PM

QUOTE(wenid @ Apr 12 2005, 12:45 PM)
If you're thinking you can just overwrite the mismatched block in the .exe we have with the correct block from the "real" firmware, I'm afraid you're out of luck. I've already tried that. I assume the .exe runs some sort of checksum on the ROM image.

View Post



It's been a long time since I played around with Hex editing but here's what I found:
There is some sort of cheksum - two of them in fact 16 bits wide.
The first one is at address 20A58 and the second one is at 20A5A

Once the mismatched block is over written with the correct code you must FIRST generate a Checksum-16 from addresses 20A98 through 6267F which will give you 'CF68'. This needs to be entered into addresses 20A5A and 20A5B.

Then another Checksum-16 needs to be generated from addresses 20A5A through 6267F which will give 'DAA7'. This needs to be entered into addresses 20A58 and 20A59

Happy editting! beerchug.gif

Now onto better things - 16X's tongue.gif

Edited by skyhi, 22 April 2005 - 05:54 PM.


#632 sness54

sness54

    X-S Enthusiast

  • Members
  • 5 posts

Posted 23 April 2005 - 01:53 AM

Thank you, skyhi, with your information, I have just reflash my LG with the original firmware.

Regards.

#633 truBB

truBB

    X-S Member

  • Members
  • Pip
  • 103 posts
  • Location:Long Beach / Lakewood, California
  • Interests:modding!
  • Xbox Version:v1.6
  • 360 version:v3.0 (falcon)

Posted 23 April 2005 - 06:10 AM

@skyhi,

the replaced code is cut from 4f80 to 4f93 from file: HitachiLG8050.bin
CODE
4f80 to 4f93
50 64 60 E7 64 E1 A6 67 7E 64 00 74 7E 66 20 70 7E 66 00 70

Right?
Or did you replace all the filler, because I didn't get the same crc16. I got: C30D.

#634 maximilian0017

maximilian0017

    X-S Senior Member

  • Members
  • PipPip
  • 161 posts

Posted 23 April 2005 - 07:59 AM

QUOTE(truBB @ Apr 23 2005, 05:16 AM)
@skyhi,

the replaced code is cut from 4f80 to 4f93 from file: HitachiLG8050.bin
CODE
4f80 to 4f93
50 64 60 E7 64 E1 A6 67 7E 64 00 74 7E 66 20 70 7E 66 00 70

Right?
Or did you replace all the filler, because I didn't get the same crc16. I got: C30D.

View Post



You have to replace it including the filler, feom 4040h to 6040h

Works like a charm!!

Going to solder a little bit later tonight biggrin.gif

#635 Jetset Willy

Jetset Willy

    X-S Enthusiast

  • Members
  • 27 posts

Posted 23 April 2005 - 02:03 PM

Forgive a less gifted one, would it be possible to give a list of which code need to be entered at which address, the above kinda went over my head...
How about the cdr issue, is the final word that it won´t read cdr´s?

#636 TKramka

TKramka

    X-S Genius

  • Members
  • PipPipPipPip
  • 830 posts
  • Location:CT
  • Interests:Computer Technology, Xbox Hardware and Modding
  • Xbox Version:v1.1
  • 360 version:none

Posted 23 April 2005 - 02:42 PM

Well, if everyone keeps up with the firmware hacking, then it might just read cdr's and go at 16x

#637 skyhi

skyhi

    X-S Enthusiast

  • Members
  • 27 posts

Posted 23 April 2005 - 03:29 PM

Yes - I did replace all the code in the flasher with the code that is in the HitachiLG8050.bin file. I used Hex Workshop 3.1 to do the editting and generating of the checksum. Glad to be of assistance as so many of you have already been! beerchug.gif

#638 TKramka

TKramka

    X-S Genius

  • Members
  • PipPipPipPip
  • 830 posts
  • Location:CT
  • Interests:Computer Technology, Xbox Hardware and Modding
  • Xbox Version:v1.1
  • 360 version:none

Posted 23 April 2005 - 03:34 PM

Now if we could only figure out what blocks CDR reading, To the Hex Editor!

#639 skyhi

skyhi

    X-S Enthusiast

  • Members
  • 27 posts

Posted 23 April 2005 - 04:00 PM

I have compared the code of the 8163B to the 8050L with the Hex Workshop and have found about 100 or so differences between them. I've actually saved all the differences into a folder and just need time (and help?) wink.gif to go through them.

My next step was going to be trying to dissassemble the differences to see if something jumps out - it's been a while since I dug this deep into code - about 18 years!

I've found a dissassembler here: http://www.8052.com/

Edited by skyhi, 23 April 2005 - 04:08 PM.


#640 Tiros

Tiros

    X-S Member

  • Members
  • Pip
  • 102 posts

Posted 23 April 2005 - 04:05 PM

Sorry for the lack of info, been away past week.
Yes, I patched the DLD with checksum patch, similar to SkiHi, but I used the HP dos flasher.
DO NOT USE THE XBINS FLASHER IT IS NO GOOD!!

Even if you patch the DLD contained in the windows EXE, the drive will only partially flash and you will not get the "good" signals on the controller outputs. The drive WILL report 8050 after the win flash, but don't be fooled.

After a successful flash the drive activity LED becomes inverted, "ready" and other signals become active.

There are still a couple of issues with regard to RF/Servo controller. I recommend cutting 2 traces and adding jumper wire. I will try to get pics, @truebb you may want to compare pin 49 and 50 8050/8163 to see what I mean.

I have a small program that creates a DLD, using the 8050.bin file as input. This board does not seem to allow attachments.



#641 Tiros

Tiros

    X-S Member

  • Members
  • Pip
  • 102 posts

Posted 23 April 2005 - 04:34 PM

CDR doesn't work after the flash either.
I was hoping it was the RF/Servo circuit difference, but it's starting to look more and more like firmware related. The drive doesn't even spin up disk if it is CDR. The laser pops on briefly as if it's "testing" the disk first. Than it just sits there.

Based on what has been going on here so far, I wouldn't hold my breath waiting for someone to patch the firmware for this problem.

AGAIN, DON'T USE THE WINDOWS FLASHER!
EVEN WITH THE DLD PATCH IT DOES NOT WORK!



#642 Tiros

Tiros

    X-S Member

  • Members
  • Pip
  • 102 posts

Posted 23 April 2005 - 04:35 PM

Board error double posted...


@SkyHi
BTW it's not an 8052....that would be too easy.

Edited by Tiros, 23 April 2005 - 04:42 PM.


#643 maximilian0017

maximilian0017

    X-S Senior Member

  • Members
  • PipPip
  • 161 posts

Posted 24 April 2005 - 02:01 AM

QUOTE(truBB @ Apr 16 2005, 06:19 PM)
]2.[/color][/b] Fully working 8163B. Tiros & wenid both have fully working drives, using exact copies of the firmware or at least firmwares binaries that are the same.
The points used are the same from 8050L which are:

[code=auto:0]
8163B                              End of Cable      Description
Eject  ============================= pin4            Eject
TP126  ====1k resistor ============= pin6            Ready (uC pin50)
TP055  ====1k resistor ============= pin7            Tray_in (uC pin65)
TP128  ====1k resistor ============= pin5            Tray_out (uC pin49)


I did the following to get to the same point as Wenid and Tiros

1. Used this wiring with 1k resistors on all wires(even eject)
2. Modded the windows flasher as per Skyhi's earlyer post
3. Extracted the dld file from the modified windows flasher(20a58-62680)(269352 bytes in explorer/properties)
4. Put it on the hp dosdisk i made(see earlyer post)overwriting the standard dld file
5. Flashed

After throwing this together i tested for a while and it seems to work 100%, ofcourse without cd/16x support(but the reading is quite fast anyway)

Maby this is interesting to the people who don't want to read origionals and want cd/16x support:
Tiros mentioned the led in front of the drive, i was looking at the same thing earlyer, it doesn't go out after the drive spins down, so that could be a much better alternate ready signal without problems with spindown.
After the mod above it came apparent to me that the origional and the fully modded 8163b do spindown, but they keep the ready signal high.
This hasn't been tested yet, but maby someone wants to take a look at it.

#644 maximilian0017

maximilian0017

    X-S Senior Member

  • Members
  • PipPip
  • 161 posts

Posted 24 April 2005 - 02:06 AM

If i understand correctly the processor is a Panasonic AN32 series, there are special tools for programming and debugging.
There is no mention of any code compliance or compability, so this is going to be a tough one to take apart.
Don't really think that hexedit is going to help here....

#645 skyhi

skyhi

    X-S Enthusiast

  • Members
  • 27 posts

Posted 24 April 2005 - 03:53 AM

Perhaps what could be done is to patch in code from the 8163B and watch for changes - time consuming but should show something.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users