Yeah, since we're low unit volume I figured it's better to just stick "everything else" on one board rather than several smaller application-specific version for now. If more people dive in it might make sense to do a "music" centric version with analog sliders on the PORTA pins, programmable filters, whatever... In the meantime the 'experimeter' board can be the do-all.uze6666 wrote: Wow, that's gonna be a heck of a board...everything and the kitchen sink!
Oh, sorry, you're right. I was "off by one" looking at my schematic... That is how it's implemented, just not how I documented it up above. So yes:Correct me if I'm wrong, but PORTD.6 is actually used for the microSD chip select no? Why move it to PORTD.7, which is btw the sound PWM pin.
PORTD.7 = PWM
PORTD.6 = chip select to uSD
PORTD.5 = (maybe second SD chip select? free "user" chip select?)
PORTD.4 = chip select to 'helper' MCU (ATTiny2313)-- provides PS/2 keyboard and Mouse ports
PORTD.3 = chip select to ENC28J60 (plus /INT connecting to PORTD.2)
Yeah. Since this could be used for 'non-gaming' apps I thought it might be useful to have an "application" card (maybe with files or whatever the app needs) and then a second card that could be removed (like for datalogging or whatever) without causing problems in the app... I think in 99% of the cases though the app would always be flash resident so a single SD or uSD would probably be plenty. I'm not married to the idea one way or the other. (If someone really wanted two SD's they could always cut a trace and run a different line to the standard SD slot... I could see doing that for an SD card 'sector copier' or other type of mastering equipment where you want a 'master' on one card and then make multiple copies to the second slot.)I'd like to ear what others have to say, but I don't see lots of application using 2 SD cards on a 64K device
I was only thinking one sound channel-- just routed to two RCA's for output. (Just so you could plug in a standard stereo RCA pair on a TV or stereo and not have to select 'mono' mode to get sound from both speakers. AKA, 'dual mono' audio. AKA, "I've got a lot of the RCA connectors so I don't mind using them".)For the dual audio channel what pin(s) did you think of?
Yep, I'm with you. Don't want to break compatibility for the gaming side of things. If somebody wants to use the experimenter board to lash up a bunch of extra circuitry and make a video based Digital Read Out for a milling machine that's fine-- an not expected to run on a 'gamer' board.I think my concern is that some great ('uzebox standard') stuff works on one board, but not in the other. Sure, if folks stick to the kernel/api we can have some slack to move things around a bit with the help of the new EEPROM config stuff. In the other hand, that makes the kernel more complex (and more heavy too).