 | | 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)
|
| |
| | Re: Long range IR mode.
|
|
(...) Just scanned through Kekoka's excellent dissection of the ROM routines. Seems like system variable/register at address $ff7b contains the relevant Long range/Short range bit flag, ie. bit 0 toggles the IR range 0 = Long, 1 = Short. Could I (...) (25 years ago, 9-Nov-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | RE: Save image word for pbForth.
|
|
(...) OhOh. Now you have got me thinking again. I can fix my make system to provide images that have optional wordsets, double precision, floats, etc. This is a good thing. (...) Check (URL) and look in the PDA section. LOTS of free stuff there. (...) (25 years ago, 8-Nov-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: Save image word for pbForth.
|
|
(...) I like the solution proposed by many Forht packages (by hForth in particular): there is a basic kernel and a few different variations with optional wordsets. For myself, I would like to see at least one additional variation to pbForth - image (...) (25 years ago, 8-Nov-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | RE: Save image word for pbForth.
|
|
(...) This is an important part of what I want pbForth to be. It should be possible lo load up "precompiled" images to let users put exactly what they want in their system. (...) Since SAVE-SYSTEM is something you do at the END of the development (...) (25 years ago, 8-Nov-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: Save image word for pbForth.
|
|
Hi Ralph, Thanks for words of cheers ;) (...) Exactly. My first attempt was to dump out the whole image and make terminal to receive it as a textual file. Uh uh... (...) Well, of course I would like to make it available for community. If you think (...) (25 years ago, 7-Nov-99, to lugnet.robotics.rcx.pbforth)
|
