 | | RE: Save image in pbForth (srec version)
|
|
(...) <snipped pbForth code> COOL! I guess you could load this in just before you actually need to do the dumping of the memory. This is a great contribution, Sergey. Do you mind if I put it in script format and package it with the standard (...) (25 years ago, 11-Nov-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | Save image in pbForth (srec version)
|
|
Hi Ralph, Finally I got it to work. Now there is XMODEM protocol and S-record writer on top of it. SAVE-SYSTEM word has been redefined to produce S-record image. Although upload time is up to 5 min now, instead I don't spend time anymore to mess (...) (25 years ago, 11-Nov-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | RE: Long range IR mode.
|
|
(...) The >R and R> words are used as little helpers. The put (or get) the top element of the data stack to the return stack. As long as you dont fiddle with the return stack between uses, they are a great way to do this. The alternative way to code (...) (25 years ago, 11-Nov-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: Long range IR mode.
|
|
(...) Great, much more generalized code. What are the >R and R> words BTW? Did FFB7 C@ . and found the contents to already FE, as in, it appears that the default IR mode is indeed Long to start with. Seems like the effective range is much shorter (...) (25 years ago, 11-Nov-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | RE: Long range IR mode.
|
|
<Range mode intro snipped> (...) I'd redefine it something like this....use upper case BASE @ HEX \ To keep from evaluating HEX every time... : RANGE_SET ( f -- ) \ non-zero is long, 0 is short >R FFB7 DUP C@ R> IF FFFE AND ELSE 0001 OR THEN SWAP C! (...) (25 years ago, 9-Nov-99, to lugnet.robotics.rcx.pbforth)
|
