Gavin Smith wrote: > If this was ported, would we be able to run native SAM apps > on top of it? Could we drop down into BASIC?
Perhaps only as much as you could with Driver, by suspending the GUI to return to BASIC. That would halt all Contiki activity while you're running the external program/BASIC tho, including the networking. It'd also rely on applications observing any RAM pages flagged as used, to avoid Contiki being overwritten. You might manage to keep the comms running if interrupts remain enabled, but the close coupling of the application and network layers makes it difficult without periodically scheduling some time for the Contiki kernel to run. Even if that's possible, it might make BASIC basic horribly slow to use. Has anyone tried an interrupt driven comms routine that runs in the background under BASIC? (Cookie?) > If we couldn't do these things, it wouldn't really be like > using our SAMs - very interesting but not SAM-like. I know what you mean, but if you think of it as an application instead of part of the system, it'd still be mightily impressive for the SAM. I was chuffed enough to get my SAM pingable from the Internet (routed through my Linux box over SLIP), despite it being an exclusive app which did nothing but respond to ICMP ECHO requests. Completely useless, but seemed like an interesting goal to aim for at the time! > I still dream of seeing my SAM on the net with a little text > web browser, basic email client, telnet, IRC etc - whilst still > being able to access BASIC Contiki covers most of the functionality you want, but returning to BASIC is a problem. You could probably manage short exclusive trips to BASIC, relying on TCP retries to keep any active connections alive, but that's a bit risky. The alternative is to have other small applets running under Contiki to do what you want (DIR disks, etc.). All fascinating stuff anyway... Si
