 | | RE: Loading firmware
|
|
If you;ve got the most recent versions of pbForth, and you have Active Tcl installed, then click on the rcxtk.tcl file and the pbForth console should be launched immediately. At that point, you can upload the pbForth.srec file using the (...) (22 years ago, 3-Sep-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | Loading firmware
|
|
I am a newbie to RIS 1.0 and would like to install pbforth as my firmware and then use it as my command(programming) language. How do I get started. I have downloaded the Active State Tcl ,rcxtel, and nqc to my computer. Where do I go from here ? (...) (22 years ago, 2-Sep-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | RE: What does =0 do ?
|
|
Richard, A little known fact is that if you "punctuate" a number with any of the following characters ,./-: you will get a double on the stack in the old FIG Forth. so 123-4567 will put the double value 1234567 on the stack. So why doesn't 0= get (...) (22 years ago, 23-Jul-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | What does =0 do ?
|
|
Hi, While entering a program last night, I typed =0 instead of 0=, and the interpreter accepted it; it took me quite a while to work out why my program wasn't working properly. =0 does not seem to be a word (ie ' =0 results in the "not found" error) (...) (22 years ago, 23-Jul-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: Aborting from ISR
|
|
(...) Hi, the nice thing in this solution is that it doesn't inspect or touch the user return stack at all. The structures that are used to get to the FIP (instruction pointer) - namely: the position of the saved D-stack in the *private* R-stack and (...) (22 years ago, 20-Jul-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: Aborting from ISR
|
|
Hi, (...) Yup, that does what I want, although I can't remember enough about forth internals to work out why it works. But it does seem to depend on the return stack having a particular structure, so I do wonder - what happens if the interrupt (...) (22 years ago, 20-Jul-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | RE: Aborting from ISR
|
|
(...) Alex, I'll have a good look at this and then post an article. I have a funny feeling you're doing it the hard way, but that's because I know the insides of the patient better than you do - I am Dr Frankenforth after all! Oh, and sorry for the (...) (22 years ago, 17-Jul-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | RE: Lazy newbieish question
|
|
(...) Matt, I see this all the time when I teach embedded C programming to desktop guys - it's an objectification of things at the wrong level. Maybe you could consider this: (setup-light-sensor 'PORT2) which expands to 3 1 SENSOR_TYPE 128 1 (...) (22 years ago, 17-Jul-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | Lazy newbieish question
|
|
If I wasn't in a hurry with so many things to do in the next two days, I would figure this out for myself. My apologies for such a simple question. We're wrapping a lot sensor input stuff at a higher level of abstraction than the raw pbForth words. (...) (22 years ago, 17-Jul-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: Aborting from ISR
|
|
It works! (after countless crashes and firmwire reloads that is ... :) By modifying the saved Instruction Pointer to point to a memory area which in turn contains the address of an "abort word", on the next execution of a word (either inside a (...) (22 years ago, 16-Jul-02, to lugnet.robotics.rcx.pbforth)
|
