Hekate: Fix sleep mode for 3.X.X

Created on 18 Jun 2018  路  14Comments  路  Source: CTCaer/hekate

bug

Most helpful comment

All 14 comments

Any ideas on this?

I've looked at the original diff for sleep support, and it seems like everything is in place for these versions.

Could the warmboot_base be wrong? I'm guessing if the patchset was wrong for these versions it wouldn't boot at all?

Yeah. Also last time I checked, the address was correct.

Yes, it would hang at boot.
I don't have time currently to work on this. If I want to try some things, are you available (what version you have)?

I am definitely available to test stuff. My console is on 3.0.1, and I'm very interested in the sleep support so I can keep my fuses the way they are.

I've got a fair bit of embedded ARM C experience (STM32, not Tegra) as well, so if you don't have time for the code but you know conceptually what needs changing/doing I can help out with that also.

I have a 3.0.0 console and am also interested in this and can do some testing.

The more the merrier.

@michaelshiel
You can start by REing your nxbootloader. There's the most important stuff for lp0 power state.

@michaelshiel @vgmoose
Anyone available please contact me via email. (Comms via discord is preferable.)

I'm also on 3.0.0 and can test.

EDITED

I have enough testers for this. Thank you all for wanting to help.

Fixed internally.

Will be released when some other changes are ready.

Thanks! Any chance you could commit the changes?

I spent a lot of time disassembling the NX Bootloader like you suggested, focusing on the sdram_lp0_save_params function, and I'm very curious where the problem actually was.

Edit: Removed wrong information

Are you sure about cross-matching/checking everything in dissasembly?
The current behavior matches Nvidia's behavior on coreboot.
https://github.com/MrChromebox/coreboot/blob/master/src/soc/nvidia/tegra210/sdram_lp0.c

EDIT:

Any chance you could commit the changes?

Will be released when some other changes are ready.

Yeah my mistake, I was interpreting the offsets incorrectly.

I think you can close this @CTCaer - Nice work btw :D

Was this page helpful?
0 / 5 - 0 ratings