More notes: 4. Forget about using debug with interupt routines. They only work in real time. 5. Version 7.2 implements HSERIN and HSEROUT which are code blocks that use the hardware UART. In theory, they should take care of interupt processing for us. But direct register use may still needed for byte by byte message parsing, the HSERIN routine may add enough overhead so it can't handle MIDI data rates. 6. To use HSERIN you also have to enable it and use the SERSETUP command to initialize the UART. --- In SynthModules@yahoogroups.com, "grantrichter2001" <grichter@a...> wrote: > Dave, > > See syncable.bas in the file section under Code > Fragments/Mbasic for how to talk to registers and enable and > disable interupts. At least as far as we have figured out yet. That > particular segment uses timer W, but the serial port should be > similar. > > Important notes: > > 1. All Peeks and Pokes are offset by $F780. The memory map is > inverted from the Motorola model with flash at the bottom and > RAM at the top. Poke 0 actually pokes to $F780, the start of RAM. > None of this is documented except in the forums. > > 2. All the registers are protected keywords and are used directly. > That is LET SSR = %00000000 or LET TEMP = TDR works. > According to Nathan, DO NOT use pokes or peeks and do not > define the registers or register addresses (it's automagic). > > 3. The interupt commands are compiler directives, not keywords. > For example, disable the interupt right before the interupt handler > name label, not inside the interupt handler routine itself. > > Via Con Dios, > > Grant
Message
Re: MIDI interupts
2004-04-10 by grantrichter2001
Attachments
- No local attachments were found for this message.