 | | Re: anyone know how to check free space on RCX?
|
|
(...) The header is ok, but int is 2 bytes = 16 bit. You can check this with this highly optimized program: #include <conio.h> int main(int argc, char *argv[]) { lcd_int( sizeof( int ) ); for(;;) ; return 0; } And in the kernel sources, mm.c says (...) (22 years ago, 12-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: anyone know how to check free space on RCX?
|
|
(...) This can't be right. I'm about 99% sure that all of the ints I've used with my legOS programs have been 2 bytes. When using LNP to send RCX ints to a PC, for example, you have to use short on the PC end of things to make it all work right. (...) (22 years ago, 12-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: anyone know how to check free space on RCX?
|
|
(...) My sources (gcc-3.0) say: #define INT_TYPE_SIZE (TARGET_INT32 ? 32 : 16) A short experiment revealed that sizeof(short)=sizeof(int)=2, sizeof(long)=4. So int is normally 16bit. Only with the switch "-mint32" I get 32 bit ints. This is with a (...) (22 years ago, 12-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: anyone know how to check free space on RCX?
|
|
(...) According to config/h8300/h8300.h in the gcc sources, int is 32bit for the h8 cross compiler. I believe the reason mm_free_mem() returns an int is because the memory manager stores the size of each free block as size_t, which is defined in (...) (22 years ago, 12-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: anyone know how to check free space on RCX?
|
|
(...) int is defined as the natural width of the processor, which on a 16-bit processor is 16 bits. longs are 64 bits on some machines as well, so you can't assume it is always 32 bits -- if your code cares, use sizeof. (...) 32-bit math on the H8 (...) (22 years ago, 12-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: anyone know how to check free space on RCX?
|
|
That is very interesting Jason. It is interesting that mm_free_mem() returns a 16bit value using a 32bit return code. Both int and long are 32bit value on most computers/compilers these days; short would be a 16bit value; and char would be an 8bit (...) (22 years ago, 11-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: anyone know how to check free space on RCX?
|
|
While the declaration for mm_free_mem is int mm_free_mem(void) The fact is that the RCX has only 32K of memory available. 32K in hex is 0x8000... there's never a need for more than 4 digits in hex. Looking at key_handler() in kernel/program.c (the (...) (22 years ago, 11-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: HOWTO Demo.c
|
|
Brilliant! Brilliant! It works! Many Thanks to Micheal Obenland and also to Steve Hassenplug Best Regards Shehryar "Michael Obenland" <obenland@t-online.de> wrote in message news:Gz1xAM.Inn@lugnet.com... (...) some (...) ---...--- (...) ---...--- (...) (22 years ago, 11-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: anyone know how to check free space on RCX?
|
|
Albert Huang, Sorry for the confusion. "most significant" = upper 16 bits and "least significant" = lower 16 bits (the free memory is a 32 bit value). If you write the values out, you will get the 32 bit value (both values are hex) ... for example: (...) (22 years ago, 11-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: anyone know how to check free space on RCX?
|
|
(...) v0.2.6) When you press the View button (with no program running) LegOS will (...) Joseph, what do you mean by most significant / least significant? I'm under the impression that those two calls just display the same value, in decimal first and (...) (22 years ago, 11-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | RE: Re: Scheduler patch
|
|
Can someone please tell me how to unsubscribe from this group! Thanks, - Subir -----Original Message----- From: news-gateway@lugnet.com [mailto:news-gateway...net.com]On Behalf Of Ed Manlove Sent: Wednesday, July 10, 2002 8:49 PM To: (...) (22 years ago, 11-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Re: Scheduler patch
|
|
Joseph, Not to add too much work load, if you have a chance could you give an overview of the proposals out there for the task scheduling and sensor modifications (if any). This could be simply a quick list of lugnet.robotics.rcx.legos threads which (...) (22 years ago, 11-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: HOWTO Demo.c
|
|
(...) Well, that's much easier than all the crap I was going through. I guess it helps if you actually know what you're talking about. Thanks Steve (22 years ago, 10-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: HOWTO Demo.c
|
|
To solve your problems with demo.c, you sent me your source. There are some problems with it, but I think they are intresting enough to say something about them. The big problem you get with your program is caused by your main function: ---...--- (...) (22 years ago, 10-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | ***legOS new name : deadline is 18.07.***
|
|
As Steve mentioned, the 23.07. is too late for the announcement of the new name at Brickfest. I think it would be great to do so, so I decided to make the deadline at Thursday, 18.07. I will publish the new name around midnight of the 18.07 and (...) (22 years ago, 10-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | lnp error message..huh?
|
|
woolley thnx for the tip on checking the RCX memory.. now i have another question.. after having run continous messages back and forth between the RCX and my program on my PC for ~10 minutes. i get this error message: ---...--- Transmit error: (...) (22 years ago, 10-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Re: Scheduler patch
|
|
(...) I'd built a maze solver. When the solver makes a step (for example forward) it uses the light sensor to search for a wall and the rotation sensor to measure the distance it has traveled. If a wall is hit, the solver steps back until it reaches (...) (22 years ago, 10-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Re: Scheduler patch
|
|
"Joel Uddén" wrote (...) not (...) Actually, each task gets equal "wakeup" checking. The only difference between a low priority task and a high priority task is that the high priority task gets a larger time-slice when it is awake. This is not an (...) (22 years ago, 10-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Re: Scheduler patch
|
|
(...) Thanks for the link, your solution of proportional timeslicing is more straightforward than mine which I like. The only downside would be that a high prioritized process would have it's wakeup conditions checked less frequently than a low (...) (22 years ago, 10-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: anyone know how to check free space on RCX?
|
|
kenneth, I believe the code you are looking for is used in program.c (for LegOS v0.2.6) When you press the View button (with no program running) LegOS will show you "FREE", press again, you will get the most significant portion of the free memory (...) (22 years ago, 10-Jul-02, to lugnet.robotics.rcx.legos)
|
