Jasper BB with bad blocks and confirmation

[Maximize]

ok there isnt a nandpro forum so Ill put this here.

I am working on a RGH1 jasper 256mb with 13146 dash.

It has bad blocks in the 600+ range.

this thread is to get you all to stroke my ego and tell me that the location and error codes are ok and I can go further.

I have done quite a few rgh and jtag's but I like to be safe.

here is the log it shows (in the 600's) error 250 at a block then quite a few error 210's then much later a error 204 at a block in the Dxx's.

Its my understanding that the 250/210's with BB's is that the block is empty but I do not know about the error 204's never seen one yet.

you will also see a bad block and its remapped location in the log.

let me know what you think and please properly cool my nerves. Thanks Guys.

log starts:

===================================================
Friday, June 29, 2012 7:51:21 PM

J-Runner v0.2 Beta (276) Started



Version v0.2 Beta (278) is available for download.
Checking Files
Downloaded *common/Pics/slim_install_diagram_final.jpg
Downloaded *common/Pics/phat_install_diagram_final.jpg
Downloaded *xeBuild/options.ini
Downloaded *xeBuild/readme.txt
Downloaded *xeBuild/data/options.ini
Downloaded *xeBuild/launch.xex
Downloaded *xeBuild/lhelper.xex
Downloaded *xeBuild/xeBuild.exe
Downloaded *J-Runner_UserGuide.pdf
Finished Checking Files
Downloaded *xeBuild/14719/bin/patches_falcon.bin
Downloaded *xeBuild/14719/bin/patches_fat.bin
Downloaded *xeBuild/14719/bin/patches_g2falcon.bin
Downloaded *xeBuild/14719/bin/patches_g2jasper.bin
Downloaded *xeBuild/14719/bin/patches_g2trinity.bin
Downloaded *xeBuild/14719/bin/patches_g2zephyr.bin
Downloaded *xeBuild/14719/bin/patches_jasper.bin
Downloaded *xeBuild/14719/bin/patches_trinity.bin
Downloaded *xeBuild/14719/bin/patches_xenon.bin
Downloaded *xeBuild/14719/bin/patches_zephyr.bin
Downloaded *xeBuild/14719/_glitch.ini
Finished Checking Files
Version: 03

Flash Config: 0x008A3020
Jasper 256MB
Reading Nand to C:\Users\Clint\Desktop\130537_jrun271\J-Runner v0.2 Beta 271\output\nanddump1.bin
Reading Nand
Error: 250 reading block 630
Error: 210 reading block 631
Error: 210 reading block 632
Error: 210 reading block 633
Error: 210 reading block 634
Error: 210 reading block 635
Error: 210 reading block 636
Error: 210 reading block 637
Error: 204 reading block D54
Done!

Reading Nand to C:\Users\Clint\Desktop\130537_jrun271\J-Runner v0.2 Beta 271\output\nanddump2.bin
Initializing Nand..
Reading Nand
Nand Initialization Finished
Error: 250 reading block 630
Error: 210 reading block 631
Error: 210 reading block 632
Error: 210 reading block 633
Error: 210 reading block 634
Error: 210 reading block 635
Error: 210 reading block 636
Error: 210 reading block 637
Error: 204 reading block D54
Done!

Comparing...Takes a while on big nands
Bad Block ID @ 0x00C6 [Offset: 0x1986000]
Bad Block ID 00C6 Found @ 0x01FF [Offset: 0x41DF000]
Block ID 01FF [Offset: 0x41DF000] remapped to Block ID 00C6 [Offset: 0x1986000]
Bad Blocks Remapped
Bad Block ID @ 0x00C6 [Offset: 0x1986000]
Bad Block ID 00C6 Found @ 0x01FF [Offset: 0x41DF000]
Block ID 01FF [Offset: 0x41DF000] remapped to Block ID 00C6 [Offset: 0x1986000]
Bad Blocks Remapped
Nands are the same

 

[LoneWolf913]

There is, however, a J-Runner forum Either way, you're fine, the only bad block was found remapped properly elsewhere in the image, so you're good to go.

 

[Maximize]

I accept your answer, BUT does j runner give reasons for such errors? since it is a nandpro error. I would assume they do but I am unaware..

thanks again

 

[LoneWolf913]

All the listed errors are just issues with the nand chip, it's not uncommon on big-block nands, those are all damaged blocks in the memory unit area, so nothing to worry about. If you're looking for a master error code list, I don't believe there is one.

 

[Maximize]

ok so I went ahead and flashed 15574 rgh dash and I get e79 everytime. I tried multiple builds and flashed them all.

I am using jrunner 278, and flashing with rawflash.

Is there a reason jrunner is no longer putting out a xenon.elf file ?

should I try flashing with nandx ?