Finally something I can work with. Thank you for the install guide. I can see there's a lot of effort put into it.
Thanks for the response! Yeah I have seen a picture showing the traces from Pins 3 and 4 being connected but yeah I'm going to go back and solder a new wire from the CPU pins 3 and 4 to the RP2040 and see if that makes a difference. If no difference I will turn my attention to the SP1 and SP2 points on the CPU caps.
I bought this chip but contacted the seller who gave me old guides on its installation, from the previous hwfly. I saw that the chip, even though it is a custom version, still needs wire soldering. Any chance you could tell me how to do it, send me a diagram? I have a switc hac -001(-01) 2020 which would be a core v2. Thanks
Just find this on aliexpress for core switch!
Got in the mail today...
Does anyone ever face with this problem? when it boot into OFW, it stuck on Joycon logo. then it was boot into CFW and it loaded atmosphere logo and after it turned into black screen. Anyone know the solution, pls help. thanks
Attachments
If the normal one is working, using sda,scl is redundant.
I mean in business perspective, time is money. Putting those sda, scl need more time. Logically you need to charge more.
Buuuuuutttt....
Of course putting those sda, scl is better, so when the normal one somehow didn't work, it might still work on the undervoltage.
Your sd card fat 32?
You add releases Atmosphere cfw files?
You see System update?
Your dat0 adapter value?
You can do nand backup?
You| pico fly firmware is?
I don't think that point is important, if it is working without these two points. SDA and SCL wires also make the glitch time worse. But I face the one stubborn switch APU which needed these two point. Without these two points I have to press reset button everytime.
1: Without these two points the glitch time is fast but I have to press reset button everytime
2: With these two points glitch time is worse from 3 sec to 10 sec arounds but I don't have to press reset button. So, you can close your switch.
My Thought: I think I'm going to add these two points everytime in future. Because in some case if mosfet becomes weak or get some loose wire or one mosfet fails. So, these two points will help to get a successful glitch. So, to me I consider these two points important for long term case. Like @abal1000x said above : putting those sda, scl is better
sd card is fat32, Atmosphere last version , dat0 value 0.745v , able to nand backup, pico fly firmware 2.73
No. connecting SDA/SCL makes the glitch a lot slower. They should only be connected on switches that can't glitch without them.
Do nand backup for more safe.try inter emummc cfw. Befor do that. Make emummc but that make partion on sd so backup sd befor do that. For more safe.
Try 2.74, with 300 MHz precision it might help with i2c undervoltage stability where the width requirement suffers
Well none of that made any difference, sadly. Glitch times still sporadic and range from 2s - 20s+. Replacing flex cable with dual mosfet setup surprisingly had no affect either. I also adjusted the DAT0 adapter as someone suggested but nothing seem to make an ounce of difference to the sporadic glitch times.
Thanks to everyone who responded with tips and suggestions. I have the board in an ultrasonic bath right now probably going to just reassemble the console and put it aside for now as not sure what else to try. I feel like this board might just have a problematic CPU when it comes to the glitch. If I had one I would fit a HWFLY and see if that performs better but currently don't have one to hand.
no need for leaving the usc on since we can update firmware over picotool box
v2.74 has glitch speed improvements (offset randomization, more MHz)
Post automatically merged:
Dirty RST line, it's very sensitive. Please clean flux
Similar threads
