Homebrew Question Overclocking Switch Lite

[ZachyCatGames]

Even at 50, let's say something happens and I get it up to 60°C, it's still WELL below the temp at which the chip starts throttling. IIRC it's 83°C it starts throttling. With a tjmax of 90°C.

It doesn't throttle in HOS, insta shutdown is around 83C and handheld has some timers at certain tskin temps, where if it sits at those tskin temps or higher for some amount of time, it shuts off.

EDIT: It might not be tskin temps, I don't remember.

EDIT 2:

 

[hartleyshc]

It doesn't throttle in HOS, insta shutdown is around 83C and handheld has some timers at certain tskin temps, where if it sits at those tskin temps or higher for some amount of time, it shuts off

Good to know. I was going off of what the specs of the chip are. I mean even with what I thought the threshold was, I wasn't even going to let it get to the point of throttling. Since it would just be worse performance at that point.

And I totally agree with Nintendo's reasoning for this. In the real world, it's only going to get to that temp with a non functional fan, or totally clogged airflow. Maybe a factory damaged heatpipe. From an RMA perspective, it makes a lot of sense to set the shutdown at what the chip throttles at so there's no chance of actual damage. And they don't have to support slow downs from throttling. End user Switch shuts down due to reaching 83, they send it in, Nintendo can just replace the cooling assembly and return to the user, or swap out the entire unit and replace the fan/cooling assembly, or clean the system and then resell as a refurbished unit.

Sent from my ONEPLUS A6013 using Tapatalk

 

[mattyxarope]

If you're running Mariko you're not really going to have any issues. We've had some discussions on what the temps could be, but on my own switch lite (the smoke clear Switch lite posted above in this thread). I run my switch lite 24/7 at 1.7ghz cpu, 921mhz gpu, and 1600mhz memory clock.

The highest temperature I've ever been able to observe is 50.x°C. I've never hit 51°C as the fan will ramp up to the high 30's% and will keep the chip hovering around this temp. (Using Xenoblade Chronicles Definitive Edition as testing. I'll probably install the 60fps mod at some point to try and ramp up the temps even more if possible).

Even at 50, let's say something happens and I get it up to 60°C, it's still WELL below the temp at which the chip starts throttling. IIRC it's 83°C it starts throttling. With a tjmax of 90°C.

Sent from my ONEPLUS A6013 using Tapatalk

I was always under the impression that the problem with overclocking was that it affected the battery negatively.

 

[ZachyCatGames]

I was always under the impression that the problem with overclocking was that it affected the battery negatively.

Mariko pretty much cut the power usage in half, on the Lite battery life might not be super great. But whatever.

 

[hartleyshc]

I was always under the impression that the problem with overclocking was that it affected the battery negatively.

Mariko is efficient enough that I don't notice any real battery loss. Not to say there's not, physics says that there is more battery being used. It's just not to the point to where it's an issue for me.

If I ever get bored one weekend I might do a basic BoTW battery test. Go out to the field and just have the analog stick held down with a rubber band so I'm spinning. Time the unit on how long it takes to shut down from 100-0. On stock clocks and then max clocks.

Right now I have 0 data to give. All I can say it's not something to where it cuts down so much to where I notice I need to keep it plugged in all the time like a 2 year old cell phone.

Sent from my ONEPLUS A6013 using Tapatalk

 

[mattyxarope]

By negatively affecting the battery, I meant to say that I recall m4xw saying something about how the increased draw on the battery physically damages it. But maybe that's different with the new processors. Btw the modded version seems to work on the Switch Lite - thanks.

 

[ZachyCatGames]

By negatively affecting the battery, I meant to say that I recall m4xw saying something about how the increased draw on the battery physically damages it. But maybe that's different with the new processors. Btw the modded version seems to work on the Switch.

Yeah, it shouldn't really be an issue on Mariko, at least on the normal sized consoles (can't really say for the Lites, they have a smaller battery, dunno if that impacts anything. But I'd guess it's fine(?))

> Btw the modded version seems to work on the Switch
Normal sized Mariko Switch? Or?

 

[hartleyshc]

By negatively affecting the battery, I meant to say that I recall m4xw saying something about how the increased draw on the battery physically damages it. But maybe that's different with the new processors. Btw the modded version seems to work on the Switch.

I mean hypothetically that could be true. I haven't looked too much into the specs of the battery or the actual draw from running max clocks. But just from an engineering aspect I'm sure it's all within spec of the power system. I still believe the switch runs at the speed it does is all based on achieving what Nintendo wanted for battery life based on the efficiency of the Erista chip, in the form factor they wanted. There was zero reason for them to raise any clocks on Mariko chips and just took the extra efficiency as extra battery life.

For me personally I still don't see that as a big issue. If I kill my battery within a year or two, I'll just buy another one.

Sent from my ONEPLUS A6013 using Tapatalk

 

[mattyxarope]

Yeah, it shouldn't really be an issue on Mariko, at least on the normal sized consoles (can't really say for the Lites, they have a smaller battery, dunno if that impacts anything. But I'd guess it's fine(?))

> Btw the modded version seems to work on the Switch
Normal sized Mariko Switch? Or?

Switch Lite - works great. Hopefully I don't hose my battery lol. But at least I'm doing it within the console's lifetime so I can get a new battery.

 

[HenryMin]

Yeah, it shouldn't really be an issue on Mariko, at least on the normal sized consoles (can't really say for the Lites, they have a smaller battery, dunno if that impacts anything. But I'd guess it's fine(?))

> Btw the modded version seems to work on the Switch
Normal sized Mariko Switch? Or?

The modded sys-clk worked well on my classic mariko console too. (iowa )

 

[hartleyshc]

Setting up the 60fps mod on XCDE.

Something seems a little off... haha

Sent from my ONEPLUS A6013 using Tapatalk

 

[mattyxarope]

Setting up the 60fps mod on XCDE.

Something seems a little off... haha

Sent from my ONEPLUS A6013 using Tapatalk

I believe that this happens when you use some methods to achieve the 60fps. Does it maintain the 60fps?

 

[ZachyCatGames]

This has 1887mhz CPU and 998mhz GPU speeds added, I have no idea if it'll do anything, dunno if HOS supports Mariko's higher speeds.
If it works, Status-Monitor-Overlay will (probably) show 1887mhz/998mhz/whatever when you have those speeds set, if it shows 1785mhz/921mhz, it doesn't work

 

[mattyxarope]

This has 1887mhz CPU and 998mhz GPU speeds added, I have no idea if it'll do anything, dunno if HOS supports Mariko's higher speeds.
If it works, Status-Monitor-Overlay will (probably) show 1887mhz/998mhz/whatever when you have those speeds set, if it shows 1785mhz/921mhz, it doesn't work

Would this work for Lite as well? Aren't these the same oc speeds for switchroot?

 

[hartleyshc]

This has 1887mhz CPU and 998mhz GPU speeds added, I have no idea if it'll do anything, dunno if HOS supports Mariko's higher speeds.
If it works, Status-Monitor-Overlay will (probably) show 1887mhz/998mhz/whatever when you have those speeds set, if it shows 1785mhz/921mhz, it doesn't work

No go.

Sys-clk app and overlay will show the 1887/998, but Status Monitor shows the 1785/921.

Which makes sense, I doubt they changed too much to Horizon when they were making the Mariko devices. At least we know for sure now.

Sent from my ONEPLUS A6013 using Tapatalk

 

[mattyxarope]

No go.

Sys-clk app and overlay will show the 1887/998, but Status Monitor shows the 1785/921.

Which makes sense, I doubt they changed too much to Horizon when they were making the Mariko devices. At least we know for sure now.

Sent from my ONEPLUS A6013 using Tapatalk

Same experience here on the Lite.

Unless Status Monitor has a cap for showing the clocks?

 

[ZachyCatGames]

No go.

Sys-clk app and overlay will show the 1887/998, but Status Monitor shows the 1785/921.

Which makes sense, I doubt they changed too much to Horizon when they were making the Mariko devices. At least we know for sure now.

Sent from my ONEPLUS A6013 using Tapatalk

Good to know, that's unfortunate, but I'm not surprised.

Yeah. Either that, or Nvidia and Nintendo use different speeds for some reason ig (and I'm not knowledgeable enough to RE pcv or whatever to check, heh)

Would this work for Lite as well? Aren't these the same oc speeds for switchroot?

Lite and non-Lite use the same SoC, it doesn't work on either though ig.
The speeds were pulled from t210b01 clockspeed tables in L4T.

 

[hartleyshc]

Would this work for Lite as well? Aren't these the same oc speeds for switchroot?

As Zach said, the speeds were pulled from the L4T which is the basis for switchroot. It has its own kernel and bypasses the Horizon OS Kernel.

However this could be added one day to Mesosphere. In fact we could be hitting real OC speeds of 2.0/2.1/2.2 within the Horizon OS.

Not sure how much use it would be. Pretty much would only be useful for a couple of Emulators, and some 60fps mods.

@ZachyCatGames being that switchroot only uses Erista, does it actually have the tables for Mariko? Are they the same? Also are the PLLs the same for both Erista and Mariko? I haven't looked too much into the actual tables in detail, or into sys-clk. I don't know if you have to input the PLL info into sys-clk, or if the PLLs are the same between both chips. I know they're posted somewhere on the Nvidia Developer forums. If not straight from source.

Sent from my ONEPLUS A6013 using Tapatalk

 

[mattyxarope]

Good to know, that's unfortunate, but I'm not surprised.

Yeah. Either that, or Nvidia and Nintendo use different speeds for some reason ig (and I'm not knowledgeable enough to RE pcv or whatever to check, heh)



Lite and non-Lite use the same SoC, it doesn't work on either though ig.
The speeds were pulled from t210b01 clockspeed tables in L4T.

I suppose the max clocks could be changed in Mesophere once it's fully implemented in Atmosphere

 

[ZachyCatGames]

As Zach said, the speeds were pulled from the L4T which is the basis for switchroot. It has its own kernel and bypasses the Horizon OS Kernel.

However this could be added one day to Mesosphere. In fact we could be hitting real OC speeds of 2.0/2.1/2.2 within the Horizon OS.

Not sure how much use it would be. Pretty much would only be useful for a couple of Emulators, and some 60fps mods.

@ZachyCatGames being that switchroot only uses Erista, does it actually have the tables for Mariko? Are they the same? Also are the PLLs the same for both Erista and Mariko? I haven't looked too much into the actual tables in detail, or into sys-clk. I don't know if you have to input the PLL info into sys-clk, or if the PLLs are the same between both chips. I know they're posted somewhere on the Nvidia Developer forums. If not straight from source.

Sent from my ONEPLUS A6013 using Tapatalk

The kernel doesn't control clockspeeds in HOS. They're controlled by the pcv sysmodule iirc, someone would have modify or reimplement that.

https://gitlab.com/switchroot/kerne...-rel32/drivers/soc/tegra/tegra210-dvfs.c#L537
https://gitlab.com/switchroot/kerne...-rel32/drivers/soc/tegra/tegra210-dvfs.c#L810

Edit: t210 ODIN CPU table for reference (NOTE: speeds above 1785mhz were added by Switchroot and aren't there in official L4T, voltage coeffs and whatever are unmodified though)
https://gitlab.com/switchroot/kerne...-rel32/drivers/soc/tegra/tegra210-dvfs.c#L359