Print

[uzi]

uhm.. hmm
lets see .. yesterday i got 250 error code at bytes 200+ ..

what i did was unplug the power for like 10 secs... pluged it back in.. did a pc reboot.. and tried again and i got a clean dump

this was for my zeyphr xbox 16mb nand...

[h4z3r]

ive read my nand several times (took about 18h each^^) and i always got on block  C78 the same error :-/
it must be an bad block

[matt_black_90]

QUOTE(h4z3r @ Jan 8 2010, 01:19 AM)

ive read my nand several times (took about 18h each^^) and i always got on block  C78 the same error :-/
it must be an bad block

yes it's a bad block.
make sure your nand backup are correct (compare all of your nand.bin)

open the nand bin with degraded thare you will see where your bad block is remapped to.

note: badblock @ xxx (your badblock)
note: block xxx found at yyy (where the block is remapped to)

after you have putten in your config.bin and kv.bin in your xbr.bin
than do:
"nandpro xbr.bin: -r512 blockxxx.bin xxx 1"
"nandpro xbr.bin: -w512 blockxxx.bin yyy 1"
(replace xxx with your bad block and replace yyy with yor remapped block position)

this is how i did on my 16MB, but I believe its the same with the 512mb

[matt_black_90]

QUOTE(h4z3r @ Jan 8 2010, 01:57 AM)

youre right on 16mb, i could even use bad block mover app, but with the 512 nand all these apps will not load, they only work with 16mb :-/

 sorry my bad, didn't know.

but i Found something, look at the post in the bottom http://forums.xbox-s...mode=linearplus


Read out your bad block from your xbr.bin patched with kv.bin and config.bin

CODE

nandpro xbr.bin: -r512 blockC78.bin C78 1

and write it direcly to your nand at block 7fff

CODE

nandpro lpt: -w512 blockC78.bin 7fff 1

[crazytim87]

i have also gotten a bad block on my 512 jasper which is brand new is this normal? and is it still safe to flash with XBR?

[h4z3r]

yes, i got this method to add the block to the end in my mind but, how does xbr know, that i moved its c78 block to the end ?

[DreddBull]

Did a little bit of reasearch and found some info about how bad blocks are managed (so called bad block management)

QUOTE

Bad Blocks are blocks that contain one or more invalid bits whose reliability is not guaranteed. Bad Blocks
may be present when the device is shipped, or may develop during the lifetime of the device.
Devices with Bad Blocks have the same quality level and the same AC and DC characteristics as devices
where all the blocks are valid. A Bad Block does not affect the performance of valid blocks because it is
isolated from the bit line and common source line by a select transistor.
[...]
 

QUOTE

[...]
During the lifetime of the NAND device additional Bad Blocks may develop. The NAND devices have a
Status Register that indicates whether an operation is successful or not. If attempts to program or erase
a block give errors in the Status Register, the block is marked as bad.
A block can also be marked as bad when the Error Correction Code (EEC) algorithm detects two or more
errors and can correct only one. In this case, the ECC marks the block as bad and the Bad Block Management
software re-maps the block address by allocating a new block.
As the failure of a page program operation does not affect the data in other pages in the same block, the
block can be replaced by re-programming the current data and copying the rest of the replaced block to
an available valid block.
[...]

Now there are two methods to replace the block.


1. Skip Block Method
2. Reserve Block Method


Like i saw on several other Post and tutorials the bad blocks recognized wir remap software were moved to the end of the nand (thats where the reserved block area is)

QUOTE

Reserve Block Method

In this method Bad Blocks are not skipped but replaced by good blocks by “re-directing” the Flash
Translation Layer to a known good block. For that purpose, the Bad Block Management software creates
two areas in the NAND Flash: the User Addressable Block Area and the Reserved Block Area.

The Flash Translation Layer can use the User Addressable Block Area to store data whereas the Reserved
Block Area is only used for Bad Block replacement and to save the Bad Block Table that also
keeps track of the re-mapped “developed Bad Blocks”.
[...]

So i would say that the method where you manualy read the blocks from the immage that would be written to a badblock and instead write them to the end of the nand should be right.

Post mentioned Above: Press Me Hard

For more info take a look at these files:

CODE

http://www.xeltek.com/software/nandflash/nand_flash_guide.pdf
http://www.samsung.com/global/business/semiconductor/products/flash/downloads/xsr_v15_badblockmgmt_application_note.pdf
http://www.eetasia.com/ART_8800354680_499486_AN_126bb8ac.HTM

[h4z3r]

thx mate, still flashing , hope it will work

[iateshaggy]

sounds like fun.  i'm dumping my new jasper and keep getting errors 250 or 210 on blocks 8F0-8FF and 28F8.

[h4z3r]

*UPDATE*
flash is working perfectly, xbr is booting fine. and gentoo is running without problems.

but sometimes xbr is stuck, i turn the console on, and nothing happens, or the starting light ring is stuck, is it an problem with xbr , or problem with my flash ? annyone had the same issues?  

[doveman007]

I've got a bad block 10 on my Jasper 512MB which is stopping Xell from working.

I tried flashing Xell block 10 to 7fff but that didn't work, and the original dump of that block only contains FFs anyway, so I didn't really expect it to.

Looking at the diagram here, it would seem that bad blocks are remapped to FE0-FFF, but I tried flashing Xell block 10 to FFF and that didn't work either.

So if anyone can help me work out where I need to flash block 10 to, I'd appreciate it as this is doing me 'ead in  

[doveman007]

Sorted. Props to Looouky and diddy147

http://forums.xbox-s...o...d=4631596