Subject:
|
Re: Some comments (long)
|
Newsgroups:
|
lugnet.robotics
|
Date:
|
Thu, 6 May 1999 21:44:07 GMT
|
Original-From:
|
John A. Tamplin <jat@liveonthenet&spamless&.com>
|
Viewed:
|
1597 times
|
| |
|
|
On Thu, 6 May 1999, Kekoa Proudfoot wrote:
> The ROM a/d isr, which is different from the ROM sensor-processing function
> I mentioned, effectively does the efficient thing you mentioned. It
> effectively throws a semaphore which causes the firmware's
> sensor-processing code to run at high priority.
Obviously you have spent much more time deciphering the ROM than I have.
I wasn't aware that the ROM supported native threads, only multiplexing
the bytecode streams it executed. How can replacement firmware hook into
this sensor-processing code?
> You mean that in general, for the JVM. The other byte code that is being
> considered, which is not based on the JVM, and which I was talking about
> when discussing debugging methods, would likely use the debugging methods I
> described; I don't think you disagree with this, but maybe you
> misunderstood - I was not talking about the JVM.
Sorry for the confusion.
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 has 2 Replies:
 | | Re: Some comments (long)
|
| (...) I've mislead you. The ROM does not support native threads. The firmware simulates cooperative threads. The firmware selects one of six functions to run based on priority and whether or not a run flag has been set for that function. The run (...) (26 years ago, 6-May-99, to lugnet.robotics)
| | | 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 (...) (26 years ago, 6-May-99, to lugnet.robotics)
|
Message is in Reply To:
| | Re: Some comments (long)
|
| (...) What is your point? If you want to make sense of the raw values, and want to leverage the ROM code to process the existing sensor types/modes, you need to call a ROM sensor-processing function every time an a/d completes. That was the point I (...) (26 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
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
Active threads in Robotics
|
|
|
|
|
|
