Escribir en la tarjeta (micro/mini)SD

Dr Katts escribió:Al parecer en esta pagina hay un apartado para desarrolladores pero no se si es la informacion que estas buscando..Espero te sirva..
http://chishm.drunkencoders.com/DLDI/index.html

Ikari Shinji escribió:[...]algo para poder incluir soporte para DLDI en mi minijuego.[...]

AleXillo escribió:Veees. No es tan dificil ser agradable !!!

Rigle escribió:Lo compilas y lo parcheas el dldi con algún programa para hacerlo

Some of the interfaces listed above have not been tested, or may appear to not work for you. If you wish to test an interface, download the DLDI Tester. Extract the contents to the root directory of the card you'll be testing, then patch it for the correct card, following the instructions above. Make sure you backup everything on the card, I accept no responsibilty if anything goes wrong. Follow the onscreen prompts and observe the outcome. Feel free to email me with results for a card that hasn't been tested already, or results contrary to those in the above table.
Developer Instructions

The DLDI IO_INTERFACE is included as part of libfat. It will be included when you use libfat within your project.

If you are still using gba_nds_fat, you can use a backported IO_INTERFACE. Copy it to your gba_nds_fat source directory and add io_dldi as the first driver in the initialization list.

You may wish to add a patching step to your makefile, following the end user instructions.
Device development instructions

1. A DLDI template is installed as part of DevkitARM r20. Get it using the DevkitPro Updater.
2. Install the NDS examples as part of DevkitARM.
3. Copy the dldi directory from <path_to_devkitPro>/examples/nds/templates/.
4. Rename the dldi folder to the four character code for the driver.
5. Replace the functions inside source/iointerface.c with ones specific to the device.
6. Open source/dldi_header.s for editting:
1. Change the text "Name of driver goes here" to an appropriate description for the device.
2. Change the text "XXXX" to the four character code for the driver.
3. In the IO_INTERFACE data section, make sure that either FEATURE_SLOT_GBA or FEATURE_SLOT_NDS is specified, depending on which slot the device goes into.
7. Compile by running make in the top level directory of the driver.
8. If you get an error containing the text "overlaps previous sections", the driver is too big to fit in the available space. Since only 32KiB are allocated for DLDI patches, you will need to reduce the size of the driver. Try reducing the size of global arrays or let some card initialisation be done by the device firmware.
9. Test it out by following the testing instructions.
10. If it works, distribute it. Feel free to send me an email (address is on the front page) with the interface to add to this page. Please include test results.