Talk:Hardware flashing

From PS3 Developer wiki
Revision as of 08:14, 10 January 2012 by Jhax78 (talk | contribs) (Testreport table)
Jump to: navigation, search

Testreport table

Board Flash Dumping Writing Remarks
COK-001 2x Samsung K9F1G08UOА-PIB0 Yes Yes bluemimmo : CECHA / COK-001 read\write NAND fine. used progskeet and 110819 software and dual NAND settings, but after patching ros using dospiedras method manually, cannot downgrade, ps3 bricked, wrote original dump, ps3 alive again.
COK-001 2x Samsung K9F1G08UOА-PIB0 Yes Yes Abkarino : CECHA / COK-001 read\write NAND fine. used a professional flash programmer and successfully downgraded from 4.00 OFW to Rogero 3.55 CFW using NAND downgrade patch.
COK-001 2x Samsung K9F1G08UOА-PIB0 Yes Yes ps3oon : CECHA / COK-001 read\write NAND fine. used progskeet+winskeet no trik editing with hex
COK-002 2x Samsung K9F1G08U0A-PIB0 Yes Yes avati : COK-002 and COK-002W: read\write NAND fine. used progskeet+winskeet 111120
SEM-001 2x Samsung K9F1G08UOА-PIB0 Yes Yes dodther : CECHG / SEM-001 read\write NAND fine. used progskeet and 110819 software and dual NAND boardtraces by jestero
SEM-001 2x Samsung K9F1G08UOB-PIB0
SEM-001 2x Samsung K9F1G08UOB-PIB0 Yes Yes Strike Venom : CECHG04 / SEM-001 read\write NAND with Infectus 2 without tricks
SEM-001 2x Samsung K9F1G08UOB-PIB0 Yes No sel99 : CECHG / SEM-001 - 1-875-384-31 - can dump both NANDs fine, have trouble writing. both with Infectus and Progskeet. Boards below CECHG / SEM-001 flash fine.
SEM-001 2x Samsung K9F1G08UOB-PIB0 Yes No delsol : SEM-001 - 1-875-384-31 - dump both NANDs fine, still not able to reflash the nands correctly. there are always differences. Tried with Infectus.
DIA-001 1x Spansion S29GL128N90TFIR2
DIA-001 1x Spansion S29GL128N90TFIR2 Yes Yes mrdrifta : Teensy++ /NORway v0.3 Reads perfectly, but no write - NORway v0.4 beta 12 write successful - needed to run erasechip first, then run writewordubm flash.bin to write to console.
DIA-001 1x Spansion S29GL128N90TFIR2 Yes No delsol : flasher still freeze at sector0 (A&B) dumping seems to works (A&B). Same result with and without resistors. Tried on winxp-sp2 and win7. // The best results i got was using the 9k & 100k resistors. the flash is unuseable but ProgSkeet_110819 doesen´t freeze anymore. // I have tried Teensy and NORway0.3: dumping of nor works fine, but everytime when i tried to flash, the pc loose usb-connection to Teensy
DIA-001 1x Spansion S29GL128N90TFIR2 Yes Yes Keeper : downgrade successfuly with Winskeet4000_111002_2 without any resistors
DIA-001 1x Spansion S29GL128N90TFIR2 Yes Yes Abkarino : successfully downgraded from 3.56 using WinSkeet 111004
DIA-001 1x Spansion S29GL128N90TFIR2 Yes Yes ps3oon : successfully downgraded from 3.56 using WinSkeet 4000 Rev 111002 with some trick
DIA-002 1x Spansion S29GL128N90TFIR2 Yes Yes AdReNaLiN_TR : successfully downgraded from 10K/100K trick using
VER-001 1x Spansion S29GL128P90TFIR2 Yes Yes kado : Downgrading 3.70 to 3.55 success with progskeet (differ ON, No special trick)
VER-001 1x Samsung K8Q2815UQB-PI4B
VER-001 1x Samsung K8Q2815UQB-PI4B Yes Yes calimba : downgrade successful with progskeet on VER-001 CECHL01 with QT port. if the program 110819 freeze you need flash first the file with the qt port.
VER-001 1x Samsung K8Q2815UQB-PI4B Yes Yes Ir0nmanNB : Used all gnds listed on the diagram. Used 3.3V pull-up, also had R7 with switch AND R8 bridged. Disconnect USB from PC and with R7 open turn PS3 on, count to 20 and close R7 then plug in USB to PC. Then open up WinSkeet4000 and write. Use 110819 for the early sectors if they fail to write, using 4/4096, differential, alternate, verify, and byteswap. Then try again with Winskeet4000, using Samsung preset then go to NOR tab and change it to 128/128.
VER-001 1x Samsung K8Q2815UQB-PI4B Yes Yes Ryd3R : Starting from NORway v0.4 Beta W/R fully supported).
VER-001 1x Samsung K8Q2815UQB-PI4B Yes Yes blakcat : succeed downgrade with my method. See Tutorial
VER-001 1x Spansion S29GL128P90TFIR2 Yes No toxie : tried 128k/128 , 4k/4096. writing without alt. all FF, with alt some random patterns with 00 and FF when writing all 00. Trying A/B trick, still at Programming Sector 0
VER-001 1x Spansion S29GL128N90TFIR2 Yes Yes marlboro12 : downgrade successfuly with Winskeet4000_111002_2 (by Ago). Pullup 10Kohms btw R8 closed and rdy, and a 100Kohms resistor btw rdy_progskeet and rdy_nor. Rogero_CFW_V2 works fine on the ps3.
VER-001 1x Spansion S29GL128N90TFIR2 Yes Yes bluemimmo : Used older winskeet and progskeet flashing stuck at sector 2 but used latest winskeet and sucessfully downgraded. Downgrade successfuly with Winskeet4000_111004. Rogero_CFW_V2 works fine on the ps3.
VER-001 1x Spansion S29GL128N90TFIR2 Yes Yes Jhax78 : Downgrade successfuly with Winskeet4000_111004. Rogero_CFW_V2 works fine on the ps3. Some sectors needed Max byte write 16 to finish on 2 consoles
VER-001 1x Spansion S29GL128P90TFIR2 Yes Yes Abkarino : Downgraded from 3.70 successfully using WinSkeet 111004 build
VER-001 1x Spansion S29GL128N90TFIR2 Yes No ares : tried 128k/128. With normal method a lot ff and same byte match. With alternate method 00 and ff and some byte match. Without resistor trick programmer freeze programming sector 0. with 100k and 9k resistor i can write but with errors (programmer completes the write, but the dump is all 00 ff, only few byte match, this with alternatemethod). with a/b tick's programmer (version A and B ) it freeze on programming sector 0 (both with or without resistors)
VER-001 1x Spansion S29GL128N90TFIR2 Yes Yes gokuhs : With 'erasechip' and 'writewordubm' method without resistors and work fine. NORway 0.4 BETA9+. I used the jestero's diagram for VER-001 motherboard without VCC pin solder
DYN-001 1x Samsung K8Q2815UQB-PI4B Yes Yes blakcat : succeed downgrade with my method. See Tutorial
DYN-001 1x Samsung K8Q2815UQB-PI4B Yes Yes marlboro12 : succeed downgrade with blackcat scheme. flasher 110819, 4/4096 all option checked. divide .bin in two equals files. first flash sector 0->2047 with any modification and without power cycle, just unplug usb and reload 110819, flash second file with resistor 10K btw a22_NOR and 3.3V.
DYN-001 1x Samsung K8Q2815UQB-PI4B Yes Yes maitre kanter : Downgrade succesfull. See [1]
DYN-001 1x Samsung K8Q2815UQB-PI4B Yes No yrr : tried 128k/128 , 4k/4096, WinSkeet40000,ProgSkeet_110819. It writes ok till sector 64(128k/128) or 08004D0xH in the dump file. From that point on no changes. No write no erase. Tried also the 10k/100k resistor trick. All the same result.
DYN-001 1x Spansion S29GL128P90TFIR2
DYN-001 1x Samsung K8Q2815UQB-PI4B Yes Yes bluemimmo : Splitted the patched known good dump into 2 parts : 000000-7FFFFF and 800000-FFFFFF. Flashed part1 with winskeet in 128/128 mode from sector 0-6 with A22 low. Then flashed part2 with progskeet_110819 select mode 4/4096 and custom sector start from 2048-4095 with A22 high. Byte swap, alternate write method, verify, differential flashing. See progskeettopic
DYN-001 1x Macronix MX29GL128ELT2I-90G Yes Yes Ryd3R : NORway 0.3 fully support R/W on Macronix MX29GL128ELT2I-90G.
DYN-001 1x Macronix MX29GL128ELT2I-90G Yes Yes Abkarino : successfully downgraded from 3.70 using WinSkeet 111004 and ProgSkeet V1.0
DYN-001 1x Samsung K8Q2815UQB-PI4B Yes Yes AdReNaLiN_TR : Downgrade Succesful. Thank you_BLACKCAT_
DYN-001 1x Spansion S29GL128P90TFIR2 Yes Yes Xb0xGuru : Downgrade successful. 100k/10k resistor trick used, Winskeet 40000 used (10 September 2011, 21:14:56)
DYN-001 1x Macronix MX29GL128ELT2I-90G Yes Yes calimba : Downgrade succesfull, used progskeet.
SUR-001 1x Macronix MX29GL128ELT2I-90G Yes Yes kado : Downgrade succesfull, used newest WT-port, nor pinout same as JSD-001
SUR-001 Spansion S29GL128P90TFIR2 Yes Yes Abkarino : successful downgrade from 3.66 to 3.55 using ProgSkeet V1.0 and WinSkeet Build 111004 - used JTP-001 norpoint listing
JTP-001 1x Spansion S29GL128P90TFIR2
JTP-001 1x Spansion S29GL128P90TFIR2 Yes Yes drako_ : success downgrading from 3.70 to 3.55 with wiring according to JSD-001 diagram, with 5 grounds and settings 128K/128 (progskeet).
JTP-001 1x Spansion S29GL128P90TFIR2 Yes Yes blakcat : success downgrading from 3.56 to 3.55 (JSD-001 diagram), with 2 grounds and settings:128K/128,winskeet,dif.Board out of ps3 with r8 and r7 closed
JTP-001 1x Spansion S29GL128P90TFIR2 Yes Yes Ryd3R : success downgrading from 3.70 to 3.55 with wiring according to JSD-001 diagram NORway v0.3 .
JTP-001 1x Samsung K8P2716UZC-QI4D Yes NOT YET TRIED TooTHPiCK : NORway and Teensy++
JTP-001 1x Samsung K8P2716UZC-QI4D Yes Yes Rogero : Downgrade succesfull, used Progskeet, flash 128/128, Dump with progskeet_110819, Patch with winskeet, Flash with progskeet_110819(differential flash/verify) using Win7(with winXP SP3 compatibility Mode/Run as Administrator) Rogero CFW V2 No_BD, Blu-Ray drive not attached
JTP-001 1x Spansion S29GL128P90TFIR2 Yes Yes yrr : success downgrading from 3.70 to 3.55 with wiring JSD-001 diagram, 2 grounds, 128K/128 (progskeet/110819).
JSD-001 1x Spansion S29GL128P90TFIR2 Yes Yes dodther : Downgrade succesfull. used progskeet and winskeet40000
JSD-001 1x Spansion S29GL128P90TFIR2 Yes Yes yrr : Downgrade succesfull. used progskeet and winskeet40000
JSD-001 1x Samsung K8P2716UZC-QI4D Yes Yes kado : Downgrade succesfull with special trick
JSD-001 1x Samsung K8P2716UZC-QI4D Yes Yes petrm79 : factory 3.56, 320gb, cech-250.b, console code 1a, standart solder without resistors etc. nor samsung (flash 128/128). using latest qt port. check alt. meth., downgrade using dospiedra v2 (manual paste), rogero.pup
JSD-001 1x Samsung K8P2716UZC-QI4D Yes Yes bluemimmo : factory 3.56, 320gb, cech-2504.b, console datecode 1a, dump with progskeet_110819, patch with winskeet, flash with progskeet
JSD-001 1x Samsung K8P2716UZC-QI4D Yes Yes Ryd3R : NORway 0.3 fully support R/W on Samsung K8P2716UZC-QI4D.
JSD-001 1x Spansion S29GL128P90TFIR2 Yes Yes

kado : Downgrading 3.70 to 3.55 success with progskeet (differ ON, alter ON) NOTE: THIS BOARD HAS different lengt normally (lenght is E990)

JSD-001 1x Spansion S29GL128P90TFIR2 Yes Yes

Hikage : Downgrading 3.72 to 3.55 success with teensy++ and NORway 0.3, dump work with norway 0.4 beta10 but partial work on write. Norway 0.4 beta12 work fine on read and write.

KTE-001 1x Spansion S29GL128P90TFIR2 Yes Yes AdReNaLiN_TR : Nor dumping/wrıtıng for downgrade do not wrıte.ps3 unbrick refresh dump progskeet.
KTE-001 1x Samsung K8P2716UZC-QI4D Yes Yes AdReNaLiN_TR :Nor Dumping/Writing downgradable no metldr2 refresh dump progskeet
KTE-001 1x Macronix MX29GL128ELT2I-90G Yes No NO GO! : Tried default Macronix settings in WinSkeet40000 v111004, ProgSkeet v1.1. soldered (360 clip 56 or ZIF 50 cable and post header pcb have shorts). Verification errors always persist when attempting to flash. Erase also gets errors.
EXA-MPLE 1x dummy Yes No example : Tried 128/128 and 4K/4096, resistor and A/B trick, always freezes on first sector
must add this one in English in the channel above (marlboro1) :
   Résumé:
   - PS3 slim CECH-2004A (DYN-001 et Samsung NOR)
   - OFW 3.70
   - Progskeet (dernier pilote)
   - Flasher 110819 et Winskeet4000 (dernière version)
    
   Installation du progskeet avec les documentations trouvées sur ps3devwiki.
   Dump réussi sans problème.
   Lors du flash, avec la première version de transplante, j'ai eu un échec.
   Ensuite impossible de réécrire avec le dump original.
   Impossible de flasher la NOR avec le dump modifié par la deuxième version du patch de dospierda.
   Ir0nman m'a conseillé de ponter R8 et de mettre en place une résistance de 10Kohms entre le 3.3V et RDY et une de 100Kohms entre le RDY du progskeet et celui de la NOR. Cela a semblé fonctionner mieux.
   Ensuite Ir0nman m'a conseillé de mettre directement la résistance de 10Kohms entre R8, qui est ponté, et RDY du progskeet. Cela m'a permis de réécrire le dump original et récupérer ma PS3 en OFW 3.70.
   Lorsque j'ai fait un dump, il est identique à celui d'origine.
   http://i1180.photobucket.com/albums/x413/Ir0nman11/IMAG0119.jpg (switch R7, R8 removed and bridged, using resistor pullup RY/BY)

Pretesters

Users With NORway (teensy++) who maybe could do pretesting :

Ryd3R

Users with Injectus who maybe could do some pretesting :

ares
damox
delsol


Progskeet QT port

OLDEST: http://www.sendspace.com/file/3bz5s5 USE AT YOUR OWN RISK
OLDER: http://www.sendspace.com/file/ijr2yb USE AT YOUR OWN RISK

Current: http://static.loping.net/private/ps3/WinSkeet40000.zip <- Qt Port, latest one, BETA STILL

<Ago> damox: ill add import / export soon
<Ago> for now, you can export the registry key
<Ago> HKEY_CURRENT_USER\Software\ProgSkeet\ProgSkeet\presets
<Ago> on linux and osx its file based

Resistor trickery

without pullup:    rdy ---[100kOhm]--- nor_rdy
with pullup:    3.3V---[10kOhm]---rdy---[100kOhm]----nor_rdy

Progskeet manual testing version

<Ago> for anyone wanting to diagnose wiring problems, i have a build that allows you to set the data and address lines by hand
<Ago> http://static.loping.net/private/ps3/WinSkeet40000_manual_test.zip
<Ago> 13:16 <Ago> there is a new tools tab
<Ago> 13:16 <Ago> there you will find address and data entry boxes
<Ago> 13:16 <Ago> you can prefix with 0x for hexadecimal input
<Ago> 13:16 <Ago> or with b for binary input
<Ago> also, this build will decode the cfi as text when dumping
<Ago> i will also add a semi-automated testing mode
<Ago> where it will set only one line to high and prompt you to check it
<Ago> then checks the next one

<No Go> Progskeet "Crystal Blue" v1.1 has a 50 pin ZIF connector which is a solderless connection. <No Go> 360 Clip manufactures a solderless clip for a 56 pin NOR and 50 wire flat cable which does not work as shorts are created. <No Go< As of Dec. 2011 there is no working solderless connection to a PS3 NOR

BD drive not found problem

Progskeet related:

<Ryd3R_> faild to downgrade just like the prev test
<Ryd3R_> with the BD drive error 
<Ryd3R_> tried jaicarb lv2diag - CFW with no BDCheck - reconnecting the BR drive
<Ryd3R_> all of them failed
     
<Ryd3R_> i found what is causing the problem
<Ryd3R_> the programmer (progskeet/NORway)  while its hooked to the mobo it somehow cause the BR drive not found problem
<Ryd3R_> what i did is desoldering the control lines and updated without any problem
<Ryd3R_> the mobo is VER-001

Other reason/solution:

<Rogero> eussNL: nice69 tested a No_BD CFW i gave him and it worked 
         for his 5 consoles that he was having problems updating
<Rogero> he tried normal lv2diag.self but didn't work for him
<Rogero> then we noticed that his consoles are refurbished... 
         these are the only consoles he had problem downgrading 
         (where the normal PUP failed to complete)
<Rogero> http://www.rogero.tortuga-cove.com/Rogero_CFW_V2_Kmeaw_LV1_Patched_3.72_spoof_Privacy_Patch_NoBD_Update.PUP
<Rogero> in case anyone needs it too ;)

Problematic Samsung / Spansion N related

Teensy

<jevin> nikitis, want to work tonight on getting samsung support working w/ teesny?
<jevin> ive got a hack to get around the different block sizes throughout the chip: just chip erase the whole thing
<jevin> and that chip erase is actually 2 chip erases, one with a22 low and one with a22 high (internally there are 2 8MB nor dies)
<jevin> then when flashing you cant use the write buffer command (there is no buffer)
<jevin> and have to instead use slower unlocked programming
<jevin> nikitis, ive had my teensy soldered up for nearly a week in the hopefully new, emi-proof location but havent hacked up the mobo shield to make it actually fit. i should try it tonight to see if it works

Progskeet

<kado> i confirm PROGSKEET HARDWARE is STABLE than other programer (teensy,etc)
<kado> the only problem is from flasher
<kado> especially for Spansion 'N' & SAMSUNG
<kado> i tested the winskeet but still not working well for those
<eussNL> ok, did it use A22 virtual chip #CE correct in your observations kado ?
<kado> actually no euss
<eussNL> shame
<kado> all flasher should be focus on SB_tristae, reset
<eussNL> so it was low all the time (virtual chip select 1) ?
<kado> and for spansion should be focus on those + #WP
<kado> and i am sure it could be emulated by flasher it self ;)
<eussNL> sure, not a problem to change the way controllines are used
<eussNL> just need a good preset that also sets the correct writing strategy
<kado> yes
<kado> thats right
<eussNL> which reminds me, that was one thing left out in winskeet (the samsung setting needs manual setting after selecting the preset)
<kado> the secreet for spansion N is only need 0v for (tristate & reset)
<kado> and do not ever modified the RDY
<kado> RY/BY NOR is controlled by SB
<kado> hope you can make this clear eusss, and explaint to all people
<kado> next secreet for Samsung "Q" (edit: K8Q2815UQB-PI4B), pls make note :
<kado> check your #WE shold be 'L'
<kado> and RESET should be 'H'
<eussNL> isnt that default kado? because Samsung Q (edit:K8P2716UZC-QI4D) already works fine afaik
<kado> once again no RESISTOR trick
<kado> i always use 110819
<kado> for write
<kado> and check those point
<kado> with all option checked
<kado> eus: the flasher could not emulated that point
<eussNL> kado, the QT port is the current one, the other is ment to be no longer maintained if I got it right
edit: NOTE that we both ment different Samsung! kado:K8Q2815UQB-PI4B // eussNL: K8P2716UZC-QI4D (reason: both have Q in their partnumber)


manual A22 virtual chip select

For dualbanked chips with A22 Virtual Chip Select pin (e.g. Samsung K8Q2815UQB-PI4B)

 128Kx128 settings to flash.
                        
 resistor 10k:
    a22 point on board (NOR) ----- 10k ----- 3,3v direct
 a22 point of prgoskeet is not connected to anything while flashing second bank
     
first flash first virtual chip with A22 low : 0-63 first bank       (000000-7FFFFF)
then flash second virtual chip with A22 high : 64-128 second bank   (800000-FFFFFF)

See also : http://www.progskeet.com/forum/viewtopic.php?f=3&t=373

<bluemimmo> : 
- Dump the NOR as many times as we like and check them they are identical.
- Use norunpack to unpack the nor dump, so if nordump extracts without any errors, then we are quite sure that nor dump is valid.
- Now make downgrade.bin from downgrade v2 patch. FYI you can have dump from any version and any mode like FSM too.
- After downgrade.bin is prepared, divide it into two parts. First part = offset:000000 - 7FFFFF and Second part = offset:800000 - FFFFFF
- Flash the part1 with winskeet in 128/128 mode from sector 0 - 63
- Now dump your full nor again and divide it into two halves as mentioned above. Now compare the first half dumped just now with the downgrade.bin part1, if both are identical then you are ok to go.
- close the winskeet and open Progskeet_110819 and switch the a22 pin to high.
- In progskeet_110819 select mode 4/4096 and custom sector start from 2048 - 4095
- Select byte swap, alternate write method, verify, differential flashing, and flash the downgrade.part2.bin
- After flashing complete and verified ok, switch the a22 pin to normal position and dump you flash again.
- Compare the recently dumped flash to downgrade.bin, if both are identical, yours is downgraded.

See also : http://www.progskeet.com/forum/viewtopic.php?f=3&t=382

<winskeet latest> No need to pull a22 line high manually, winskeet will do automatically. Tested and works fine.

Read CFI data

<Ago> guys, we need people to supply us with nor cfi data
<Ago> we're most interested in samsung
<Ago> i'm currently uploading a test version that dumps cfi
<Ago> http://static.loping.net/private/ps3/WinSkeet40000_CFI_Test3.zip
<Ago> select preset and press dump cfi on nor tab
<Ago> then send the resulting file
      
<Oliveira> CFI is a section of the PS3 flash image ?
<Oliveira> or is it the chip ID stuff ?
<Ago> no, its information about hte flash chip itself
<Ago> like how it wants to be written, erased and how big it is
<Ago> we currently do not use it at all
<Ago> but we think the samsung problems and maybe the spansion n problems are because of that
http://static.loping.net/private/ps3/cfi/Spansion%20S29GL128N90TFIR2.cfi
http://static.loping.net/private/ps3/cfi/Spansion%20S29GL128P90TFIR2.cfi
http://static.loping.net/private/ps3/cfi/Samsung%20K8Q2815UQB-PI4B.cfi
http://static.loping.net/private/ps3/cfi/Macronix%20MX29GL128ELT2I-90G.cfi

Offboard flashing / Replacement NOR talk

<Rogero> eussNL: about flashing a nand/NOR externally, 
         once removed from the board and into a socket, 
         will this work for sure ?
<Rogero> i mean could be done, no problems if the nand is standalone
<eussNL> this will work for sure for board originated problems.
<eussNL> that still leaves us the Samsung dualbanked issue
<eussNL> e.g. VER-001 are most likely to benefit from offboard solution
<eussNL> perpaps it is a solution to exchange the banked Samsung for the uniform one, 
         or a Spansion/Macronix - someone tried that on a VER,
         but ran into board related issues afaik
<eussNL> because reading isnt the problem, writing is - 
         so read a banked Samsung offboard, 
         and flash patched in a nonbanked/uniform one offboard and resolder
<eussNL> offboard also means no need for messing with resistor trickery
         (pullup/down´s) on control-lines (RY/BY)
<nice69> read and write externally, then re-solder the chip
   
<Xb0xGuru> right, so it's the board layout which is the problem?
<eussNL> 2 fold
<eussNL> 1) Samsung banked 2) VER-001 board
   
<Xb0xGuru> what about the DYN-001 board? Would a Spansion work on there as a replacement?
<eussNL> and if board modification is on order, it would be most likely a controlline, 
         like RY/BY, which was the target of the resistor trickery
<eussNL> DYN-001 works fine with Macronic Xb0xGuru 
<eussNL> see http://www.ps3devwiki.com/index.php?title=Talk:Hardware_flashing#Testreport_table
         for the patterns of problems
   
<eussNL> you can use others flash too, 
         the one I list there is just the one Sony used on a different version of the board.
         See http://www.ps3devwiki.com/index.php?title=Flash_%28Hardware%29#NOR 
         for all the current NORs used
         (and stay away from dualbanked and perhaps ¨N¨ serie spansion too)
<eussNL> anyhow Samsung K8P2716UZC-QI4D = uniform/nonbanked and is fastest. 
         The Macronix and Spansion are 90ns
<eussNL> Replacements for NOR have to be 
         =>128Mbit x8, 
         VCC 3V (2.7V~3.6V), 
         <=90ns, 
         56-TSOP1, pincompatible, 
        uniform/nonbanked, non OTP, non encrypted.
     	
<Xb0xGuru> I successfully transplanted a Spansion P NOR onto my DYN-001 board that had a Samsung NOR on there previously.
<kado> r u sure??
<Xb0xGuru> yes - all done
<Xb0xGuru> downgraded to 3.55 CFW.
<kado> wow thats good to know
<Xb0xGuru> flashed it initially with the original 3.70 dump and it fired up nicely too
<Xb0xGuru> Spansion P came from another DYN-001 board, if that matters

Heavily edited log. Interesting read IMO

NAND clips

http://img15.imageshack.us/img15/611/progskeet360clip.png



Old reference

(don't remove, not all is on mainpage)


NAND

NAND (256MB, old FAT models, needs 32 wires, 15 per NAND + GND + VCC)
2 chips: Samsung K9F1G08U0A-PIB0

FlowRebuilder v.4.1.0.0

TSOP sockets:

NOR

NOR 16MB, newer FAT models + Slims
needs 44 I/O wires: 23 address lines:A0-A22 + 16 Data lines:D0-D15 + 5 control lines: CE#,OE#,WE#,RESET#,TRISTATE (optional:#RY-BY) + GND + VCC
(NB: RY/BY is optional only for Teensy, Progskeet NEED ALL controllines!)

1 chip: Spansion S29GL128N90TFIR2 or Samsung K8Q2815UQB-P14B

NOR uses 1024 byte sector, just as NAND.

(Note : PIC32 flasher for Spansion is very slow: dumping 16MB = ~15min / writing full dump = 4 hours)

TSOP sockets:




Alternatives for Infectus2 and Teensy 2.0++:


Atmel AT90USB1286 datasheet

NORway / Teensy experimental Samsung support

THIS IS UNTESTED CODE! DO NOT TRY THIS UNLESS YOU HAVE A VERIFIED GOOD DUMP OF YOUR FLASH AND ARE WILLING TO WORK OUT ANY BUGS IN FLASH WRITING!!!

This modification of NORway.py attempts to support samsung dualbanked flash chips (e.g. K8Q2815UQB-PI4B). It performs a chip erase (with a22 low then high) then programs the entire flash using unlocked, single-word programming. Programming ranges is not supported because partial erasing is not implemented. Programming will be slow because it waits for RY after programming every single word. The author's teensy install has EMI issues so they were not able to test this code! The file works with NORway's original Teensy firmware.

[2]

link for improper NOR dump start

...is dead. i mean this one: "If your dump starts like this: http://pastebin.com/sS69Vhvf[...]" - anyone has the proper link?