 | | legos.sourceforge.net - Problems with SSL logon
|
|
Does anybody have problems logging on via HTTPS to legos.sourceforge.net? My browser do not connect at all. I'm using IE 5.01 with latest patches (also for SSL) but I continue to get errors. Note that before this problem, with the same browser & (...) (25 years ago, 5-Mar-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: CVS and SourceForge
|
|
(...) used (...) a (...) line (...) I did it without problems (for download) using command line version. But I'm using NT... I think I've read something about problems with Win95... What OS are you using? I have no success for now with wincvs, but I (...) (25 years ago, 5-Mar-00, to lugnet.robotics.rcx.legos)
|
| |
| | CVS and SourceForge
|
|
I downloaded the necessary software to gain access to the legOS project in SourceForge, but have been unable to get the files to download. When I used the GUI version of cvs (wincvs), I get the error message "you must specify a module name" (isn't (...) (25 years ago, 5-Mar-00, to lugnet.robotics.rcx.legos)
|
| |
| | New Windows HOWTO
|
|
This is a little premature since I have not yet made the compiler tools available, but I thought I would post this information now. Luis, would you like these instructions converted to HTML with all the proper links? ---...--- legOS on Windows HOWTO (...) (25 years ago, 4-Mar-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: malloc() bug found -- BAD MEMORY REGION :-(
|
|
(...) I'm afraid this made no difference for me. I still get dll crashes. My particular symptom is that if I make a 1 line change to legOS then download it, it crashes straight away at the next dll. Even if I undo the change, then rebuild & download (...) (25 years ago, 3-Mar-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Recommended change to MAKEFILE
|
|
(...) Martin, Rossz, you guys both now are registered and have CVS write access. Be aware that sourceforge changes those things with a cron job that runs every six hours or so, so it may be a few hours before you /actually/ have write access. Enjoy (...) (25 years ago, 3-Mar-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Recommended change to MAKEFILE
|
|
(...) Rossz didn't have CVS access until about... oh... 3 minutes from now? -Luis ###...### Profanity is the one language that all programmers understand. -Anonymous ###...### (25 years ago, 3-Mar-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Recommended change to MAKEFILE
|
|
(...) imho, a very good idea. Perhaps you should check that in to CVS ? -- Martin (25 years ago, 3-Mar-00, to lugnet.robotics.rcx.legos)
|
| |
| | Recommended change to MAKEFILE
|
|
Currently, legOS uses this in the makefile: # for the kernel .depend makedepend $(LEGOS_ROOT)kernel/*.c -Y $(CINC) -f- | $(FIXDEPS) $(LEGOS_ROOT)kernel/ > .depend # for a typical program .depend: makedepend *.c -Y $(CINC) -f- | $(FIXDEPS) (...) (25 years ago, 2-Mar-00, to lugnet.robotics.rcx.legos)
|
| |
| | Windows/DOS Cross-Compiler - Finally!
|
|
After two months of struggling, I have finally been able to build a complete set of h8/300 cross compiler tools that work natively in a Window's DOS box. So what does this mean? If you don't run Windows 9x/NT/2k, absolutely nothing. What this means (...) (25 years ago, 2-Mar-00, to lugnet.robotics.rcx.legos)
|
| |
| | Memory
|
|
I intend to implement some reinforcement learning algorithms with the RCX. My program is running big. Im using legOS 0.2.3 how many memory does it uses? Im using all sensors. How many is left for me. THe size of the *.lx file is the size I should (...) (25 years ago, 2-Mar-00, to lugnet.robotics.rcx.legos)
|
| |
| | LNP-Packets
|
|
I need to use the comunications with VC++ and Im going to do that. Can anyone tell the exact meaning of the following blocks. |F0|LEN| IDATA |CHK| |F1|LEN|DEST|SRC| ADATA |CHK| F0 and F1 is just a simple bit like 0 for F0 and 1 for F1? CHK is (...) (25 years ago, 2-Mar-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: malloc() bug found -- BAD MEMORY REGION :-(
|
|
Great! Well done, Martin! Toni "Martin Cornelius" <Martin.Cornelius@t-online.de> wrote in message news:38BDC2FD.85668C...line.de... (...) (25 years ago, 2-Mar-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: malloc() bug found -- BAD MEMORY REGION :-(
|
|
(...) My hangups are gone too! Danke! Jürgen (25 years ago, 2-Mar-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: malloc() bug found -- BAD MEMORY REGION :-(
|
|
(...) Great! (...) This has always been a problem- it was an issue with firmdl before dll. Nothing serious, so it was never fixed. (...) You've actually had programs that large? Wow. -Luis (trying to make this more than a one-sided conversation...) (...) (25 years ago, 2-Mar-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: malloc() bug found -- BAD MEMORY REGION :-(
|
|
(...) made some tests, and - Yep, it works ! I'd strongly encourage everybody experiencing strange hangups to apply the little fix to mm_init() i suggested. For me, it makes malloc() and dll work perfectly. BTW, there are some minor flaws in dll[x], (...) (25 years ago, 2-Mar-00, to lugnet.robotics.rcx.legos)
|
| |
| | malloc() bug found -- BAD MEMORY REGION :-(
|
|
It looks like it's not a bug in legOS, but in the RCX hardware: Memory from 0xfb80 to 0xfd7f is simply NOT WRITEABLE, or more exactly, always read as 0xff, at least on my RCX ! Try the following little test: // // memory test // #include <conio.h> (...) (25 years ago, 1-Mar-00, to lugnet.robotics.rcx.legos)
|
| |
| | malloc() bug haunt: getting closer..
|
|
Yesterday evening i found something, that might be the reason for some of the crashes reported lately: The chain of memory blocks used by malloc() has a broken entry, say: the reserved block at 0xfd7c has a length word of 0xfffe. This will cause (...) (25 years ago, 1-Mar-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Odd behavior
|
|
(...) afaik, with vanilla legOS-0.2.3, lnp_addressing_write and lnp_integrity_write are not thread-safe, there is a little patch fixing this in the lnpd tarball. (25 years ago, 29-Feb-00, to lugnet.robotics.rcx.legos)
|
| |
| | Never mind
|
|
Well, my so-called "working" program crashed again, after adding two sleep statements and two sound calls, neither of which my program actually got to. So, I guess there are other causes behind my hangs as well. Ah the joys. :) -- "Though I am not (...) (25 years ago, 29-Feb-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Odd behavior
|
|
(...) For me, at least, it's not hanging during dll. My earlier problem was that dll just wouldn't complete with my program, but it didn't crash the RCX. By the way, I think I've found my crashing problem. It looks like I had some LCD calls that (...) (25 years ago, 29-Feb-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Directions to compile GCC
|
|
Luis Villa <liv@duke.edu> : (...) box (...) for (...) Wow Thanks! Here is the error I am getting-> loading cache ./config.cache checking if compiler cc1obj has been built... yes checking for gcc... h8300-hitachi-hms-gcc checking whether the C (...) (25 years ago, 28-Feb-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Directions to compile GCC
|
|
I've also been struggling with building the cross compiler. I'm trying to create a DJGPP hosted version. Once I am successful, we will be able to use Markus's legOS on DOS/Windows as-is. Currently, I have to rewrite Makefile.Common, Makefile.Kernel, (...) (25 years ago, 28-Feb-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Directions to compile GCC
|
|
(...) This may not be the case- the cross-compiler will try to compile something, but at least with the directions most of us use, there is no standard C library created and so the compiler thinks it doesn't work. The trick (then) is to use Markus's (...) (25 years ago, 28-Feb-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Directions to compile GCC
|
|
"Markus L. Noga" <markus@noga.de> : (...) Thanks! In one of the sections under this document there is a short paragraph explaining that cross compilers may not like having 32 bit ints (Like BeOS uses) turn into 16 bit ints (Like I bet the RCX uses) (...) (25 years ago, 28-Feb-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Directions to compile GCC
|
|
Jim Jackson <jjackson@jnjackson.com> : (...) GCC-2.95.2 (...) --host=i586-pc-beos (...) This gave me the Idea to tell the configure that I was running a Linux box (instead of a bebox) It almost worked too. At the end of the make the machine says I (...) (25 years ago, 28-Feb-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Odd behavior
|
|
(...) currently i believe there is some really subtle bug in malloc(), that shows up only under special circumstances. I experience similar problems with a fat kernel/application that disappear after adding one cputw(), making the binary a little (...) (25 years ago, 28-Feb-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Odd behavior
|
|
(...) Or worse, MacOS. I use and love my Macs, but lord they sure don't have much crash protection right now. I just wish there was a way to avoid having to reload the firmware every time it breaks, but I suppose that without an MMU, that's a bit (...) (25 years ago, 28-Feb-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Directions to compile GCC
|
|
Are you using gcc-2.95 or the earlier egcs? What's your host machine? I'm running an Intel Pentium (pre-MMX) and Linux and had to specify the additional parameter: --host=i586-pc-linux Not sure whether BeOS is supported where linux is specified (...) (25 years ago, 28-Feb-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Odd behavior
|
|
(...) I'm afraid that mysterious hangs may be a permanent part of the life of a legOS user- in almost any serious program that I have written, perfectly legitimate code- simple code!- has occasionally caused weird hangs and needed hard reboots. (...) (25 years ago, 28-Feb-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Odd behavior
|
|
(...) I'm not so sure about my problem either. In fact, I'm getting some mysterious hangs much like you describe now that things are working. Maybe I'll try putting in some cputs or similar. -- "Our doubts are traitors, and make us lose the good we (...) (25 years ago, 28-Feb-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Odd behavior
|
|
(...) I don't think this was my problem, since other, shorter programs would download fine, just not my 5k monster. -- "Our doubts are traitors, and make us lose the good we oft might win by fearing to attempt." - William Shakespeare Mike Ash - (...) (25 years ago, 28-Feb-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Directions to compile GCC
|
|
Hi Bill, this page is captioned "Using and Porting GNU CC". It should give you an overview of the process. (URL) (25 years ago, 28-Feb-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Odd behavior
|
|
I saw the same behavior some time ago when I worked on a pretty fat program (about 6KB compiled code). Sometimes it worked OK, then I removed my debug code (some cputs defined by macros) and it hanged miserably... I thought it was some kind of (...) (25 years ago, 28-Feb-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Odd behavior
|
|
I think you may have had the same problem that I did, but if you did, you have answered the question yourself. (...) I had a bright light over the tower, and the batteries in the tower were running low. Redirect the light and install a new battery (...) (25 years ago, 28-Feb-00, to lugnet.robotics.rcx.legos)
|
| |
| | Directions to compile GCC
|
|
Does anyone have directions on how to compile GCC/LegOS. I am looking to get LegOS working on the BeOS but can not get the GCC cofigure command to work. The script ends explaining that my platform is not supported. I am not convinced that the (...) (25 years ago, 28-Feb-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Odd behavior
|
|
Well, it looks like I beat everybody to a solution. Except that I didn't. Oh, don't get me wrong, it works now and everything. The thing is, I don't know why. I spent some time today figuring out how to recompile the OS, and doing so. That didn't (...) (25 years ago, 27-Feb-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Odd behavior
|
|
I always feel a bit stupid replying to myself, but I realized I didn't give exactly what happened when the program download failed. When I run dll, it successfully deletes the old program off of the RCX, and then sits there occasionally popping out (...) (25 years ago, 26-Feb-00, to lugnet.robotics.rcx.legos)
|
| |
| | Odd behavior
|
|
I'm having a bit of trouble with dll and I was hoping someone kind on this list might be able to help me out. Basically, I have a program that's grown to become fairly large and complex, and I can no longer download it to the RCX. There's one (...) (25 years ago, 26-Feb-00, to lugnet.robotics.rcx.legos)
|
| |
| | mysterious hangs with fat kernel and dll (Stack corruption ?)
|
|
Hi there, after having made the legOS kernel about 2k fatter, i experience strange problems with dll. Uploading a fat application that mostly consists of an 8k initialised array works as before, i also can start the application. Trying to upload the (...) (25 years ago, 22-Feb-00, to lugnet.robotics.rcx.legos)
|
