[OLED] Picofly RP2-82 RST/B issue (**) - Alternate B point?? changes error to D0 (=*) | GBAtemp.net

[Nintendo Switch] Raika Azahar - The 3DS Emulator aimed at base Nintendo Switch

Raibatsu · 2026-08-07T06:39:15+00:00

------ Thank you so much, Noihs for providing the incredible Fedora-donned rat eating a citrus ------ Many of you may know me through Raikopon - which was a fork of Dekopon, which was aimed at experimental code for the sake of speed & testing purposes. It got a lot of good feedback and the good vibes from many people amongst both this community and Discord made me want to think about 3DS emulation seriously - with better architecture. I present to you - Raika Azahar - a fork of Azahar - aimed for Nintendo 3DS emulation on the Switch with people running on stock speeds. I know a lot of you overclock your console but I personally do the opposite mostly - run at as low power as possible to conserve battery life. I am sure there are many of you like me out there. Therefore, this is a fork aimed at those people that want to maximize how many hours they get before running out of charge. The first build of Raika Azahar has already been live for a couple of days now - on the same page as Raikopon. However, I wanted to make a formal, better post here so we can refocus on Raika Azahar and one day, make this the most stable, easy-to-use, feature-rich 3DS emulator for our beloved handheld console. ============================== What makes Raika Azahar unique: ============================== Async Shader Compilation - First one to implement it in fact! Very proud of it. We are making massive strides toward eliminating shader stutter. Moving from Raikopon v1.0 to Raika Azahar v2.0 has already achieved over a 90% reduction in shader compilation time, while significantly cutting down the overall number of shaders that need to compile. Direct On-Device Cheat Editor - No need to hop onto a PC—you can now write, edit, and manage your cheats directly on the console UI. Direct On-Device Mods Manager - After copying your mods to adequate location, you can easily manage your mods on your Switch. Fully Customizable Dual-Screen Layouts - Complete freedom over your display. Adjust screen sizes, drag them around, tweak opacity, change rotation, or hide/show screens using touch or controller inputs. Built-In App Updater - Stay up to date without ever leaving your Switch. Download and install the latest builds seamlessly in-app. Experimental Features & Performance Hacks - I love pushing the limits and trying new ideas! Raika introduces experimental features like Ubershaders, an enhanced FMV hack for smooth video playback, and granular per-game settings. Cross-Fork Integration & Community Driven - I’m continuously porting and adapting the best features from across the scene (Citra-MMJ, Azahar, Tico, and more) to bring them together into one place. If there's a feature from another fork you'd love to see brought over, drop a comment below! ========= Features: ========= Most 3DS games that are aimed at 30 FPS run at full stock speeds at 1x resolution. There are some exceptions which run at horrible performance and require tweaking. I plan on adding an in-device community-driven compatibility poll too. True async shader compilation that provides a seamless, good experience while playing games. You will experience some huge stutters at the start of your first boot. These are the biggest hurdle left. After you compile these shaders once, the gameplay becomes infinitely smooth. Per-game configuration options so you can make separate configurations for each game. Very feature-rich in-game settings overlay that allows you to change many settings and make custom layouts. Experimental features from other forks such as Fastmem, Async GPU, Skip Slow Draw, Skip Texture Copy, Skip CPU Write. Thanks Dekopon, Citra MMJ for providing these features. They will be rewritten to provide stability in the future. Ability to remap your controls on-the-go. This is one-key only for now. We are going to add multi-key support to these in the future. Install CIAs - apps, updates, DLCs right on the emulator. Ability to clear shaders on-the-go if you are having visual corruptions. No one likes constantly going to the file manager to delete/edit files. Very fast, very lean NXVK | Vulkan backend for Nintendo Switch. This is only the tip of the ice-berg. We are going to have a whole lot of features in the future! The project is currently in the process of a huge rewrite, as was mentioned in my Raikopon post. ============================== Latest Version: 2.5.0 | 18/08/2026 ============================== Downloads: GitHub | Releases Source code: GitHub | Source Code <- This source code reflects Raikopon right now. The current Raika Azahar changes are extremely experimental and will be released as soon as the code has been finalized. ROMs default location is /switch/azahar/roms/. Default location for emulator is /switch/azahar/. I ask that you keep a separate location for Raika Azahar from your other Azahar forks to maintain maximum compatibility. At max, I recommend separating the shaders and config folders. These will cause conflicts and crashes! There have been a lot of requests regarding keeping a separate folder for save files. I plan on adding that in one of the upcoming updates. =========================== Recommended configuration: =========================== - Turn Async Shader Compilation to ON. - Turn Ubershaders to OFF. - Turn Compile Boost to OFF. - Set Async GPU to OFF. - Ensure both hardware Shader and Disk Shader Cache are ON. - Disable Right Eye Render should be ON unless a game demands it. - CPU JIT should be ON. - Fastmem should be ON. - Skip Slow Draw, Texture Copy, CPU Write should be OFF by default unless needed in some games. - Set "New 3DS Mode" to OFF unless a game needs it. Toggling this option causes huge performance drops in some games. Please note that I will not be providing any support if you are using cheats or mods. Have a lovely day to all of you!

DonP

New Member

Newbie

Level 1

Today at 12:03 PM

Im installing the picofly rp2040 on my nintendo switch oled, and encountered some issues. Ill provide images and diode mode readings before I fully explain my issue.

IMAGES :

Diode mode readings:
3v3 = .379
D = .412
A = .428
C = .690
B = .378
Gnd = 0
CPU = .252

You might notice I have my RST line soldered in a weird spot.. I made some sort of mistake earlier in the process and fried out the original B pad? At least I think thats what happened. I'm not sure why that pad behaved different from any of the other ones ive been using- like the other B pad ive been soldering to and desoldering a few times now.

Originally, I was using the normal B pad -

** error, boot to OFW.

Then I reflowed the B joint on the picofly chip, HOORAY - I booted successfully into the No SD card screen. Then all of a sudden after a few more minutes of fiddling and putting the console back together like slightly more than it was just so it wouldnt spill its guts upon being tilted - Same ** error appeared.

I reflowed the joint again- this time it crapped out though and stopped taking solder. Maybe I ripped it at some point with something- again not sure exactly what caused it to break that was just a total skill issue on my end.

I then moved the wire and connected it instead to the B pad near the top of the chip, I ASSUMED it was just an alternate spot, since they are in continuity and share the same readings- and they might be totally fine.

Now with this current setup, I get the readings listed, and now the chip gives me the error =*. Indicating no dat0. Im aware that the dat0 adapters can be spotty, but considering I just booted successfully minutes ago, and I am now soldering the B to a new place that I haven't confirmed fully whether or not its totally chill to place it there- It could totally be the chip freaking out about that and giving a dat0 error in its place??? Theres not much of an easy way for me to know considering I'm not recieving any spotty readings - the .690 on C IS weird right now I think right? - other than getting another chip and just seeing if it works, or doing kamikaze. I mean ideally - both of these. Im mainly posting to see if anything is obviously wrong with the additional B pad that im trying to use because theres probably something obviously wrong with it thatll make me feel a bit dumb then hooray its fixed. I plan to troubleshoot more tomorrow though.

It could easily be that the successful boot I had into the No SD card found was an insane stroke of luck, and the dat0 adapter decided to hate me forever or something. Right now my finger is primarily pointed at the B pad because I was dealing with that error originally before the pad gave out.

Im pretty glad that It does boot into OFW consistently still - Its gotta be a scary time dealing with a bricked switch lol thankfully this is not that- YET haha

Hacking [OLED] Picofly RP2-82 RST/B issue (**) - Alternate B point?? changes error to D0 (=*)

New Member

Similar threads

Popular threads in this forum