 | | More LNP Issues
|
|
Thanks to Rainer for helping me with the stupid compiler bug :) Now that the PC side of LNP is working, I'm having troubles with the RCX side... I've modified the LNP sample provided on the WinLNP page as follows (with the includes trimmed): #define (...) (23 years ago, 22-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | Question for John Barnes
|
|
hi John, Some time ago there was a discussion about keeping the IR-tower alive. I want to keep the IR-tower alive, for fast data transport from RCX to PC. You mentioned that you had drawn the circuit diagram, but you never published it. Do you have (...) (23 years ago, 22-Apr-01, to lugnet.robotics.rcx)
|
| |
| | Re: Revisions to RcxCC
|
|
(...) Hmmm, it seems to be correctly passing -TRCX2 on the command line in my testing. I haven't actually tested with a brick containing the RCX2 firmware, but when I put an RCX2-only command in a program it compiles fine when I've selected RCX2 but (...) (23 years ago, 22-Apr-01, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Revisions to RcxCC
|
|
(...) With the amount of work you have put in on this it should be I who apologizes for pestering you. I tried the most recent version. It is correctly finding the nqc compiler now. Unfortunately it doesn't appear to be passing the correct command (...) (23 years ago, 22-Apr-01, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Revisions to RcxCC
|
|
(...) Whoops. I was assuming that since Mark's version put NQC in the same directory as RcxCC everyone was using the NQC in the same directory. I hadn't tried it differently myself. So in one of my past revisions I stuck a path on the front of the (...) (23 years ago, 22-Apr-01, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Revisions to RcxCC
|
|
(...) Hi John, I just downloaded the 'latest' version, RcxCC.exe is timestamped 4/16/01 5:23pm. It looks like this version, like the one immediatly before it, requires that nqc.exe is in the same directory as rcxcc.exe. With previous versions of (...) (23 years ago, 22-Apr-01, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Revisions to RcxCC
|
|
(...) Dean, I may have broken something in RcxCC related to running NQC. I'll take out the code I put in that pops up that error message and, with any luck, things will be back to normal. The odd thing is I can't figure out the conditions that make (...) (23 years ago, 22-Apr-01, to lugnet.robotics.rcx.nqc)
|
| |
| | CD-ROM Sample for Creative Projects with LEGO Mindstorms!
|
|
The link is small from the fatbrain site, so I barely noticed it: (URL) - Instructions and Movies Flashlight Follower - Movies and Programs Copy Cat - Movies only (The link is from here: (URL) (23 years ago, 21-Apr-01, to lugnet.books, lugnet.robotics, lugnet.robotics.rcx)
|
| |
| | HELP, has anyone ever seen SPIRIT.OCX events ??
|
|
The spirit.ocx definies a number of events (far more than in the ocx documentation are mentioned), but neither one of them seems to work. I've logged them all, but a never saw one comming up. Someone reported the same problem with the cybermaster. (...) (23 years ago, 21-Apr-01, to lugnet.robotics.rcx)
|
| |
| | SALE on Creative Projects with LEGO Mindstorms at Fatbrain!
|
|
***Creative Projects with LEGO Mindstorms is 30% off!!! Sale lasts until April 30.*** ROBOTICS SPOTLIGHT (URL) INTERVIEW, Ben Erwin (me) (URL) INTERVIEW, Joe Nagata (URL) (23 years ago, 21-Apr-01, to lugnet.books, lugnet.robotics, lugnet.robotics.rcx)
|
| |
| | Re: H8/300 Assembler/C interface
|
|
(...) By looking at your work with 'RCX internals', dumb is not the word i'd use :) I'd rather think of something like 'bit wizard' Björn (23 years ago, 21-Apr-01, to lugnet.robotics.rcx)
|
| |
| | Re: Revisions to RcxCC
|
|
I feel pretty stupid asking this question, but I can't seem to solve the problem myself. When I try to compile a program using John's RcxCC tool I keep getting the message: Unable to execute NQC. Check your installation. I'm running Windows 98. To (...) (23 years ago, 21-Apr-01, to lugnet.robotics.rcx.nqc)
|
| |
| | RE: H8/300 Assembler/C interface
|
|
(...) Sorry, looks like I need sleep too! (...) Hmm, looks like r2 is a copy of the high byte of the second long, but the complete long is pushed onto the stack! So the thing about GCC NOT splitting is true, it just keeps a copy of the higher order (...) (23 years ago, 21-Apr-01, to lugnet.robotics.rcx)
|
| |
| | Re: raw touch sensor values
|
|
(...) SENSOR_1 gives you the raw value from sensor 1. TOUCH_1 gives you the boolean value if it's a touch sensor. In fact SENSOR_1 gives you the raw value no matter what type sensor it is. HTH ROSCO (23 years ago, 21-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: H8/300 Assembler/C interface
|
|
(...) -fomit-frame-pointer, but it can cause problems debugging (obviously not important here). John A. Tamplin jat@jaet.org 770/436-5387 HOME 4116 Manson Ave 770/431-9459 FAX Smyrna, GA 30082-3723 (23 years ago, 21-Apr-01, to lugnet.robotics.rcx)
|
| |
| | Re: H8/300 Assembler/C interface
|
|
(...) Not my GCC: 00000016 <_main>: 16: 6d f6 mov.w r6,@-e7 <-- save frame pointer 18: 0d 76 mov.w r7,r6 <-- new frame pointer 1a: 6b 00 00 00 mov.w @0x0:16,r0 <-- r0r1 is 1st long param 1e: 6b 01 00 00 mov.w @0x0:16,r1 22: 6b 02 00 00 mov.w (...) (23 years ago, 21-Apr-01, to lugnet.robotics.rcx)
|
| |
| | raw touch sensor values
|
|
Hello, Can you access the raw touch sensor values in legOS? I know you can do it in NQC but I haven't figured it out in legOS. Thanks in advance, Nate Ridderman (23 years ago, 21-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | RE: H8/300 Assembler/C interface
|
|
(...) Geez Kekoa, get some sleep. The GCC makes the callee clean up the stack. My pbForth ROM interface routines assume that the caller cleans up the stack, just like your RCX library which must have been confusing for you :-) I'll post all this in (...) (23 years ago, 21-Apr-01, to lugnet.robotics.rcx)
|
| |
| | Re: H8/300 Assembler/C interface
|
|
(...) A brief review of the ROM disassembly seems to indicate the routines in ROM save r0-r5 if necessary. For example, the routine at 070c saves all registers. Like you said, parameters are passed in r6 with extra parameters on the stack. The (...) (23 years ago, 20-Apr-01, to lugnet.robotics.rcx)
|
| |
| | RE: H8/300 Assembler/C interface
|
|
One more question for Kekoa before I'm done... The RCX ROM routines take a parameter in r6, with additional params on the stack. Return value is in r6 too. Are all other registers considered volatile through the call, or do the ROM routines save (...) (23 years ago, 20-Apr-01, to lugnet.robotics.rcx)
|
