|
 | | Re: signals / legOS internals
|
| (...) I should add that since many things are vectored in this version of Librcx, overriding functionality is easy for the advanced user to do. For example: extern void (*__event_vector)(void); void my_setup_func() { // ... __event_vector = (...) (25 years ago, 24-Jun-99, to lugnet.robotics.rcx.legos)
| |
|  
event
(score: 0.160)
|
|
| | Re: signals / legOS internals
|
| (...) They could. In fact, there may be cases where that is exactly what you want to do. However, that requires you to write your code to examine the semaphore at every point where you would want to consider processing the event. It is more work. (...) (25 years ago, 26-Jun-99, to lugnet.robotics.rcx.legos)
| |
|
event
(score: 0.159)
|
|
| | Re: signals / legOS internals
|
| (...) Now keep in mind that this is coming from someone who won't take Duke's OS class until next spring- is there any reason the current semaphore implementation couldn't be used for a large percentage of these tasks? I.E., thread A checks (or uses (...) (25 years ago, 26-Jun-99, to lugnet.robotics.rcx.legos)
| |
|
event
(score: 0.159)
|
|
| | Re: signals / legOS internals
|
| (...) No, you should not abandon your implementation - not if you want to use LegOS. I was only explaining how I implemented similar functionality, for the sake of comparison. Regarding Librcx, I might release another version at some point, to add (...) (25 years ago, 26-Jun-99, to lugnet.robotics.rcx.legos)
| |
|
event
(score: 0.159)
|
|
| | Re: signals / legOS internals
|
| Ola, I do not see why you persist. I understand that a signal handler is very low level, that it is difficult to use right, that it only allows some things and not others, unless you're very careful. But you still missed my point, which was this: (...) (25 years ago, 25-Jun-99, to lugnet.robotics.rcx.legos)
| |
|
event
(score: 0.159)
|
|
| | Re: signals / legOS internals
|
| (...) An ISR can certainly modify data that is used by the executing code. For example, if it doesn't save registers that are used the interrupted code will certainly be affected. In fact, the ISR is of little use if it doesn't modify data that can (...) (25 years ago, 23-Jun-99, to lugnet.robotics.rcx.legos)
| |
|
event
(score: 0.159)
|
|
| | Re: signals / legOS internals
|
| (...) This is the same thing as most modern RTOS use, called various things. The terminology I use for this is FLIH/SLIH (first level interrupt handler and second level interrupt handler). Coupled with lock priority inheritance, it makes for a very (...) (25 years ago, 23-Jun-99, to lugnet.robotics.rcx.legos)
| |
|
event
(score: 0.159)
|
|
| | Re: signals / legOS internals
|
| (...) Because they are useful at times, and Markus directed me to implement them. I think the upcoming network code is going to use them, too (at least, that's what I heard). Just 'cause they're there doesn't mean you have to use them. (...) How do (...) (25 years ago, 23-Jun-99, to lugnet.robotics.rcx.legos)
| |
|
event
(score: 0.159)
|
|
| | Re: signals / legOS internals
|
| (...) But hardware interrupts schedule a different context (the interrupt process or ISR) from the one already executing. A Unix-style signal asynchronously signal interrupts the executing process and jumps to a different location in the code that (...) (25 years ago, 23-Jun-99, to lugnet.robotics.rcx.legos)
| |
|
event
(score: 0.159)
|
|
| | [ANN] pbFORTH 1.0.5 for RCX
|
| Finally, I have got pbFORTH to where I can release it again. It now has: - A simple cooperative tasker - A marker word so you can erase things easily - Support for poweroff - High res (10msec) count down and stop timers - Various and sundry fixes (...) (25 years ago, 21-Jun-99, to lugnet.robotics, lugnet.robotics.rcx.pbforth)
| |
|
event
(score: 0.159)
|
|
| | Re: Multi-RCX Dreaming
|
| (...) Along these lines, I'm still curious about those ruminations that were talked about on this list or maybe the .rcx or .rcx.legos lists regarding transmission algorithms. Not really having enough interest in the topic, I do not have the (...) (25 years ago, 18-Jun-99, to lugnet.robotics)
| |
|
event
(score: 0.158)
|
|
| | Re: Multi-RCX Dreaming
|
| (...) [ ... ] (...) Well, it hasn't actually died, just slowed down a bit. If you look on lugnet.robotics.rcx.legos there has been some very low-level talk recently. I haven't done *any* lego stuff recently, but, when I do I'll likely be doing (...) (25 years ago, 18-Jun-99, to lugnet.robotics)
| |
|
event
(score: 0.158)
|
|
| | RE: Rotation sensors?
|
| (...) Thanks for attaching the code Jonathan. Before I go through the steps of trying this out, what do you mean by doesn't work? ie. 1. Does it hang and not display anything? 2. Does it display the same data all the time? 3. Does it not respond to (...) (25 years ago, 4-Jun-99, to lugnet.robotics.rcx.pbforth)
| |
|
event
(score: 0.157)
|
|
| | Re: Sending raw IR characters.
|
| (...) The problem is that you can't simply use a terminal program to communicate with the RCX. The IR interface doesn't allow the transmission of arbitrary patterns of bytes and therefore won't allow it. You need to encode bytes before sending them, (...) (25 years ago, 28-May-99, to lugnet.robotics)
| |
|
event
(score: 0.156)
|
|
| |
|
event
(score: 0.155)
|
|
| | Re: Mindstorms article in Forbes
|
| (...) action. (URL) the way, I am the effects person the forbes article is about. The Mindstorms page will have a complete write up on the event soon. So will some of the competitors web pages. The event was put together by the company handling the (...) (25 years ago, 20-May-99, to lugnet.robotics)
| |
|
event
(score: 0.155)
|
|
| | Lego at E3
|
| Hi all. Being a resident of Los Angeles, I had the opportunity to attend E3 this year (Electronic Entertainment Expo). Primarily a trade event for the video game industry; I was somewhat surprised to see Lego setup there with a "Mindstorms" booth. I (...) (25 years ago, 17-May-99, to lugnet.robotics)
| |
|
event
(score: 0.155)
|
|
| | I'm being stupid. But how?
|
| I've written a test program using the 19990330 LegOS snapshot[1], and it's misbehaving oddly. The program looks like this: (the headers are the result of my frobbing the LegOS headers to refer to <mindstorms/{legOS header}>...) #include (...) (25 years ago, 29-Apr-99, to lugnet.robotics.rcx.legos)
| |
|
event
(score: 0.153)
|
|
| | Re: Something else is needed, I think...
|
| (...) I don't deny that these are reasonable things to want. But you don't need the JVM to get these. The problem with the JVM is that there is so much extra fluff associated with Java. You mentioned 64-bit floats and ints, security, etc. Why start (...) (25 years ago, 3-May-99, to lugnet.robotics)
| |
|
event
(score: 0.153)
|
|
| | case statement doesn't work- any clue?
|
| I'm trying to program some very rudimentary debugging stuff- just outputting variables to the screen. Basically, I want to use a switch/case statement to read an integer variable (in this case ID_number) which is then linked (by the case statement) (...) (25 years ago, 3-May-99, to lugnet.robotics.rcx.legos)
| |
|
event
(score: 0.153)
|
