Jump to content


Premium Members
  • Posts

  • Joined

  • Last visited

Everything posted by sgstair

  1. Yes, it's presently designed to support user malloc/free functions. And, there is the option to go with fully static allocated memory too. -Stephen
  2. Hiya, Right now the ds wifi memory footprint is just under 40k, and sgIP memory usage is also just about 40k (note though, dynamic memory is presently being used on a per-connection basis) So, I don't think it's unreasonable to say that the entire package should use around 96k of ram under normal conditions. This can be tweaked and tuned, and I'll probably drop the amount of memory a while after the first revision has been out for a while. (when I get a chance to play around with some apps and figure out just how much is actually being used.) -Stephen
  3. yeah, it is indeed TCP/IP and no, reverse engineering the MK stack is not impossible by any means it's simply pointless. And, as I'm nearly done with my version, it's also quite unnecessary -Stephen
  4. That's a common mistruth - flashme does not overwrite all of firmware, and things like the mac address are *not* modified. So no, not every flashme'd DS has the same MAC address. -Stephen
  5. -gasp- That's *entirely* not fair. -Stephen
  6. TV? Tea? Books? Please don't distract me... I'm trying to work on the computer -Stephen
  7. Surprisingly enough, I'm using the latest version of devkitarm. I've verified that the.nds doesn't have a built in loader. I'll look into it further. -Stephen
  8. Jaja... just renaming a.nds is not enough to make it work. you do need a loader - I don't know of any that have gui interfaces though. -Stephen
  9. to clarify, the tool is a firmware viewer... lines 30 and 38 are just the lines labeled with "000030" and "000038", and the mac address is 6 bytes starting at 0x000036 -Stephen
  10. Eh, I tend more towards being shy - I don't really like being around people. On the other hand though, I have more than my share of projects to work on, so I don't really have time to mess around with the rest of the world anyway. -Stephen
  11. I will probably make blocking sockets the default and allow an option to switch to non-blocking... There isn't really much need for more details, but more info will be released when it is complete. -Stephen
  12. Normatt: no hard feelings, I was just a bit frustrated over your first post (after I spent all the trouble making the video in the first place) -Stephen
  13. Oy, I do take offense because this video does provide the detail for anyone who wants to to completely pick it apart (which was the intention) - it goes through several stages yes, but you can see exactly what it's doing and to call it just 6 pictures... just means you didn't but glance at it. ... -Stephen
  14. You want a video? You got a video. 1Emulation News post - DS Wifi video -Stephen
  15. No, not at the moment.... That wasn't my choice though. -Stephen
  16. Probabably not initially, however it might be possible, depending on the chipset of the USB stick. Someone will have to write a driver for it though. -Stephen
  17. sgstair


    Er, Maybe... That hasn't been decided yet. Probably not a good idea ...Maybe.. Well, we'll try to avoid this Yes, once we get some games that *store* them to the firmware chip. Reading/understanding them is a piece of cake, but predicting how Nintendo is going to store them is very difficult indeed. So, at least initially the settings will probably not be stored. Once the Nintendo wifi connection is released the code may be modified to use it's data, or something else entirely could be done. At the moment though, whether the settings are saved or not is *entirely* up to the person writing the application. -Stephen
  18. ...plug it into their computer with blazingly fast t3 connection.... piped over a blazing slow 2mbit wifi connection Won't gain much from that upgrade, I'm tellin' ya. -Stephen
  19. Well uh, I won't add this to the faq until I release my documentation..... but, it's complicated. Reeeeeally complicated... the DS Wifi is a custom hardware register set integrated onto the main DS chip with all the other hardware (video, sound, etc) - it contains some dedicated ram and a huge register map (over 100 registers) and is tied in to the interrupt system, and has serial connections to 2 chips in the RF daughterboard. Mainly what is required to use the wifi, is a whole lot of init and some basic understanding of how a few important parts of the hardware work. The ds hardware does a lot of the work for you, but it's unclear just how much it does, that will require very extensive testing to figure out and I haven't managed to get through anywhere near all the possibilities yet. At the core of what I consider to be the "important" parts of wifi is a hardware FIFO/circular buffer in the attached memory chunk, the hardware system of sending data(register and interrupt based), and the hardware interfaces to the two external chips. well, now you're going to ask for more information, but that'd take much longer to explain, so it's best just to wait for my documentation which I promise is comprehensive about the topics I know about, specificly the ones that are important. At the rate I'm presently going, it shouldn't be long, either. -Stephen
  20. sgstair


    I think you misunderstand the problem Basicly all nintendo code uses the same wifi code to talk to the hardware, In this case we'd actually be looking for an entirely different feature in a completely different part of the code. It's not going to be practical to reverse engineer nintendo's TCP/IP stack when we have one of our own -Stephen
  21. sgstair


    It is a nightmare, but it is doable - it's very similar to the kind of work I've been doing to figure out the hardware in the first place (albeit probably easier) -Stephen
  22. Nah, there never was an overall completion.... Plus I don't think of things in terms of being "complete overall" - my projects never get done, I just choose to stop them at a reasonable level I'm documenting the completion on the current feature set I'm working on, which I think is a reasonable approach, because the feature set required will change from time to time. -Stephen
  23. The only real disadvantage to using a router is if you don't know how to set it up, it'll be less secure... It of course won't be as easy as the usb stick, but it's also has other advantages. Whatever, it's your money - pay a little more or learn a little more -Stephen
  24. Yes, of course it'll allow multiple connections. The goal is to provide an environment roughly identical to that on a PC, a PC doesn't have such silly limitations -Stephen
  25. oh, I've got a few around... here's one It's been a while since I've posted an image of any kind anyway though. -Stephen
  • Create New...