[abelcher1523]

Hey anyone know the solution to this, last night finally got cmd to load NORway.py after having to restore my windows 7 x64 back to an earlier date. but encounterd this while trying to get my teensy 2.0++ to dump the nor flash.


C:\NORway>NORway.py COM4
NORway.py v0.6 beta - Teensy++ 2.0 NOR flasher for PS3 (judges@eEcho.com)
(Orignal noralizer.py by Hector Martin "marcan" <hector @marcan soft.com>)

Usage:
C:\NORway\NORway.py serialport [command] [filename] [address]

serialport Name of serial port to open (eg. COM1, COM2, /dev/ttyACM0, etc)
command dump Reads entire NOR to [filename]
erase Erases one sector/block (128KB/64KB/8KB) at [address]
erasechip Erases entire NOR
write Flashes (read-erase-modify-write) [filename]
at [address] to NOR (buffered programming mode)
writeword Flashes (read-erase-modify-write) [filename]
at [address] to NOR (word programming mode)
writewordubm Flashes (read-erase-modify-write) [filename]
at [address] to NOR (word prgrmmng/unlock bypass mode)
vwrite Flashes (read-erase-modify-write-verify) [filename]
at [address] to NOR (buffered programming mode)
vwriteword Flashes (read-erase-modify-write-verify) [filename]
at [address] to NOR (word programming mode)
vwritewordubm Flashes (read-erase-modify-write-verify) [filename]
at [address] to NOR (word prgrmmng/unlock bypass mode)
verify Verifies NOR content with [filename] at [address]
release Releases NOR interface, so the PS3 can boot
bootloader Enters Teensy's bootloader mode
filename Filename for [dump|(v)write|(v)writeword|(v)writewordubm|verify]
address Address for [erase|(v)write|(v)writeword|(v)writewordubm|verify]
Default is 0x0, address must be aligned (multiple of 0x20000)

Examples:
C:\NORway\NORway.py COM1
C:\NORway\NORway.py COM1 dump d:\myflash.bin
C:\NORway\NORway.py COM1 erase 0x20000
C:\NORway\NORway.py COM1 erasechip
C:\NORway\NORway.py COM1 write d:\myflash.bin
C:\NORway\NORway.py COM1 write d:\myflash.bin 0xA0000
C:\NORway\NORway.py COM1 writeword d:\myflash.bin
C:\NORway\NORway.py COM1 writewordubm d:\myflash.bin 0x40000
C:\NORway\NORway.py COM1 verify d:\myflash.bin
C:\NORway\NORway.py COM1 release

C:\NORway>

... I get the same thing with 0.5. My ps3 is 80gb cechL ver-001 board.
I type in NORway.py COM4 and it just gives me that instead of pinging.
any ideas what could be happening?

[kipper]

i think you had the same problem as me change the file name inside norway programs to norway instead of norway v0.5

[BwE]

reinstall the python software etc that came with the original norway.

or ask the grand wizard @judges

[abelcher1523]

Actually, i think its just an issue with windows 7 x64 compatability, dont know the solution to get it to work on that distro. I just happened to find an older computer laying around that had xp on it. Worked like a charm! anyone who is having trouble with this, would be simpler to just have a computer with xp or a partition. I read somewhere that said x64 versions of window 7 were tricky to get NORway to work on..

[judges]

Originally Posted by abelcher1523 I type in NORway.py COM4 and it just gives me that instead of pinging. any ideas what could be happening?

Yes. It's a python/windows issue. Can occur with e.g. multiple python installations. It's a problem with the registered .py extension. Arguments aren't passed under certain cirumstances.

To work around that issue you can enter this at your cmd prompt:

"<Full path to you python installation>\python.exe" norway.py com4

To permanently fix this you have to modify the registry. Start regedit and search for all occurrences of this:

python.exe" "%1"

This is what the value of found reg-keys should look like this:

"<Full path to you python installation>\python.exe" "%1" %*

In your case it'll probably look like this in one or more occurrences:

"<Full path to you python installation>\python.exe" "%1"

Edit those keys and add the missing %* at the end.
************* [ - Post Merged - ] *************

Originally Posted by kipper i think you had the same problem as me change the file name inside norway programs to norway instead of norway v0.5

Bull****. ;-)
************* [ - Post Merged - ] *************

Originally Posted by abelcher1523 I read somewhere that said x64 versions of window 7 were tricky to get NORway to work on..

Bull****. ;-)

[abelcher1523]

Brilliant judges, Thank you! That did the trick, NORway works now on x64 windows 7 with that fix. Saved me the trouble of getting out the old tower computer for this job..
************* [ - Post Merged - ] *************
I have another issue i was working with on the tower computer when i got NORway running, trying to flash a ver-001 Board with a Samsung K8Q2815UQB-PI4B nor chip. I Keep getting this..


"Pinging...
Set SB to tristate

NOR chip manufacturer: unknown (0xff)
NOR chip type: unknown (0xffffff)

STATUS_TRIST_N: LOW
STATUS_RESET_N: LOW
STATUS_READY: HIGH
STATUS_CE_N: LOW
STATUS_WE_N: HIGH
STATUS_OE_N: HIGH

Resetting NOR...
Ready.

Dumping NOR...
16384 KB / 16384 KB
Done. [0:01:14.045000]

Closing serial device...
Done.

C:\NORway>"

and my dumps are usually all FF, or 00 with rarely a few dumps with some code in them, only a small bit though, no where near the amount i should be getting. could this be a NORway problem (i.e because the nor chip im working with has a unique architecture, and the program isnt reading the chip correctly?) or is it a simple voltage problem. as in i need to check all my connections, mabye switch from my voltage regulator on it and power my teensy 2.0++ with the mainboard 3.3v. Would too much power coming in from usb create the board to pull dumps like this? I bought this ps3 off ebay and the guy said that it had the rsod, after updating from 3.56 to 3.70 or so.. figured i had to flash it after no progress with a dongle. Any ideas would help alot since ive got some time to wait till my new kynar wire supply arrives aswell as more solder.

[judges]

Originally Posted by abelcher1523 could this be a NORway problem (i.e because the nor chip im working with has a unique architecture, and the program isnt reading the chip correctly?) or is it a simple voltage problem. as in i need to check all my connections, mabye switch from my voltage regulator on it and power my teensy 2.0++ with the mainboard 3.3v. Would too much power coming in from usb create the board to pull dumps like this?

It's not a NORway problem. In rare cases certain mobos require some trickery. And usb never provides too much power..

1. Check your wiring. Whatever you'll try won't work if your wiring is faulty.
2. Power Teensy from console (remove voltage regulator). This might already work.
3. If 2. doesn't work, power Teensy from console and try this: http://www.ps3hax.net/showpost.php?p...postcount=1575
4. If 3. doesn't work you can try running Teensy at 5V. No voltage reg, 5V pads bridged, 3V pads not connected (like it comes from factory). Don't connect Teensy's Vcc to console's Vcc.

-- judges

[abelcher1523]

i desoldered the teensy from the ps3, and now the ps3 turns on but stays on. It doesnt show any hdd light like it used to and when i hold down the power button it just shuts off and the second time shuts straight off with out the double beeps. so i cant get into recovery mode. ive tried releasing the nor chip, same result. examined the tristate connector and thats fine. its either in a deeper bricked state, or some how still in tristate. or i was worried that i fried the nor chip but i dont think i could of. i resoderd on the teensy with good connections and i tried it with the 3.3 v regulator on it. i got dumps with more data but its still a bad dump. and no chip information. i tried it when it was totally off aswell. i took off the 3.3v regulator and powered the teensy via console and still getting bad dumps not all FF and 00, but no where near what it should look like. still no chip information. i then took your advice and soldered the 5v short and disconnected the vcc to the console and teensy. tried that off and on and still bad dumps with no chip information. what could be going on. the ps3 had rsod from an update to 3.70 or something. could the firmware be this corrupted that i cant get any good dump from it? any one been able to get a clean dump off a 80gb pal CECHL04 with a Samsung K8Q2815UQB-PI4B chip?