xboxscene.org forums

Author Topic: Flashing 1.4 With Unknown Tsop  (Read 184 times)

zx6r6

  • Archived User
  • Newbie
  • *
  • Posts: 33
Flashing 1.4 With Unknown Tsop
« on: May 18, 2009, 03:18:00 PM »

I bought a 1.4 board that has an upgraded cpu and 128mb ram, the tsop was flashed with an x2 bios. I'm not sure what make the tsop is as the markings are VERY feint but I can see its been removed/replaced at some point. I've bridged the common tsop flash points (ie not sharp)

I'm trying to reflash the tsop but am unable to do so with eurasia or evox. Evox says the Manufacturer ID is 09, Dev ID is 00 and says the chip is a Winbond W49F020T but freezes at the erasing part.

Eurasia says Man. ID is 0xAD, Dev ID 0x40 but says unknown chip.

I've googled a fair bit today but can't find any mention of the eurasia ID's listed. I'm wondering if its some sort of 'generic' tsop chip? or are these just 'your soldering stinks, do it again' errors?

Anyone any suggestions?

Logged

Heimdall

  • Archived User
  • Hero Member
  • *
  • Posts: 3862
Flashing 1.4 With Unknown Tsop
« Reply #1 on: May 18, 2009, 03:57:00 PM »

Confusing. Evox giving you "Manufacturer ID 09, Dev ID 00" usually means the chip isn't writeable (TSOP points not soldered properly). The "Winbond W49F020T" bit is a red herring - an error in evox.ini.

Manufacturer ID 0xad would make the chip a Hynix, BUT I'm not sure if Eurasia swaps the manufacturer ID bytes (Evox does) - and manufacturer ID 0xda would make it a Winbond. Not that it helps much, because I can't find a chip 0x04 or 0x40 for either manufacturer.

Try cleaning and resoldering the TSOP points, then try Evox again - see if it gives you the same IDs.
Logged

zx6r6

  • Archived User
  • Newbie
  • *
  • Posts: 33
Flashing 1.4 With Unknown Tsop
« Reply #2 on: May 18, 2009, 04:23:00 PM »

I've redone the points 3 times today 'just' in case, same codes each time. sad.gif
I'll try some alternative points tomorrow.

Just a thought, would having an x3 fitted (disabled when flashing) cause any issues with id's? I'll unplug tomorrow in case but can't imagine it would.
Logged

Heimdall

  • Archived User
  • Hero Member
  • *
  • Posts: 3862
Flashing 1.4 With Unknown Tsop
« Reply #3 on: May 18, 2009, 04:35:00 PM »

Having the X3 connected shouldn't make a difference, but disconnecting it wouldn't hurt.

Are there any readable markings on the chip? Even fragments might help narrow down the search for a flash ID.
Logged

ldotsfan

  • Archived User
  • Hero Member
  • *
  • Posts: 2072
Flashing 1.4 With Unknown Tsop
« Reply #4 on: May 18, 2009, 06:36:00 PM »

Why do you want to flash the tsop ? For better LBA48 support for hdd? You could use a BFM bios and load it through PBL. That way you don't have to mess with the unknown tsop.
Logged

zx6r6

  • Archived User
  • Newbie
  • *
  • Posts: 33
Flashing 1.4 With Unknown Tsop
« Reply #5 on: May 23, 2009, 04:36:00 AM »

Finally got a chance to have another lookie at this. Checked for continuity between an alternative set of bridging points and they both are ok so that rules out the soldering.

Disconnecting the X3 makes no odds, but that was no suprise.

Looked closer at the tsop chip and noticed it had a thin layer of a strange sooty like substance over it, after cleaning up some of the writing was just about readable. I think its an HY(possibly V)29F040T-12.

Time for a bit of googling me thinks.


@ldotsfan
I need to flash with MS retail bios. I'm looking to consolidate 2 boxes into 1, this one (1ghz 128mb), the other with 1tb, x3+ control panel, xbox live safe etc etc.


Logged

ldotsfan

  • Archived User
  • Hero Member
  • *
  • Posts: 2072
Flashing 1.4 With Unknown Tsop
« Reply #6 on: May 23, 2009, 09:56:00 AM »

QUOTE(zx6r6 @ May 23 2009, 05:28 PM) View Post

I think its an HY(possibly V)29F040T-12.

Reference from here

Flash = 0xada4,"Hynix HY29F040A",0x80000


Logged

zx6r6

  • Archived User
  • Newbie
  • *
  • Posts: 33
Flashing 1.4 With Unknown Tsop
« Reply #7 on: May 23, 2009, 10:49:00 AM »

Does it not matter that mine ends in a T not an A?
In my googling today (assuming I understand them correctly!) the spec sheets said its a 512k (4 mbit) chip not the usual 256k for a 1.4.
Logged

ldotsfan

  • Archived User
  • Hero Member
  • *
  • Posts: 2072
Flashing 1.4 With Unknown Tsop
« Reply #8 on: May 23, 2009, 07:38:00 PM »

QUOTE(zx6r6 @ May 23 2009, 11:41 PM) View Post

Does it not matter that mine ends in a T not an A?
In my googling today (assuming I understand them correctly!) the spec sheets said its a 512k (4 mbit) chip not the usual 256k for a 1.4.

Actually it matters - but I don't know how the resizing works out for ms retails bios for a 512k bank. Wait for somebody more experienced to shed some light on this.
Logged

lordvader129

  • Archived User
  • Hero Member
  • *
  • Posts: 5860
Flashing 1.4 With Unknown Tsop
« Reply #9 on: May 24, 2009, 10:34:00 AM »

QUOTE(ldotsfan @ May 23 2009, 05:30 PM) View Post

Actually it matters - but I don't know how the resizing works out for ms retails bios for a 512k bank. Wait for somebody more experienced to shed some light on this.

it would just write the 256k bios twice (just like the 1.0/1.1 bios is 256k written 4 times)

however if the chip actually is 256k and evox thinks its 512, im not sure how it will react to that
Logged

zx6r6

  • Archived User
  • Newbie
  • *
  • Posts: 33
Flashing 1.4 With Unknown Tsop
« Reply #10 on: May 30, 2009, 03:32:00 PM »

Couldn't find any more info that would give me a definate yes or no so figured I'd do a 'sh*t or bust". I added an entry to the raincoat config, resized the ms retail bios to 512k, then tried flashing. What do ya know, it actually worked! smile.gif So the tsop on my xbox has been changed and is a 512k chip.

Looks like I will be able to finish my super xbox after all. wahoo

Thanks to everyone for the help and advice.
Logged