Print

[sizanx]

hey,

After following the FreeBOOT_XeLLous Tut I soldered my LPT-cable on my Falcon, and dumped the first 2 mb's 3 times and compared them. No bad blocks here and they matched. So I wanted to check CB via Degraded and dumped 16 mb of my NAND, but it find bad blocks with error 250 and 204:

http://img46.imagesh...1/imag0031x.jpg
http://img205.images.../imag0054vb.jpg

I have set it to dump a 16mb again, and already same error at 86.
So can I still JTAG this beast or?

[thwack]

Yep - fully Tag'ble

The bad blocks on it are all reallocated, so it's not a read/write issue. Keep following Looouky's tut, Xellous will deal with the reallocation of the bad blocks for you

[Unknown45678]

QUOTE(sizanx @ Aug 11 2010, 09:22 PM)

thanks for the quick reply. My 2x16mb are exatly the same (using the fc command), and the "errors" shown in Degraded are the same, but in the cmd line my nand2.bin doesn't have a Error 204 at B8.

Btw m8, after I have Jtagged and wrote the Nand, can I just cut the lpt wires or pins?

I think there will be no problem in removing the cables seeing as if you need to flash your nand again all you would need is XeXmenu and flash360. Plus that would be much faster than using lpt. Though don't bin the cables as one day you may do something wrong and the LPT will be your best friend

[thwack]

Yep - save your LPT wiring - just desolder them and keep it as a just in-case (I used to put LPT/USB ports on the JTAG's I did as a backup).
Don't worry too much about XexMenu + Flash360 (although that method is fine), as you've got Xellous on there you can flash via USB stick/Debian whenever you like

[sizanx]

Hehe, I think it's because I posted the first post accidentally as another thread, the real thread is the second post. Admin must have merged them

[Looouky]

As long as they match your are fine to proceed, 250 and 204 are almost identical errors to my understanding one means data is unreadable, and the other one is block is blank.