Is there a way to turn off the trinket when not in use so that it doesn't kill the battery when off for an extended period of time?
It does it by itself. In deep sleep, power consumption is measured in uA.
Power consumption is basically nothing.
I think you need to update your payload file, but @mattytrog will tell you for sure as I'm still new to this.
Hello.
I have an issue, I installed the Trinket m0. I installed the wires and everything.
I used this from part 1:
SWITCHBOOT_TRINKET_JOYCON_VOLUME.uf2
I used this for part 2: TRINKET.UF2
I flashed the trinket and it works fine with booting. I press the power and it goes into CFW and not OFW. I tried volume + power and that didn't work obviously. So I wanted to flash the chips again with the correct files this time.
When i press the reset twice and now connect it to my pc. it just says USB device not recognised, no matter how many times I tried.
I did sighly nug i believe the resistor near the 3.3v one and it came out of place, where you show on your diagram to connect. but everything was working fine with booting.
The other issue was on the trinket trace 2 actually teared off due to the wire i used. (When you remove the usb port, trace 2 from left to right) but i was able to still solder and connect a wire. Basically, all of it is done to your diagram but those were the only two mistakes i made. Nudging the resistor and with that trace? I'm wondering if it could be any of these? If it is the trace, is there anyway I could fix it? I see connection points at the back for + and - is that D+ and D- ?
Maybe I could just connect the wires there and it will work? Thought I'd ask you
OK... Quick trial of something here.
I`m slowly working through questions people so bare with me!
Attached is a UF2. A new feature I am testing.
Just for TRINKET at the minute. You MUST have the USB strap fitted to try this... If you don`t, obviously it won`t work. It will just be normal.
Flash this UF2 as usual, leave USB plugged in, again as usual so the chip can get a port reading...
Switchboot will load up. As usual.
In "Boot Options", you will see a new option "Power-off after USB disconnect".
If you enable this, you can now disconnect USB when in RCM mode and the Switch will power completely off, instead of rebooting to Switchboot menu. You will need an SD inserted.
Let me know if it works for you! It does here.
I`m slowly working through questions people so bare with me!
Attached is a UF2. A new feature I am testing.
Just for TRINKET at the minute. You MUST have the USB strap fitted to try this... If you don`t, obviously it won`t work. It will just be normal.
Flash this UF2 as usual, leave USB plugged in, again as usual so the chip can get a port reading...
Switchboot will load up. As usual.
In "Boot Options", you will see a new option "Power-off after USB disconnect".
If you enable this, you can now disconnect USB when in RCM mode and the Switch will power completely off, instead of rebooting to Switchboot menu. You will need an SD inserted.
Let me know if it works for you! It does here.
Last edited by mattytrog,
Thicker wire on the whole modchip, or just the joycon strap? I'm having issues as well with thin magnet wire.
@mattytrog I wired up an itsbitsy with switchboot on it, right now it's behaviour is flashing red lights and boots into normal horizon with pwr button, pwr and volume + goes to a black screen. I checked to see if I could flash over usb and at one point I could view the switchboot folder, but now windows says it can't identify the connected usb device. Any advice for trouble-shooting?
Should mention lots of flashing red lights
Should mention lots of flashing red lights
Question:
I saw the following line on the first page under the Fusee-UF2 section:
Now let's say I use Hekate as payload.bin and have bootwait set to 0. In the readme it says:
How would be I be able to enter Hekates menu on boot, if PWR and VOL- is already set by Fusee-UF2 to not launch a payload.bin ?
I saw the following line on the first page under the Fusee-UF2 section:
Now let's say I use Hekate as payload.bin and have bootwait set to 0. In the readme it says:
How would be I be able to enter Hekates menu on boot, if PWR and VOL- is already set by Fusee-UF2 to not launch a payload.bin ?
I think you have dropped the wrong UF2 for part 2 on there. Part 1 appears correct as its entering RCM.
Depends what file you are using for external. It will timeout after so long and go to sleep, necessating a reset press.
Because both VOL buttons overrides all.
Press both vol buttons - it stops payload.bin, autoboot and nyx.
From power off, hold both vol buttons and press power until menu pops up.
EDIT: I see you are using fusee-uf2... and you are using standard Hekate? Normal Hekate is just vol- to override autoboot.
Last edited by mattytrog,
Correct, but let's say I want to enter Hekate menu on power up - so I hold VOL- and press PWR.
According to the first page, this would disable loading the payload.bin (hekate) on boot - so I would never reach hekates menu, if it doesn't load.
Isn't that a conflict?
That doesn`t apply to Fusee-UF2. Fusee-UF2 always has payload.bin enabled.
So the boot chain would go...
Power-on > Fusee-UF2 (look for payload.bin) > found > boots payload.bin(Hekate) > If payload.bin in my Hekate is NOW disabled, the menu will show, or autoboot will continue.
Thanks!
Then the information on the first page doesn't seem correct I fear
Probably. You have to remember, I have idiotitis.
Will see if I can tidy the OP up later.
LOL, no worries
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.
Similar threads
