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

[mattytrog]

@mattytrog

Hello I've always used the TRINKET_LEGACY3_SIMPLE_UF2_UF2,
but the new Hello I've always used the TRINKET_LEGACY3_SIMPLE_UF2_UF2 does not work for me anymore,
but the previous one already...

When I flash the new UF2, everything looks fine in the beginning,
but as soon as I turn off the console,
all LEDs light up and the console stays black when I want to start the CFW.

Always start the console with + button and power for the CFW


Please help
Thank you and best regards

Ok sir will take a look

 

[TheSearch]

@mattytrog

Hello I've always used the TRINKET_LEGACY3_SIMPLE_UF2_UF2,
but the new Hello I've always used the TRINKET_LEGACY3_SIMPLE_UF2_UF2 does not work for me anymore,
but the previous one already...

When I flash the new UF2, everything looks fine in the beginning,
but as soon as I turn off the console,
all LEDs light up and the console stays black when I want to start the CFW.

Always start the console with + button and power for the CFW


Please help
Thank you and best regards

Ok sir will take a look

Thank you so much

 

[mattytrog]

Yes I see the problem.

Just had an "I`m an idiot" moment... Looks like a bugfix version is coming up

 

[TheSearch]

Yes I see the problem.

Just had an "I`m an idiot" moment... Looks like a bugfix version is coming up

many thanks

no, no idiot, I am very grateful for your work

 

[josete2k]

Does this affect to all users? I'm on RCMX86 as I said..... Thanks in advance.

 

[mattytrog]

Does this affect to all users? I'm on RCMX86 as I said..... Thanks in advance.

Looks like it.

Its a fault in the joycon strap detection code causing a perpetual loop. It`s only 4 fucking lines! I win the twat award for such a basic error. In theory, once you press reset on the chip, it should go back to normal.

But I`ve now fixed the bug. Will make new UF2s shortly

 

[TheSearch]

Looks like it.

Its a fault in the joycon strap detection code causing a perpetual loop. It`s only 4 fucking lines! I win the twat award for such a basic error. In theory, once you press reset on the chip, it should go back to normal.

But I`ve now fixed the bug. Will make new UF2s shortly

Have tried the reset button, and it seems to work ...

Purely as information

 

[mattytrog]

Updated UF2s now uploaded. 0.9.9r4a online.

• Fixed joycon strap detect which was causing chip to hang on initial boot.
• Full EEPROM reset now resets all strap detection too in the emulated EEPROM. For a "fresh-flash" experience.

 

[peteruk]

Updated UF2s now uploaded. 0.9.9r4a online.

• Fixed joycon strap detect which was causing chip to hang on initial boot.
• Full EEPROM reset now resets all strap detection too in the emulated EEPROM. For a "fresh-flash" experience.

Matty - Do I need this

 

[mattytrog]

Matty - Do I need this

If you are having problems, yes.

If all is working, no. It's only the initial boot that was affected.

 

[TheSearch]

Thank you so much, for your grate Work

 

[FromZero]

@mattytrog Is this normal?

Originally, I had your install guide done with Rebug chip using 0 folder and 01.s2 and start.bin. That was (is) great. Switching to Atmosphere now though and using your new simple current.uf2 I get a 60-80 second delay from power button press (using autoRCM) to SEPT screen. During which the screen is all black and I just wait. Is there something I am missing or something I did in the initial version that is hindering me now?

Admittedly I was out of the current news on the switch for a few months but as I try to catch up I can't find anything on this. Switching back to your old set up with the 0 folder brings back normal boot times.

And thank you for the great work.

 

[Adr990]

I just loaded the SX payload, installed emuNAND on a hidden partition.
Set up the license and copied back the payload.bin, and tried to boot again.

I'm not sure if this is a Switch problem or a SX problem but it booted to the Nintendo Logo from the SX splash screen, and the screen went black.
Now... I can't turn it on or off it seems, no matter if I try to charge it or hold the power button.
No more LEDs from the Trinket M0 either...

I'm now trying to keep it on the charger, but it's kinda worrisome and odd.

Edit: It seems that it boots again after this long while. Still odd I can't boot into my SX/EmuNAND FW since it goes black...

Edit 2: Alright... now it doesn't want to boot, again. Only booted into OFW then powered off.

Edit 3: Maybe it has to do with exFAT, my SD Card is formatted in exFat and my sysNAND doesn't support exFAT yet. This might cause some kind of weird error with booting the EmuNAND or something?

 

[mattytrog]

@mattytrog Is this normal?

Originally, I had your install guide done with Rebug chip using 0 folder and 01.s2 and start.bin. That was (is) great. Switching to Atmosphere now though and using your new simple current.uf2 I get a 60-80 second delay from power button press (using autoRCM) to SEPT screen. During which the screen is all black and I just wait. Is there something I am missing or something I did in the initial version that is hindering me now?

Admittedly I was out of the current news on the switch for a few months but as I try to catch up I can't find anything on this. Switching back to your old set up with the 0 folder brings back normal boot times.

And thank you for the great work.

Hello.
Nothing in Simple-UF2 should cause such a long delay. I have running latest Atmosphere, booting thru CFW option in my modded Hekate menu. Sept does its thing, then it boots. I tried the SD card maker (Kosmos is it?) website and it worked like a charm.

Something is wrong somewhere for a delay to be that long... Mind telling me your exact configuration?

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

I just loaded the SX payload, installed emuNAND on a hidden partition.
Set up the license and copied back the payload.bin, and tried to boot again.

I'm not sure if this is a Switch problem or a SX problem but it booted to the Nintendo Logo from the SX splash screen, and the screen went black.
Now... I can't turn it on or off it seems, no matter if I try to charge it or hold the power button.
No more LEDs from the Trinket M0 either...

I'm now trying to keep it on the charger, but it's kinda worrisome and odd.

Edit: It seems that it boots again after this long while. Still odd I can't boot into my SX/EmuNAND FW since it goes black...

Edit 2: Alright... now it doesn't want to boot, again. Only booted into OFW then powered off.

Edit 3: Maybe it has to do with exFAT, my SD Card is formatted in exFat and my sysNAND doesn't support exFAT yet. This might cause some kind of weird error with booting the EmuNAND or something?

Could very well be exfat related.

I`d change to fat32 if it were me.

 

[FromZero]

Hello.
Nothing in Simple-UF2 should cause such a long delay. I have running latest Atmosphere, booting thru CFW option in my modded Hekate menu. Sept does its thing, then it boots. I tried the SD card maker (Kosmos is it?) website and it worked like a charm.

Something is wrong somewhere for a delay to be that long... Mind telling me your exact configuration?

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

Thanks for the reply.

• SwitchMe chip, 4 wire install to eeprom, rcm soldered joycon pins but also auto rcm from choidujour.
  
• Fat32 128gb
• Switched from sxos to atmosphere
• Nx 7.0.0
  
• Payload.bin is for atmosphere
• Reverting to using old 0 folder setup with sx and 6.2 causes no delay

 

[mattytrog]

Thanks for the reply.

• SwitchMe chip, 4 wire install to eeprom, rcm soldered joycon pins but also auto rcm from choidujour.
  
• Fat32 128gb
• Switched from sxos to atmosphere
• Nx 7.0.0
  
• Payload.bin is for atmosphere
• Reverting to using old 0 folder setup with sx and 6.2 causes no delay

I`ve just tried it.

Booted normal for me. Using fusee-primary as payload.bin

I`d double-check your SD card. Boot times are normal for me in all circumstances. Puzzled.

 

[FromZero]

I`ve just tried it.

Booted normal for me. Using fusee-primary as payload.bin

I`d double-check your SD card. Boot times are normal for me in all circumstances. Puzzled.

Thank you, I'll build up a test SD card.

 

[TheSearch]

@mattytrog

Hello Is there actually a way to disable the TrinketM0 with a simple UF2 file and of course to reactivate?

Greetings and thank you

 

[mattytrog]

@mattytrog

Hello Is there actually a way to disable the TrinketM0 with a simple UF2 file and of course to reactivate?

Greetings and thank you

There is, but I've disabled it in current version.

Check further back, I made a disable uf2. Next version will have a 30 second vol+ hold feature that will disable/enable the chip entirely.

 

[FromZero]

Thank you, I'll build up a test SD card.

@mattytrog Looks like I have a corrupted NAND, as I now cant get into horizon at all. Going to try restoring it in about 12 hours. Just wanted to let you know in case it helps in your travels.