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

[FR0ZN]

@mattytrog

I caught up a bit on this thread and saw user post this picture of a new revision of the RCMX86:

Spoiler

Are you still sure that this fix applies to the corresponding pins on the older revision you posted here?:

Spoiler

 

[Phenj]

Jesus fucking christ this thread has a LOT of information for a newbie.
Alright, i've installed a SwitchMe into my Switch and i wanna boot Hekate first (i know how to access the chip etc and i KNOW i need to place a hekate .uf2 file in there)
what the heck do i do

 

[mattytrog]

@mattytrog

I caught up a bit on this thread and saw user post this picture of a new revision of the RCMX86:

Spoiler

Are you still sure that this fix applies to the corresponding pins on the older revision you posted here?:

Spoiler

The fix isn`t required for the newer revision as the D+/D- are broken out before the logic IC(yellow circled pads)

Jesus fucking christ this thread has a LOT of information for a newbie.
Alright, i've installed a SwitchMe into my Switch and i wanna boot Hekate first (i know how to access the chip etc and i KNOW i need to place a hekate .uf2 file in there)
what the heck do i do

Don`t worry...

Just download Fusee-UF2, either place hekate in SD root renamed to payload.bin, or (preferable) make an SD card (Kosmos) and put it on to the SD card. Fusee-UF2 will find update.bin (that Kosmos provides in bootloader folder)automatically.

 

[Phenj]

The fix isn`t required for the newer revision as the D+/D- are broken out before the logic IC(yellow circled pads)



Don`t worry...

Just download Fusee-UF2, either place hekate in SD root renamed to payload.bin, or (preferable) make an SD card (Kosmos) and put it on to the SD card. Fusee-UF2 will find update.bin (that Kosmos provides in bootloader folder)automatically.

Very kind! Thank you so much

 

[FR0ZN]

The fix isn`t required for the newer revision as the D+/D- are broken out before the logic IC(yellow circled pads)

Yes that's what I mean, the yellow circled pads don't lead to the same pins that you marked on the fix for the older revision

 

[mattytrog]

Yes that's what I mean, the yellow circled pads don't lead to the same pins that you marked on the fix for the older revision

They don`t. They are different chips thats why.

E18 = QFN32
G18 = QFN48

Different packages. Pinouts are still the same, just in a different place (eg PA07 = Trinket pin 3). On the E18, it is physical pin 8. On the G18 it is physical pin 12 but still PA07(we go off the datasheet).

 

[FR0ZN]

They don`t. They are different chips thats why.

E18 = QFN32
G18 = QFN48

Different packages. Pinouts are still the same, just in a different place (eg PA07 = Trinket pin 3). On the E18, it is physical pin 8. On the G18 it is physical pin 12 but still PA07(we go off the datasheet).

Daaaaaaaaaamn you are right ... I'm blind man, shit

One last question before I go on that journey.
Can you please explain that USB strap thingy to me? I cannot seem to find any information at all about it.

Thanks and regards!

 

[mattytrog]

Daaaaaaaaaamn you are right ... I'm blind man, shit

One last question before I go on that journey.
Can you please explain that USB strap thingy to me? I cannot seem to find any information at all about it.

Thanks and regards!

Yep. It ensures the payload gets pushed when you disconnect the console from the PC for example.

Normally, if you have all straps connected (excluding usb), and you plug in to USB to maybe test a payload or mount SD or something... The chip will pull the straps low as usual, to trigger RCM. However, because the console is connected to PC, the chip cannot push the payload due to the USB bus being in use, talking to PC.

The USB strap overcomes this, by sensing when the USB port is unplugged(thus freeing the USB bus on the Switch) and the chip will interpret this as "Cool. USB now free... Lets try to push a payload to get out of this RCM shit.".

If you don`t have the USB strap, you have to double-check the console is powered completely down as it will be in RCM and will stay in RCM until the battery dies otherwise.

 

[starlander]

I’m having problems getting SWITCHBOOT drive to open now.

I have followed the FAQ steps with no success.

V1.2.0 with vol+ strap fitted. Double tap puts Trinket M0 into rapid blinking mode. “Unable to charge” message when in CFW or OFW and connecting USB to PC.

Does the group have any suggestions before I tear down and resolder all of the points?



Sent from my iPhone using Tapatalk

 

[FR0ZN]

Yep. It ensures the payload gets pushed when you disconnect the console from the PC for example.

Normally, if you have all straps connected (excluding usb), and you plug in to USB to maybe test a payload or mount SD or something... The chip will pull the straps low as usual, to trigger RCM. However, because the console is connected to PC, the chip cannot push the payload due to the USB bus being in use, talking to PC.

The USB strap overcomes this, by sensing when the USB port is unplugged(thus freeing the USB bus on the Switch) and the chip will interpret this as "Cool. USB now free... Lets try to push a payload to get out of this RCM shit.".

If you don`t have the USB strap, you have to double-check the console is powered completely down as it will be in RCM and will stay in RCM until the battery dies otherwise.

Let's say I don't solder the USB strap - can I cooldboot the switch while it's docked?
I kinda see a problem there no ?

 

[mattytrog]

I’m having problems getting SWITCHBOOT drive to open now.

I have followed the FAQ steps with no success.

V1.2.0 with vol+ strap fitted. Double tap puts Trinket M0 into rapid blinking mode. “Unable to charge” message when in CFW or OFW and connecting USB to PC.

Does the group have any suggestions before I tear down and resolder all of the points?



Sent from my iPhone using Tapatalk

Thats the correct behaviour. Try launching a newer Switchboot with SAMD update function and follow the onscreen instructions

 

[starlander]

Thats the correct behaviour. Try launching a newer Switchboot with SAMD update function and follow the onscreen instructions

My trouble right now is that I can’t get switchboot drive open to update the trinket at all. My update to v1.20 was the last time I had it working.

I have followed the steps in the FAQ to open the drive, tried launching a payload or booting to CFW/OFW with no success. That’s why I’m thinking there may be a soldering defect. Any other tricks?


Sent from my iPhone using Tapatalk

 

[mattytrog]

My trouble right now is that I can’t get switchboot drive open to update the trinket at all. My update to v1.20 was the last time I had it working.

I have followed the steps in the FAQ to open the drive, tried launching a payload or booting to CFW/OFW with no success. That’s why I’m thinking there may be a soldering defect. Any other tricks?


Sent from my iPhone using Tapatalk

Get your console in RCM and connected to PC so the payload can`t be pushed...

Download the v1.3.4 BIN file and launch with TegraRCMsmash. Select SAMD update mode and follow instructions.

 

[Adr990]

Here I am again, on 1.2.2, I would like to update to 1.3.4, but again I can't get the Trinket M0 to appear as a drive.

What I did:
Boot into the Horizon home screen, get the Trinket M0 to go to the steady red LED and the slightly breathing red LED.
Then connect the official Nintendo USB C from the Pro Controller to a USB 2.0 on my motherboard (and a 3.0).
Nothing.

Doing the same from the Hekate main menu, getting it to the red breathing LED mode. For which I (by the way) do: 1 Rest button press, then double press the Reset button, other wise it just shows the Green and Red LEDs blinking and that is not the correct mode, right?

From Hekate after it's breathing the red LED, I plug in the USB C cable by Nintendo, I boot the SecondaryFusee.bin, and hope it will pop up on my computer.
Nothing.

I tried both Debian and Ubuntu, no luck.

Anything I've missed or done wrong?
Thanks!

I do also see the SAMD Update option in the Hekate screen, but following it's instruction (I think) doesn't make it appear on my computer as a drive either...

 

[mattytrog]

Here I am again, on 1.2.2, I would like to update to 1.3.4, but again I can't get the Trinket M0 to appear as a drive.

What I did:
Boot into the Horizon home screen, get the Trinket M0 to go to the steady red LED and the slightly breathing red LED.
Then connect the official Nintendo USB C from the Pro Controller to a USB 2.0 on my motherboard (and a 3.0).
Nothing.

Doing the same from the Hekate main menu, getting it to the red breathing LED mode. For which I (by the way) do: 1 Rest button press, then double press the Reset button, other wise it just shows the Green and Red LEDs blinking and that is not the correct mode, right?

From Hekate after it's breathing the red LED, I plug in the USB C cable by Nintendo, I boot the SecondaryFusee.bin, and hope it will pop up on my computer.
Nothing.

I tried both Debian and Ubuntu, no luck.

Anything I've missed or done wrong?
Thanks!

I do also see the SAMD Update option in the Hekate screen, but following it's instruction (I think) doesn't make it appear on my computer as a drive either...

Hmmm... Let the screen go black, then double-press reset, then connect.

 

[mattytrog]

OK... FINAL Update of Fusee-UF2 just to iron some problems out...

v3 coming today. Along with a Switchboot bugfix. Probably 1.3.4a or something.

Fusee-UF2 v3 changelog:

• This is the final version. No more updates after this (unless a new SAMD chip needs support, or a serious bug found).
• Default behaviour reverted to simply run payload.bin (or payload<number>.bin).
• Made additional controls more "logical" and ergonomic...
• Generated txt files no longer clutter up SD root. They go in bootloader/fusee

Please read the new README which can be generated by holding VOL- and VOL+:

Welcome to Fusee-UF2 Information.
Usable paths... Only payload.bin and payloadx.bin are displayed on error screen.
Made to just boot payload.bin(or payloadx.bin depending of selection in SAMD21, eg payload2.bin)

Hidden hardcoded paths:

Heirarchy of payloads looked for (in order...paths/files should be EXACTLY as below... Choose one...

The first one found will boot.

1. payload.bin (Can be anything you want it to be)
2. payload1.bin (changes depending on SAMD setting)
3. bootloader/payloads/payload.bin (Can be anything you want it to be)(keeps SD root tidy)
4. bootloader/payloads/payload1.bin (changes depending on SAMD setting)(keeps SD root tidy)
5. argon/argon.bin (touchscreen payload launcher)
6. bootloader/switchboot.bin (my hekate mod for chipped units)
7. bootloader/update.bin (last chance saloon - for Kosmos etc users - no need for payload.bin if this present - probably hekate)

Remember... First entry found will boot. Kosmos users don`t need to do anything... update.bin will boot automatically

Controls:
[VOL+]+[VOL-] - create paths_info.txt
[VOL+] - create SXOS licence.dat
[VOL-] - launch bootloader/switchboot (if present). If not present, launch argon/argon.bin. If neither present, try bootloader/update.bin

So... hold VOL+ and PWR, licence.dat will attempt to be created.

hold VOL- and PWR, payload.bin etc skipped and tries to launch a "tool" payload (switchboot / argon / hekate)

Just pressing power looks for "payload.bin", "payload<number>.bin", "bootloader/payloads/payload.bin", "bootloader/payloads/payload<number>.bin"

More info on Switchboot bugfix later on. Got to sort out this tip of a kitchen first and mow the front lawn. Bloody kids!

 

[starlander]

Get your console in RCM and connected to PC so the payload can`t be pushed...

Download the v1.3.4 BIN file and launch with TegraRCMsmash. Select SAMD update mode and follow instructions.

No luck. I can’t get the switch to register with PC in RCM mode either. I have booted into v1.2.0 then chosen “reboot (rcm)” to get to black screen.

In addition, I tried reaching RCM with jig, putting the chip into double-reset mode, and tried multiple cables. Seems like I’m locked out until I check the wiring.


Sent from my iPhone using Tapatalk

 

[mattytrog]

No luck. I can’t get the switch to register with PC in RCM mode either. I have booted into v1.2.0 then chosen “reboot (rcm)” to get to black screen.

In addition, I tried reaching RCM with jig, putting the chip into double-reset mode, and tried multiple cables. Seems like I’m locked out until I check the wiring.


Sent from my iPhone using Tapatalk

Yep. Check your wiring.

Take some pics of your install and stick them in modchip thread if you like
................................

Anyway... Anyone who is interested...
Just put another "tweak" into v1.3.5.

When generating keys, two files will be made.

1st will be the regular "prod.keys" as Lockpick does.
2nd will be a ChoiDuJour-ready "keys.txt" containing JUST the keys required for Choidujour(Shell version) written to SD root. Choi is fussy about what keys it has in its keyfile. Or it was fussy. Not checked on it for a bit.

Copy/paste this to your Choi folder on your PC and it saves you a job of messing around getting keyfiles etc...

Will push later on when I get time

So... Fusee-UF2 v3 FINAL later today...
Switchboot 1.3.5 later today(bin & UF2 files)

 

[peteruk]

Yep. Check your wiring.

Take some pics of your install and stick them in modchip thread if you like
................................

Anyway... Anyone who is interested...
Just put another "tweak" into v1.3.5.

When generating keys, two files will be made.

1st will be the regular "prod.keys" as Lockpick does.
2nd will be a ChoiDuJour-ready "keys.txt" containing JUST the keys required for Choidujour(Shell version) written to SD root. Choi is fussy about what keys it has in its keyfile. Or it was fussy. Not checked on it for a bit.

Copy/paste this to your Choi folder on your PC and it saves you a job of messing around getting keyfiles etc...

Will push later on when I get time

So... Fusee-UF2 v3 FINAL later today...
Switchboot 1.3.5 later today(bin & UF2 files)

looking forward to this release, can't wait - thank you for your hard work

 

[Romain80200]

Hello,
Can we add a led to the rcmx86 chip?
Thanks.