Where to start...
This is continued from the links section. ----------- I did just read that the GBA has a ARM processor. Is there much of a difference (in programming) between the two different ARM processers? If we start at GBA, we won't need to use passme. We just need a flashcart (or GBAMP/Supercard). If we start at DS, we would need flashcart and passme. Then I agree with you (Dex), we'll start at GBA. --------- I think gbadev.org will help out a lot. http://www.gbadev.org/tools.php http://www.gbadev.org/docs.php http://www.gbadev.org/docs.php?section=arm http://www.gbadev.org/docs.php?section=tutorials I won't start now. I just updated my supercard with the newest frimware. Playing around with it for a while. Jas2o

It will be about a mouth, before i can give any time to GBA programming as i need to finish ramdisk, editor, fasm port on Dex4u first :cry: .

Hmm... Most things are C tuts :( Let me know when you get a card (flashcart/gbamp*/supercard*) and your ready to start GBA programming. Jas2o

I am thinking about getting this what do you think ?. http://www.divineo.co.uk/cgi-bin/div-uk/m3-adapter-cf As for most things being in C, thats always the case, but once we get going, hopefully that will change :) .

I did a lot of research. I didn't have a lot of money, so i didn't look at the M3. I was originly looking at GBAMPs, but found out they didn't have ram, so the size of apps was limitted. I wanted something compact, M3, GBAMP and SC CF stick out. So I got a SC SD. I think the M3 has a longer battery life than the SC. I think that M3, GBAMP and SC are much better than a flashcart as they are easier to write to. I think the M3 is a good choise. It seems to come with a passme type device too. Jas2o

You've got an ARM processor (or 2) in the DS, and I think the GBA is also ARM based, so learn to asm for the ARM architecture, should be good.

I know we will start on GBA but I just want to post some ASM for DS realted things (may not be useful). Asm files seem to have the extension *.s (for devkitpro?) Here is a topic on gbadev in the ds section (about coding in asm) http://forum.gbadev.org/viewtopic.php?p=68306 That is all I have found for now. It's not much but could help. Jas2o

Most of the work for ASM DS programming will need to be done by trial and error, starting with the basics and working from there. Maybe by making a GBA/DS emulator for Dex4u, it may help us understand the inner workings.

Oh yes, I forgot to add emulators to the links, I'll add them now (BTW I added the tech wifi in the homebrew section). I should take me a few minutes. Jas2o

I have ordered this: http://www.divineo.co.uk/cgi-bin/div-uk/m3-adapter-cf I will let you know when it comes.

The .s is a generic extension used by GCC. I havn't seen it elseware, as most plain assemblers use .asm . IIRC: ".s" is preprocessed, ".S" is not. This is looking a tad more interesting than I orginally antisipated... So who's going to write "DEX4DS"? lamo, now THERE'S something interesting :D. Cheers, DH.

I have always thought that it would be good to have a PC + extera device combo, to get round the Sound and graphic card problem with PC ( eg: need to have so many graphic card drivers ). You could use the PC to do most of the work and extera device to do sound and graphics, the device would need to be common, cheapish , and standard, so the the GBA os DS fits the bill. A example of use would be a robot controller, most of the obstacle avoidance etc would be done by the laptop with the info being displayed in text mode, but info from mic and camera would be feed to the DS.

@DEX: Your pretty much talking about that weird controller hook-up for the GBA and GameQube. It was (IMHO) a flop. For the general-gamer, nope. If your working on a robot and want a nice, standardized interface; ya. But i think your really making more work for yourself by going through the DS/SP/GBA because you need a driver for that too. Not to mention that not everybody has one *raises hand*. If you want a maxium audience, generics are the way to go. SoundBlaster 16 is almost universal (or is it 32?), and VESA is widly used (though I'd prefer VGA for it's better speed and control). Mice are pretty much limited to Serial and PS/2 (though I've heard of various cavets surrounding PS/2 ones). To be honest... a DS/SP/GBA isn't worth much in the interface department. I take that back, the DSs touchscreen would be interesting to play with on a regular computer, and would make DS Emulators _practical_. Cheers, DH. Freedom of controllers forever :lol:

@Dragon_Hilord, Its true that not everyone has a GBA/DS and a driver is needed, but theres the point, if i make a driver and its works on my GBA, it should also work on any body else's GBA, also if you ask people on the net what graphic card they have and if they own a GBA/DS you will find more have a GBA/DS than the same graphic card, as for sound blaster 16 some cards are SB16 compatable, but are set to not emulate as standard, so you need to switch the bit on, but it differant on every card. Vesa's good, but will always be slow, handhelds will just get faster. My idea is to send graphic and sound by wi-fi, to the device.

maybe you want to look at some of the DSwifi programs? Win2DS PointyRemote They are VCN type programs for the DS. Jas2o