 | | Re: LNP - lets get coding.
|
|
(...) I have just grabbed a copy - will have a look! Where do you suggest we go from here? I'm up for creating an initial API and getting some code cut (Within my limits - I know little/nothing about Linux & MacOS, and as yes LegOS). However, I'm (...) (25 years ago, 1-Aug-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LNP - lets get coding.
|
|
(...) No, you didn't - I just didn't wanted to make sure I wasn't :) (...) This has already been done, for Librcx at least; don't know if anybody took a look at the code I put at: (URL) mentioned wanting to maybe take a look at that; porting to (...) (25 years ago, 31-Jul-99, to lugnet.robotics.rcx.legos)
|
| |
| | LNP - lets get coding.
|
|
(...) Hi, Didn't mean to come across as arguing - sorry if I did! As you say, lets get coding LNP (My assumption is that the coding bit hasn't started yet, if it has, please accept my apologies & let me know how it is going!). I guess the things (...) (25 years ago, 31-Jul-99, to lugnet.robotics.rcx.legos)
|
| |
| | emulegOS: quick bug fixes
|
|
I received this message by Mark Falco: (...) The site is now updated and emulegOS_unix.zip contains the new patched versions of ir-rover.cpp and irclient.tcl. The URL is: (URL) Mark Mario (URL) (25 years ago, 30-Jul-99, to lugnet.robotics.rcx.legos)
|
| |
| | RE: LNP Repost
|
|
(...) I think Kekoa means that we should calculate the CRC16 and use only the high byte in the message, to save space. If we then tag the low byte on later, the old code expecting only the high byte won't break.... Cheers, Ralph Hempel - P.Eng (...) (25 years ago, 30-Jul-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LNP Repost
|
|
(...) I'm not sure you can construct a sensible CRC16 that has a CRC8 as one byte. Cheers, Ben. -- (URL) grandfather once told me that there are two kinds of people: those who work and those who take the credit. He told me to try to be in the first (...) (25 years ago, 30-Jul-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LNP Repost (Me banging on about checksums)
|
|
(...) You will miss about 1 in 256 errors that you do not catch earlier using collision detection. I think your error rate per message will be much less than 1 in 256 if you (can?) get the collision detection code right. But we shouldn't argue the (...) (25 years ago, 29-Jul-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LNP Repost (Me banging on about checksums)
|
|
(...) With much respect, I would suggest that CRC8 is probably not sufficient, especially if we go for a broadcast (Ethernet) solution, where lots of collisions, and hence errors, will probably occur - with CRC8 you will probably miss about 1 in 256 (...) (25 years ago, 29-Jul-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LNP Repost
|
|
(...) My only thoughts are that not everybody will need or want the generality of port support in the protocol. I would suggest reordering the first four bytes, moving the payload length up toward the front, and defining it to explicitly include the (...) (25 years ago, 28-Jul-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS and Markus in Forbes
|
|
(...) Me, too ;-) Markus. (25 years ago, 28-Jul-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LNP Repost
|
|
(...) As am I - it looks interesting, but looks like it may have died. Hopefully not! (...) election process. I had wondered about this. My big suggestion is for us to come up with a software API for both the RCX end and PC (or whatever) end. This (...) (25 years ago, 28-Jul-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LNP Repost (Checksum algorithm)
|
|
This has little (Err... nothing in fact) to do with Lego, but worth noting as it is handy when you need a good SW checksum! (...) Indeed, as you say the standard I mentioned does use mod 255 (See Annex C ISO/IEC 8473-1 : 1994 [(URL) As far as I can (...) (25 years ago, 28-Jul-99, to lugnet.robotics.rcx.legos)
|
| |
| | New pbFORTH 106 release
|
|
This is a bulk mailing of notice of the new pbFORTH 106 release. If you don't want to be on this list, please email me so I can take you off. The latest and greatest pbFORTH is now available. Enhancements include: 1. Fixed issues with timers (thanks (...) (25 years ago, 28-Jul-99, to lugnet.robotics.rcx, lugnet.robotics.rcx.pbforth, lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS and Markus in Forbes
|
|
This was my reaction too. In fact, I was gleefully skipping around with a printout! Congrats and thanks to those involved. -Suz. (...) (25 years ago, 28-Jul-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LNP Repost
|
|
I am coming into the middle of this (or at the end considering the posting dates), and am hoping I don't sound like a fool putting out these ideas (since I don't yet know how legOS works). Is the RCX# used as a sort of ethernet MAC address? If you (...) (25 years ago, 28-Jul-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS and Markus in Forbes
|
|
Yahoo! Maybe we adult lego enthusiasts can finally come out of the closet & say, "were here, we like lego's, GET USED TO IT!!!" : ) Michael Aaron (...) (25 years ago, 28-Jul-99, to lugnet.robotics.rcx.legos, lugnet.robotics)
|
| |
| | Re: legOS and Markus in Forbes
|
|
(...) That's kind of only a tiny mention. I meant that it didn't really talk about it in-depth. That's what's so cool about the new article, IMHO -- it's a first step toward a larger awareness. --Todd (25 years ago, 27-Jul-99, to lugnet.robotics.rcx.legos, lugnet.robotics)
|
| |
| | Re: legOS and Markus in Forbes
|
|
It does talk about the " using an open architecture system. " "MindStorms robot developers were creating code in a variety of languages like Visual Basic and C on their PCs and uploading the code to the RCX units. " John A. Donaldson (...) (25 years ago, 27-Jul-99, to lugnet.robotics.rcx.legos, lugnet.robotics)
|
| |
| | Re: legOS and Markus in Forbes
|
|
(...) (I guess I should have posted, instead of going to lunch! ;-) But there *IS* a URL...they just didn't put http:// in front of it, so your browser may have missed it. They mentioned Markus' site ((URL) in that same paragraph. (They mention (...) (25 years ago, 27-Jul-99, to lugnet.robotics.rcx.legos, lugnet.loc.us.ca.sf)
|
| |
| | Re: legOS and Markus in Forbes
|
|
(...) This is BIG NEWS and GREAT exposure for Markus and friends!!! -- a major business magazine recognizing the pursuits and achievements of adult LEGO fanatics on the net to extend the RCX technology toward greater heights! In May, Forbes also had (...) (25 years ago, 27-Jul-99, to lugnet.robotics, lugnet.robotics.rcx, lugnet.robotics.rcx.legos, lugnet.general, lugnet.publish, lugnet.announce)
|
| |
| | Re: LNP Repost
|
|
(...) I remember that! But aren't you supposed to do it mod 255 for maximum effectiveness? Cheers, Ben. -- (URL) grandfather once told me that there are two kinds of people: those who work and those who take the credit. He told me to try to be in (...) (25 years ago, 27-Jul-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LNP Repost
|
|
Hi, I'm kinda new to LUGNET, so if I get this wrong - sorry! I'm interested in this LNP idea that seemed to be floating around a few months ago. Is it still alive, and if so what state has it got to? I would be grateful if someone can post or e-mail (...) (25 years ago, 27-Jul-99, to lugnet.robotics.rcx.legos)
|
| |
| | legOS and Markus in Forbes
|
|
Check it out here- brief, and unfortunately no URLs, but... (URL) (who is only slightly hurt that his documentation wasn't mentioned :) (25 years ago, 27-Jul-99, to lugnet.robotics.rcx.legos)
|
| |
| | better test value for touch sensors
|
|
FYI: The simple-rover example uses an unsafe test value for touch sensors. Touch sensor should be tested against <0xf000, NOT <0x2000 (e.g. simple-rover.c) Reason: Not pressed has a constant value >0xf000. Pressed varies depending on battery change, (...) (25 years ago, 26-Jul-99, to lugnet.robotics.rcx.legos)
|
| |
| | The IR FIX -- was: Re: Is IR considered broken?
|
|
(...) I had the same problem. (...) Here's the fix: enclode the old handler code in #ifdef TRASH, use the new #else part. I'll say a few things about the motivation below. (If you prefer to patch, download (URL) it's based on LegOS 0.1.7 but should (...) (25 years ago, 26-Jul-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Rotation sensors?
|
|
Thanks Mark, those changes got rotation-sensor.c working for me. (...) (25 years ago, 22-Jul-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: emulegOS: a new release
|
|
Just a note about a small bug. The supplied sample program ir-rover.cpp doesn't work on the real RCX. I think this may be due to IR complications under legOs. I'm working on a version which will work on both the emulator and the real system and will (...) (25 years ago, 21-Jul-99, to lugnet.robotics.rcx.legos)
|
| |
| | emulegOS: a new release
|
|
Mark Falco improved his Tcl/Tk version of emulegOS with tons of cool features. This version is now considered the "official" version of emulegOS, and we hope to release a Tcl based Windows version soon. The new features include: - IR support: (...) (25 years ago, 21-Jul-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Rotation sensors?
|
|
(...) [snip...] If you want to have more info about the sotry of this problem search this newsgruop for "rotation sensor bug found". Mario (URL) (25 years ago, 21-Jul-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Rotation sensors?
|
|
Yep, others have reported having these problems. Here's a fix I came up with, but has also only been tested on my system. There have been reports that the existing code works for some, and not for others, so you may need to customize this. just (...) (25 years ago, 20-Jul-99, to lugnet.robotics.rcx.legos)
|
| |
| | Rotation sensors?
|
|
Hello, Rotation sensors appear to be broken in the 990330 snapshot. Here's part of the code I'm using: ds_active(&SENSOR_3); ds_rotation_on(&SENSOR_3); ds_rotation_set(&SENSOR_3, 0); while (!PRESSED(button_state(), BUTTON_VIEW)) { (...) (25 years ago, 20-Jul-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Barcode Reader on LegOS page
|
|
Here is alex's webpage taken from the Legos page: (...) (25 years ago, 20-Jul-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Barcode Reader on LegOS page
|
|
What is Alex's page? (25 years ago, 19-Jul-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: is IR considered broken?
|
|
(...) For all who are interested, I copied the source to: (URL) porting hints, e-mail me directly. -Kekoa (25 years ago, 16-Jul-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: is IR considered broken?
|
|
Yes I would be interested in seeing the libRcx implementation of the IR functions. thanks, Mark (...) (25 years ago, 16-Jul-99, to lugnet.robotics.rcx.legos)
|
| |
| | application termination
|
|
Hi, what is the magic in LegOS to quit the application so that it can be restarted again? In some demos it works, but the same mechanism (i.e. 1 stopper process that kills the other on [run] button) quits the program, but the display says some (...) (25 years ago, 16-Jul-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: is IR considered broken?
|
|
(...) I have working IR code, but it does not work with LegOS. It works with that "custom, as-yet-unreleased version of Librcx" I mention every so often. It probably wouldn't take much to port it to LegOS. Changes would be: - modify hook to get a (...) (25 years ago, 16-Jul-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: firmdl for Win32? (Re: random numbers)
|
|
(...) I can compile it for use with Cygwin (Unix for NT), but since I have not (yet) figured out how to configure and use the serial port under NT, there is no NT version as of yet. But there are other firmware downloaders for NT already. To compile (...) (25 years ago, 16-Jul-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: random numbers
|
|
(...) The firmware supports random numbers using some method that whose name I can't remember at the moment. Something about feedback. Anyways, the algorithm there boils down to: int seed; int rand (void) { char bit; bit = (seed & (1 << 1)) >> 1; (...) (25 years ago, 16-Jul-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: random numbers
|
|
(...) The author claims it has very good spectral properties, but I have no way of testing that. The only other reference I have found to it on the net is from a group at the University of Salzburg, who state that it performed well in their tests. (...) (25 years ago, 14-Jul-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: random numbers
|
|
(...) You could either take just the source file out of gnulibc and link it in, or you could change your setup to actually use the gnulibc (which is what I am doing, although not with legOS). (...) It depends on what you want the RNG for. If all you (...) (25 years ago, 14-Jul-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: random numbers
|
|
(...) Probably a dumb question, but how do I link in another copy of libc, besides the hacked-down one already present in legOS? I can't just copy the one on top of the other, and the linker should just link in the first it finds, correct? At any (...) (25 years ago, 14-Jul-99, to lugnet.robotics.rcx.legos)
|
| |
| | firmdl for Win32? (Re: random numbers)
|
|
(...) Hi, Luis Villa - author of HOWTO has some that he will soon include into the HOWTO. If you need just random 16 bit integer, you can use for example this random = 25173*previous + 13849; but I don't know how good it is; start with an arbitrary (...) (25 years ago, 14-Jul-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: random numbers
|
|
(...) gnulibc has a good LCGM you can just link in. John A. Tamplin Traveller Information Services jat@LiveOnTheNet.COM 2104 West Ferry Way 256/705-7007 - FAX 256/705-7100 Huntsville, AL 35801 (25 years ago, 14-Jul-99, to lugnet.robotics.rcx.legos)
|
| |
| | LegOS HOWTO- updates
|
|
For those of you who have looked at the LegOS HOWTO before, or for those who have not, there are some new topics covered, some of which may make you think twice about sticking to the old firmware. new topics: *random number generation. Don't make (...) (25 years ago, 14-Jul-99, to lugnet.robotics.rcx.legos, lugnet.robotics)
|
| |
| | Re: is IR considered broken?
|
|
Sorry it took so long to reply, Mark... I somehow seem to have deleted your mail and only noticed it on the newsgroup by accident. Here are my thoughts. (...) Uhuh. This is (apparently) not a unique experience. (...) I have not had that experience, (...) (25 years ago, 14-Jul-99, to lugnet.robotics.rcx.legos)
|
| |
| | random numbers
|
|
I'm most of the way to getting it working myself, but I was curious to see if anyone has implemented a random number generator in their bot. Anyone? Anyone? -Luis ###...### Profanity is the one language that all programmers understand. -Anonymous (...) (25 years ago, 13-Jul-99, to lugnet.robotics.rcx.legos)
|
| |
| | is IR considered broken?
|
|
The precompiled tm-and-ir, kinda works for me. It is pretty good at receiving data, but the transmitted message often has garbage. When I compile it myself using the latest legOS snapshot, it always transmits garbage, others seem to have seen the (...) (25 years ago, 12-Jul-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: more fun with cross-compilers
|
|
Well, neither the latest release of egcs nor the latest binutils 2.9.1 seems to do it. Apparently, though, the beta binutils (2.9.4, use at your own risk, blah, blah, blah) works. The gcc compilation is now crashing in a different location. Using my (...) (25 years ago, 9-Jul-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: more fun with cross-compilers
|
|
Thanks for the help, Matt. solaris2.7 was correctly selected as the host by conf.guess, so that is not the problem. I would have no authority to apply any patches, even if I could find them, so I'm building egcs-1.1.2 instead. We'll see how that (...) (25 years ago, 9-Jul-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: more fun with cross-compilers
|
|
(...) There were some changes in Solaris 2.7 that break the compilation of some stuff, if I remember correctly. Have you checked with the gcc maintainers to see if they have a patch for this? Another thing to try would be specifying the host type (...) (25 years ago, 9-Jul-99, to lugnet.robotics.rcx.legos)
|
| |
| | more fun with cross-compilers
|
|
I posted here quite some time about this, and got a single personal response which has now been lost into the bowels of my pine folder "system." (hah!) Has anyone successfully set up a cross compiler on solaris 2.7? While building the binutils, I (...) (25 years ago, 6-Jul-99, to lugnet.robotics.rcx.legos)
|
| |
| | Barcode Reader on LegOS page
|
|
I've sent a mail to Alex Howanski at alex.wankwood regarding his Barcode sourcecode for legOS, but still do not see any reply. His page was updated on June 19th, so it's still current. Anyone out there communicate with alex and / or have his or (...) (25 years ago, 3-Jul-99, to lugnet.robotics.rcx.legos)
|
| |
| | legOS for Win 95/98 was: legOS make newbe question
|
|
I must have been sidetracked and posted this by mistake to ..build. Sorry, -Phil (...) (25 years ago, 29-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | RE: legOS make newbe question
|
|
(...) I'm waiting... :) If anyone can help out, Just let me know locations where I can grab files, or let me know that you have something so that I can give you a temporary FTP account to upload to my machine. Preferably, I'd like someone with a (...) (25 years ago, 28-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS make newbe question
|
|
I am a professional in the QA area and used to writing documentation as a part of my job, and am going to take the "challenge". Thanks for the offer to host the info. Give me a week or so (i'm very busy with some chip-level failure analysis right (...) (25 years ago, 28-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | RE: legOS make newbe question
|
|
(...) Great!!! I know Gavin's toolset works for Win98, you might ask if you can pinch a copy and host it on your site. I'm not against building the tools, or the tools themselves. In fact, the GNU assembler and debugger (and m4) were the tools I (...) (25 years ago, 28-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | RE: legOS make newbe question
|
|
(...) No argument from me here. Forth is not very popular anymore with the advent of really good C compilers for embedded processors (my specialty). BUT if you want a way to interactively control your LEGO bots, and have alook at the insides of the (...) (25 years ago, 28-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | RE: legOS make newbe question
|
|
(...) Like I said, I'm willing to host such a site for at least a year if others would like to contribute. That offer includes any necessary binaries for other tools as well- pbFORTH, NQC, etc. -Luis ###...### Profanity is the one language that all (...) (25 years ago, 28-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS make newbe question
|
|
(...) platform. (...) Same here.. That Gavin package...that might have been the one I downloaded...but even that one had a crazy directory structure, and all the compiled EXE's had names about 16 letters long! How about something simple like GCC (...) (25 years ago, 28-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS make newbe question
|
|
I appreciate your help, and it does sound interseting. However, I'm sure I'm not alone when I say that I'd prefer to leverage my (much more marketable) C skills when writing programs for the RCX. That's why I'm using NQC right now - I already know (...) (25 years ago, 28-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | RE: legOS make newbe question
|
|
(...) As a professional programmer, I just don't have the time, interest, or inclination to fiddle with building the GNU tools. I have tried to do this by following other folks best efforts and got something that was 95% functional. and in the end, (...) (25 years ago, 28-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | RE: legOS make newbe question
|
|
(...) Geez, I hate to plug my own work, but why not try the new pbFORTH. You can have arrays, as many variables as you want, simple multitasking, etc... No need for a compiler, just a terminal emulator will work. You DO have to try and learn FORTH, (...) (25 years ago, 28-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS make newbe question
|
|
The existing HOWTO is nice, and I know he worked hard on it BUT.... What I think we need is a howto with a REALLY narrow scope... which, ironically, would cover more people than any other group. You know what's probably out there right now? A ton of (...) (25 years ago, 28-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS make newbe question
|
|
Phil, Matt, other Windows/LegOS users- If anyone would like to write them up, I'd love to add Windows instructions to my LegOS HOWTO. Only problem is that I cannot test them myself, so I need others to provide them and make them usable. Currently, I (...) (25 years ago, 28-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS make newbe question
|
|
I'm thinking - we need just such a list! I mean - the only info out there for Win98 users is confusing at best. What is needed is a VERY SIMPLE explanation - basically, several steps. Download THIS zip file Unzip it to THIS directory name Put the (...) (25 years ago, 28-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS make newbe question
|
|
You are sooo smart. I am not sure I completely understand everything you have said in the last two posts, but if I just blindly type "make --unix" IT WORKS!!!. I will now go back and see if I can follow everything you have suggested and see if I can (...) (25 years ago, 27-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: signals / legOS internals
|
|
(...) So is the idea that you might have a "shell" app that lets you control a button or two and that takes over the lcd at times (say), and lets you start, suspend, and stop other apps that control different, presumably disjoint sets of motors and (...) (25 years ago, 26-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | 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)
|
| |
| | Re: signals / legOS internals
|
|
(...) Yes, that is it. A classic example is a full screen app such as vi. When being stopped, vi sets the terminal mode to something generic and saves any screen info that it needs. When resumed, it sets the terminal mode back to what it wants and (...) (25 years ago, 26-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | 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)
|
| |
| | Re: legOS make newbe question
|
|
(...) Damn, I am too used to tcsh, and yet I still remembered the export. Make that: MAKE_MODE=UNIX; export MAKE_MODE (followed by make) Again, make --unix should also do the trick if that is easier to remember. Oh. My MAKE_MODE environment variable (...) (25 years ago, 26-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: signals / legOS internals
|
|
(...) What am I missing? Why do you need callbacks in the process structure? I was thinking if you can reference the thread, you can just call a system function (e.g. suspend(thread)), and that will suspend the thread. You do not need callbacks (...) (25 years ago, 26-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS make newbe question
|
|
(...) Some versions of make look for the sh shell, others use the dos shell. Probably, make is using the dos shell and not sh. As far as I know, make does not parse the parens, the shell does. And dos does not understand the parens. My cygwin make (...) (25 years ago, 26-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS make newbe question
|
|
Thanks Lou, I am sure that you are right. I also don't know what could cause it or how to fix it. I just hope there is some bright person who reads this NG and can get me on to the next step. Based upon the discussion topics that I have seen, this (...) (25 years ago, 26-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: signals / legOS internals
|
|
(...) Cool. I will proceed. (...) Yup. I was out of the loop for awhile, and am once again whompin' on this project. (...) That is true. Signals would give the task the opportunity to stop/start tasks under its control, though, without the task that (...) (25 years ago, 26-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS make newbe question
|
|
(...) More to the point, it cannot recognize the '(cd' command. Now, why that is, or how you can fix it, I do not know. It would appear to be a problem with make or with your shell. It should just be farming the entire line off to the shell, which (...) (25 years ago, 26-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | 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)
|
| |
| | Re: legOS make newbe question
|
|
I reinstalled everything and I have progressed to the point of seeing the first-c++.o file and it stops with the following error: -snip- C:\legOS-0.1.7>make h8300-hms-g++ -DCXX -O2 -fno-builtin -fomit-frame-pointer -Wall -Wno-unused -Wno (...) (25 years ago, 26-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: signals / legOS internals
|
|
(...) So, should I abandon my implementation? If something every bit as good is already there, it may be silly for me to continue. I haven't looked at Librcx yet, so I don't completely understand how it works. I think one of the original reasons for (...) (25 years ago, 26-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | 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)
|
| |
| | Re: signals / legOS internals
|
|
(...) When a frame or character has been received by the IR port it signals an interrupt to the processor. The processor (OS) handles this by invoking an ISR (Interrupt Service Routine). In OSE ISR's are known as interrupt processes and they execute (...) (25 years ago, 25-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | 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)
|
| |
| | Re: signals / legOS internals
|
|
(...) I think you're missing the point. Now correct me if I'm wrong, Lou -- I believe the intent of the signal mechanism is to allow a way to specify a function to run when a system event occurs: e.g. a message arrives across the IR port. It is (...) (25 years ago, 24-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: signals / legOS internals
|
|
I misspoke when I said before that we have semaphores. What I meant was mutexes. We have had mutexes for quite awhile. Certainly long before I started on this signal thing. I started this long enough ago that I don't remember what particular problem (...) (25 years ago, 23-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | RE: signals / legOS internals
|
|
(...) Ummmmm, I don't want to speak for Markus, but most embedded kernels (and I use a lot of them) use the term signal and semaphore interchangably. I'm willing to bet a couple of bricks that the intent is to implement semaphores to facilitate (...) (25 years ago, 23-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | 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)
|
| |
| | Re: signals / legOS internals
|
|
(...) This second methed doesn't really solve anything since you still have to communicate with the compute thread from the receive thread. (...) But what can you actually do in the signal handler? Modify the state of the state of the executing (...) (25 years ago, 23-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | 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)
|
| |
| | Re: signals / legOS internals
|
|
(...) In OSE interrupt processes (first class processes, that is why we don't call them ISR's) use OS mechanisms (usually messages) to communicate with normal processes. The OS handles all update of shared data structures (such as message queues). A (...) (25 years ago, 23-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | 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)
|
| |
| | 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)
|
| |
| | Re: signals / legOS internals
|
|
(...) An asynchronous signal models a hardware interrupt. There are times when that is the appropriate interface. There are times when other interfaces are less error prone and are easier to write correctly. Frequently using only synchronous (...) (25 years ago, 23-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: signals / legOS internals
|
|
(...) Why signals?!? Unix-style asynchronous signals is the last feature I would ever want to implement or use. Brain-dead and very dangerous "feature". As you write; "The problem is that a signal can happen at any time". You shouldn't pass this (...) (25 years ago, 23-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: signals / legOS internals
|
|
(...) Actually, gcc moves the stack pointer before using any variables, so it is always safe to use stack below the current stack pointer. If you are using a different C compiler or doing assembly tricks, then you are on your own. (...) Traditional (...) (25 years ago, 23-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | RE: signals / legOS internals
|
|
(...) Not to put too fine a point on it, and I hope Kekoa agrees, but the "fluff" is the reason why replacement firmware works in the first place. Without the ROM vectors being dispatched through RAM pointers that are initialized by the ROM and then (...) (25 years ago, 23-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: signals / legOS internals
|
|
(...) Since it sounds like it might matter to you, I should point out that the interrupt situation on the RCX is a bit more complicated than the H8 manual makes it out to be. Interrupt vectors are in ROM, but the ROM does a dispatch to interrupt (...) (25 years ago, 23-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: signals / legOS internals
|
|
(...) Yes, that is correct. As for passing parameters to a function, they are simply pushed onto the stack before the function call. Therefore, the H8 stack usually looks something like e.g. this: function param sp+10 function param sp+8 return (...) (25 years ago, 23-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: signals / legOS internals
|
|
(...) I may have answered my own question here. Since the SP is adjusted before anything is actually done with the local variables, the rule about it always pointing to the last valid datum is not violated even if local variables are placed after (...) (25 years ago, 23-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: signals / legOS internals
|
|
(...) I may have down and up reversed, since different machines grow the stack upward or downward, and I've worked with a few. I do have push and pop clear in my mind, though. So, yeah, down. So, by the "always" rule, nothing will ever be below the (...) (25 years ago, 23-Jun-99, to lugnet.robotics.rcx.legos)
|
