Hacking WIP [Trinket] [Rebug] [Others] SWITCHBOOT_UF2 / FUSEE_UF2 modchip software

[mattytrog]

What uf2 files to use with trinket mo for atmosphere 8.5 thanks

Use trinket/debug.

Rename fusee-primary.bin to payload.bin

 

[darrin41]

Use trinket/debug.

Rename fusee-primary.bin to payload.bin

So will this boot straight to cfw with power button. And where do u place the payload.bin file. Il be flashing the trinket with that uf2 one u suggested

--------------------- MERGED ---------------------------

So will this boot straight to cfw with power button. And where do u place the payload.bin file. Il be flashing the trinket with that uf2 one u suggested

I don't see trinket/debug one can u link me to it thanks

 

[mattytrog]

So will this boot straight to cfw with power button. And where do u place the payload.bin file. Il be flashing the trinket with that uf2 one u suggested

--------------------- MERGED ---------------------------

I don't see trinket/debug one can u link me to it thanks

Post 2 in op. Big letters. Will take you to GitHub and download from there

 

[darrin41]

I'm sorry no such file in there

 

[mattytrog]

https://github.com/mattytrog/Simple-UF2/tree/master/SIMPLE-UF2_v099r1/UF2

It is there. But here is my git

 

[darrin41]

U mean trinket/ rebug

 

[feral]

Heres one for you boys and girls...

Launch this with TegraRCMsmash and see if you can find the new feature...

Yes, the built-in bootlogo is now a black screen due to space purposes...

Nice, added the new LockpickRCM in there. Unfortunately whatever it did ran so fast I didn't actually see what happened. Maybe because I have already dumped my keys?

EDIT: I'm dumb. LockpickRCM wants you to reboot, and if you have a chip that autolaunched your payload it will boot your payload instead of going back into Hekate to run Lockpick the 2nd time.

 

[darrin41]

Which one is it matfrog

 

[noX1609]

No its probably me thats got it wrong. Like I say, I haven`t worked out the details yet.

Heres one for you boys and girls...

Launch this with TegraRCMsmash and see if you can find the new feature...

Yes, the built-in bootlogo is now a black screen due to space purposes...

Hmm ok but how can i then change the Mode i want without soldering a wire to the mode select pin?
Because i would like to use Mode 4, so it goes to the next payload if inject fails (e.g. pressing reset when console is alteady bootet). For that i need the offset and value to edit. Or could you do one for me in mode 4 and send it via private message?
Last thing would be you tell in which file the default mode is set so i can chamge the source code and complile the file. (First or secound methode would be best because otherwise i habe to search how to compile the file for the Trinket.

EDIT: On looked at the source code and from that i can see that Mode 5 would be the one i need, right? Because there are not 4 as listed in the first post of the thread, there are 5 and also in differend order than in the first post.
To use the ino file i have to use Arduino IDE and compile and upload it to the Trinket M0 correct?

 

[popy]

@mattytrog: Its been a while since i was here and i saw, that you keep going the amazing work [emoji3] thx for that.

Just a quick question. My last trinket modchip update i made after the usb strap Story.

Whats the features you have added up to the recent version? Is it worth upgrade?

Thanks a lot and keep the ball rolling
pOpY

Gesendet von meinem LG-H815 mit Tapatalk

 

[mattytrog]

@mattytrog: Its been a while since i was here and i saw, that you keep going the amazing work [emoji3] thx for that.

Just a quick question. My last trinket modchip update i made after the usb strap Story.

Whats the features you have added up to the recent version? Is it worth upgrade?

Thanks a lot and keep the ball rolling
pOpY

Gesendet von meinem LG-H815 mit Tapatalk

Can't remember! There is change log in post 2. There are some test versions of just the payload. Obsolete now. New version coming with the latest hekate changes and lockpickrcm built in. You will be able to get every key from within hekate directly. And fixed a couple of gfx bugs that got introduced with 4.9.
Adjustable dotstar brightness
Toggle initial launch text on/off
Fixed a stack corruption bug too but I think that was fixed anyway in 4.9. working at it! Been sons birthday and been building trampolines up
So keep an eye out for it!

 

[fate6]

Haven't looked at updating my trinket in a long time, I have iirc and old method 1, its 4 wires and I use autoRCM for that sweet instant CFW action.
I grabbed "TRINKET_LEGACY3_SIMPLE_UF2_V099r1.UF2", Is this correct? seems to work fine beside it not powering off like the old uf2 i had did tho that could be from me switching to athmo recently.

 

[popy]

Can't remember! There is change log in post 2. There are some test versions of just the payload. Obsolete now. New version coming with the latest hekate changes and lockpickrcm built in. You will be able to get every key from within hekate directly. And fixed a couple of gfx bugs that got introduced with 4.9.
Adjustable dotstar brightness
Toggle initial launch text on/off
Fixed a stack corruption bug too but I think that was fixed anyway in 4.9. working at it! Been sons birthday and been building trampolines up
So keep an eye out for it!

Thx, will keep an eye on it.

Gesendet von meinem LG-H815 mit Tapatalk

 

[darrin41]

Haven't looked at updating my trinket in a long time, I have iirc and old method 1, its 4 wires and I use autoRCM for that sweet instant CFW action.
I grabbed "TRINKET_LEGACY3_SIMPLE_UF2_V099r1.UF2", Is this correct? seems to work fine beside it not powering off like the old uf2 i had did tho that could be from me switching to athmo recently.

r u using atomsphere

 

[metaljay]

@mattytrog i know you are in the middle of helping people, but any idea why since updating to the latest beta I turn my switch on and I’m greeted with “looking for payload” every time even though i have payload.bin on the root of my SD - After a second it boot anyway. Can you also update to CTR latest version when you get 5minutes?

Edit: should have just read up a few posts... sorry!

 

[Adr990]

Does Matty or anyone else familiar with the modchip code in C know if there is any way to detect if the Reset button is pressed?
Maybe more specifically, if the modchip still executes code when the physical reset button is pressed (not sure), is that state readable?

"ENABLE_STRAPS_ON_HARD_RESET" < the comments in the code say it's "//Obsolete? ...", but that would essentially be a global variable to detect whether the reset button is pressed, correct? Which is used to execute "dropstraps();".

If so, on the Trinket M0 pin 3 is unused, as far as I can see in the code.
I would like to fork the code for my self, or just ask right here (to Matty) if it's cool add a functionality to pin 3.

When the if statment here:
"if (ENABLE_STRAPS_ON_HARD_RESET == 1) {
dropstraps(); //pull straps low
}"
detects the reset press, Pin 3 could provide a voltage (3v for example, if that's the default pullup) before putting the Trinket to sleep.

---

In short, if the modchip drops the straps and let the system boot into normal/OFW mode, not RCM, could Pin 3 supply a signal (voltage) to let a different circuit (Transistor setup) know that the system is not gonna boot into RCM, or not.

This would allow, with addition of a transistor circuit to supply power to either one or the other eMMC module.
Giving the ability to have a on the fly dual-boot system. I'm currently designing a PCB layout to plug into the Switch that would allow two eMMC modules. Allowing power to one or the other eMMC module as mentioned before, through the Pin 3 signal I'm thinking about.


Or... there is already such a signal ready to use and I'm making a fool out of my self over thinking things here.

 

[mattytrog]

Does Matty or anyone else familiar with the modchip code in C know if there is any way to detect if the Reset button is pressed?
Maybe more specifically, if the modchip still executes code when the physical reset button is pressed (not sure), is that state readable?

"ENABLE_STRAPS_ON_HARD_RESET" < the comments in the code say it's "//Obsolete? ...", but that would essentially be a global variable to detect whether the reset button is pressed, correct? Which is used to execute "dropstraps();".

If so, on the Trinket M0 pin 3 is unused, as far as I can see in the code.
I would like to fork the code for my self, or just ask right here (to Matty) if it's cool add a functionality to pin 3.

When the if statment here:
"if (ENABLE_STRAPS_ON_HARD_RESET == 1) {
dropstraps(); //pull straps low
}"
detects the reset press, Pin 3 could provide a voltage (3v for example, if that's the default pullup) before putting the Trinket to sleep.

---

In short, if the modchip drops the straps and let the system boot into normal/OFW mode, not RCM, could Pin 3 supply a signal (voltage) to let a different circuit (Transistor setup) know that the system is not gonna boot into RCM, or not.

This would allow, with addition of a transistor circuit to supply power to either one or the other eMMC module.
Giving the ability to have a on the fly dual-boot system. I'm currently designing a PCB layout to plug into the Switch that would allow two eMMC modules. Allowing power to one or the other eMMC module as mentioned before, through the Pin 3 signal I'm thinking about.


Or... there is already such a signal ready to use and I'm making a fool out of my self over thinking things here.

That was meant for old method 3. But because we have SWITCHBOOT, it is obsolete.

If you aren`t using SWITCHBOOT and still have a old method 3 setup, you would enable the straps.

Otherwise, full-time CFW boot or dual-boot is enabled by flashing the appropriate SWITCHBOOT uf2.

 

[Adr990]

That was meant for old method 3. But because we have SWITCHBOOT, it is obsolete.

If you aren`t using SWITCHBOOT and still have a old method 3 setup, you would enable the straps.

Otherwise, full-time CFW boot or dual-boot is enabled by flashing the appropriate SWITCHBOOT uf2.

Ah yes, of course, makes sense.

I'm actually not sure which Trinket M0 set up I have yet, I haven't received my previously "rekt" Switch from you yet. (beginning of next week )
Perhaps you remember from the top of your head?

I guess what it comes down to is, is there a way to detect if the Switch is gonna boot into RCM or not? (Hardware wise)
I haven't looked into the SWITCHBOOT bootloader yet much, but I assume the same can be achieved from the bootloader, pulling up the unused pin 3 if the reset button is pressed and the straps are being dropped?

 

[mattytrog]

Ah yes, of course, makes sense.

I'm actually not sure which Trinket M0 set up I have yet, I haven't received my previously "rekt" Switch from you yet. (beginning of next week )
Perhaps you remember from the top of your head?

I guess what it comes down to is, is there a way to detect if the Switch is gonna boot into RCM or not? (Hardware wise)
I haven't looked into the SWITCHBOOT bootloader yet much, but I assume the same can be achieved from the bootloader, pulling up the unused pin 3 if the reset button is pressed and the straps are being dropped?

Your ahem... "special" switch has the new method with all straps connected. You have the full-time CFW version of SWITCHBOOT which drops both tyhe straps. If you want to change to dual-boot, drag the uf2 over.

 

[Adr990]

Ohh, I always thought pressing the reset button on boot would prevent the modchip from doing it's thing at all. Not loading the payload, and not doing anything with the straps.
The more you know, hah.