 | | Re: light sensor problem? —Luis Villa
|
| | | (...) :) Bad is, of course, all relative... (...) Yes, though IMHO fast = good. It allows us to do things with legOS that might not be doable with other firmwares. (...) I'm not sure which comments you are referring to- do you have a URL for the (...) (24 years ago, 24-Jul-00, to lugnet.robotics.rcx.legos)
|
| | | |
| | | | | Re: light sensor problem? —Eddie C. Dost
|
| | | | | (...) (URL) > I doubt we need this very fast reading of sensors. This makes implementing (...) Yes, when we have user space timers... (...) This is correct, but there are many good reasons for keeping assembly low bandwidth, like pitfalls in (...) (24 years ago, 24-Jul-00, to lugnet.robotics.rcx.legos)
|
| | | | | |
| | | | | | | Re: light sensor problem? —Luis Villa
|
| | | | | | (...) proof that this occurs (even though his logic does seem pretty dead on.) (...) Well, we do... time_t current_time = sys_time; while (sys_time < current_time + the amount of time I want to wait) { do nothing; } It's not pretty, but it is (...) (24 years ago, 24-Jul-00, to lugnet.robotics.rcx.legos)
|
| | | | | | |
| | | | | | | | Re: light sensor problem? —Eddie C. Dost
|
| | | | | | (...) This is why I want to measure things in our lab at work ;) (...) And keeps lower prio tasks from running, which they could do if we slept... (...) Oh well, there are some optimizations missing. I just looked at the code generated by (...) (24 years ago, 24-Jul-00, to lugnet.robotics.rcx.legos)
|
| | | | | | |
| | | | | | | | Re: light sensor problem? —Luis Villa
|
| | | | | | (...) Right. I made the connection between Kekoa saying "I need to test" and you saying "I will test" right /after/ sending the message, of course :) (...) True. (...) I figured this would be the case. gcc is a wonderful tool, but it does tend to (...) (24 years ago, 24-Jul-00, to lugnet.robotics.rcx.legos)
|
| | | | | | |
| | | | | Re: light sensor problem? —Kekoa Proudfoot
|
| | | | (...) I personally forget the numbers of the lugnet posts. The gist is that the firmware and LegOS were, at the time, different in a critical way. I don't know the current status of LegOS. At the time, LegOS cycled through the 4 A/D sensors, reading (...) (24 years ago, 25-Jul-00, to lugnet.robotics.rcx.legos)
|
| | | | |
| | | | | | RE: light sensor problem? —Ralph Hempel
|
| | | | | (...) And I'll add the reminder (for all the newbies) that without Kekoa's efforts in doing the low-level documentation, we would not be where we are today.... Thanks again, Kekoa....... As a side note, I wonder how the power to the LCD controller (...) (24 years ago, 25-Jul-00, to lugnet.robotics.rcx.legos)
|
| | | | | |
| | | | | | | Re: light sensor problem? —Kekoa Proudfoot
|
| | | | | | (...) I remember wondering what port 6 bit 3 did and so I think I tried setting it on and off and not noticing anything broken either way. Maybe I didn't test enough though. Somebody might want to try repeating the experiment. Some extra evidence is (...) (24 years ago, 26-Jul-00, to lugnet.robotics.rcx.legos)
|
| | | | | | |
| | | | | | Re: light sensor problem? —Michael Obenland
|
| | | | (...) Can you please tell me where to find this documentation? Mike (24 years ago, 27-Jul-00, to lugnet.robotics.rcx.legos)
|
| | | | |
| | | | | | Re: light sensor problem? —Kekoa Proudfoot
|
| | | | (...) (URL) particular, scroll down to "notes on addresses" and "notes on routines". The routines for the firmware start at 0x8000. The routines for the ROM start at 0x3ae. Ultimately, both kinds of routines are important to figuring out how the (...) (24 years ago, 28-Jul-00, to lugnet.robotics.rcx.legos)
|
| | | | |
