Jtag Jasper issue

[seanr28]

I have an issue with a jtagged jasper that I completed about a year ago, for a friend

Its was jtagged using the AuD_clamp and TRay_open method.

It was working fine, until my mate tried to update the freeboot image, this failed and the console now just sits there with a black screen and flashing middle led (no dvd drive present)

ANyway I manged to find the original Nand dumps, I sucessfully flashed it back and it boots to normal dash (7371) without any issues at all, however when you try to see memory options from the menu (mem card) etc it just sits there and does nothing (its a 256Mb Jasper) so I guess tha the nand could be partially corrupt??

using the orginal nand dumps I have tried all availbale tool to create the correct freeboot image, but none of them do anything, just sits there with black screen and middle led flashing.....I have tried several times and no matter what I do i get the same issue. I have since flashed back the original nand and its working again up until the memory card issue.

The orginal dumps I have a 256Mb images ( I know that I could have just dumped the first 64mb, this was done some time ago before I realised), both nand dumps have O mis-mactches.

Any ideas please?

just got xell to boot but get this....

 

[Martin C]

Re: Jtag Jasper issue - FAO Martin C

lol I'm being hollered in Topics now

Flash Xell to it - should be the first thing you do. Make sure it boots.

 

[seanr28]

Re: Jtag Jasper issue - FAO Martin C

as above, must have been updating whislt you were typing

 

[Martin C]

Re: Jtag Jasper issue - FAO Martin C

Let's see if we can get Freeboot working. We'll then worry about the onboard MU.

Xell will fail with the kv because you don't have it in the xell build - don't worry about this.

Is that Xell or Xellous? If Xell, reflash with Xellous.

Did you get a 64MB freeboot build out of whatever tool you used? If so, rename the built freeboot (with AUD_CLAMP and TRAY_OPEN) to updflash.bin. Put it on a USB stick and let Xellous flash it for you.

 

[seanr28]

Re: Jtag Jasper issue - FAO Martin C

Martin,

I have done as you have described and now have freeboot working Thankyou.


Why did this make a difference than using Nandx to flash?

Strangly enough it sees one profile, but when you goto memory, it reports no storage devices??

 

[Martin C]

Re: Jtag Jasper issue - FAO Martin C

it failed because unfortunately, it only takes a small amount of interference during the write process to throw out a block. We don't verify the blocks during the write, which is probably something we should build into Nandpro (using the collective 'we' here, not my program!).

Writing via XeLL and USB eliminates this and would suggest to anyone having issues with writing back when they are booting ok to XeLL to do so via USB.

As for the MU, try to erase it via NANDpro:

nandpro usb: -e512 1000

I know you said it's a 256 but in case it's not, this will do it for both. If it errors halfway through you know it's a 256! Either way, blocks from 0x1000 upwards will be erased.

 

[seanr28]

martin, thankyou.

Very odd though, done exactly as you said above and had no power to console (still able to wriet to the nand though)

C:\Nandpro30>nandpro usb: -e512 1000
NandPro v3.0a by Tiros
Looking for usb interface device
Flash Config: 0x008A3020
Block Size: 128KB Block Limits: 0x001000..0x007FFF
File:
Erasing
Error: 202 erasing block 12A0
Error: 202 erasing block 20F0
Error: 202 erasing block 3FE8
Error: 202 erasing block 3FF8
Error: 202 erasing block 52A0
Error: 202 erasing block 60F0
Error: 202 erasing block 7FE8
Error: 202 erasing block 7FF8
7FFF
C:\Nandpro30>

 

[Martin C]

Write back the other NAND you created but put

nandpro usb: -w64 nand.bin 0 1000

(shouldn't need the '0 1000' part but put anyway)

 

[seanr28]

forgot to mention, the fans were also at full speed at this point

Tried writing image back and get black screen again, I also tried writing back just xell and xellous but the same?????

how come erasing at the MU card level has caused this to happen?

 

[Martin C]

It hasn't - the issue is you're having problems writing to your NAND.

Keep your NAND wires away from anything else and certainly away from any power sources.

Try writing back Xell like this until you get it booting again, then go for the updflash.bin option. If you need to trim your nand, use this:

nandpro nand.bin: -r64 newnand.bin

 

[seanr28]

Martin, your a legend, finally got it going and the MU is fine.

I have been doing this for a couple of years now and I have never had issues writing to the nand before......and everything has always been done in exactly the same place..verry odd.


Thanks again for all you hlep.....

 

[garageinc]

glad its sorted mate. i followed this thread and it was great for learning, thanks to you both. martins knowledge is unreal on anything jtag and now rgh and yours is coming along nicely too mate. i pick up so much info from you both i just had to say thanks for it all

 

[seanr28]

thanks, thats the best way to learn, I generally spend quite a a bit of time on here just to learn....generally dont have too many issues myself but when I have done Martin as always sorted it

 

[garageinc]

totaly agree mate. i'm getting pretty clued up on everything xbox thanks to guys like yourself and martin. everything i know pretty much has come from here. its been days and days of reading but every minute worth it. i'm just waiting on a new nand x and i'll be good to go on these and got the whole family lined up except zephyr so look forward to putting this knowledge to good use.
just done my first reball and god damn the thing booted green i'm bouncing round the house lmao.
thanks again matey.

 

[Martin C]

Am ok to close this thread now before my head gets any bigger ?

 

[diaboliq20]

be fair Martin - you do appear to be a god among mortals here lol.....

 

[garageinc]

sod it mate lap it up

 

[seanr28]

yes please....

 

[Martin C]

Closed!