mw0uzo wrote:Access to the Pi (and the wifi, web, storage etc) would be a *TERMINAL away. So I can develop for Pi side and BBC side at the same keyboard/monitor.
Just to be clear - you won't, I think, get anywhere trying to talk to the pi over serial when it's acting as a copro. You'd need to boot it into a full OS, and of course set the serial speed down to something the Beeb can handle. Then, to use the Pi as a copro, you'd need to swap cards and boot into PiTubeDirect. (Because PiTubeDirect is running on bare metal, it has no OS and has no drivers for any of the peripherals except serial-out. With some serious sleeves-rolled-up programming, you could change that...)
Yes, the plan is to run with lite OS install, so wifi drivers, SD card etc are available - not in the CoPro configuration.
My plan is to write a utility that presents functionality available over a list of serial commands, this includes storage, web requests, graphics and sound operations. And also presents a full-screen window for graphics on the Pi. Then bash together a ROM that interfaces to the user via * commands, additional system calls etc.
The idea being I can get something working, then swap out the serial layer with something more appropriate. I know it sounds silly, an accelerated adaptor over serial, its just a first step and familiarity exercise really. It might, maybe, have potential to tie into the CoPro project somehow, even if just the initial setup is being able to issue a command to swap over the kernels and reboot into CoPro mode. Or use a slower, bodged comms mode over the Tube. Not sure about that yet.