 | | Major breakthrough serial wise.
|
|
I have been fiddling with serial interrupts with little success. Today I finally figured out that interrupts are masked in the CCR until you run the word RCX_INIT. I was blindly assuming that interrupts were generally enabled and I only had to deal (...) (24 years ago, 1-Jun-00, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: NQC 2.2 a2
|
|
(...) I'm really busy recently; it'll probably be a few more days before I have the Linux builds done. (Since it's an alpha release, it doesn't make my top priority list. I'll drop everything for the final release. *grin*) (24 years ago, 31-May-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: serial number
|
|
Well, the purpose would be that it would save me the trouble of recompiling the kernel every time I have to download to a new RCX. I might end up with as much as 8 of them. Other than that, I was just curios. Torkel Luis Villa <liv@duke.edu> wrote (...) (24 years ago, 31-May-00, to lugnet.robotics.rcx, lugnet.robotics.rcx.legos)
|
| |
| | Re: serial number
|
|
As far as I know, there is no way to access it. Why? If you intend to use it for unique identification for networking purposes, you can go into the config files in legOS and change the network address there... Luis (...) ---...--- "Going to (...) (24 years ago, 31-May-00, to lugnet.robotics.rcx, lugnet.robotics.rcx.legos)
|
| |
| | serial number
|
|
There is a serial number printed on the RCX. Is it possible to access that serial number through the hardware, or is it only printed on the outside? Torkel (24 years ago, 31-May-00, to lugnet.robotics.rcx, lugnet.robotics.rcx.legos)
|
| |
| | legOS HOWTO announcement
|
|
After much delay and deliberation, there is now a very, very rough cut of the 0.2.x legOS HOWTO at legOS's sourceforge site. There is still a lot to be done- for example, it doesn't mention winlegOS yet, nor does it cover the new rotation sensor (...) (24 years ago, 30-May-00, to lugnet.robotics.rcx.legos, lugnet.robotics)
|
| |
| | MacNQC 2.2 a2
|
|
Alpha release of MacNQC 2.2 is at (URL) the most part this release just incorporates the latest NQC compiler into the MacNQC GUI. Dave Baum (24 years ago, 30-May-00, to lugnet.robotics.rcx.nqc)
|
| |
| | java/RCX combo
|
|
Can't find the email address right now, but there were some questions here a week or so ago about interfacing Java and the RCX. I lied and said that nothing had been published on the web about the Sun Jini demonstration. In fact, there is a link (...) (24 years ago, 29-May-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Syntax for reserving variables in NQC?
|
|
(...) I would suggest leaving it simple. For example: #pragma 1 Would reserve var. one. #pragma 1 5 9 10 31 Would reserve var.'s 1, 5, 9, 10 & 31 It's the easiest to see at a glance and would be easy to adjust as you changed your code. Dean -- (...) (24 years ago, 29-May-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: DJGPP/DOS legOS Howto
|
|
(...) Rossz- I'm home for the summer (which means Windows only for now) so my deepest thanks for everything :) While I'm sitting and waiting for the download to finish, I have a question. You mention that Active Perl is needed for a kernel rebuild. (...) (24 years ago, 29-May-00, to lugnet.robotics.rcx.legos)
|
| |
| | NQC 2.2 a2
|
|
Second alpha release of NQC 2.2 is at (2 URLs) for the list of changes. Dave Baum (24 years ago, 29-May-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Syntax for reserving variables in NQC?
|
|
Although I would much prefer to see NQC reserveing the variables for itself, I prefer the syntax with a start and end on it. #pragma reserve 1 3 James P (24 years ago, 29-May-00, to lugnet.robotics.rcx.nqc)
|
| |
| | winlegos needed
|
|
I am in desperate need of the winlegos installation file. I have lost my own, my installation is corrupt, and without a correct installation I can't work. Pretty please, someone. /Torkel (24 years ago, 29-May-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: debugging gcc or ld
|
|
I found the problem. gcc hosted on LinuxPPC uses unsigned chars by default, and one of the h8300 support files for gas assumes signed chars. The bug fix was easy, but rather than take a chance on other lurking signed/unsigned errors, I just forced (...) (24 years ago, 29-May-00, to lugnet.robotics.rcx.legos)
|
| |
| | debugging gcc or ld
|
|
I'm trying to get started with legOS but I'm having some trouble getting things to link because I keep getting 'relocation truncated' errors. In order to determine if its ld or gcc that's at fault, could someone with a functional (...) (24 years ago, 29-May-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Syntax for reserving variables in NQC?
|
|
Dave Baum schreef: (...) This looks a bit confusing, the alternative looks more logical to me. (...) Now this I can understand :-) Looks awesome. (24 years ago, 28-May-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Syntax for reserving variables in NQC?
|
|
(...) Handling a range should't be too tough - perhaps like this #pragma start [count] where count is assumed to be 1 if not present // reserve location 1 #pragma 1 // reserve locations 5,6 and 7 #pragma 5 3 --- The alternative would be #pragma (...) (24 years ago, 28-May-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Syntax for reserving variables in NQC?
|
|
Dave Baum schreef: (...) It looks perfectly logical to me. Will it be possible to reserve a range or do we need to reserve each location separately? No need for an extra keyword indeed. (It's hard enough already. Well I guess part of that comes from (...) (24 years ago, 28-May-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Syntax for reserving variables in NQC?
|
|
The fact that in RCX2 the counters are overlapped with global variables has brought about an interesting problem. How should a programmer indicate to the NQC compiler that a certain RCX variable location is to be left untouched (not assigned to any (...) (24 years ago, 28-May-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Differences between RCX 1.0, 1.5 and 2.0?
|
|
(...) From what I've gathered: 1.0 to 1.5 Removed the power adapter board. Less components on the board. 1.0 to 2.0 from what I gathered a slightly newer board with a 32k ROM instead of the 16K in the 1.0. (The 1.0 is designed to hold a 32k ROM. As (...) (24 years ago, 26-May-00, to lugnet.robotics.rcx.legos, lugnet.robotics.rcx.nqc)
|
