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

[duke_srg]

Froze about half way through

Completely, how log did you wait?

 

[Madridi]

Completely, how log did you wait?

Yeah completely. I initially didn't notice it even froze. Waited around 5 minutes, no change. Pressed B to cancel operation to see if it's just the dump is frozen or the screen, but nothing happened. Had to hard power off

 

[duke_srg]

Yeah completely. I initially didn't notice it even froze. Waited around 5 minutes, no change. Pressed B to cancel operation to see if it's just the dump is frozen or the screen, but nothing happened. Had to hard power off

Ok 5 minutes is an infinite loop. Normally it will slowdown only for several seconds.
Now added full card reinitialization on error, could help. Maybe a bit inaccurate, so also could hang

 

[Madridi]

Ok 5 minutes is an infinite loop. Normally it will slowdown only for several seconds.
Now added full card reinitialization on error, could help. Maybe a bit inaccurate, so also could hang

Yep, same behaviour as the previous commit. No change

 

[duke_srg]

Yep, same behaviour as the previous commit. No change

Fixed a bug. The one was in both versions, could result with infinite loop regardless of the rror fixed or not.
Try latest commit pls

 

[Madridi]

Fixed a bug. The one was in both versions, could result with infinite loop regardless of the rror fixed or not.
Try latest commit pls

Same thing.. No change

 

[duke_srg]

Same thing.. No change

Just in case... comment
https://github.com/dukesrg/rxTools/blob/dev-cardboost/rxtools/source/lib/tmio/tmio.c#L167 to 171
and
https://github.com/dukesrg/rxTools/blob/dev-cardboost/rxtools/source/lib/tmio/tmio.c#L216 to 220

 

[Madridi]

Just in case... comment
https://github.com/dukesrg/rxTools/blob/dev-cardboost/rxtools/source/lib/tmio/tmio.c#L167 to 171
and
https://github.com/dukesrg/rxTools/blob/dev-cardboost/rxtools/source/lib/tmio/tmio.c#L216 to 220

Got it, but I'll be off for a while. Will try in a couple of hours

 

[duke_srg]

Got it, but I'll be off for a while. Will try in a couple of hours

Fine, anyway I'll be ready to check deeply later tonight too.

 

[duke_srg]

Actually I f**ed up sd read/write error retry loop . Fixed now, you can try once again (branch head was reset).
Again, in my system this build works.

 

[Madridi]

Actually I f**ed up sd read/write error retry loop . Fixed now, you can try once again (branch head was reset).
Again, in my system this build works.

Perfect timing, just became free myself
dev-cardboost or dev-a9lh?

 

[duke_srg]

Perfect timing, just became free myself
dev-cardboost or dev-a9lh?

dev-cardboost, but I squashed several commits, so reset before pull

 

[Madridi]

dev-cardboost, but I squashed several commits, so reset before pull

Deleted the whole thing, git clone --recursive, and.. Same result

 

[duke_srg]

Deleted the whole thing, git clone --recursive, and.. Same result

Uncomment here
https://github.com/dukesrg/rxTools/blob/dev-cardboost/rxtools/source/lib/tmio/tmio.c#L166
and there
https://github.com/dukesrg/rxTools/blob/dev-cardboost/rxtools/source/lib/tmio/tmio.c#L215

 

[Madridi]

Uncomment here
https://github.com/dukesrg/rxTools/blob/dev-cardboost/rxtools/source/lib/tmio/tmio.c#L166
and there
https://github.com/dukesrg/rxTools/blob/dev-cardboost/rxtools/source/lib/tmio/tmio.c#L215

Well, that too changed nothing..

There is something that might be too much of a coincidence for me to not say anything about it:
It's freezing for me, not in the same place, but same "block" everytime. I mean, the freeze should be random, yet it's always somewhere between 1/3 to 1/2 way through.

That, and, the fact that I didn't get this with sysnand, makes me more suspicious about my emunand.

I am sure my emunand is not an issue. I barely have any games installed, nothing out of region, and it's clean in general. But still..

We really need more testers to determine if it's a code issue, or a user issue

 

[duke_srg]

Well, that too changed nothing..
I am sure my emunand is not an issue. I barely have any games installed, nothing out of region, and it's clean in general. But still..
We really need more testers to determine if it's a code issue, or a user issue

It's not emunand itself, it all about the card. Since backing up sysnand we have to write the dump and read background images for screen update only, while with emunand dump we have to read emunand image itself too. It is most likely not a fatal card issue, but a timeout which must be worked out.

 

[duke_srg]

A new day - a new idea
Please test with the new commit - stop transmission may help restore card state after error.

 

[Madridi]

A new day - a new idea
Please test with the new commit - stop transmission may help restore card state after error.

Reached halfway point this time, was getting antsy about it finally working.. Until it froze again .. So no change

 

[duke_srg]

Reached halfway point this time, was getting antsy about it finally working.. Until it froze again .. So no change

Ok, now added suspend mode switch force and back.

upd: if still the same, the next one will be with the detailed SD contoller error registers printout.

 

[Madridi]

Ok, now added suspend mode switch force and back.

upd: if still the same, the next one will be with the detailed SD contoller error registers printout.

Yeah it's the same, with the latest commit.
It also felt slower this time but that might just be me