Hacking Hekate CTCaer v4.6 SVC Beta released

RattletraPM

Well-Known Member
OP
Member
Joined
Jan 18, 2017
Messages
897
Trophies
1
XP
8,341
Country
Italy
hekate.png

A new version of @CTCaer 's Hekate mod has just been released, precisely v4.6 SVC Beta. Some of the improvements are rather specific, for example fixing sleep mode for users running firmware 6.X.X and the stock secure monitor with debug mode turned on, a GPU bugfix on Linux when warmbooting and a real-time clock driver which will disable the wake up alarm when the "Auto HOS Power Off" function is enabled (which was mainly done to help a very specific case with AutoRCM users - if you've ever experienced Hekate showing the logo then shutting down when choosing its shutdown function after a poweroff from Horizon, this last one aims to fix that). However, there was also one more addition that could catch one's interest: a patch for svcControlCodeMemory which will help emulators with their dynamic recompilers, thus improving their performance.

As usual, you can find the full changelog below:
Added patch for svcControlCodeMemory that helps dynarec on emulators.
Fixed sleep mode when debug mode is on and official 6.X.X secmon is used
Added RTC driver which now also disables wake up alarm when Auto HOS Power Off is used
Helps when users that use AutoRCM inject and power off pretty fast.
Fixed GPU on Linux when booting from warmboot
Added missing fallback auto calibration of sd cards and plus some small fixes.

While emulation and retrogaming enthusiasts can find this new addition interesting, it should still be stressed that this is a beta and as such, it can contain bugs

Still, if you want to test this new version yourself, you can download it from Hekate's GitHub repository (link in the sources). However, keep in mind that this release only contains the RCM payload: if you already had installed a previous version of Hekate on your Switch then you can use it out of the box, however if it's your first time trying it then you will need to download a previous release and copy the "bootloader" folder on the root of your microSD card.

:arrow: Source
 
Last edited by RattletraPM,

CTCaer

Developer
Developer
Joined
Mar 22, 2008
Messages
1,154
Trophies
0
XP
3,008
Country
Greece
if you've ever experienced Hekate showing the logo and shutting down during the bootup process with AutoRCM on, this last one aims to fix that
Have in mind that this behavior (hekate logo) is actually intended to alert the user that hekate is powering off (instead of letting the user wait on a black screen without knowing what happened).

The new addition (RTC driver) is for users with AutoRCM that press PWR and inject right away after a HOS power off and hit hekate's power off, inside a 15s time frame.
Now it disables the alarm, so for this edge case scenario, the console will not wake up again.
 

RattletraPM

Well-Known Member
OP
Member
Joined
Jan 18, 2017
Messages
897
Trophies
1
XP
8,341
Country
Italy
Have in mind that this behavior (hekate logo) is actually intended to alert the user that hekate is powering off (instead of letting the user wait on a black screen without knowing what happened).

The new addition (RTC driver) is for users with AutoRCM that press PWR and inject right away after a HOS power off and hit hekate's power off, inside a 15s time frame.
Now it disables the alarm, so for this edge case scenario, the console will not wake up again.
Heh, I'm one of those users... It happened to me a few times whenever I was chaing configs/payloads or messing around with KIPs ^^"
Thanks for fixing it by the way, it may be for an edge case scenario but it's still a very welcome one!

(I'll edit OP while I'm at it)
 
Last edited by RattletraPM,

bottmint

Well-Known Member
Newcomer
Joined
Oct 28, 2017
Messages
91
Trophies
0
Age
31
XP
385
Country
United States
When you shutdown from horizon, it sets an alarm that wakes the console up. If you use autorcm, your switch will wake up and be waiting for a payload. With autoHOS power off, if you inject hekate while the alarm is still set, hekate will properly power off your switch.

However, if you press power, then inject hekate, then use hekate's power off, the alarm is still set, and the console will still wake up into rcm mode.

The RTC driver clears the alarm. So, if you push hekate and use hekate's power off within 15 seconds of powering off from Horizon, your switch will stay powered off.

To put it simply, if you don't use autorcm, turn off AutoHOS power off. If you don't want hekate to handle properly powering off your switch for you as you'd rather do it yourself, don't use AutoHOS power off.
 
  • Like
Reactions: ShonenJump

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
  • K3Nv2 @ K3Nv2:
    13,600 MB/s though
  • DinohScene @ DinohScene:
    I got a 980 pro iirc
  • K3Nv2 @ K3Nv2:
    Soldigms been pretty solid
  • DinohScene @ DinohScene:
    yeh 980 pro
  • DinohScene @ DinohScene:
    good enough tbf
  • K3Nv2 @ K3Nv2:
    https://a.co/d/gMNhZNI never heard about them but reviews are good
  • SylverReZ @ SylverReZ:
    @DinohScene, Crucial SSDs work fine. I have one installed in my Xbox.
  • SylverReZ @ SylverReZ:
    Reviews seem positive.
  • DinohScene @ DinohScene:
    I believe I had some Patriot RAM running in a computer somewhere
  • K3Nv2 @ K3Nv2:
    $250 is pretty solid considering
  • K3Nv2 @ K3Nv2:
    With the refund it'll be about $150
  • K3Nv2 @ K3Nv2:
    6tb nvme pc ftw
  • DinohScene @ DinohScene:
    500 GB NVMe, 750 GB
    SATA SSD 1 TB HDD
  • DinohScene @ DinohScene:
    honestly I don't play pc games
  • K3Nv2 @ K3Nv2:
    I don't game
  • K3Nv2 @ K3Nv2:
    Once I buy this I'll be around 20tb worth of storage tho if we're talking all my drives
  • K3Nv2 @ K3Nv2:
    All this crap I got and all I do is pick up the GabeDick to fiddle with his happy stick
  • DinohScene @ DinohScene:
    idk the total storage cap I have
  • DinohScene @ DinohScene:
    50 TB orso
  • SylverReZ @ SylverReZ:
    @DinohScene, I don't play PC games often. Mostly its all 90s-00s games.
  • K3Nv2 @ K3Nv2:
    Hm doing research quite possible my issue with this drive is bios related not detecting it fully
  • DinohScene @ DinohScene:
    run crystaldisk?
  • K3Nv2 @ K3Nv2:
    Don't think it would do much if gnome live even sees it as 2mb
  • K3Nv2 @ K3Nv2:
    Vmd issue possibly
    K3Nv2 @ K3Nv2: Vmd issue possibly