SynthModules

drmabuce (11:37 AM 4/8/2004) wrote:

 >Hi Mark
 > Ipromisedmyselfi'dstayoutofthisIpromisedmyselfi'dstayoutofthisIpromisedmyse
 >lfi'dstayoutofthisIpromisedmyselfi'dstayoutofthisIpromisedmyselfi'dstayoutof
 >this

tee-hee. :)


 >--- 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

'k

{insert looking time...}
{gauging level of appropriate reaction...}
{issuing reaction...}

"eek".


 >> - 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

Yeah... I was wondering how this was gonna work. The Magic Baud Rate has 
always been an issue in working with UARTs.


 >> - 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

'k. What you may be seeing is that you've picked an address which is 
actually a memory mapped port, so the data at the "address" would change.

How did you pick the memory address to poke at?


 >>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..

Right... Which kinda' circles back to how fast you can move memory; how 
deep the INT buffer is on the H8; what the inherent overhead of an ISR is 
(in relation to moving data fast enough to keep up with pitch tracking); etc.


 >Ipromisedmyselfi'dstayoutofthisIpromisedmyselfi'dstayoutofthisIpromised
 >myselfi'dstayoutofthisIpromisedmyselfi'dstayoutofthisIpromisedmyselfi'd
 >stayoutofthis

heh... All of my free time would be gone if I had my PSIM...

...in fact, I'd be tempted to bring it to work and create "free time" here 
to play with it. :)