Print

[whitey76]

Double check all or your soldering points on the cable. I believe the error 250 is pretty common, so its nothing major that cant be fixed, but it really sounds like you should check the solder joints on the cable.

[Treadstone]

Hi as long as you  have the error in the same place in all 3 dumps,you should be ok.Open your nand image in badblock remover and it will move it to a spare area of the nand, if you don't move it you will have problems

[Arlen777]

QUOTE(an2ny0515 @ Mar 31 2010, 02:49 PM)

hellow guy's, I jtag my 4th xenon box and i get an Error:250 reading block 016, i dump it 3times and get a same results, and did get an error 202 programming block 016. this is my firts time to see this error and i don't dont what to do, I hope somebody help's me.
sorry for my bad english....

i had the same problem with xenon here is what solved it
get bad block mover, press analyze microsoft image, it will find bad blocks, then press reposition bad blocks and choose xbr image

[jview]

use a better gnd point.

worked for me, when writing.,

[ZerOneX]

If your XBR or FreeBOOT does not work properly because this badblock, you should try flash it with Linux + XBRFlash.

It was the only solution that worked fine for me in one of my xenon consoles with bad blocks between 0x00 and 0x90 (critical area)

[m00nstone]

So... I have spent the last 2 days trying to boot Xell on a Jasper 256MB. I get an error 250 at block 20. Xell install always returns a black screen. I can then reflash my original nand and I'm back to square one.

Everything I've read so far is telling me that I need to remap bad blocks to get Xell going but even with that done I will only be able to flash XBReboot with a "Debian v5.0 Mini LiveCD" – Free60 disc. If true, will I be able to install freeboot after following that process?

I've read about XBReboot shortcomings and I'm also worried about lack of support due to the growth of Freeboot.

BTW I seem to be able to read/write ok, but should I still be concerned about my soldering?