Subject:
|
Re: Some comments (long)
|
Newsgroups:
|
lugnet.robotics
|
Date:
|
Thu, 6 May 1999 22:09:57 GMT
|
Original-From:
|
John A. Tamplin <jat@AVOIDSPAMliveonthenet.com>
|
Viewed:
|
1217 times
|
| |
|
|
On Thu, 6 May 1999, Kekoa Proudfoot wrote:
> I'm not sure what you mean by how can replacement firmware hook into the
> sensor processing code. Assuming you read my last message, the firmware
> would (when it got around to it) look at the bit for the sensor handler,
> see that it was set, and call the ROM sensor-processing code three times,
> once for each sensor. So the hook into the sensor-processing code is a
> function call into the ROM.
>
> I should revise what I said about the ROM/firmware doing the efficient
> thing you had mentioned a while ago now. The firmware really polls what I
> called the semaphore, so that not as efficient as it could be. But it is
> not contintually polling and processing the sensors, which is where the
> majority of the work is.
Thanks, I think I understand how it works.
John A. Tamplin Traveller Information Services
jat@LiveOnTheNet.COM 2104 West Ferry Way
256/705-7007 - FAX 256/705-7100 Huntsville, AL 35801
--
Did you check the web site first?: http://www.crynwr.com/lego-robotics
|
|
Message is in Reply To:
 | | Re: Some comments (long)
|
| (...) I didn't answer your question with the last message. The ROM does not execute byte codes, the firmware does. The firmware multiplexes between byte codes. I'm not sure what you mean by how can replacement firmware hook into the sensor (...) (25 years ago, 6-May-99, to lugnet.robotics)
|
42 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
