devkitPro

I'm doing some remote compatibility testing and one of my testers are reporting that nitro is not initializing correctly. This is not the standard argv issue, but it seems to exit in the first line in the nitroFSInit function. if (__NDSHeader->fatSize == 0 ) return false; Before this, fatInitDefault...

Just to follow up on this. Not using callbacks was my real problem. With the "ASM9 being busy" I meant that some operations that I'm doing can take up to a second, and if the user is spamming the touch-screen during that time, which added commands to the FIFO, ARM7 crashed due to the queue...

would the latency really be that bad from a shared circular buffer? maybe even have the arm7 update the buffer at a lower frequency then it collects data? No, I don't see why a shared buffer could reduce latency. I was assuming that FIFO worked with a shared buffer under the hood. I've never bother...

I'm not completely sure how that works, but it does. The main problem is solved. Thanks!

I'm still interested in how to send large amounts of data without needing to send ACKs back to avoid the FIFO to overflow crash.

Short version: Is there a way where I can still access 4 bytes of shared memory between ARM7 and ARM9 with the FIFOfied libnds? Long version: I'm using a heavily modified ARM7 core for my new version of Colors!. Basically, what it does is that it with maximum speed reads input (>500Hz) from the touc...

As far as I could see, there was no special-cases in the code you posted above. That was all basic input code and is well handled by the default ARM7 core. You just have to change your ARM9 side to work with it, and that's should be well documented in the nice input examples. Regarding the sound stu...

As usual. After spending 2 days trying to debug this, I finally asked for some help here. Then 1 hour later I got it solved myself. It turns out that I had libcurl configurated in a way so that closesocket() wasn't called. Wasn't sure why this caused all the weird behavior, but things worked much be...

I'm in the midst of a very long debug session trying to figure out why my Wi-Fi implementation isn't working. I'm using libcurl to commnicate with a web-server and suddenly "connect" just stops working. Even worse, if I try to log stuff to disk, it surprisingly stops logging before I'm get...

Hmm. I'm not sure what I'm looking for as this is more low-level than I usually poke around, but I didn't find anything in the SVN either. Is the devkitARM code in a different place? Or is the memory manager a part of a gcc package or something? Either way, a find in files for the implementation of ...

I'm trying to find the source to the memory manager used on the DS to help me with some debugging. I'm not sure where to look though, and all I've found is the devkitPro tar-ball. Can anyone point me in the right direction? (What I'm really trying to fix is this: http://forum.gbadev.org/viewtopic.ph...