R-JTAG Jasper Full dump and soldering quality check

MrKronic

Full Member
Jun 2, 2013
70
0
Hi,

I've recently started doing the R-JTAG mod by myself. So far I came across a couple of problems and have some queries that need to be answered.

My first board is a Jasper BB with a 512mb NAND, of which I made 4 normal dumps and 2 full dumps. Although I didn't have any problems with the normal dumps, I encountered an error with the full dumps which looks like this:

===================================================
Wednesday, April 30, 2014 12:46:55 AM


J-Runner v0.3 Beta (1) Started




WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button




Version v0.3 Beta (4) is available for download.
Checking Files
Finished Checking Files
Version: 10
Flash Config: 0x00AA3020
CB Version: 6754
Version: 10
Flash Config: 0x00AA3020
CB Version: 6754
Jasper 512MB Manually Selected
Reading Nand to C:\Users\Mista Kronic\Desktop\J-Runner\output\nanddump1.bin
Reading Nand
Done!
in 13:19 min:sec


Reading Nand to C:\Users\Mista Kronic\Desktop\J-Runner\output\nanddump2.bin
Initializing nanddump1.bin..
Jasper BB
Reading Nand
Jtag Selected
Nand Initialization Finished
Done!
in 13:19 min:sec


Reading Nand to C:\Users\Mista Kronic\Desktop\J-Runner\output\nanddump3.bin
Comparing...Takes a while on big nands
Reading Nand
Nands are the same
Done!
in 13:19 min:sec


Reading Nand to C:\Users\Mista Kronic\Desktop\J-Runner\output\nanddump4.bin
Comparing...Takes a while on big nands
Reading Nand
Nands are the same
Done!
in 13:19 min:sec


Comparing...Takes a while on big nands
Nands are the same
Version: 10
Flash Config: 0x00AA3020
CB Version: 6754
Jasper 512MB Manually Selected
Reading Nand to C:\Users\Mista Kronic\Desktop\J-Runner\output\nanddump1.bin
Reading Nand
Error: 250 reading block 1828
Done!
in 106:17 min:sec


Reading Nand to C:\Users\Mista Kronic\Desktop\J-Runner\output\nanddump2.bin
Initializing nanddump1.bin..
Reading Nand
Jasper 512MB
Nand Initialization Finished
Error: 250 reading block 1828
Done!
in 106:05 min:sec


Comparing...Takes a while on big nands
Nands are the same
===================================================



My question is, will that affect the Xell image/retail image in any way if I try to build one using the full dumps? I want to be sure on its safety before I progress onto writing Xell into the NAND....

Also, regarding the POST qsbs.... How can I ensure a perfect connection with the qsb and the mobo? Will a continuity test be enough or do I take readings at specific voltages/amps?

Here are the pics of the solder job. Please don't hesitate to point out any problems. Thanks in advance....
 
Last edited:

ultimate360

VIP Member
Nov 11, 2013
786
48
MN, USA
You will be fine, that error is not in the first 50 blocks so xell will boot up fine. Yes, you can build an image off the full dumps. I have gotten this error on many jasper bb's, it won't affect anything unless it's in the first 50 blocks, so you're okay. Your post soldering looks ok and seems to be connected, but it looks like a few points could use some more flux and a quick touch up so they get shiny. Nand wires should be fine since you were able to get valid dumps.
 

MrKronic

Full Member
Jun 2, 2013
70
0
Thanks for the quick response. What if I need to return back to retail ? Won't I need to use the full dump to make the retail image then?

Also how can I check whether my POST points ( in general) are perfectly soldered? For this one, I used a meter to check for continuity from the points under the CPU heatsink and the corresponding points on the ribbon cable. The results turned out fine, but will that be enough of a confirmation?
 

MrKronic

Full Member
Jun 2, 2013
70
0
Thanks for the quick response. What if I need to return back to retail ? Won't I need to use the full dump to make the retail image then?

Also how can I check whether my POST points ( in general) are perfectly soldered? For this one, I used a meter to check for continuity from the points under the CPU heatsink and the corresponding points on the ribbon cable. The results turned out fine, but will that be enough of a confirmation?
And what about the POST continuity check?
 

MrKronic

Full Member
Jun 2, 2013
70
0
Ah, nice of you to intervene Martin C, and quite a timely one too, because I think there is a bigger problem......

Basically I just flashed the Xell image to the NAND and installed all the other QSBs and the alt cpu_rst point and everything and checked for continuity with the multimeter. However when I tried to run the console, the R-JTAG chip flashes green approximately 3-4 times and then it RRODs with the error code 0022 (which is for no proper NAND image in the NAND, i presume?). So, I ran a POST monitor test afterwards which gave me the following result:

===================================================
Friday, May 02, 2014 12:48:30 AM


J-Runner v0.3 Beta (4) Started


Checking Files
Finished Checking Files
Initializing nanddump1.bin..
Jasper BB
Jtag Selected
Nand Initialization Finished
Comparing...Takes a while on big nands
Nands are the same
Checking Console..
Version: 10
Flash Config: 0x00AA3020
00AA3020
Jasper 512MB
CB Version: 6754
Aud_Clamp Selected
R-Jtag Selected
Creating Directory C:\Users\Mista Kronic\Downloads\J-Runner\xeBuild\16747\bin
Downloaded *xeBuild/16747/bin/addon.idx
Downloaded *xeBuild/16747/bin/nofcrt.bin
Downloaded *xeBuild/16747/bin/nohdd.bin
Downloaded *xeBuild/16747/bin/nohdmiwait.bin
Downloaded *xeBuild/16747/bin/nointmu.bin
Downloaded *xeBuild/16747/bin/nolan.bin
Downloaded *xeBuild/16747/bin/patches_falcon.bin
Downloaded *xeBuild/16747/bin/patches_fat.bin
Downloaded *xeBuild/16747/bin/patches_g2corona.bin
Downloaded *xeBuild/16747/bin/patches_g2falcon.bin
Downloaded *xeBuild/16747/bin/patches_g2jasper.bin
Downloaded *xeBuild/16747/bin/patches_g2mcorona.bin
Downloaded *xeBuild/16747/bin/patches_g2mtrinity.bin
Downloaded *xeBuild/16747/bin/patches_g2trinity.bin
Downloaded *xeBuild/16747/bin/patches_g2zephyr.bin
Downloaded *xeBuild/16747/bin/patches_jasper.bin
Downloaded *xeBuild/16747/bin/patches_trinity.bin
Downloaded *xeBuild/16747/bin/patches_xenon.bin
Downloaded *xeBuild/16747/bin/patches_zephyr.bin
Downloaded *xeBuild/16747/su20076000_00000000
Downloaded *xeBuild/16747/readme.txt
Downloaded *xeBuild/16747/_glitch.ini
Downloaded *xeBuild/16747/_glitch2.ini
Downloaded *xeBuild/16747/_glitch2m.ini
Downloaded *xeBuild/16747/_jtag.ini
Downloaded *xeBuild/16747/_retail.ini
Creating Directory C:\Users\Mista Kronic\Downloads\J-Runner\xeBuild\common
Downloaded *xeBuild/common/cba_13121.bin
Downloaded *xeBuild/common/cba_13180.bin
Downloaded *xeBuild/common/cba_13181.bin
Downloaded *xeBuild/common/cba_1925.bin
Downloaded *xeBuild/common/cba_1926.bin
Downloaded *xeBuild/common/cba_1927.bin
Downloaded *xeBuild/common/cba_1928.bin
Downloaded *xeBuild/common/cba_1941.bin
Downloaded *xeBuild/common/cba_1942.bin
Downloaded *xeBuild/common/cba_4559.bin
Downloaded *xeBuild/common/cba_4560.bin
Downloaded *xeBuild/common/cba_4561.bin
Downloaded *xeBuild/common/cba_4562.bin
Downloaded *xeBuild/common/cba_4569.bin
Downloaded *xeBuild/common/cba_4574.bin
Downloaded *xeBuild/common/cba_4575.bin
Downloaded *xeBuild/common/cba_4576.bin
Downloaded *xeBuild/common/cba_4577.bin
Downloaded *xeBuild/common/cba_5772.bin
Downloaded *xeBuild/common/cba_5773.bin
Downloaded *xeBuild/common/cba_5774.bin
Downloaded *xeBuild/common/cba_6752.bin
Downloaded *xeBuild/common/cba_6753.bin
Downloaded *xeBuild/common/cba_6754.bin
Downloaded *xeBuild/common/cba_7377.bin
Downloaded *xeBuild/common/cba_7378.bin
Downloaded *xeBuild/common/cba_9188.bin
Downloaded *xeBuild/common/cba_9188_mfg.bin
Downloaded *xeBuild/common/cba_9230.bin
Downloaded *xeBuild/common/cba_9231.bin
Downloaded *xeBuild/common/cbb_13121.bin
Downloaded *xeBuild/common/cbb_13180.bin
Downloaded *xeBuild/common/cbb_13181.bin
Downloaded *xeBuild/common/cbb_1925.bin
Downloaded *xeBuild/common/cbb_1926.bin
Downloaded *xeBuild/common/cbb_1927.bin
Downloaded *xeBuild/common/cbb_1928.bin
Downloaded *xeBuild/common/cbb_1941.bin
Downloaded *xeBuild/common/cbb_1942.bin
Downloaded *xeBuild/common/cbb_4559.bin
Downloaded *xeBuild/common/cbb_4560.bin
Downloaded *xeBuild/common/cbb_4561.bin
Downloaded *xeBuild/common/cbb_4562.bin
Downloaded *xeBuild/common/cbb_4569.bin
Downloaded *xeBuild/common/cbb_4574.bin
Downloaded *xeBuild/common/cbb_4575.bin
Downloaded *xeBuild/common/cbb_4576.bin
Downloaded *xeBuild/common/cbb_4577.bin
Downloaded *xeBuild/common/cbb_5772.bin
Downloaded *xeBuild/common/cbb_5773.bin
Downloaded *xeBuild/common/cbb_5774.bin
Downloaded *xeBuild/common/cbb_6752.bin
Downloaded *xeBuild/common/cbb_6753.bin
Downloaded *xeBuild/common/cbb_6754.bin
Downloaded *xeBuild/common/cbb_7377.bin
Downloaded *xeBuild/common/cbb_7378.bin
Downloaded *xeBuild/common/cbb_9188.bin
Downloaded *xeBuild/common/cbb_9230.bin
Downloaded *xeBuild/common/cbb_9231.bin
Downloaded *xeBuild/common/cb_1921.bin
Downloaded *xeBuild/common/cb_1922.bin
Downloaded *xeBuild/common/cb_1923.bin
Downloaded *xeBuild/common/cb_1940.bin
Downloaded *xeBuild/common/cb_4558.bin
Downloaded *xeBuild/common/cb_4571.bin
Downloaded *xeBuild/common/cb_4572.bin
Downloaded *xeBuild/common/cb_4578.bin
Downloaded *xeBuild/common/cb_4579.bin
Downloaded *xeBuild/common/cb_5770.bin
Downloaded *xeBuild/common/cb_5771.bin
Downloaded *xeBuild/common/cb_6723.bin
Downloaded *xeBuild/common/cb_6750.bin
Downloaded *xeBuild/common/cb_7373.bin
Downloaded *xeBuild/common/cb_7375.bin
Downloaded *xeBuild/common/cd_12905.bin
Downloaded *xeBuild/common/cd_13180.bin
Downloaded *xeBuild/common/cd_13181.bin
Downloaded *xeBuild/common/cd_1921.bin
Downloaded *xeBuild/common/cd_1925.bin
Downloaded *xeBuild/common/cd_1926.bin
Downloaded *xeBuild/common/cd_1927.bin
Downloaded *xeBuild/common/cd_1928.bin
Downloaded *xeBuild/common/cd_1941.bin
Downloaded *xeBuild/common/cd_1942.bin
Downloaded *xeBuild/common/cd_4558.bin
Downloaded *xeBuild/common/cd_4559.bin
Downloaded *xeBuild/common/cd_4560.bin
Downloaded *xeBuild/common/cd_4561.bin
Downloaded *xeBuild/common/cd_4562.bin
Downloaded *xeBuild/common/cd_4569.bin
Downloaded *xeBuild/common/cd_4574.bin
Downloaded *xeBuild/common/cd_4575.bin
Downloaded *xeBuild/common/cd_4576.bin
Downloaded *xeBuild/common/cd_5770.bin
Downloaded *xeBuild/common/cd_5773.bin
Downloaded *xeBuild/common/cd_5774.bin
Downloaded *xeBuild/common/cd_6723.bin
Downloaded *xeBuild/common/cd_6753.bin
Downloaded *xeBuild/common/cd_6754.bin
Downloaded *xeBuild/common/cd_7377.bin
Downloaded *xeBuild/common/cd_7378.bin
Downloaded *xeBuild/common/cd_8453.bin
Downloaded *xeBuild/common/cd_9230.bin
Downloaded *xeBuild/common/cd_9231.bin
Downloaded *xeBuild/common/cd_9452.bin
Downloaded *xeBuild/common/ce_1888.bin
Downloaded *xeBuild/common/cf_4532.bin
Downloaded *xeBuild/common/cg_4532.bin
Downloaded *xeBuild/common/xenonclatin.xtt
Downloaded *xeBuild/common/xenonjklatin.xtt
Downloaded *xeBuild/common/ximedic.xex
Finished Checking Files
R-Jtag de-Selected
Aud_Clamp de-Selected
Checking Console..
Version: 10
Flash Config: 0x00AA3020
00AA3020
Jasper 512MB
CB Version: 6754
Checking Console..
Version: 10
Flash Config: 0x00AA3020
00AA3020
Jasper 512MB
CB Version: 6754
XeLL file created Successfully jasper_bb.bin
Checking Console..
Version: 10
Flash Config: 0x00AA3020
00AA3020
Jasper 512MB
CB Version: 6754
Version: 10
Flash Config: 0x00AA3020
Writing Nand
jasper_bb.bin
Done!
in 0:18 min:sec


Device not found.
Version: 10
Press Escape to exit
Waiting for POST to change
Post 10 - Payload/1BL started
Post 0C
Post 11 - FSB_CONFIG_PHY_CONTROL
Post 12 - FSB_CONFIG_RX_STATE
Post 15 - FETCH_OFFSET
Post 18 - FETCH_CONTENTS
Post 19 - HMACSHA_COMPUTE
Post 1A - RC4_INITIALIZE
Post 1B - RC4_DECRYPT
Post 1C - SHA_COMPUTE
Post 1D - SIG_VERIFY
Post A0 - Panic - VERIFY_SECOTP_6
Post 10 - Payload/1BL started
Post 11 - FSB_CONFIG_PHY_CONTROL
Post 12 - FSB_CONFIG_RX_STATE
Post 15 - FETCH_OFFSET
Post 18 - FETCH_CONTENTS
Post 1A - RC4_INITIALIZE
Post 1B - RC4_DECRYPT
Post 1C - SHA_COMPUTE
Post 1D - SIG_VERIFY
Post 1E - BRANCH
Post A0 - Panic - VERIFY_SECOTP_6
Post 11 - FSB_CONFIG_PHY_CONTROL
Post 12 - FSB_CONFIG_RX_STATE
Post 15 - FETCH_OFFSET
Post 18 - FETCH_CONTENTS
Post 1B - RC4_DECRYPT
Post 1C - SHA_COMPUTE
Post 1D - SIG_VERIFY
Post A0 - Panic - VERIFY_SECOTP_6
Post 11 - FSB_CONFIG_PHY_CONTROL
Post 12 - FSB_CONFIG_RX_STATE
Post 15 - FETCH_OFFSET
Post 18 - FETCH_CONTENTS
Post 1B - RC4_DECRYPT
Post 1C - SHA_COMPUTE
Post 1D - SIG_VERIFY
Post A0 - Panic - VERIFY_SECOTP_6
Post 10 - Payload/1BL started
Post 11 - FSB_CONFIG_PHY_CONTROL
Post 12 - FSB_CONFIG_RX_STATE
Post 15 - FETCH_OFFSET
Post 18 - FETCH_CONTENTS
Post 19 - HMACSHA_COMPUTE
Post 1A - RC4_INITIALIZE
Post 1B - RC4_DECRYPT
Post 1C - SHA_COMPUTE
Post 1D - SIG_VERIFY
Post A0 - Panic - VERIFY_SECOTP_6


===================================================
Friday, May 02, 2014 3:03:20 AM


J-Runner v0.3 Beta (4) Started




WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button




Checking Files
Finished Checking Files
Initializing nanddump1.bin..
Jasper BB
Jtag Selected
Nand Initialization Finished
Checking Console..
Version: 10
Flash Config: 0x00000000
Can not Continue
Can not continue
Checking Console..
Version: 00
Wrong Version.
Can not continue
Jasper 512MB Manually Selected
Version: 00
Wrong Version.
Version: 00
Wrong Version.


===================================================
After the POST test ended, I shut off the console and shutdown the PC (power issues). After this, J-Runner doesn't detect the console at all anymore.....What could be the issue? :(
 

Attachments

Last edited:

AllyNerd

VIP Member
Feb 25, 2013
1,179
0
Philadelphia
Reseat your cables. Of course for the Rrod have u tried all the combinations(dip settings voltages) as per the installation guide?
 

The Result

Senior Member
Jan 15, 2014
128
0
Dayton, Ohio
I'm not sure of your problem but im sure you will get help you are probably getting those nand errors because of your soldering of the nand wires, they are not horrible but could be better. Although your yellow looks pretty f**ked up
 

nofeloniesyet

VIP Member
Jan 16, 2011
4,830
128
Nowhere
I'm not sure of your problem but im sure you will get help you are probably getting those nand errors because of your soldering of the nand wires, they are not horrible but could be better. Although your yellow looks pretty f**ked up
yea you actually didnt do too bad on the soldering,but some of the spi points do look to be cold soldered,touch em up a tad,also make sure your nand reading device shows up in jrunner after u plug it up to pc.ive had to reflash the hex files to i dont know haw many jr programmers in the past after issues like these.it may be the pic also but the post qsb looks like it has a couple cold soldered to it as well.again,not bashing,your solder def looks a thousand times better than some you see on here,just use some flux and touch em up a tad :)
 

MrKronic

Full Member
Jun 2, 2013
70
0
Reseat your cables. Of course for the Rrod have u tried all the combinations(dip settings voltages) as per the installation guide?
Haven't tried that yet, the dip settings are set to the standard 7-8 ON, others OFF combo. Will give it a shot right now..... :)

yea you actually didnt do too bad on the soldering,but some of the spi points do look to be cold soldered,touch em up a tad,also make sure your nand reading device shows up in jrunner after u plug it up to pc.ive had to reflash the hex files to i dont know haw many jr programmers in the past after issues like these.it may be the pic also but the post qsb looks like it has a couple cold soldered to it as well.again,not bashing,your solder def looks a thousand times better than some you see on here,just use some flux and touch em up a tad :)
Thanks a lot....Yes, I do admit my soldering looks real sh*tty, but I blame it on the equipment I have which is unfortunately the best I can manage :/ (especially the 30W soldering iron i own with a fairly thick tip that's definitely NOT suited for fine work). Hence the butchered yellow wire and the cold joints on the POST qsbs.... :/

Now I have several suspicions regarding the boot failure. Could it be that I refitted the DVD drive to the console before doing the Xell boot or is the because of using the alt CPU_RST point topside?
 
Last edited: