Subject:
|
Memory, Motors and Odd Things
|
Newsgroups:
|
lugnet.robotics.rcx.legos
|
Date:
|
Wed, 10 Dec 2003 22:01:21 GMT
|
Viewed:
|
4009 times
|
| |
|
|
I ran into something odd, and I'm wondering if someone can explain it.
I have a pretty large BrickOS program, (the .lx is about 9k) and it uses around
2k for variables. (I think)
I've noticed when the program is running, it's not doing anything with the
motors, but they seem to buzz. I hooked up some diodes and lights, and found
the outputs are going both + and -.
I assume my variables are writing into the motor control area of BrickOS. Is
that possible?
Is there something I can do to stop it?
Any other thoughts?
Steve
|
|
Message has 1 Reply:
 | | Re: Memory, Motors and Odd Things
|
| (...) Hi Steve, Are you using BrickOS 0.2.6.10? In earlier versions, it was possible for malloc() to return pointers to RAM in the range [F010,FB7F], which was shared with the motor port controller. Writing to this memory adversely affected the (...) (21 years ago, 11-Dec-03, to lugnet.robotics.rcx.legos, FTX)
|
3 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
