I've never noticed the order of ORG statements to matter. The assembler builds all the pieces as specified in the source.andy123 wrote:The error listings returned "ASM ERROR progra01 overwriting previous address contents" for large sections of code.
Question; Is the code embedded in the code window in the proper sequence with the ORG statements in the right order?
Unfortunately I have no useful thoughts. As you can see, the macro is merely a single CALL followed by the inline text data which gets stored in flash memory. The called routine reads the character string from flash and hammers it out the serial port, then cleans up the stack before returning. I would think the equivalent BASIC statement would be something like [PRINT #port "constant string"] where <port> refers to the desired serial port.andy123 wrote:Hi
The simple stepper BOBstep program is giving me the run a round when attempting to assemble through the PBP3 compiler with the #asm #endasm set to cover all the assemble code. The macro _SERPrint will not reference, throws out errors. Any thoughts?
The ISR is the part that does all the heavy lifting for generating the stepper pulse trains. It is a 2-axis engine, so it should serve your needs, at least to start. If you can get the ISR running happily behind your PICBASIC code, you should be laughing. The "Start_Move" function shows how to feed the ISR to get it to perform a move. The tough part might be the serial receive routine. The ISR polls the serial receiver and maintains the receive queue and the hardware handshaking. This is unlikely to mesh nicely with PICBASIC so you would likely have to write your own code to pull characters from the receive queue. Follow the code starting from "move_loop" to see how my code does that.andy123 wrote: If all else fails I can use the PICBASIC serial I/O routines to get the characters out to screen. Thank you for your guidance. How is the latest iteration of the G code interpreter going?
Users browsing this forum: No registered users and 1 guest