Apologies in advance for my stupidity.
Since I can see a LED light up inside the switch. that means I have the VOL + strap fitted. So I should be able to use this if I understand correctly, right?
Next, does this in any way allow me to essentially automatically boot hekate and properly charge the battery of my switch while it's off / battery empty?
So, do I just try to flash "Trinket" for "Fusee_Suite part 1" first, then "Trinket" for "Fusee_Suite part 2" after?
Or do I just use "SAMD21 Update Payload"?
Since I can see a LED light up inside the switch. that means I have the VOL + strap fitted. So I should be able to use this if I understand correctly, right?
Next, does this in any way allow me to essentially automatically boot hekate and properly charge the battery of my switch while it's off / battery empty?
So, do I just try to flash "Trinket" for "Fusee_Suite part 1" first, then "Trinket" for "Fusee_Suite part 2" after?
Or do I just use "SAMD21 Update Payload"?
I have a vol + strap and used it to access the drive via usb to pc. I copied over part 1. The drive disappeared but this time it didn't come back. I reboot my switch and now my trinket is solid red with a smaller pulsing red. I tried resetting it, but it cant be accessed for its part 2 file
Last edited by bevis,
Hi there!
It's been a long time that I flashed my Trinket, I did the "both straps" mounting (Vol+ & joycon) to always boot to CFW.
I still doesn't want to burn efuse (not sure if it's still important or not?) but I need to upgrade to 9.1.0 (I'm currently on 6.2.0), do I have to flash a new UF2 on the chip ?
Furthermore, is there a way to dualboot on both emuNAND CFW and sysNAND OFW without burning efuses?
Thanking you in advance and keep the good work!
It's been a long time that I flashed my Trinket, I did the "both straps" mounting (Vol+ & joycon) to always boot to CFW.
I still doesn't want to burn efuse (not sure if it's still important or not?) but I need to upgrade to 9.1.0 (I'm currently on 6.2.0), do I have to flash a new UF2 on the chip ?
Furthermore, is there a way to dualboot on both emuNAND CFW and sysNAND OFW without burning efuses?
Thanking you in advance and keep the good work!
Just wanted to say that i have been following your work for years and never properly thanked you, so here it goes, a BIG THANK YOU
Hello everyone.
Back after prolonged period of illness.
Slowly getting back up to speed.
Anyway... Before I went down with illness, I finished the "newest" (actually a fortnight old now) version.
Some under the hood changes.
These are:
If you want a special bootlogo, just for your modchip side (excluding hekate-side), rename your bootlogo to bootloader/bootlogo1.bmp.
If bootlogo1.bmp is found, this will be shown INSTEAD of bootlogo.bmp. This will free Hekate or whatever to use bootlogo.bmp as usual, permitting you to have 2 different bootlogos if you wish. (1 for fusee, 1 for Hekate).
Example:
You have a "Fusee" bootlogo you want to use at power-on and you have an "atmosphere" one you wish to use via Hekate.
Name the Fusee one bootlogo1.bmp and the Atmosphere one bootlogo.bmp (as Hekate will use it). Both will show in order.
To completely disable bootlogo from being rendered, this can be done in modchip settings or just place an empty file called "fusee_bootlogo_disabled" in bootloader folder. This will enable you to use the OEM boot animations from previous releases, if you wish.
So percentage AND voltage is checked now.
If both % and voltage are down, charging without booting (cutting out bootloop) will happen as it should.
If voltage is down, but % is being reported as higher, this will begin charging loop also. And visaversa.
Releases coming later today. Will make various specials too.
Cheers and thanks for reading and testing my stuff. Thanks for your patience for waiting for me. I hate being away for this length of time, but its been serious!
Matty
Back after prolonged period of illness.
Slowly getting back up to speed.
Anyway... Before I went down with illness, I finished the "newest" (actually a fortnight old now) version.
Some under the hood changes.
These are:
- Ability to use a bootlogo... Usage is as follows...
If you want a special bootlogo, just for your modchip side (excluding hekate-side), rename your bootlogo to bootloader/bootlogo1.bmp.
If bootlogo1.bmp is found, this will be shown INSTEAD of bootlogo.bmp. This will free Hekate or whatever to use bootlogo.bmp as usual, permitting you to have 2 different bootlogos if you wish. (1 for fusee, 1 for Hekate).
Example:
You have a "Fusee" bootlogo you want to use at power-on and you have an "atmosphere" one you wish to use via Hekate.
Name the Fusee one bootlogo1.bmp and the Atmosphere one bootlogo.bmp (as Hekate will use it). Both will show in order.
To completely disable bootlogo from being rendered, this can be done in modchip settings or just place an empty file called "fusee_bootlogo_disabled" in bootloader folder. This will enable you to use the OEM boot animations from previous releases, if you wish.
- Flat battery code is now checking battery voltage as well as a percentage of SOC (state of charge).
So percentage AND voltage is checked now.
If both % and voltage are down, charging without booting (cutting out bootloop) will happen as it should.
If voltage is down, but % is being reported as higher, this will begin charging loop also. And visaversa.
- Percentage and mV is shown on screen now.
- Longer timeouts for screen dimming / screensaver
- SD card is checked for mounting every half-second, via a resetting counter that triggers a refresh
- A quick glance over the thread, people have asked why we cannot set chip particulars within Fusee directly... This is because, as of yet, I have not figured out how to enable serial over USB from the Switch / BPMP side. Other workarounds to this, are using one of the GPIOs that are currently connecting joycon, vol or USB and reprogramming the chip that way. I just don`t yet know enough about how the USB subsystem operates to implement a solution.
Releases coming later today. Will make various specials too.
Cheers and thanks for reading and testing my stuff. Thanks for your patience for waiting for me. I hate being away for this length of time, but its been serious!
Matty
Glad to have you back Matty and more happy you're feeling better
V6_090220 uploaded.
Check OP and have a look at controls section. As usual, not mandatory to update at all.
Check OP and have a look at controls section. As usual, not mandatory to update at all.
Hi thanks for all ,
But since I have install the 2 UF2 files, everything works fine, but I can't access anymore to my modchip by double click on the reset button...
I have a REBUG chip and this is the first time I use your file (before I took UF2 file from Aboshi Github)
Thanks
But since I have install the 2 UF2 files, everything works fine, but I can't access anymore to my modchip by double click on the reset button...
I have a REBUG chip and this is the first time I use your file (before I took UF2 file from Aboshi Github)
Thanks
Use the SAMD21 update payload. This will get you in.
If you haven`t updated your Horizon firmware, you should be able to access just as before. Or use the option in the menu of Fuseesuite.
Nintendo changed USB access and made accessing UF2 mode from within Horizon more troublesome.
Thanks for your responce.
I already try to boot on the update payload, but I'll try again today.
I also try the update option in fusesuite, but after double clic on reset buttons, nothing happen.
My horizon is up to date unfortunately
[EDIT]
Even if I try with the update payload, the screen turn to black, I clic twice on the reset button and connect USB cable, but nothing happen. I tried diffrent USB port, no effect
I already try to boot on the update payload, but I'll try again today.
I also try the update option in fusesuite, but after double clic on reset buttons, nothing happen.
My horizon is up to date unfortunately
[EDIT]
Even if I try with the update payload, the screen turn to black, I clic twice on the reset button and connect USB cable, but nothing happen. I tried diffrent USB port, no effect
Last edited by nExNihilo,
You will need to double press reset somehow, unless you have vol+ strap. If you have vol+ strap, disconnect from pc if connected, hold down vol+ for around 30 seconds until steady white flashing light appears through the grilles.
Then power off, restart and connect to pc. Done.
The first post says it all:
Part 1 (links below) is responsible for strap control and dual-boot / perma-CFW settings.
Part 2 (links below) is responsible for pushing the payload, whatever it may be, and battery control.
Similar threads
-
- Article
-
The Real Jdbye
*is birb*
-
@
K3Nv2:
I'd like to see a DS emulator that allows casting top screen to TV then use bottom for the touch screen stuff+1 -
-
-
@ HiradeGirl:
@K3Nv2 I did that using Citra for 3DS games. Bottom screen was my smartphone. Until I got the touch screen. -
-
-
-
@
Psionic Roshambo:
Ken I have that sort of set up on Drastic on Pi for games that don't require touch -
-
-
Any TV with your PC connected with Citra and any smartphone to use as a screen using a free play store app.+1
-
-
-
-
-
-
-
-
-
-
-
-
-
-
