Report Bugs / Give Suggestions: J-Runner - Build 283

[BraveH43]

To try to maintain a single sensible thread, Please use this one to report any bugs within the latest current version (Build 283)

This is not to be used for those who are just struggling to get their botched wiring or misunderstanding of the process answered - if you have those issues please open your own thread!

This thread is to be used to report an actual bug! or make sensible suggestions for the current build.

Upon release of new version this thread will be closed and another made in its place.

 

[stj2112]

Just one small suggestion

I have done many RGH installs and never until my last mod came across reading a orig nand with bad blocks

I had probs with a Trinity RGH & Demon install because of bad blocks detected.
I was making glitch images for the Demon side that were not booting and didn't know why.
It was because of bad blocks in orig nand read.

My suggestion is just to have the bad block tab on J Runner change colour (Say Red) or a little yellow warning triangle appear on bad block tab when they are detected just to highlight the fact bad blocks have been found.

I would find this very usefull

Thanx

 

[Oggy]

Bad blocks take up a large portion of the log window, no excuse for not noticing them to be fair. That's not to say a warning icon couldn't be added though!

 

[stj2112]

Bad blocks take up a large portion of the log window, no excuse for not noticing them to be fair. That's not to say a warning icon couldn't be added though!

Yea thanks OggyUK fair comment
Will always now pay more attention now to the log window

 

[Martin C]

1. SMC Config doesn't seem to be displaying correctly for Corona 4GB boards.

Different offset for 16MB (0x00FEB800) and 4GB (0x02FF0000). Length of 0x10000 is the same (64kb).

2. FCRT.bin doesn't extract from a NAND without headers as the offset isn't known. It can be calculated by searching for 3E C0 00 00 01 40 in the dump, going back 0x11A and then grabbing a length of 0x400 (16kb). The 3E C0 00 00 01 40 could definitely be used as an offset checker.

I've not been sitting on these BTW - only found out in the last 30 mins or so.

---------- Post added at 16:01 ---------- Previous post was at 15:58 ----------

Yea thanks OggyUK fair comment
Will always now pay more attention now to the log window

Bad blocks are NOT an issue.

Provided your NAND dump is complete with a good header and both dumps match, you should be good to go.

All remapping of blocks is done by the software (where needed). I think there's a genuine case to replace 'write NAND' function with the one for the 'Write Fusion NAND' though. Just need to ensure that 'noremap' has been ticked from the xebuild first (or it'll be offsetting and empty block).

 

[sarah1331]

CPU scan folders doesn't work already reported just so you don't miss it buddy

 

[Martin C]

I think an option to build an RGH / JTAG image with an amended Console ID / Serial Number might be pretty cool. You only need to change 1 number in both. It would ensure you weren't connecting to XBL accidentally, especially if Dashlaunch isn't doing the job.

 

[stefanounick]

1. SMC Config doesn't seem to be displaying correctly for Corona 4GB boards.

Different offset for 16MB (0x00FEB800) and 4GB (0x02FF0000). Length of 0x10000 is the same (64kb).

2. FCRT.bin doesn't extract from a NAND without headers as the offset isn't known. It can be calculated by searching for 3E C0 00 00 01 40 in the dump, going back 0x11A and then grabbing a length of 0x400 (16kb). The 3E C0 00 00 01 40 could definitely be used as an offset checker.

I've not been sitting on these BTW - only found out in the last 30 mins or so.

---------- Post added at 16:01 ---------- Previous post was at 15:58 ----------



Bad blocks are NOT an issue.

Provided your NAND dump is complete with a good header and both dumps match, you should be good to go.

All remapping of blocks is done by the software (where needed). I think there's a genuine case to replace 'write NAND' function with the one for the 'Write Fusion NAND' though. Just need to ensure that 'noremap' has been ticked from the xebuild first (or it'll be offsetting and empty block).

I think an option to build an RGH / JTAG image with an amended Console ID / Serial Number might be pretty cool. You only need to change 1 number in both. It would ensure you weren't connecting to XBL accidentally, especially if Dashlaunch isn't doing the job.

hmm, tried 3 different 4GB nands with smc config and it was displaying properly

what do you mean with no header?

i wouldnt trust it with all those users :/
im sure they will try to create a retail nand from that image and it wont work

 

[Martin C]

Did you try to extract the smc-config too?

No header meaning an ECC image. The offsets are stored in that part of the NAND and invariably the FCRT.bin extracted isn't correct.

 

[stefanounick]

that should be fixed if it wasnt already

 

[Martin C]

not fixed in release version..

https://www.dropbox.com/s/b981q4mf8hp7q4e/SMC Corona 4gb.jpg

 

[Krafter]

It would be nice to be able to associate a nick with a serial number/key in both the DB and folder name.

 

[LoneWolf913]

It would be nice to be able to associate a nick with a serial number/key in both the DB and folder name.

Here here, that'd be great. Label 'em by username, or email, or something.

Also I know this is me being lazy, but seeing as J-Runner already knows what CBs are RGH1 or 2, why doesn't it auto-detect JTAG CBs and select the JTAG radio button for us? I know I've forgotten to click the button once or twice and accidentally built a glitch image before checking the log and re-building..

 

[Martin C]

Here here, that'd be great. Label 'em by username, or email, or something.

Also I know this is me being lazy, but seeing as J-Runner already knows what CBs are RGH1 or 2, why doesn't it auto-detect JTAG CBs and select the JTAG radio button for us? I know I've forgotten to click the button once or twice and accidentally built a glitch image before checking the log and re-building..

Yep, it's you being lazy :tongue:

 

[BraveH43]

not fixed in release version..

https://www.dropbox.com/s/b981q4mf8hp7q4e/SMC Corona 4gb.jpg

but is fixed for next

 

[Martin C]

but is fixed for next

Link To Image

Now try to extract it from a 48MB Corona 4GB image

 

[BraveH43]

Now try to extract it from a 48MB Corona 4GB image

meh! i'll ask a man that can! :rolleyes2:

 

[stefanounick]

That's fixed for the next version

 

[Martin C]

Cheers - just need XeBuild to inject the SMC config properly now

 

[IronMan72]

Another thing that would be nice would be if the xebuild image name allowed wildcards to be used to define a filename. For example, I like to name my image files with the Serial Number, dash version and build type in this format '123456789012 16197 JTAG.bin' so I know exactly what the image is at a glance. To support variations of this a wildcard format such as this could be used

%S = Serial Number
%D = Dash Version
%T = Build Type
%C = CPU Key
etc..

In the string field for xebuild image name one could use a specific filename as it is today or could use wildcards to customize the filename for each image built. So for the format I use the field would be populated like this '%S %D %T.bin'.