 | | 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)
|
