Correct.
Awesome stuff. Thanks.
Sent from my iPhone using Tapatalk
Correct.
Correct.
It does it by itself. In deep sleep, power consumption is measured in uA.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?
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!
All straps = Joycon, VOL+, USB Power on reset, USB data, PWR+ and GhND.
They are all straps.
Go to various points on the motherboard, to emulate putting a jig in and plugging in a payload pusher.
I have a weird issue.
I think that maybe just my joycon pin is soldered wrong.
I am using a trinket m0.
Ground is soldered from Gnd to the alternative ground near the switch battery wire.
Usb wires are in the normal location.
vol+ is soldered to point 0.
3 volt is on the underside of the nand chip
Point 3 on trinket is soldered to pin 10 on the physical joycon rail.
I can not figure out how to use the trinket to enter RCM.
the data wires, ground, and 3v are working because I can update the trinket UF2 from the usb-c port on the switch.
The vol+ is working because when I press it, the trinket has a red led turn on.
The means there must be something wrong with the joycon strap.
I am using the tiny gauge magnetic wire for this one.
I tried:
All three joycon strap points and trimming the magnetic wire shorter.
The only way I can enter RCM is to pull the nand, and after power on and reinsert, I am greeted with hekate pushed by the trinket.
Any ideas as to what I might be doing wrong?
--------------------- MERGED ---------------------------
Nevermind, I just replaced with a thicker wire and now it works. Weird.
Yep hopefully. Got one in from Oz at the moment waiting on parts lol.Hey @mattytrog, I've botched an install I don't think I can fix. Reckon you can help me out?
VOL- and PWR - PREVENT autoboot of "payload.bin" or "payload1.bin" (or indeed "payload2.bin"... ...) and launch a "tool" payload.
0: Disable (It also disables bootlogo. Having VOL- pressed since injection goes to menu.), #: Time to wait for VOL- to enter menu.
@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
@mattytrog
Got it running via an external trinket connected to the switch with USB-C!
However, to inject payload I have to press the reset button on the Trinket once. Is this normal?
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 ?
EDIT: I see you are using fusee-uf2... and you are using standard Hekate? Normal Hekate is just vol- to override autoboot.
That doesn`t apply to Fusee-UF2. Fusee-UF2 always has payload.bin enabled.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.