To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.robotics.rcx.legosOpen lugnet.robotics.rcx.legos in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Robotics / RCX / legOS / 2948
2947  |  2949
Subject: 
Re: Motor Control Register (0xf000)
Newsgroups: 
lugnet.robotics.rcx, lugnet.robotics.rcx.legos
Date: 
Thu, 14 Nov 2002 05:02:49 GMT
Viewed: 
193 times
  
It also turns out that there are 8 bytes of external
RAM that peek through at addresses 0xff80-0xff87.
Writes to these locations also affect the motor
control register.  I suppose there's a small advantage
in using these registers to control the motor since
accesses to these locations can use the processor's
8 bit addressing modes.  And, because of the
"shadowing" by the RAM, the various bit instructions
seem to work fine.  I bet the H8 designers left this
little hole just so these instructions could be used
on external devices.

Mark

"Kekoa Proudfoot" <kekoa@graphics.stanford.edu> wrote:
Mark Riley <markril@hotmail.com> wrote:
So, I wrote a little test program that wrote a unique
pattern to all memory in the range 0xf000-0xfb7f.
I then inspected the memory, and sure enough the
entire pattern was intact.  It turns out that the entire
range is RAM, even the address 0xf000!

This is interesting.  It makes sense that the memory backing these
locations still works, but I never would have thought to try to use it.  I
will make a note of this on my pages.

-Kekoa



Message has 2 Replies:
  Re: Motor Control Register (0xf000)
 
(...) In that case, why didn't the RCX designers use an 8 input NAND to decode their addresses, to leave more of the RAM usable? Maybe there werent aware of this possibility? Jürgen (22 years ago, 14-Nov-02, to lugnet.robotics.rcx, lugnet.robotics.rcx.legos)
  Re: Motor Control Register (0xf000)
 
(...) Yeah, I missed that, I'll add that to the notes. (...) Too bad they didn't document the hole well enough to make it obvious to the people at Lego, who apparently had no idea. They use "mov.w rx,@0xf000:16" all over the place instead of the (...) (22 years ago, 20-Nov-02, to lugnet.robotics.rcx, lugnet.robotics.rcx.legos)

Message is in Reply To:
  Re: Motor Control Register (0xf000)
 
(...) This is interesting. It makes sense that the memory backing these locations still works, but I never would have thought to try to use it. I will make a note of this on my pages. -Kekoa (22 years ago, 13-Nov-02, to lugnet.robotics.rcx, lugnet.robotics.rcx.legos)

16 Messages in This Thread:








Entire Thread on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact

This Message and its Replies on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    

Custom Search

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR