[liranantebi]

Originally Posted by DebugBrain What kind of external power supply are you using? The external power supply must have at least 1800mA of power for recognize correctly the nands

You need that much current only if you are powering the NAND while it is connected to the PS3. the reason for this is that while you power the NANDs - they are connected to other components in the PS3 and so require more current.

If the NAND is stand-alone - e.g. connected via ZIF - less current is needed. I was able to work w/ the 3.3v regulator using the USB power supply (~100mA as per the specs)

Edit: it's also an option - to use external power supply for stand-alone configuration. just make sure that there are no spikes. anyhows - two different power supplies can create unpredictable behavior.

[DebugBrain]

Right, sorry, I had not read it right, I had not considered this aspect of the question, I have never used a ZIF, I always read the nand directly from the motherboard,
I hope this info might help at least to people like me have to do it all without a ZIF

[zeruel85]

Now I had able to dump perfectly both the nands, using ProgSkeet 1.2 and not an external power supply ( @DebugBrain , usually I use a ATX power supply), but 3V3 directly from the ProgSkeet, and it works!

I've just sent an email for Dump Checking Thread, I think the dumps are good.

If I have enough time, I'll desoldered again the ProgSkeet e retry with the Teensy.

Important: I'm not working with the mobo; I've desolderes both the nands from the mobo and install them in a zif socket tsop48.

[liranantebi]

Originally Posted by zeruel85 Now I had able to dump perfectly both the nands, using ProgSkeet 1.2 and not an external power supply ( @DebugBrain , usually I use a ATX power supply), but 3V3 directly from the ProgSkeet, and it works! I've just sent an email for Dump Checking Thread, I think the dumps are good. If I have enough time, I'll desoldered again the ProgSkeet e retry with the Teensy. Important: I'm not working with the mobo; I've desolderes both the nands from the mobo and install them in a zif socket tsop48.

I'm happy that you were finally able to dump your NANDs.. it's always fun to have a good dump
I will be happy if in the future you can try it again and update whether it worked with Teensy as well.

[DebugBrain]

Originally Posted by zeruel85 Now I had able to dump perfectly both the nands, using ProgSkeet 1.2 and not an external power supply ( @DebugBrain , usually I use a ATX power supply), but 3V3 directly from the ProgSkeet, and it works! I've just sent an email for Dump Checking Thread, I think the dumps are good. If I have enough time, I'll desoldered again the ProgSkeet e retry with the Teensy. Important: I'm not working with the mobo; I've desolderes both the nands from the mobo and install them in a zif socket tsop48.

When I was doing experiments on my 60Gb, to dump the nands there was only Infectus (which I still have), even with Infectus can powering the nands with 3.3 v, but not using a ZIF socket on the motherboard 3 , 3v provided by infectus not enough and you may have problems, that's why I used an external power supply, I did not have an ATX available at that time.
I sacrificed ps3 for make many experiments, until he gave me the YLOD , now I keep it for spare parts.
Apart from all... 60 Gb models, are very delicate, so since then I decided not to modified those of others, buy nand clips or a ZIF, cost a lot at that time because in my area are not for sale, probably using a ZIF can powering properly the nand even with Infectus, I could not do this test but according to your words I'm sure it should work
Since then I use a Teensy2 + + because I happen always ps3 slim, sin ... if I had had my 60 Gb I can try the teensy for the nands

[baileyscream]

Originally Posted by raiden[MENTION=215751 Consoleopen;533993]Giving my 2 cents to this amazing project... I don't like to solder everytime so many wires, i built with guerriero a zif socket shield (adding pictures later). There was something odd reading this thread, everyone has tristate High (or True) on norway.py output, in fact my dumps where fine on Spansion P but the device was unknown, Samsung P was instead recognized correctly... So i looked up to F7 (tristate) on teensy, it wasn't connected anywhere, i supposed giving 3,3 volt to it could change the identification problem (couldn't write with unknown spansion but could write with recognized samsung, odd!), after that connection spansion was recognized but not entirely (s29gl128 text wasn't there, ) and dumping wasn't valid anymore (random bits)... Again something fishy, i supposed tristate introduced some kind of noise to 3,3 volt line (generated by regulator 1086-33), added 100 nF capacitor between 3.3 volt and ground, magically s29gl128 appeared in the identification output and dumps were correct once again. Ended that way ? No Happy and sure to got it right i started writing, it fails with every single command (write, writeword, writewordubm), tried erasechip also, i'm investigating now, error occurs after a certain percentage of completion, i presume it's related to insufficient current to the nor, added 10k resistor between F7 and 3,3 volt line, gonna test later and let you know... While waiting i'm writing with progsh1t 1.0, 10 hour to wait for spansion + zif shield, sh1tty chip... ok, i can confirm something... zif + norway, if correctly wired, dumps fine even without identification itself (without tristate wired), will investigate nor writing problem next spansion on my hands. please post schematic for nandway, testing zif socket here if posted

i can confirm there is a problem with TEENSY++ and Spansion P.
I have allways had ppl wanting a different flasher attached everytime I had this chip on a board so I never noticed before.
but I have been at 1 today and it does dump and verify just fine but as Norway.py wont detect the nor it wont flash
@judges have you come across this?
I will try your prev versions of Norway on your git and report back tomorrow if they detect or not.

************* [ - Post Merged - ] *************
btw raiden (at) consoleopen
you need to take the (at) out of your name as it is impossible to quote you with that in your name

[judges]

Originally Posted by baileyscream i can confirm there is a problem with TEENSY++ and Spansion P. I have allways had ppl wanting a different flasher attached everytime I had this chip on a board so I never noticed before. but I have been at 1 today and it does dump and verify just fine but as Norway.py wont detect the nor it wont flash @judges have you come across this? I will try your prev versions of Norway on your git and report back tomorrow if they detect or not.

That's not related to Spansion P at all (I have one). Actually all kinds of NORs can be written just fine. It's related to the mobo. If all "standard" methods of flashing fail (teensy powered by usb/voltage reg, teensy powered by console/without voltage reg, CrackMyDay's method) then you might have to connect an external psu eventually.

-- judges

[baileyscream]

Originally Posted by judges That's not related to Spansion P at all (I have one). Actually all kinds of NORs can be written just fine. It's related to the mobo. If all "standard" methods of flashing fail (teensy powered by usb/voltage reg, teensy powered by console/without voltage reg, CrackMyDay's method) then you might have to connect an external psu eventually. -- judges

right got you.
i'm going to lift the nor off this board and try again.

thanks judges

[WalangAlam]

Could somebody post a JTP-001 pinout for teensy? I can't get into ps3devwiki. Is ps3devwiki down?

edit: NVM ps3devwiki is up.

[Gadorach]

Though mostly unimportant at this point, I thought I should mention that I did get the NOR to write, but I had to use an E3. Unfortunately, no matter what I did, the Teensy++ 2.0 just wouldn't do it. Still, all's well that ends well, so maybe next time.

Thanks @judges and @DebugBrain for the help back then regardless!

- Gadorach