Hacking [Pre-release, WIP] Yet another rxTools?

[duke_srg]

Emunand tool? I thought you meant backups from d9 or something. Emunand tool according to several devs is outdated now and might be dangerous to use. I'm not comfortable using that as I don't really want to lose anything.

If d9 still is fine to use for this experiment, then ok, I'll do the backup and restore later tonight, then fill the card up. After filling it up, do I just delete what I filled, copy rxTools to sd again, and try?

Yeah, it's still a matter that has to be within rxtools no matter what the result is. In which case, I suppose div_4 should be the current solution, even if it gains no speed improvements. Until a solution is found that is.

If you formatted your emunand with GATEWAY a long time ago, then emunand tool is safe to use.
D9 uses the same old sdmmc driver with no error checking at all! You may have the same errors there but D9 will just silently skip errors. Lower clock rates is only a measure to lower the probability of underruns to balance between high transfer speed and error handling routine occurance. The PS SD card reader will handle all the errors, as far as it is correctable by SD card controller itself, so the data will be read and written properly until SD card controller or wear-leveling reserved area are failed.
So there is a safe solution:
1. backup with D9
2. backup another one time with emunand tool
3. restore with emunand tool
4. restore with D9, if you prefer
Well, and fill the rest of the card with junk

 

[duke_srg]

Commited version which will halt if second read/write attempt failed with complete error status and CID/CSD registers of the failed storage device printed. Please check.

 

[Madridi]

Commited version which will halt if second read/write attempt failed with complete error status and CID/CSD registers of the failed storage device printed. Please check.

I just tried this, and once again, emunand dumped on the first try. I timed it this time, 4.37 minutes.

I will dump one more time to see if it works fine or if it locks up again.

Hopefully, there won't be a need to do the thing in the other reply

Edit: dump completed again, 4.40 minutes .. Can we finally consider this to be solved?
Edit2: dumped sysnand just to see how long, 4.33 minutes!

 

[duke_srg]

I will dump one more time to see if it works fine or if it locks up again.

In case of error handling, this is just like the previous one, except of it will halt on second error instead of the infinite loop.
Oh, nevermind, I screwed up and this will halt and report error details on the first failure!

 

[Madridi]

I j

In case of error handling, this is just like the previous one, except of it will halt on second error instead of the infinite loop.
Oh, nevermind, I screwed up and this will halt and report error details on the first failure!

i just dumped a third time. It froze again. No error no nothing. It just froze

At least something is more reliable in these last 2 commits. It might even be my sd starting to behave nicely a bit..

 

[duke_srg]

I j

i just dumped a third time. It froze again. No error no nothing. It just froze

At least something is more reliable in these last 2 commits. It might even be my sd starting to behave nicely a bit..

Oh, it is indeed fails on second one, but can't reach it since hangs somewhere before it.
So just replace
if (dblerror++ > 0)
with
if (dblerror==0)
twice
And it will display error status.

 

[Madridi]

Oh, it is indeed fails on second one, but can't reach it since hangs somewhere before it.
So just replace
if (dblerror++ > 0)
with
if (dblerror==0)
twice
And it will display error status.

tmio.c?

 

[duke_srg]

tmio.c?

Yes! I'm on mobile now

 

[Madridi]

Yes! I'm on mobile now

There are 2 locations where that if statement exist. Should I change both?

 

[duke_srg]

There are 2 locations where that if statement exist. Should I change both?

Yes both. One for the read and one for the write operation.

 

[Madridi]

Yes both. One for the read and one for the write operation.

Sorry it took a while, I ran into some trouble with my PC.

Anyway, on my 5th dump now. 4 dumps were fine. Now the 5th dump I got a msg in red "press any button to reboot"

Now what? Should I press something?

 

[duke_srg]

Sorry it took a while, I ran into some trouble with my PC.

Anyway, on my 5th dump now. 4 dumps were fine. Now the 5th dump I got a msg in red "press any button to reboot"

Now what? Should I press something?

And nothing else? there must be a huge diagnostics screen

 

[Madridi]

And nothing else? there must be a huge diagnostics screen

Nope, nothing else. Maybe it appeared and disappeared? Cause I wasn't looking at the screen the moment it locked up.
Should I press any button and see what happens?

 

[duke_srg]

Nope, nothing else. Maybe it appeared and disappeared? Cause I wasn't looking at the screen the moment it locked up.
Should I press any button and see what happens?

It should be displayed with the reboot request. And anyway it will reoboot after button pressed, yes you can try it

 

[Madridi]

It should be displayed with the reboot request. And anyway it will reoboot after button pressed, yes you can try it

Well, I don't know.. nothing was displayed..
Also, when I pressed a button, it actually turned off instead of rebooting. But who cares

 

[duke_srg]

Ok, found a small issue that can prevent message show. Check the latest commit changes and don't forget to disable double error check

upd: shutdown->reboot also fixed.

 

[Madridi]

Ok, found a small issue that can prevent message show. Check the latest commit changes and don't forget to disable double error check

upd: shutdown->reboot also fixed.

You mean change the if statement to ==0?

 

[duke_srg]

You mean change the if statement to ==0?

Yes! I left 2x error as a regular handler.

 

[Madridi]

Yes! I left 2x error as a regular handler.

I'm getting a black screen with the new commit
Edit: worked fine on second boot. That was weird

 

[duke_srg]

I'm getting a black screen with the new commit
Edit: worked fine on second boot. That was weird

If it was without dblerror fix, it is posibly hang on error reading before interface boot.