 | | cvs changes
|
|
Hi, I checked into the CVS repository some changes today. They include: A) a fix to util/dll-src/Makefile to reference ../../kernel/lnp.c, so a symbolic link or copy is not required. B) small changes to various makefiles to get c++ support working (...) (23 years ago, 21-May-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: c++
|
|
Hi, Sorry that I've been AWOL! Attached is a set of patches you can apply to the 2.5 distribution to clean up most of the make process. You will still have to correctly specify the TOOLPREFIX in Makefile.common, or via the make command line. You can (...) (23 years ago, 21-May-01, to lugnet.robotics.rcx.legos)
|
| |
| | c++
|
|
Is c++ supported in legOs2.5 ? We've been unable to compile even the demos! (I already posted about that) Please give us a voice! thanks Ciao, Vittorio (23 years ago, 20-May-01, to lugnet.robotics.rcx.legos)
|
| |
| | Trouble loading programs
|
|
Hi all, I'm new to legos and am having some problems loading programs. I have searched the news pages for my particular error and there are some that are close but not exactly. I hope someone can help because I am currently "dead in the water". Here (...) (23 years ago, 19-May-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Floating ponts ??
|
|
(...) Exceptions to the 0th law: You are manipulating and comparing floating-point values you know are integers with a magnitude less than a million or two. You are manipulating and comparing values you know are integer multiples of some power of (...) (23 years ago, 17-May-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Floating ponts ??
|
|
Hi there! (...) 0th law of computer science: NEVER use == on floats; it simply doesn't work as expected. In most cases a value cannot be exactly represented as a float variable; so MOST comparisons for equality WILL fail. (this is NOT an issue of (...) (23 years ago, 17-May-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: lnpd
|
|
Ah. Those links. I have asked Markus to move those a couple of times but he no longer responds to my emails. I'm afraid that until he does those links will remain in place (and remain quite dead.) Sorry... Luis (...) ---...--- "Nobody ever said that (...) (23 years ago, 16-May-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: lnpd
|
|
(...) This is old news, but I didn't find any answer to it while there are still two such links on (URL) the Doc section, the link to the HOWTO points to (URL) in the File section, the link to the Windows 9x/NT compiler points to (URL) (23 years ago, 16-May-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: permissions
|
|
(...) Thanks! But rather than do things for a single user I opted for: chmod 666 ttyS0 If I'm not mistaken, this will give every user access to Serial port 0 (comm 1). Since my system only uses comm 1 for the lego tower this seems like a safe thing (...) (23 years ago, 15-May-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: permissions
|
|
the following error as a user. [James@Sauron demo]$ ../util/dll helloworld.lx open: Permission denied opening tty: Permission denied To what directory or files does my user need permission? I tried using a find on tty to no avail. A little help? if (...) (23 years ago, 15-May-01, to lugnet.robotics.rcx.legos)
|
| |
| | permissions
|
|
Hello, The first thing I have ever installed on a *nix platform was legOS on my recently (last week) converted Redhat Linux PC. I didn't really know how this sort of thing is supposed to work, so I did the whole install as root. Of course after I (...) (23 years ago, 15-May-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: API changes
|
|
I agree with most of Luis statement. I've worked for three years in the embedded software development (for cars), and I think it's quite dangerous to have RCX functions with the same name that Unix ones, because they don't do the same thing. Using (...) (23 years ago, 14-May-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: API changes
|
|
I'm actually on my way to my baccalaureate ceremony right now, but I do want to say that I feel very strongly that API changes for the sake of API changes should not be checked in. The current API, while not always intuitive, is well documented and (...) (23 years ago, 12-May-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: API changes
|
|
(...) I don't imagine that these changes will increase memory usage much, since they are largely just re-working existing features. I will look into the memory usage before releasing, though. In fact, I think that after I redid the networking a bit (...) (23 years ago, 12-May-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: API changes
|
|
My only concern with these proposed changes is possible increased memory usage. Encapsulation, error reporting, thread synchronisation etc are nice; but with just 32k of RAM I would question whether these are appropriate for some applications. For (...) (23 years ago, 11-May-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: API changes
|
|
(...) These seems to me good ideas. Adding errno would also be useful. bye Bernardo New e-mail: dibbe@freestation.it (23 years ago, 10-May-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: new features
|
|
(...) I think it'll be very useful. (...) I worked on a reliable transport protocol written on top of LNP for my thesis a few months ago. It was my intention to make it available on the Internet, but I wasn't very happy with the implementation, (...) (23 years ago, 10-May-01, to lugnet.robotics.rcx.legos)
|
| |
| | API changes
|
|
In using legOS, I've found that many of the design decisions seem somewhat backwards, and I think that this is due to a desire to keep the interface as similar as possible to NQC. I was wondering what people would think about changing the core API (...) (23 years ago, 10-May-01, to lugnet.robotics.rcx.legos)
|
| |
| | new features
|
|
I just checked in a change to CVS which adds a new feature. Let me know if you have any problems with this: /* When no program is running, pressing the "view" button cycles through * a display of the amount of the amount of free memory (in decimal (...) (23 years ago, 10-May-01, to lugnet.robotics.rcx.legos)
|
| |
| | problems with legOS 0.2.5 and C++ compiling
|
|
due to makefile used in 0.2.5 version, when i try to make a c++ program it searches for h8300-hitachi-g++ but this executable cross compiler is not present in the file conataining gcc cross compiler and the other tools - i downloaded it from this (...) (23 years ago, 4-May-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Floating ponts ??
|
|
(...) Double check the actual program you are test to make sure that you don't have: p = 0.4 /* Only one = */ This is the number one "c" typo and is easy to overlook Lester been there, done that (23 years ago, 4-May-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Floating ponts ??
|
|
(...) I can't check this out now, but keep e-mailing me until I do. -Kekoa kekoa@graphics.stanford.edu (23 years ago, 4-May-01, to lugnet.robotics.rcx.legos)
|
| |
| | Floating ponts ??
|
|
Hello everybody I am writing a program that uses floats, but I have some problems. If I write /******/ float p; p = 0.3; if(p == 0.4) do something; /******/ The if statement evaluates to true. Is there anything special I have to do to use floats in (...) (23 years ago, 3-May-01, to lugnet.robotics.rcx.legos)
|
| |
| | RE: LegOS bug - firmware unlock string not below CC00h in some circumstances
|
|
(...) Argh! This is so typical of many embedded projects that I have seen go sour over the years. It's due to not using the linker to full advantage. In my firmware, I declare the string in its own .text section (you can do this in inline assembler (...) (23 years ago, 29-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | LegOS bug - firmware unlock string not below CC00h in some circumstances
|
|
Just thought I'd better report this... Firmdl3 is unable to download very large statically linked programs (with a .text segment greater than 4c00h bytes). Unlike previous size related bugs, this is *not* caused by firmdl, but rather by kmain.c. (...) (23 years ago, 28-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: C standard functions with legOS?
|
|
(...) As other people have pointed out, its not possible to use them straight off. I've written some floating point code for my own use to do conversions between rectangular (x,y) and polar (dist, bearing) calculations. The codes not documented I'm (...) (23 years ago, 27-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: C standard functions with legOS?
|
|
(...) I've been meaning to butt in on this discussion sometime, but I got caught up in things, but better late than never. The source you refer to is probably mine. I wrote a suite of fixed-point math routines for multiplication, division, and (...) (23 years ago, 27-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: C standard functions with legOS?
|
|
(...) An alternative is using fixed point math. There was some posts time ago, with C source for trigonometric functions. If you are interested, I should have links to them, somewhere (or do a `search' :-). bye Bernardo New e-mail: (...) (23 years ago, 26-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: C standard functions with legOS?
|
|
(...) The cross-compiler is set up to not use standard libraries. This is to give more control over the code produced. Also, many standard functions just wouldn't work on the H8. There is a float library (lib/float), which allows use of floating (...) (23 years ago, 25-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | C standard functions with legOS?
|
|
Is it possible to use functions from C standard libraries with legOS, e.g. sin() from math.h or abs() from stdlib.h? They are a part of gcc, but e.g. math.h seems to produce compiler errors. Best regards. Michael Wisse (23 years ago, 25-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: lcd
|
|
Yes, if you have three values, just display them like this : cputw((VALUE_1 << 8) + (VALUE_2 << 4) + (VALUE_3)); (...) (23 years ago, 25-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | lcd
|
|
Is it possible to display 2 lcd intergers on the screen at the same time? ie 2 rotation sensors. Thanks in advance chris (23 years ago, 25-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Sensor Commands and legOS 0.2.3
|
|
(...) TOUCH_1 is a macro defined in dsensor.h starting form version 0.2.4. If you don't want to upgrade, here is the code: #define TOUCH(a) ((unsigned int)(a) < 0x8000) #define TOUCH_1 TOUCH(SENSOR_1) #define TOUCH_2 TOUCH(SENSOR_2) #define TOUCH_3 (...) (23 years ago, 24-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | Sensor Commands and legOS 0.2.3
|
|
I just installed legOS 0.2.3 under Redhat 6.2, using the RPM's that were linked to in the HOWTO. Everything I have tried so far has worked great, except for getting my touch sensors to work. The documentation I have read said that in 0.2.x one could (...) (23 years ago, 24-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | RE: LegOS scheduler questions
|
|
(...) I don't /think/ so, but I don't have time to check to be certain and it has been now literally 10 months since I looked at kernel source. :\ (...) See #1. :\ (...) By design? As many as you can throw at it- there is no hard-coded limit, and (...) (23 years ago, 24-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | RE: LegOS scheduler questions
|
|
Folks, This is my first day with Leogs. I just installed Legos, compiled a program and have run it successfully. Haven't got a chance to take a look at the kernel source. I have the following questions and any response will be greatly appreciated. (...) (23 years ago, 24-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | WinLNP issues
|
|
For those who prefer the Java programming language, I've written some classes that may help with LNP. What you need is : the JDK 1.2, the Java Communication APIs (classes for Java communication through the serial port, and my classes located at : (...) (23 years ago, 23-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | More LNP Issues
|
|
Thanks to Rainer for helping me with the stupid compiler bug :) Now that the PC side of LNP is working, I'm having troubles with the RCX side... I've modified the LNP sample provided on the WinLNP page as follows (with the includes trimmed): #define (...) (23 years ago, 22-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: raw touch sensor values
|
|
(...) SENSOR_1 gives you the raw value from sensor 1. TOUCH_1 gives you the boolean value if it's a touch sensor. In fact SENSOR_1 gives you the raw value no matter what type sensor it is. HTH ROSCO (23 years ago, 21-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | raw touch sensor values
|
|
Hello, Can you access the raw touch sensor values in legOS? I know you can do it in NQC but I haven't figured it out in legOS. Thanks in advance, Nate Ridderman (23 years ago, 21-Apr-01, to lugnet.robotics.rcx.legos)
|
