oh ok thank youYou can only use flashcards that are compatible with the 3DS. I don't think the TTDS is even compatible with the DSi.
oh ok thank youYou can only use flashcards that are compatible with the 3DS. I don't think the TTDS is even compatible with the DSi.
You'd need to assert TWL_FIRM's setup is sufficient for retail bootchain (TWL_FIRM uses a boot2 rigged to load an SRL, signed + encrypted with dev rsakey), then you may have some luck with retail boot2 + retail launcher. I believe TWL launch copies out keys where they're expected though, for either launcher.Oh nice. I could have used this a few months ago when I was installing DSi system apps to my n3DS TWL nand. I had DSi System Settings do a system update. Which I eventually succeeded in doing so. I just had to manually swap out pending files to their correct locations so it can move on to the next one. I almost got system menu to boot, but it appears I'd have to get retail launcher to load from twlBg, but haven't found away of doing that since i don't know how to change where it's loaded in the .code since retail launcher is larger then dev launcher. (it would either have to be moved to the end or redirected to NAND/SD somehow)
I wonder if a dev.kp could be created for a 3DS...I always have to use one from a DSi which may still prove to be a road block to system menu booting in the end...
I just checked and it seems HWID.sgn isn't used by the launcher - it's probably just for online features to varying degrees.It may be easier to patch out checks in retail launcher and create a custom HWID.sgn I suppose. I thought launcher was boot2. I wasn't aware there was one for 3DS. How would I go about obtaining DSi boot2 and putting it in twlBg?
Thing is, I don't think Arm11 has TWLN/NAND access (which is where twlBg is loaded I think), so I'm not sure how a DSi Boot2 will help since I think it would attempt to access Launcher from TWLN and fail to do so.
I take it we can't manipulate the memory range and status registers? (Or can we?) If we can, it might be possible, with some tricks, to get it working properly (ofc it's not easy)The DSi hardware sits in a weird place with GBA support. The cart memory range and similar status registers and such basically act as if no cart is inserted, and it seems that there's not even hardware support for reintroducing the GBA slot.
This is sorta weird because DS obviously supports GBA, and 3DS also natively supports GBA by mapping memory in place of the cart slot (as well as doing hardware-based save memory emulation). DSi is the only post-GBA console to not support it in hardware.
Well, memory accesses return 0xFF instead of open bus values. That implies they're probably pulled high inside the SoC and thus inoperable. It's actually more likely that you'd be able to get the second DS cart slot working than the GBA slot, as the pins for it seem to still exist on the retail SoC, albeit not connected and not utilized by existing software.I take it we can't manipulate the memory range and status registers? (Or can we?) If we can, it might be possible, with some tricks, to get it working properly (ofc it's not easy)
AH, damn... thanksWell, memory accesses return 0xFF instead of open bus values. That implies they're probably pulled high inside the SoC and thus inoperable. It's actually more likely that you'd be able to get the second DS cart slot working than the GBA slot, as the pins for it seem to still exist on the retail SoC, albeit not connected and not utilized by existing software.
A bit of a novice question, but I'm a bit confused:
A while ago, I splurged and bought a brand new Nintendo DSi Matte Blue I found at a GameStop for 60 dollars. I've used it every now and again, but haven't checked out the DSiWare shop or connected to the internet with it at all.
I recently checked and the system came with Version 1.4.4U. Can I use TWLTool with this?
From what I gather in the first post, I either have the option of hardmodding the DSi in order to get it's NAND and downgrade it, or I can just inject the DSiWare Hax save with this tool (which seems like the better option). Is this correct, or do I still have to downgrade? Would upgrading to 1.4.5U be worth it?
You absolutely do have to have your console properly ticketed to inject hacked saves and downgraded apps. What that means is that you need to update the console to the latest firmware and buy the hackable game from the DSi Shop, while it's still available.Does anybody know anything about this?