 | | 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 (25 years ago, 20-Apr-01, to lugnet.robotics, lugnet.robotics.rcx)
|
| |
| | Re: H8/300 Assembler/C interface
|
|
(...) No no no! Sorry. They are NOT split. Boy am I dumb. -Kekoa (25 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 (...) (25 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 (25 years ago, 20-Apr-01, to lugnet.robotics.rcx)
|
| |
| | Re: H8/300 Assembler/C interface
|
|
(...) I wrote C code and then disassembled it. :) -Kekoa (25 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 (25 years ago, 20-Apr-01, to lugnet.robotics.rcx)
|
| |
| | Ross
|
|
Thanks Ross, I apreciate and value your advice in my persuit of enlightment:-) (25 years ago, 20-Apr-01, to lugnet.robotics.rcx)
|
| |
| | 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 (...) (25 years ago, 19-Apr-01, to lugnet.robotics.rcx)
|
| |
| | Re: H8/300 Assembler/C interface
|
|
(...) By the caller? No. They are callee-save. -Kekoa (25 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 (25 years ago, 19-Apr-01, to lugnet.robotics.rcx)
|
| |
| | Re: H8/300 Assembler/C interface
|
|
(...) Yeah, you are right. My bad. -Kekoa (25 years ago, 19-Apr-01, to lugnet.robotics.rcx)
|
| |
| | RE: H8/300 Assembler/C interface
|
|
(...) Not necessarily, that's why I'm asking. If the caller cleans up the stack, then the function just does an RTS and the caller adjusts the stack because it knows how much stuff was pushed on. For programs with lots of calls, this generates extra (...) (25 years ago, 19-Apr-01, to lugnet.robotics.rcx)
|
| |
| | Re: H8/300 Assembler/C interface
|
|
(...) Also: - caller cleans up parameters on stack - stack pointer is r7 The caller must clean up stack parameters b/c the return address is pushed after parameters are. -Kekoa (25 years ago, 18-Apr-01, to lugnet.robotics.rcx)
|
| |
| | Re: H8/300 Assembler/C interface
|
|
(...) Somebody correct me if I'm wrong. I just compiled some programs to check this. I believe that maybe the *ROM* calling convection is as Ralph described, but almost definitely the GCC calling convention is: - r0, r1, r2 hold parameters from left (...) (25 years ago, 18-Apr-01, to lugnet.robotics.rcx)
|
| |
| | RE: RCX+PC=Rubik's Cube Solver
|
|
(...) DUDE! These are unbelievable......I would never even consider doing something like this due to other time constraints like partners and kids. These are amazing - a must see and candidate for Site of the Week, no? Cheers, Ralph Hempel (25 years ago, 18-Apr-01, to lugnet.robotics, lugnet.robotics.rcx)
|
| |
| | RCX+PC=Rubik's Cube Solver
|
|
All -- There's recently been some discussion in the Mindstorms Forums about the feasibility of producing an RCX-based Rubik's Cube solver. I am happy to report that I have finished a functional "late beta" version. You can see it at (URL) are (...) (25 years ago, 18-Apr-01, to lugnet.robotics, lugnet.robotics.rcx) !!
|
| |
| | H8/300 Assembler/C interface
|
|
Does anyone know offhand what the calling convention between C/C++ and H8/300 assembler is using the GNU tools? The assumptions I'm making are as follows: R7 is the stack pointer R6 is the first (leftmost) parameter passed and the result R0-5 are (...) (25 years ago, 18-Apr-01, to lugnet.robotics.rcx)
|
| |
| | Re: Dropping your RCX on the floor...
|
|
"Tobias Möller" <tobias.moller@telia.com> wrote in message news:39DDEC5A.24DD89...lia.com... (...) didn't... Heh, this reminds me of when I first opened my RCX set. I hadn't used lego for years, and was working as a programmer, and thought, (...) (25 years ago, 16-Apr-01, to lugnet.robotics.rcx)
|
| |
| | Re: R: May I use RCX to play a .wav file?
|
|
Zhengrong Zang escribió: (...) WAV2RCX makes a "MIDI" of the wav. I'm also trying to play a wav with the RCX, and I have found this information. The pages explain how to play a tone and a PCM wave with 1 bit speaker, like the famous PC-speaker, (...) (25 years ago, 11-Apr-01, to lugnet.robotics.rcx)
|
| |
| | AI, Neural Nets
|
|
A month ago or so, I read a message which had a link about Lego and Artificial Intelligence (is not the van dam one). I remember it had several videos: -Simple Method -Adaline -Neural net ... The higher level the better results. Does anyone know (...) (25 years ago, 11-Apr-01, to lugnet.robotics.rcx)
|
