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

  • Thread starter Thread starter mattytrog
  • Start date Start date
  • Views Views 347,855
  • Replies Replies 1,803
  • Likes Likes 29
LOL, no worries :D

I wonder however, if you have any plans to make a real barebones UF2, that just looks for payload.bin on the SD card root.
Barebones == no buttons combos, no strap info, no license gen, no nothing - just something that loads payload.bin if it exists and that's it.
Try v1 of Fusee-UF2. Thats barebones.

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

https://github.com/mattytrog/Fusee-UF2/blob/master/Fusee-UF2-V1_UF2/TRINKET_REBUG_FUSEE_UF2_V1.UF2
 
  • Like
Reactions: FR0ZN
@mattytrog
Working great now! Think it was a bad usb-c connection.

Any way to power the trinket from usb-c plug on the switch?
Using external buttoncell right now.
 
@mattytrog
Working great now! Think it was a bad usb-c connection.

Any way to power the trinket from usb-c plug on the switch?
Using external buttoncell right now.
Sadly not. in RCM, no power to mean anything is output. Apart from uA from the USB signal lines.

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

That's nuts, thank you!

This is information that needs to be added to OP :wub:
There is v2 as well. Have a play see which one you like.
 
Sadly not. in RCM, no power to mean anything is output. Apart from uA from the USB signal lines.

Damn. Oh well, guessing the buttoncell with last a long time since the trinket is powered so shortly each time.

Maybe possible to use the usb-c port as a power switch, so it doesn't need to manually be powered on/off each time?
 
Can you give a me quick rundown, what the differences are for v1, v2, v3?

I beleive I read somewhere that v1 for example does indeed have this USB Strap functionality.
Honestly? I can't remember!

I do remember that v1 only looked for payload.bin.

Nothing else. No payload1.bin or anything.

I'll look through the source see if it jogs my memory
 
Honestly? I can't remember!

I do remember that v1 only looked for payload.bin.

Nothing else. No payload1.bin or anything.

I'll look through the source see if it jogs my memory

That would be awesome, because I believe a lot more people are just looking for a way to just run one payload and let t he rest be handled by it (for example Hekate).
 
That would be awesome, because I believe a lot more people are just looking for a way to just run one payload and let t he rest be handled by it (for example Hekate).
It's always been there. I had to much time on my hands.
 
I built an external gemma m0 dongle... I used this file from your github (just downloaded minutes ago) v1.51: generic_gemma_dongle.uf2
Hekate is booting up but it's saying 5.0.1?
Thanks for keeping this up to date!

Maybe I am being really dumb here, but I have the same issue. If I boot with no SD card I load up switchboot 1.5 DOS menu with Hekate 5.0.2. But with the SD card in I load up the touch interface of 5.0.1.

I don't have any payload.bin's that are overriding anything in the root of the SD and nothing saved to my INI and I am running the latest version of Kosmos. I have 0 idea where this is booting from.

Any help is appreciated.
 
Maybe I am being really dumb here, but I have the same issue. If I boot with no SD card I load up switchboot 1.5 DOS menu with Hekate 5.0.2. But with the SD card in I load up the touch interface of 5.0.1.

I don't have any payload.bin's that are overriding anything in the root of the SD and nothing saved to my INI and I am running the latest version of Kosmos. I have 0 idea where this is booting from.

Any help is appreciated.
It is nyx.bin.

In /bootloader/sys on SD.

If running switchboot, hold both Vol buttons to bypass it. Or rename it/delete it if you don't require it
 
  • Like
Reactions: Sparacis
Hi there, I soldered a trinket m0 for my friend's switch and when vol+ strap is soldered the vol+ button itself is acting as a vol-, vol- isn't functional and when I press launch without a microsd card inserted the "couldn't init microsd card" error message is being displayed all across the screen and softlocks the device. I didn't short anything while soldering, I even tried to solder the strap to the ribbon with the buttons instead the make sure it isn't my soldering and setup the trinket from scratch. Can anyone help? I'm clueless.
 
I keep getting my device isn't recognised on windows after connecting my Switch to the PC. But when I disconnect both the USB cables on the trinkets (traces 2 and 3) via desoldering them then I can connect the cable to the pc and everything works. Does this mean, I wouldn't be able to usb install stuff. I usually use nxmtp you see to connect my switch to the pc, but since those wires are connected I can't and when I remove them, I can use nxmtp to explore my switch content and usb install stuff. Is this normal? Here's what I disconnect to get everything working normally.
 
Hi there, I soldered a trinket m0 for my friend's switch and when vol+ strap is soldered the vol+ button itself is acting as a vol-, vol- isn't functional and when I press launch without a microsd card inserted the "couldn't init microsd card" error message is being displayed all across the screen and softlocks the device. I didn't short anything while soldering, I even tried to solder the strap to the ribbon with the buttons instead the make sure it isn't my soldering and setup the trinket from scratch. Can anyone help? I'm clueless.
1) Is the Trinket flashed OK?
2) There is a capacitor... Shunt capacitor. Gives the "discrete" voltage somewhere to go if current too high. Makes the pressing action nice and smooth. A bit like a condenser on a car ignition system. If it fails, it shorts GPIO to GND, leading to a "constantly pressed" condition. Doesn`t happen often during installs. Replace with something like a 100nF 6.3v 0201.

This could be shorted.

Remove and retest console. If vol buttons now work, then replace this.
volup_cap.jpg


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

I keep getting my device isn't recognised on windows after connecting my Switch to the PC. But when I disconnect both the USB cables on the trinkets (traces 2 and 3) via desoldering them then I can connect the cable to the pc and everything works. Does this mean, I wouldn't be able to usb install stuff. I usually use nxmtp you see to connect my switch to the pc, but since those wires are connected I can't and when I remove them, I can use nxmtp to explore my switch content and usb install stuff. Is this normal? Here's what I disconnect to get everything working normally.


It will conflict if trying to update Trinket.

Use the samd_21_update payload in OP. Send that payload - console will appear dead. Double-press RESET, plug into USB. Trinketboot or whatever should pop up.
 
Last edited by mattytrog,
It will conflict if trying to update Trinket.

Use the samd_21_update payload in OP. Send that payload - console will appear dead. Double-press RESET, plug into USB. Trinketboot or whatever should pop up.

Alright I will try this. Thank you and I will get back to you sir
 
  • Like
Reactions: mattytrog
1) Is the Trinket flashed OK?
2) There is a capacitor... Shunt capacitor. Gives the "discrete" voltage somewhere to go if current too high. Makes the pressing action nice and smooth. A bit like a condenser on a car ignition system. If it fails, it shorts GPIO to GND, leading to a "constantly pressed" condition. Doesn`t happen often during installs. Replace with something like a 100nF 6.3v 0201.

This could be shorted.

Remove and retest console. If vol buttons now work, then replace this.
View attachment 185316

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



It will conflict if trying to update Trinket.

Use the samd_21_update payload in OP. Send that payload - console will appear dead. Double-press RESET, plug into USB. Trinketboot or whatever should pop up.
I flashed the trinket like 5 times so I don't think anything's wrong with it. I'll check the cap when I arrive home and report back, thanks!
 
Use the samd_21_update payload in OP. Send that payload - console will appear dead. Double-press RESET, plug into USB. Trinketboot or whatever should pop up.

Unfortunately, the moment I just connect the Switch to the PC it just brings up device is not recognised. Another guy on here, said he was experiencing the same problem on a thread I created. I don't know whether it's an issue with Windows or just the D- and D+ pads, once I desolder them off everything is fine and when they're connected I get the issues.
 

Site & Scene News

Popular threads in this forum