Power Value & Power VCS - Ran out of values

[01DawG10]

Good day gentleman,

Hope all is glitchin well

I'm still up and tuning on my stubborn Falcon, but, my wings seems to be running out of feathers....

After a looooong struggle, my Falcon was running great (or thats what I thought), I ran a few games for some hours without any problems, so I decided to put all and all together (show-off pic). Played a bit more more and suddenly.....Freeze.... So I though, maybe I havent tuned it to the best of its ability as instaboot was not occuring every time, and anyways wanted to flash my drive (for in-case) so I ripped all open and started twinkeling again.. Many hours later I found that I'm not able to get a better glitch and it does boot every time, but the freezing still occurs randomly (everytime). The longest I ran was about 20 minutes of Raging Blast (cpu vs cpu to test)..

I just played again, 2 sessions aprox 10 minutes each. This does not seem to be a temperature issue, the below shot was taken seconds before it froze (lucky me)


Now, Ive seem to run out of options as my Power Value is down to 8080. Stock 8280 did not work at all (MartinC knows ), higher values not at all, 8180 gave me instaboot everytime but games froze before even reaching the menu and connecting a USB resulted in screen flickering and artifacts. My Power VCS control value is 8565 (stock 8555 did not work, cant remember exactly why).

I am able to help my self, provided I have the necessary info. By reading alot on this forum I found you guys holding back, which is fair, but currently, I need to be educated.

I know what tweaking these values does, but I'm not sure what they are for, and what actually changes. I would like to share my own conclusions but dont want to noobify my name..

Anybody knows what can be tweaked next, or which values to change (And please, if allowed, some technical explanation for it )

Thanks are given in advance as assistance is always prompt and spot on :cool2:

 

[Martin C]

I think the first thing to do is post pics of how everything's soldered.

SMC Config values normally affect temps, which isn't the case here.

 

[01DawG10]

I think the first thing to do is post pics of how everything's soldered.

SMC Config values normally affect temps, which isn't the case here.

Hi Martin, thanks for the reply.

I have not disconnected anything after my previous thread, so my soldering would still be the same. But, if you need it again, I am happy to repost.

I had a situation with regards to the voltage on the R-JTAG, while testing I set it to default (instead of 1.2v) and I got some awkward display artifacts. Setting it back to 1.2v fixed the issue. So, not being sure what the explanation is, it seems to me that this issue might be affected by the power/clock settings of either CPU or GPU.

When on 8180, the screen glitched when I connected an external HDD, the same type of artifacts (as above) appeared as well, although the box did not freeze and everything worked behind the flickering and artifacts. Setting down to 8080 fixed this issue. So, will I be wrong saying the GPU was "starved" from volts/current due to the SMC config not being set to supply the right amount of current?

If the above is true, and I have no more options with regards to increasing the power/current, would I need to reball the GPU? Perhaps due to weak connections current is shorted of to ground for dissipation or something?

 

[Martin C]

It's possible you have a GPU issue, yes.

 

[01DawG10]

It's possible you have a GPU issue, yes.

In the sense of incorrect clock/voltage or a bit more physical?

 

[Martin C]

if you're getting graphical glitches. Either that or you have interference on a solder point/wire/etc.

 

[01DawG10]

if you're getting graphical glitches. Either that or you have interference on a solder point/wire/etc.

Ok. I wont know the answers to questions I do not ask.

- Which part of the R-JTAG would have a direct influence as such on the GPU?
- And the glitches, how does the SMC config change your opinion about the problem, in the sense that certain settings does glitch and other not at all?

And, the whole console does not seem to freeze. It seems as if it tries to rectify the problem itself (screen going blank every 20th second or so for a moment) and the remote sync button still jingles the lights when its pushed. Any way of logging errors and/or crashes?

Thanks

 

[Martin C]

You can't really debug a retail kernel. troubleshooting might be an issue.

I would advise you return to stock by removing everything and reflash the retail NAND. Then, check the console by stress-testing it for a few hours with a new game (CoD/BF4/GTA). Note any anomalies.

 

[01DawG10]

You can't really debug a retail kernel. troubleshooting might be an issue.

I am willing to try anything in order to shed more light on the subject.

I would advise you return to stock by removing everything and reflash the retail NAND. Then, check the console by stress-testing it for a few hours with a new game (CoD/BF4/GTA). Note any anomalies.

A few days before I bought it, it was running GTA V quite fine (it was a friend of mines who borrowed it to his dad), but I understand the fact that there has been physical changes (soldering etc.).

By removing everything, do you mean physically desoldering everything or just removing power from the R-JTAG and disconnecting post ribbon?

 

[Martin C]

I'd desolder as much as possible.

 

[01DawG10]

I'd desolder as much as possible.

Ok, so I didnt desolder anything. I got hold of a copy of XSDK, and RGLoader. XDK was intended to run some debugging/logging.

I created a 16537 image in jrunner and changed the power value to 8180 (the one which glitched perfectly) leaving the Power VCS value intact. I then used that image with RGLoader and created and flashed a 16537 Jtag dev image.

After copying all the needed files to the original hdd I was able to boot to the Minimal Dev App/Dash.

I could not load the NXE dash but was able to install and run FSD.

I was gaming for an hour and a half without any sign of issues. I then reflashed the 16537 image from jrunner (which I loaded in RGLoader) and it was freezing every 2-8 mins.

So, my question would be: What could have gone wrong with the SMC used in Jrunner. I tried multiple SMC's without any luck. I reinstalled windows on another hdd, I redownloaded Jrunner and the needed dashes, I used a clean SMC and nothing changed the situation.

As you guys are more informed, could someone please share their opinion?

Thanks

EDIT: Why is it that as soon as I create an image for any version of the dash, the CB version changes from 5774 to 5770?

And, which part of the whole exploit/hardware runs after boot?