|
| | Re: pbForth vs RCX 1.0
|
| (...) Yes, please :-) I actually knew the EMIT and KEY words, but had never thought of using them to make two RCXs communicate. For some stupid reason in my head I was expecting some special API words was necessary to manage this communcation, while (...) (22 years ago, 2-Jul-02, to lugnet.robotics.rcx.pbforth)
| | | | RE: Linux driver for USB tower
|
| (...) Richard, That's great, but I just realized there is no URL....how can we test it if we can't find it? :-) Cheers, Ralph (22 years ago, 2-Jul-02, to lugnet.robotics.rcx.nqc, lugnet.robotics.rcx.pbforth)
| | | | RE: CPR for RCX?
|
| (...) ld is a linker. It takes the object code generated by the assebles and "links" it together to form an image that can be loaded. The file: ld/h8300_rcx.ld specifies how the objects are stiched together. (...) No, the firmware uploader splits (...) (22 years ago, 1-Jul-02, to lugnet.robotics.rcx.pbforth)
| | | | Re: CPR for RCX?
|
| (...) I knew Assembler would come into play sooner or later. I have downloaded a copy of the H8/300 Assembly language spec. What I still don't understand is how you turn the object code into 'S'-type records with 'ld'? (...) Can I assume the RCX has (...) (22 years ago, 1-Jul-02, to lugnet.robotics.rcx.pbforth)
| | | | RE: pbForth vs RCX 1.0
|
| (...) What you describe would work exactly. Normally, the "outer interpreter" of pbForth waits for input using "KEY" - which of course is just a char from the IR. You can make a special word that waits for anything you like... Cheers, Ralph (22 years ago, 30-Jun-02, to lugnet.robotics.rcx.pbforth)
| |