SynthModules

Hi Mark
 Ipromisedmyselfi'dstayoutofthisIpromisedmyselfi'dstayoutofthisIpromisedmyselfi'dstayoutofthisIpromisedmyselfi'dstayoutofthisIpromisedmyselfi'dstayoutofthis

--- In SynthModules@yahoogroups.com, Mark Pulver <mark@m...> wrote:
> bunch of questions...
> 
> - I trust that there's ISR handling of some sort in the language 
> implementation?
>
yes, take a look at syncable.bas in the code fragments folder of the files section. it's not beautiful or very intuitive but it does appear to work
 
> - Is the PIC mapped such that you can control it? Either port or memory?
> 
don't know yet

> - Can the UART be setup to be memory mapped so that it dumps a byte 
> straight to memory, or is it port mapped?
>
don't know yet
 
> - Have you done any timings on reading from a port, moving a byte/word of 
> memory?
> 
the jury is still out...
so far...i get inconsistent results using TIMERW - One barrier appears to be that 31.25Kbaud has to be implemented as a custom baud rate it's not one of the 'standard' selections

> - Does this BASIC allow for PEEK and POKE? 
yes, 
but again i'm getting some erratic results, ie: not always PEEKing back what i POKEd to a static location
but i'm just getting my feet wet in this though so it's a bit early for me to make a call about how reliably PEEK & POKE work

>Can you get the address of a 
> variable? 
don't know - haven't tried
 
>The thought behind this is that PEEK/POKE would be faster than:
> 
>    CommBuffer[CommIndex] = $UARTIn
>    CommIndex = CommIndex + 1;
> 
definitely!
that's my instinct too. the big boogeyman with this micro-environment is the dire threat of the buffer spilling over with pitch-bend data or the like..

Ipromisedmyselfi'dstayoutofthisIpromisedmyselfi'dstayoutofthisIpromisedmyselfi'dstayoutofthisIpromisedmyselfi'dstayoutofthisIpromisedmyselfi'dstayoutofthis
-doc