 | | 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)
|
| |
| | Re: Breaking from infinite loops
|
|
(...) Hi, if you just want to stop your "own" program use the Forth word ABORT or ABORT" : TEST 1000 0 DO \ do something run-button-down? ABORT" Aborted by user!" LOOP ; or if you want what looks like a "reset" use COLD: run-button-down? IF (...) (22 years ago, 16-Jul-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: Aborting from ISR
|
|
Ah I see... intriguing idea :) Rereading your original post it should have been quite clear what you wanted. Unfortunately (as far as I know) Mario is right, there doesn't seem to be a clean solution other than manipulating the return stack. I've (...) (22 years ago, 16-Jul-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | Breaking from infinite loops
|
|
This feels vaguely similar to a question just recently posed, almost. I need a way to get out of a user program that intentionally defines an infinite loop. My best attempt so far at an exit word : exit POWER_OFF LCD_4TH LCD_REFRESH ; in the context (...) (22 years ago, 16-Jul-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: Aborting from ISR
|
|
(...) I see. Tired of re-booting hey? :o)) There's no way already available that I know of. I think that Mr. Hempel is looking into this. Maybe if we play with the return stack... (...) The way Forth works is that it is running the program. If you (...) (22 years ago, 15-Jul-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: Light sensor question
|
|
Hi Matt, I'll try to help. :o) First, you have to specify the type of sensor that is hooked on the port. You do that with: type port SENSOR_TYPE Let me know if you need to know the different values for 'type'. 3 is a light sensor. Ports are numbered (...) (22 years ago, 15-Jul-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: Aborting from ISR
|
|
Hi, (...) My questions were a bit ambiguous. I don't want to abort the routine running on the ISR; I want (from the ISR routine) to abort a currently running user routine - eg abort something started from the console. So, for example, if a program (...) (22 years ago, 15-Jul-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: Light sensor question
|
|
(...) With obvious mappings, of course. (...) Put another way, at no point does the red LED on the light sensor light up, and I consistently read the same value from the light sensor, regardless of whether I set the mode to RAW or percent value. In (...) (22 years ago, 15-Jul-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | Light sensor question
|
|
I want to expand the Scheme procedure (get-light-value <sym | num>) where <sym> is one of 'PORT1, 'PORT2, 'PORT3 and num is either 0, 1, or 2 to the FORTH code 128 <port> SENSOR_MODE <port> SENSOR_CLEAR <port> SENSOR_READ <port> SENSOR_VALUE So, if (...) (22 years ago, 15-Jul-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: Aborting from ISR
|
|
(...) This should be : IsISRFree? 'UserISR ['] NoOp = ; of course. (22 years ago, 14-Jul-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: Aborting from ISR
|
|
(...) To remove your program from the UserISR just set 'UserISR to ['] NoOp - or even better: to the previously stored old value. (...) Yes, you just have to read the current value of 'UserISR. If no other program is hooked to the ISR this is the (...) (22 years ago, 14-Jul-02, to lugnet.robotics.rcx.pbforth)
|
