 | | 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)
|
| |
| | Re: Interfacing Sharp's GP2D02 Distance Sensor to the RCX
|
|
(...) Hi All, Philo has a really excellent and well documented solution to the issue 'distance sensor at RCX'. quoting 'connect the analog output GP2D12 sensor using the simplest design possible ' visit: (URL) u.. Andreas (23 years ago, 20-Apr-01, to lugnet.robotics, lugnet.robotics.rcx)
|
| |
| | RoboLab Webring
|
|
|I am interested in starting a webring for web sites that primarily use |RoboLab. I noticed that there was a Mindstorms webring, but that the sites |associated with this webring mainly focus on the RIS programming |environment. I have found that the (...) (23 years ago, 20-Apr-01, to lugnet.robotics.rcx.robolab, lugnet.edu, lugnet.robotics)
|
| |
| | Re: H8/300 Assembler/C interface
|
|
(...) No no no! Sorry. They are NOT split. Boy am I dumb. -Kekoa (23 years ago, 20-Apr-01, to lugnet.robotics.rcx)
|
| |
| | RE: H8/300 Assembler/C interface
|
|
(...) Not to be too obtuse, but your first message says that long and float are never split across r2 and stack. So you're saying that they ARE split? That's fine, because it makes things a lot easier - not that any of my functions actually need to (...) (23 years ago, 20-Apr-01, to lugnet.robotics.rcx)
|
| |
| | Re: H8/300 Assembler/C interface
|
|
(...) To be more specific, I wrote C code, then disassembled it. The C types "long" and "float" are both split. -Kekoa (23 years ago, 20-Apr-01, to lugnet.robotics.rcx)
|
| |
| | Re: H8/300 Assembler/C interface
|
|
(...) I wrote C code and then disassembled it. :) -Kekoa (23 years ago, 20-Apr-01, to lugnet.robotics.rcx)
|
| |
| | RE: H8/300 Assembler/C interface
|
|
(...) I've just done some more browsing and found this tidbit: (URL) It seems to indicate that tghe registers are always filled and that a long may be split across r2 and the stack. Comments? Cheers, Ralph (23 years ago, 20-Apr-01, to lugnet.robotics.rcx)
|
| |
| | Re: error from makelx: address out of bounds
|
|
I've found it. They must be declared as static: static LightSensor s(LightSensor::S3,false); int main(){ ... } Regards. Michael Wisse (...) (23 years ago, 20-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: WinLNP Issues
|
|
Hi Matt, i had the same problem. That's a Microsoft *feature* ;-) that comes with visual C++ 6.0. (This problem is described in the MSDN. If you've got it installed, you 'll find details there.) You have to get a service pack for this compiler. Get (...) (23 years ago, 20-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | Ross
|
|
Thanks Ross, I apreciate and value your advice in my persuit of enlightment:-) (23 years ago, 20-Apr-01, to lugnet.robotics.rcx)
|
| |
| | WinLNP Issues
|
|
I'm trying to compile WinLNP, and I've run across a baffling problem: h:\program files\microsoft visual studio\vc98\include\...til.h(101) : fatal error C1001: INTERNAL COMPILER ERROR (compiler file 'msc1.cpp', line 1786) Please choose the Technical (...) (23 years ago, 20-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: code
|
|
(...) [snip] (...) Can't see anything glaringly obvious, except you've used different priorities for your tasks. As they're infinite loops with no waiting, it's probably better to make their priorities equal. But the best way is probably to do all (...) (23 years ago, 19-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | RE: H8/300 Assembler/C interface
|
|
(...) Ahhh, that makes it awkward with the RCX ROM calls, but I'm pretty sure I can make my assembler source compatible with this. I'm just getting ready to release an assembler RCX serial library that is either polled or interrupt driven. Any (...) (23 years ago, 19-Apr-01, to lugnet.robotics.rcx)
|
| |
| | Re: H8/300 Assembler/C interface
|
|
(...) By the caller? No. They are callee-save. -Kekoa (23 years ago, 19-Apr-01, to lugnet.robotics.rcx)
|
| |
| | RE: H8/300 Assembler/C interface
|
|
(...) Thanks Kekoa. One more question, are the other registers r3,r4,r5,r6 considered volatile across a function call in GCC? Cheers, Ralph (23 years ago, 19-Apr-01, to lugnet.robotics.rcx)
|
