Do not use the RS Media Macro editing software. At least, don't try to export a macro from it. This shouldn't be a big deal, people shouldn't really be using this software to complete their assignments anyway...
The deal is that my office is on the South Side, so it's hard for me to have regular office hours on-campus. So, I can meet with you over here at my office (McGowan institute laboratory building, 3025 E Carson St.) really any time, and on campus before or after class, just let me know in advance. The BIRC shuttle goes back and forth to the S. Side from behind Posner weekdays - details. You can also see the prosthetics lab (from my talk) if you come over here.
Also also, I'm worried that we don't have direct enough access to the JVM if we want to add hardware. The only easy way I see "in" is through communication at the terminals on the board. Do you want me to pursue this? (as in, can I take the thing apart and mess with it) I don't have a lot of time to work with it, but I have a feeling that's going to be the only way to add something that can communicate with the external world.
Let's get the students to work on this.
Other options: USB - they wrote an (unreleased) custom driver with the mass storage profile, so it's going to be hard to get this to work for serial/useful/live communication. Not that it's not possible, but you'd sort of need another way in to get access to it. I don't really want to try to cross-compile something over and over and keep loading it and trying it over the SD card.
Let's get the students to work on this.
SD - use the SD slot for an SDIO bluetooth card - you'd need to insert a kernel module or recompile it, which again needs another "way in"
Let's get the students to work on this.
Right now it appears that you can execute arbitrary code from the SD card but that doesn't help tremendously until we can get another device driver loaded for any of the other hardware... otherwise it's trial and error with a 3 minute testing cycle...
Let's get the students to work on this.