rar file, which need to be unzipped (or unrar) using the WinZIP or WinRAR program. This firmware may sometimes be provided in a disc but most likely nowadays to be available for download from the DS card manufacturers site or from the reseller site (like us -> NDS-Gear). No other files are needed, simply drag and drop the homebrew onto the exe file.The first step to get the DS card to work is to get the DS card firmware. If you have an EZ-Flash V please use this DLDI patcher. Note: EZ-Flash V users will need to use a separate DLDI patcher to make DLDI work. nds homebrew files in the ‘binaries’ section.
Homebrew games/apps that do not read or write to your card do not need to be patched.ĭLDI is either automatically patched by the cartridge software or manual patching is necessary. What Homebrew games/apps do I need to patch?Īny homebrew game or application that uses FAT access and supports DLDI. You can download DLDI patches from the official site. Some carts that are compatible with the interface include the following: Most cart developers have advanced beyond manual DLDI patching in various ways, such as automatic DLDI patching. Virtually all cartridges support DLDI either officially or via third-party intervention. The beauty is that once a DLDI patch has been made for your cart it’ll be compatible with every piece of homebrew that has DLDI support.ĭLDI support is defined as, at a minimum, the ability to patch a. So if you have an R4 DS you apply the R4 DS DLDI patch to the homebrew. You would then simply patch the homebrew game or application with your cart’s DLDI patch and it will work on your cart. Instead each flashcart has a specific DLDI patch made for it which houses all the read/write commands. The developers don’t have to worry about making their project compatible with a whole range of different carts. It is a single interface that homebrew developers attach to their projects. This interface developed by Chishm unifies everything. As there are so many flash carts on the market many were left out because to keep your homebrew project working on 15 + different kits would be a nightmare!Īlong came DLDI. Under the old system homebrew projects that used read/write commands (FAT access) only worked on the flashcarts they were specifically coded for. This is a big hassle for developers and flash cart owners a like.
That would mean to get your game working on four different flashcarts you’d need to code it with all four different read/write methods. Every flash cart uses different read/write commands. This forms the read/write commands which are essentially what libfat is. And if you wanted to read the image so you can edit it again you’d need access to the read capabilities of the flash cart. To save this image on the flash cart the developer would have to know the specific piece of code that allows you to write things to the cart. Let’s say a homebrew developer makes a DS game where you can draw a picture and save the image to your flash cart.
I’ll break it down to more understandable terms.
It is an interface for libfat that homebrew developers attached to their projects. 4 How do I patch my homebrew games/apps?ĭLDI stands for ‘Dynamically Linked Device Interface’.3 What Homebrew games/apps do I need to patch?.1 What is DLDI? (how did it come about?).