I ended up soldering to the SWI bus and programming the stock firmware via stlink and it worked! then i got confident and tried to reinstall 7.2 with the stlink and proceeded to break everything. hello darkness my old friend. HWfly picofly rp2040 for me so i don't have to redo the flex ribbon cable.
Fair enough - i am an embedded systems engineer, i have a bag of about 15 different programmers, i'm glad i could use my cheap stlink for once. what i don't like is the clone of a clone / poor documentation, but what can one expect.
what. i said i was using a programmer before. you said that it's not possible to flash the device. i nearly stopped based on your response.
ah, i see. thank you
Aaand it's fixed. programmed the attached firmware and bootloader through the four soldered wires schematic above via stlink. Back in hekate, everything lives.
don't spread misinformation
I don't really understand, it's quite frustrating, the chip wasn't cheap.
My plan is to follow this pinout and use a programmer to attempt a new firmware, only real question is i'm not sure which firmware
I tried to update my V5 switch with firmware 0.7.2, then when the switch was one it would only go into OFW during which the hwfly LED was fully white. The usb breakout ribbon cable must have microfractures because it doesn't work properly so I was thinking of using my j link or stlink to update...
No, the SD card flex is fine. i can see in OFW it's all good.
I guess i am being fooled in thinking this was official (the storefront did look like the 'official' one when i bought it). It was sold as V5 but the text 'Mv1-6' is confusing me, is this V6 or V5? I am thinking of digging out my J...
You're not wrong there - however it started acting up hence my last ditch effort at doing the risky thing. I was in between swapping /transferring microSDs and when done, on both SD cards, sometimes booting up would get into hekate, and mostly it would not, usually without the SD it'd say...
I have an official v5 and tried updating with 0.7.2, and it seems i'm too stuck on solid white. now when i try to plug the micro usb B in the computer, it says the usb device malfunctioned. is there anyway back to functionality or is this chip dead? I can still boot to OFW
Yeah, i was worried if there was a point in the setup of hekate etc where you need the touchscreen but i just checked and it seems like I won't need it, so i think it's good to go.
As the title alludes, I came into possession a very broken switch, after a lot of time bringing it back to life (the whole thing was bent in half about 5 - 10 degrees, all in pieces, no screws) I came to realise the digitiser never worked. I replaced the digitiser twice. Could never get it to...
Sorry if this question is inappropriate.
I'm trying to run the status monitor overlay, and I note that with the sigpatches from rentry, core 3 shoots to 100% when running the overlay, which makes the overlay unresponsive until reboot, or if I turn on flight mode. Similarly, if i turn on flight...
I like that games can be fixed after the fact, hate that it's being abused via beta tests... And DLC... I was a 7800 owner back in the day and loved Impossible Mission, turns out I couldn't beat it because it was actually impossible lol