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