Hacking Launch Fusee gelee on Shield tv

Man4

Member
OP
Newcomer
Joined
Aug 25, 2018
Messages
7
Trophies
0
Age
46
XP
206
Country
Spain
Hello,

After reading a comment from Kate about the validity of the vulnerability found in Tegra X1 shared by several devices:

"Yeah, fusee.bin drives to panel and not the HDMI output. You'll need a custom payload for that. :) I think someone's working on a proof-of-concept for it."

I was wondering what are the knowledge and steps necessary to start adapting some code to make this work. Can someone tell me what is the way to go?

My knowledge is limited but my illusion is not, so, taking advantage of the fact that the source code is open, I have started by looking at the fusee code, to start with something, inside t210.h there is a base address for video, but how do we make the information go through the HDMI output and not the internal panel as it happens in the Switch ?.


Any suggestions / help is welcome.

P.d: I have a bricked bootloader 2015 Shield Tv (pid 0x7721) that I wish to return from death ... some day ... first: step 0 ;-).
 
  • Like
Reactions: KiiWii

Man4

Member
OP
Newcomer
Joined
Aug 25, 2018
Messages
7
Trophies
0
Age
46
XP
206
Country
Spain
Thank you!

I had already started with that document but I have not yet seen a direct relationship between what I read and the initialization code of the hardware found in Fusee or other payloads, for example the relation of that base address:
#define DISPLAY_A_BASE 0x54200000
I am aware that the community is now very focused on switch but what I read would be many common things.

I will continue investigating ...
 

CTCaer

Developer
Developer
Joined
Mar 22, 2008
Messages
1,154
Trophies
0
XP
2,499
Country
Greece
Careful with the pinmuxing. You can fry parts of shield tv if you use the same as hekate's hwinit (basically switch's hw init).

Most things remain the same. For example DISPLAY_A_BASE remains the same because it's the mmio base addr for display A.

It's better to read TX1 TRM to understand what the registers do.

What changes is mostly where everything is connected on the SoC (pads/pins/gpios/sfios/etc).

EDIT:
Check shield's tv linux kernel sources also. You will find the most board configs there.
 
Last edited by CTCaer,

Man4

Member
OP
Newcomer
Joined
Aug 25, 2018
Messages
7
Trophies
0
Age
46
XP
206
Country
Spain
No, i think sdk will be very "switch specific", i try to understand the code and adapt to the shield tv. My first goal is to be able to launch a fusee on shield and see some feedback on the screen (hdmi output).
I started with fusee because i think is the simplest payload of all (as far as i know).

Thanks CTCaer! I admire your work. I will follow your advice.
I thought that the switch was working in low demand (relative to the shield) and that using those adjustments I was in a safe working area.
Apart from what I find here and there, does the community of the scene have some reference documents? for example, how the hardware part is initialized ... although I suppose that is the talent part of each one, the construction of its own documentation and notes.
 

CTCaer

Developer
Developer
Joined
Mar 22, 2008
Messages
1,154
Trophies
0
XP
2,499
Country
Greece
If you by low demand you are talking about voltages, that's not the case.
It's ok for the SoC and other parts of it.
But you need to know what is connected where.

For example the pmic pin that powers sth else in switch, may power sth other in shield. These are vendor implementation specific. The exploit works, but the hw bring up is different.

It's better to take parts from shield's kernel and try to use them in a payload. And research a lot for it's I/O configuration.

The biggest and most complete reference for switch is switchbrew.org.
 

Man4

Member
OP
Newcomer
Joined
Aug 25, 2018
Messages
7
Trophies
0
Age
46
XP
206
Country
Spain
So before try anything more, better to now what's going on inside hardware part deeply.

I wonder also how similar to Jetson TX1 can be, not only shield, switch also.

Ok, i have a lot of things to check, smells good ;-).

Thanks!.
 
General chit-chat
Help Users
  • No one is chatting at the moment.
  • The Real Jdbye @ The Real Jdbye:
    very dark scenes are more common than very bright scenes so i think i made the right choice
    Gift
  • The Real Jdbye @ The Real Jdbye:
    there was also a sony with worse local dimming and the glow was really apparent
    Gift
  • SG854 @ SG854:
    Human vision is non linear anyway. 100 nits is about 50% of the peak output of a 10,000 nit display.
    Gift
  • Julie_Pilgrim @ Julie_Pilgrim:
    "very dark scenes are more common than very bright scenes" not in the games i play
    Gift
  • The Real Jdbye @ The Real Jdbye:
    really have to buy the top end model to get a tv that doesnt have any of those compromises and that would've had more dimming zones too but i am not made o money
    Gift
  • The Real Jdbye @ The Real Jdbye:
    @Julie_Pilgrim "very bright" is essentially pure white
    Gift
  • The Real Jdbye @ The Real Jdbye:
    pure white doesn't show up all that much it's mainly when looking at a bright sky
    Gift
  • The Real Jdbye @ The Real Jdbye:
    and if the clouds in the sky have slightly less definition to them because i turned on the contrast enhancer who cares
    Gift
  • The Real Jdbye @ The Real Jdbye:
    that's not important
    Gift
  • The Real Jdbye @ The Real Jdbye:
    i can't tell the difference
    Gift
  • The Real Jdbye @ The Real Jdbye:
    but i can certainly tell the difference with black crush if i'm watching a scifi movie and i can't see wtf is going on
    Gift
  • SG854 @ SG854:
    Human vision is logarithmic, it's not linear. And nits doesn't tell the whole story of perceived brightness. OLED'S look brighter then LCD's even when both are set to the same nit values because of the higher contrast ratio on OLED's
    Gift
  • SG854 @ SG854:
    OLED's have a 3D look
    Gift
  • kenenthk @ kenenthk:
    Charging port is more likely to fry up or battery fail before the display tbh lol
    Gift
  • The Real Jdbye @ The Real Jdbye:
    "And nits doesn't tell the whole story of perceived brightness" it's not about perceived brightness it's about all HDR content in TV and movies being mastered for 1000 nits so it doesn't look right with anything lower, it's also about dynamic range
    Gift
  • The Real Jdbye @ The Real Jdbye:
    "OLED's have a 3D look" no they don't lol
    Gift
  • SG854 @ SG854:
    As an owner of a OLED and you saying that you never seen an OLED I think I know what I'm talking about lol. I'm not talking about 3D as in 3D glasses. I'm talking about depth and pop in the picture
    Gift
  • kenenthk @ kenenthk:
    I mean to be fair og vitas are still kicking and not many have suffered from pixel bleed and they're going on nearly 10 years
    Gift
  • SG854 @ SG854:
    OLED's can get away with a lower peak brightness and still provide punchy HDR because of their contrast ratio. Like I said human vision is logarithmic. The higher the peak brightness the diminishing returns in perceived brightness.
    Gift
  • kenenthk @ kenenthk:
    Just get 5 years enjoyment out of it until Nintendy releases something and everyone forgets about switch games lol
    Gift
  • SG854 @ SG854:
    @The Real Jdbye Oleds hit around 750 nits nowadays. The difference between a 1000 nit and a 750 nit isn't huge. It's only about a 4% increase in perceived brightness. Not huge at all. You'll need at least 2000 nit displays to notice a bigger difference.
    Gift
  • SG854 @ SG854:
    Read this thread it explains it. 1000 nits is not a huge jump from 750 the LG OLEDs can hit. As I said human vision is non linear.
    +2
    Gift
  • Gift
  • mr_switch @ mr_switch:
    Not exactly 3D but the colors does pops out more
    Gift
  • mr_switch @ mr_switch:
    I just want a true dark mode theme
    for OLED Switch
    Gift
    mr_switch @ mr_switch: I just want a true dark mode theme for OLED Switch