[Mr.Dutch]

Originally Posted by baileyscream the starship and syscon can still draw power from the NANDS.

you are not that well informed.
and you need to read posts better.

i will post back if i find more errors in your post...lol.

[baileyscream]

Originally Posted by Mr.Dutch you are not that well informed. and you need to read posts better. i will post back if i find more errors in your post...lol.

lol i have syscon on the mind
i ment the southbridge ((i'm fairly sure this time lol ))

[zeruel85]

Hi everybody!

Today I tried again, but same result: always different dumps. I cleaned again both zif socket and the nands, but it doesn't work. The dump terminate correctly at 100%, but when I compare the two (or more) dumps they are always different.

I'm using the same configuration that works with nand K9F1G08U0A-PIB0. With this type of nand I have never had a problem, always identical dumps, why can't I correctly dump this one, K9F1G08U0B-PIB0?

Please help me, I'm available for testing something new.

[underwurlde]

Hopefully the settings used are:

COMMON TAB
Differential Flash: Yes
Verify: Yes
Abort on error: No
16 Bit: No
Swap Bytes: greyed out
Cycle Period (ns): 125
Read Delay (µs): 50

NAND TAB
Pages per Block: 64
Block Count: 1024
Big Block: Yes
Raw: Yes

Andy

[Sarah1331]

Solder directly to it with wires or get one of my adaptor boards to solder it to


Sent from my iPhone 5 using Tapatalk

[zeruel85]

I think that tonight or tomorrow I'll try with Teensy++ and NANDway 0.1 Beta. Will see...

@underwurlde :
Yes, the settings are right (WinSkeet recognizes the nand as ECF1009540).

@Sarah1331 :
I think the problem isn't the zif socket. Nands 'type A' are always read well, without any problems.

Thank you to all for your support!

[Sarah1331]

Originally Posted by zeruel85 I think that tonight or tomorrow I'll try with Teensy++ and NANDway 0.1 Beta. Will see... @underwurlde : Yes, the settings are right (WinSkeet recognizes the nand as ECF1009540). @Sarah1331 : I think the problem isn't the zif socket. Nands 'type A' are always read well, without any problems. Thank you to all for your support!

Progskeet 1.2
Or socket Deffo!! If your sure not socket it's skeet

I did here someone saying he had to change the bit stream to dump and again to write




Sent from my iPhone 5 using Tapatalk

[guerrierodipace]

ciao Zeruel, i used similar configuration (we know well each other ) but powering from progskket 1.2 and I can read type B samsung nand.

But the ones I made I can dump write compare correctly with bad block, but resoldered don't work

[Abkarino]

Originally Posted by zeruel85 I think that tonight or tomorrow I'll try with Teensy++ and NANDway 0.1 Beta. Will see... @underwurlde : Yes, the settings are right (WinSkeet recognizes the nand as ECF1009540). @Sarah1331 : I think the problem isn't the zif socket. Nands 'type A' are always read well, without any problems. Thank you to all for your support!

@zeruel85 this is the same setup that i use to read/flash NAND flash's using ProgSkeet and ZIF socket with 48-pin NAND Socket also.
All you have to do to have a good dump is to wire the Vcc and Gnd lines in both ZIF Socket sides.
If you did not do that you will have your NAND recognized but you will have a bad dump always.
Just be sure that you feed the NAND Vcc and Gnd to both NAND sides and also try to use a good wires also
I hope that will help you fix your problem.

[zeruel85]

Thank you Abkarino, I shorted VCC 12 pin with 37, and GND 13 with 36 pin. The nand is fed to both side (I always did that).

Now I want to try with Teensy and NANDway Beta, I'm curious...