gbadev.org forum archive

This is a read-only mirror of the content originally found on forum.gbadev.org (now offline), salvaged from Wayback machine copies. A new forum can be found here.

DS development > Post your test cycle

#173391 - Lazy1 - Sun Apr 04, 2010 3:09 pm

Okay, I know some of you must have an amazingly quick test cycle on hardware...
So, what's your secret?

Here is mine:
1) Eject card from slot-1
2) Eject microsd from card
3) Insert microsd into reader
4) Insert reader into computer
5) Copy application
6) Eject/unmount reader
7) And so on until....
95) Wait for cart menu to load
96) Launch hbmenu
97) Launch copied application

There has to be a better way which supports argv :/

#173402 - 0xtob - Sun Apr 04, 2010 10:07 pm

Same for me, except with my trusty GBAMP. I've tried WMB and DSFTP but always went back to the old card swapping because it's just the fastest. There was an announcement of a transfer method via DSerial, but this didn't happen yet. I want a USB Gecko for DS!
_________________
http://blog.dev-scene.com/0xtob | http://nitrotracker.tobw.net | http://dsmi.tobw.net

#173404 - Pete_Lockwood - Sun Apr 04, 2010 10:52 pm

Those first steps in your list got real old real quick for me, now I just send my app to the DS over a tiny bit of custom socket code. I posted about it a while ago..

http://forum.gbadev.org/viewtopic.php?t=16451&highlight=

So the steps are now:

1. Turn on DS
2. Select the receiver app.
3. Run the sender on the PC.
4. Wait for xfer to complete.
5. Reset DS, load app and test.
_________________
It's not an illusion, it just looks like one.

#173424 - sverx - Tue Apr 06, 2010 9:36 am

what about wi-fi microSD cards? I've read about these cards but actually never seen one... would it be possibile to use them to avoid all the extract-insert-extract-insert task?

#173425 - Pete_Lockwood - Tue Apr 06, 2010 11:23 am

The DS has its own WiFi, why not just use that?
_________________
It's not an illusion, it just looks like one.

#173427 - elwing - Tue Apr 06, 2010 1:06 pm

Pete_Lockwood wrote:

The DS has its own WiFi, why not just use that?

maybe to try to avoid that:
Pete_Lockwood wrote:

1. Turn on DS
2. Select the receiver app.
3. Run the sender on the PC.
4. Wait for xfer to complete.
5. Reset DS

#173428 - TwentySeven - Tue Apr 06, 2010 1:13 pm

I'll pay good money for a version of that app that can also dldi patch+boot the .nds up after downloading it :)

#173429 - Pete_Lockwood - Tue Apr 06, 2010 1:35 pm

Um. What? Does the WiFi SD card know by telepathy that you want to send stuff to it? And similar thought transferrence lets the PC know to send the code? Maybe there's something I'm missing here but I don't see which steps you'd be able to eliminate.

27: the code's there, shouldn't be a big deal to integrate it into a loader. I've already got a job so sorry, I'm too lazy :D
_________________
It's not an illusion, it just looks like one.

#173431 - SteveH - Tue Apr 06, 2010 1:54 pm

Pete_Lockwood wrote:
Um. What? Does the WiFi SD card know by telepathy that you want to send stuff to it? And similar thought transferrence lets the PC know to send the code? Maybe there's something I'm missing here but I don't see which steps you'd be able to eliminate.

27: the code's there, shouldn't be a big deal to integrate it into a loader. I've already got a job so sorry, I'm too lazy :D


Basicaly the MicroSD WiFi card emulates a small HDD that you can access via WiFi, so it reduces the steps to:

1) switch on DS
2) Copy file from PC to DS
3) Boot nds file
4) Exit from the nds file and return to step 2

Only problem is I've not seen any of the microSD cards with a WiFi and storage space available anywhere.

#173432 - TwentySeven - Tue Apr 06, 2010 2:14 pm

Me too, hence I'd rather pay for it =)

Although if theres some good source+documentation for a .nds loader out there I guess I could have a look at it. Hmm.

#173434 - ritz - Tue Apr 06, 2010 4:06 pm

SteveH wrote:
I've not seen any of the microSD cards with a WiFi and storage space available anywhere

Maybe this: [retailer link deleted] ?

EDIT1: hmm, doesn't look like there's storage on it
EDIT2: removed the retailer link, just google "SDW-823"


Last edited by ritz on Wed Apr 07, 2010 3:23 pm; edited 1 time in total

#173439 - wintermute - Tue Apr 06, 2010 9:35 pm

google eyefi, no idea if they'll work as expected though.
_________________
devkitPro - professional toolchains at amateur prices
devkitPro IRC support
Personal Blog

#173440 - 0xtob - Tue Apr 06, 2010 10:12 pm

I don't think wireless SD cards are necessary here since the DS can do all the transferring and storing just fine. We would just need a loader on the DS that waits for the PC to send a DS binary, store it on the SD card and execute it. The new devkitpro homebrew menu will support for DS homebrew to return to the loader (science!) which could also be useful for this wireless loader since it would spare us turning the DS off and on all the time.

The workflow I'm envisioning would be this:

1. type "make wifi" and have your .nds copied to and executed on the DS
2. test your app
3. press L+R+A+B to return to the loader

The only problem I'm having with this is that it's limited to WEP encryption. If I want my home network to be WPA secured, then a USB wireless dongle would be required as a workaround. Oh, incidently: Any ideas?
_________________
http://blog.dev-scene.com/0xtob | http://nitrotracker.tobw.net | http://dsmi.tobw.net

#173442 - vuurrobin - Tue Apr 06, 2010 11:35 pm

yea, wireless sd cards aren't necessary, and it might not be easy to find a microsd version, and then there is the question if it works on the flashcards.

the return to loader might be a bit tricky (or not). it would be easiest if you can execute an nds file without touching the bootstub code. that way, resetting the nds file would bring you back at the menu, where you can just run the receiver again.

an other (harder) option would be that the receiver saves the bootstub code, and then installs its own. that way, when you reset the nds file, you can immediately send another one, and quiting the receiver would return you to the menu.
_________________
my blog:
http://vuurrobin.100webcustomers.com/

#173564 - wallacoloo - Fri Apr 16, 2010 1:43 am

I just avoid as much of the unnecessary inserting/ejecting stuff as possible.

1. eject miniSD card
2. Insert the SD Card reader into my computer if not already plugged in
3. insert miniSD card into reader
4. copy program to miniSD card
5. remove miniSD card from reader
6. insert miniSD card into flash cart
7. boot DS
8. wait for card menu to load
9. select and boot program (directly from cart menu)

Note that I have a SuperKey and a SuperCard MiniSD, but is it actually necessary for you to eject your slot-1 card each time with your setup?

After reading this thread, I plan on making a program that compiles my project and immediately copies the resulting file onto my miniSD card. For me, the copying is the longest step as of now.

#173567 - ritz - Fri Apr 16, 2010 3:14 pm

DS-Xtreme looks like it would've been great for homebrew testing. It seems you could just leave the flashcart in your DS and have it always connected to your computer via USB. Had built in storage (4gb)... no need for a microSD.

http://gbatemp.net/reviews/dsx/DSCF0150.JPG
http://gbatemp.net/reviews/dsx/DSCF0107.JPG

I've never used it myself, but the idea of a flashcart like that would be great, IMO.

I could see the test cycle like this:

1. Type make (this would include the .nds copy to your card, on successful build)
2. Power on the DS
3. Test it
4. Power off DS

I wonder if the DS could stay on the whole time? Then it could be:

1. Exit to menu
2. Type make (includes file copy)
3. Test it

#173568 - Sektor - Fri Apr 16, 2010 3:53 pm

DS-X doesn't boot if it is being powered by USB. It would have been great if it did. I still use one, it's faster/easier to connect the USB cable than fiddle with a microSD.
_________________
GTAMP.com/DS

#173569 - ritz - Fri Apr 16, 2010 5:29 pm

What if you boot the card first and then plug it into the computer? Then a person could just leave the DS on. Test the rom, soft reset back to the menu, write updated rom to card, and then use the card's menu to go up a dir and back in (to re-read the dir containing new rom). Or maybe the firmware needs to "unload" the device and re-init first. Too bad we couldn't get the Homebrew Menu on that card and then we could code the necessary functions to do the re-init if required. I dunno, just babbling.

#173574 - Miked0801 - Fri Apr 16, 2010 6:49 pm

My test cycle? Code it and immediately check it in without testing because I NEVER make mistakes - Ever :)

(new someone one time who actually believed this. Didn't last too long in their job...)

#173697 - protomank - Fri Apr 23, 2010 9:52 pm

The best solution I've seen so far for development is the one used by ps2dev.org:
- run a server app in the console that listens to a given port
- run an app (ps2client) in your computer that connects to the console and transfter all data (app binary and program files) to the console RAM throught network
- the server app then executes the transfered binary that is in RAM

You get printfs in your computer and can even run gdb.
If DS had a system like this one, development would be sooooooooo much easier I can't even tell you guys.
_________________
Iuri Fiedoruk
http://rockbot.upperland.net

#173707 - Lazy1 - Sun Apr 25, 2010 2:18 am

Thanks to GrizzlyAdam/chishm's supercard cf hack I can auto boot into hbmenu for fast launching, argv and return to loader support. :D
The test cycle is greatly reduced as well since the compactflash card sticks out the front for easy removal.

#173722 - elwing - Mon Apr 26, 2010 7:29 am

Miked0801 wrote:
My test cycle? Code it and immediately check it in without testing because I NEVER make mistakes - Ever :)

(new someone one time who actually believed this. Didn't last too long in their job...)


why dd'you want to test? if it compiles then it's ok :D

#173725 - fincs - Mon Apr 26, 2010 2:43 pm

elwing wrote:
Miked0801 wrote:
My test cycle? Code it and immediately check it in without testing because I NEVER make mistakes - Ever :)

(new someone one time who actually believed this. Didn't last too long in their job...)


why dd'you want to test? if it compiles then it's ok :D


o rly?