jasper nand identification

chkennedy

Noob Account
Feb 2, 2012
7
0
I've just installed a CR w/ QSB into a jasper phat. The nand is a hynix hy27us08281a. I have not programmed the glitcher or r/w the nand. From what I've read, the way to identify which nand is by booting into the dash and checking the details of the memory module. Is it safe/possible to boot into the dash under the above conditions?...or better yet, can anyone tell me based on the information on the chip? Thank you in advance!
 
  • Like
Reactions: Dragon Slair

bruno_rv

VIP Member
Jun 8, 2010
181
0
Croatia
Hynix are mostly 16mb. But best way is to read nand with nand-x and nandpro and see what config it has:

01198010 - Xenon, Zephyr, Opus, Falcon
00023010 - Jasper 16mb ,Trinity (valhalla) 16MB
008A3020 - Jasper 256mb
00AA3020 - Jasper 512mb
 
  • Like
Reactions: chkennedy

Icy-Tank

Senior Member
Oct 22, 2010
168
0
Agreed with Bruno.

Most of the consoles I've ever worked on are Hynix (All for 16MB)

Your big block consoles I do believe are all Samsung.

Again, this isn't something that I routinely document, but just from memory, I can only recall Samsun being the big block NAND chips onboard the motherboard.

Hynix may very well make a 64MB NAND chip, but I am not sure if Microsoft contracted them for purchase of if they stuck with Samsung as their supplier during the Jasper BB era.

But if you are really that curious, just boot to the dashboard, go to System Settings > Memory > _______

If it has onboard memory, you've got a Big Block, if not, you've got a small block. The good thing is, there's not gray area with this, either there is onboard memory or there isn't.

If it does have onboard memory, dump your NAND and see what your config is.. (Or just check in System Settings > Memory ... and see what memory it has)
 
  • Like
Reactions: chkennedy

socalbill

VIP Member
Nov 30, 2011
356
0
Valhalla
the easiest way is to use XNandhealer and hit the detect button before dumping.

I have had 256 and 512 jaspers whose MUs did not show up in System Settings...I am sure that has been the case with some posters here who just dumped 16mb instead of 64 and wondered why their jasper wouldn't glitch.
 

Icy-Tank

Senior Member
Oct 22, 2010
168
0
Really? That's bizarre. Generally if there is a MU onboard, then it should register (I would think)

Then again, like I said, I'll never put anything past the Xbox 360 at this point. I've seen some REALLY bizarre things come from those little possessed boxes.
 
  • Like
Reactions: chkennedy

chkennedy

Noob Account
Feb 2, 2012
7
0
It was indeed the 16mb nand. The install went without a hitch. I'm looking forward to running some homebrew, soon. Thanks again for the responses to my noob questions...and thanks to Team Xecuter for their development and thorough testing.
 

Dragon Slair

Full Member
Aug 31, 2011
39
0
I would Like to say thanks to chkennedy for starting a help thread that also answered some questions I had.
 

chkennedy

Noob Account
Feb 2, 2012
7
0
Thank you for the road-map. I read it, along with several other guides. Somehow I overlooked this line: "nandpro usb: -r1 test." It wasn't an issue of choosing to read it or not to read it. Again, thank you. It was helpful.