I'm having trouble w/Teensy2++ and Samsung K8Q2815UQB running NORway 0.4 beta 12.
I'm able to dump and issue erasechip while console is in standby, or unplugged with
I'm not able to issue writeword or writewordubm commands in any mode (on/standby/unplugged). I've tried with the power regulator installed and console in standby, which worked for dumping, but this errors out after about 1200 KB/16384 KB. I've tried removing the regulator as per CrackMyDay's method and cannot issue either write command.
This is the message I receive:
I'm not sure if this message is indicating that my Teensy is crashing, or if the NOR is overwhelmed and stopped responding to pings. I've looked at the NORway.c Teensy code and it appears that on ping attempts no data is going between Teensy to NOR, so I'm thinking that it's the first case.
__main__.NORError: Ping failed (expected 42, got ff)
I've hooked up my ~OE (0), ~CE (1), ~WE (2), RY/~BY (3), and A22 (4) lines to a logic analyzer and got this output while issuing writewordubm. The failure occurs around the part of the graph where A22 goes high, and the write halts at about 1100-1400 KB/16384 KB with the Python error shown.
Does anybody have any ideas on what may be my problem? My final resolution is to replace my Samsung chip with a Macronix MX29GL, but I'm not sure if my dump and PS3 (CECH2001A) will be compatible.
Thanks for any opinions or ideas
Don't use Linux.
After installing Python 2.7 on a Windows computer with Teensy drivers, this Python error went away.
I was able to leave the regulator installed and not have to connect the Vdd on the NOR chip to anything, able to write with PS3 on standby.