 | | RE: h8/300 16-bit multiply
|
|
(...) <snipped code...> Are you sure that it works for signed numbers :-) (...) If you like, I can give you some notes on how my Forth was developed. I'm using a simple pseudo-assembler that lets me port this Forth to a new processor in less than a (...) (23 years ago, 4-Mar-02, to lugnet.robotics.rcx)
|
| |
| | Re: h8/300 16-bit multiply
|
|
Thanks. I have a version just 2 words longer that doesn't use the ROM code. Basically it's the ROM's code, trimmed down after assuming high words are zero initially. It's completely untested though, so there may be a bug. CODE UM* \ 16x16=32 (...) (23 years ago, 4-Mar-02, to lugnet.robotics.rcx)
|
| |
| | RE: rotation sensors
|
|
(...) Yes, you need to read the rotation sensor continuously. Be careful to not read it TOO quickly, especially if the sensor is turning slowly or you get the jumpy count problem. There is a fix for it and I might add it too the rotation sensor code (...) (23 years ago, 4-Mar-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | RE: problems with communications
|
|
(...) Keep digging. Try using a PC first and get that working. (...) Yep. (...) Sounds like pbForth is picking up steam again. Good. It's emails like this that keep me motivated to keep development going. I'm just back from a vacation, so I'll do (...) (23 years ago, 4-Mar-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | RE: h8/300 16-bit multiply
|
|
(...) The easiest thing is to cast your 16 bit values to 32 bits and use the built-in 32x32 multiply... Here's the code from pbForth that does it. (It's written in a pseudo- assebler, but you can probably figure it out...) #---...--- # UM* UM* ( u1 (...) (23 years ago, 4-Mar-02, to lugnet.robotics.rcx)
|
| |
| | RE: Support for pbForth in BricxCC
|
|
(...) John, This is great news! My own Tcl based GUI is a bit lacking, and a grand unified firmware uploader sounds like a great idea. I've been away on holidays and conferences most of the month, so I've missed most of this thread. Quick question, (...) (23 years ago, 4-Mar-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: Support for pbForth in BricxCC
|
|
(...) I wrote a hack to dump all the words, and here's the result for version 2.0.0. The word list has changed since 1999. I think the list is complete, but no guarantees. ?DUP 2SWAP 2OVER 2DROP 2DUP RSHIFT DLShift LSHIFT MOD / * */ SM/REM /MOD (...) (23 years ago, 4-Mar-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: Support for pbForth in BricxCC
|
|
(...) My plan is to simply have the editor syntax highlight the built-in words in various (configurable) ways. Comments, for instance, () and \ would be highlighter in a certain way. Numbers in another. Standard Forth words that are not simple (...) (23 years ago, 3-Mar-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: Support for pbForth in BricxCC
|
|
(...) I'm also playing with interfaces to pbforth at the moment. What you're doing and I'm not is syntax highlighting. I'm not actually sure how well that works in pbforth, since I'm not sure how the editor knows which words have been defined (...) (23 years ago, 3-Mar-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | rotation sensors
|
|
Do I have to manually frequently read the values from rotation sensors for the count to work, or does the firmware monitor the sensor for me? I have home-brew passive sensors, touch sensors and light sensors working fine, but the rotation sensor is (...) (23 years ago, 3-Mar-02, to lugnet.robotics.rcx.pbforth)
|
