No. I took out the battery info code due to space restrictions. However now, I have made space for it.@mattytrog:
What does "Battery info code added back. Sorry about that!" in v1.10 changelog mean?
Battery info in hekate or have you finally found a way to charge the switch when its powered off and show the "battery osd?"
thx
pOpY
I'm not brave enough!@mattytrog have you thought about a pull request rather than a separate loader?
Hey, how's it going? I saw that you marked the X86RCM dongle as "in testing", do you have anyone that has flashed it successfully, or just nobody who has one has popped up to try it? I'm asking because I dug mine out last night and decided to see what was going on with your project and came across this new thread/software. It was like 4am and I was on the low-end of brain fuel, and was not successful. That may be just because I was doing something wrong though, I haven't had time to play with any Arduino stuff in a few months and am in no way an expert.
So my question is just, are you aware of anyone who has successfully flashed and used this on the X86RCM dongle? Thanks.
Thanks. As I posted, it is a dongle not a bare board. In OP board is marked as "in testing" (I believe possibly due to the buttons pins being different, IIRC). I appreciate the reply though.I don't have one, but it's just a atsamd21 based chip - you just need to connect Voltage + Ground and D+ D-. You could wire that straight to a usb cable if you don't already have it installed, just connect the reset pin 2 ground twice within 2 seconds and you'll boot into 'trinket mode', at this point it will show up as a com port and you can flash it with Arduino if you have the correct files on your computer.
I've had no feedback one way or the other. I cant get hold those dongles eitherThanks. As I posted, it is a dongle not a bare board. In OP board is marked as "in testing" (I believe possibly due to the buttons pins being different, IIRC). I appreciate the reply though.
View attachment 162511
Maybe I am dumb(most likely I am) but since flashing v1.10 I am forced to select CFW 2 times now when launching. First selection tells me it found pkage1(xxxxxxxxxx) Sept needs to run please re-select this option on reboot. Reselect CFW when it reboots and atmosphere launches. However if I use hekate directly as a payload.bin I can launch CFW first time no issues. Any idea what might be causing that or is it by design in v1.1?
1.2 aint out yet!When I launch regular Hekate it works fine I will flash 1.2 and report back, Thanks for all your hard work on this!
Yeah its obsolete nnow mate. Its still on my git somewhere if you insist on itQuick question after a few months break. I used to install a rebug with the 4 wire method and the simple loader program, so all I had to do was drop my payload in the "0" folder and I was done.
Now I cant find any mentions of this "0" folder anymore. Is there a solution where it isnt needed anymore? I like to keep my root sd card folder as clean as possible, so if there is a way to update and autoboot a payload inside the bootloader or argon folder, which steps or files do I need to take?