 | | Re: Aborting from ISR
|
|
(...) This should be : IsISRFree? 'UserISR ['] NoOp = ; of course. (22 years ago, 14-Jul-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: Aborting from ISR
|
|
(...) To remove your program from the UserISR just set 'UserISR to ['] NoOp - or even better: to the previously stored old value. (...) Yes, you just have to read the current value of 'UserISR. If no other program is hooked to the ISR this is the (...) (22 years ago, 14-Jul-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | Running legOS under DJGPP Status
|
|
With increase discussion about running legOS under DJGPP I started investigating this process. The following is a status report of where I am and the steps I took to get there. Beware that I have jumped around some, left some tasks unfinished, and (...) (22 years ago, 14-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | whats up with lnp_init?
|
|
i have 2 threads (pthreads), 1 that sends and 1 that recieves on my PC. both of these runs in while(1) sentences. so.. i thought lnp_init was to be run only once, but unless i run the lnp_init routine each time i want to send a message nothing get (...) (22 years ago, 14-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | Aborting from ISR
|
|
Hi, Is there any way of ABORTing the current program from the ISR ? I want to attach a routine to 'UserISR and have it ABORT and then execute POWER_OFF when the off/on button is pressed. I would also like to know whether a user program or the idle (...) (22 years ago, 14-Jul-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | *** legOS new name - reminder ***
|
|
What is the better name for legOS? Is it osmOS or brickOS? Make up your mind and send your vote, either for brickOS or for osmOS, with the usual identification phrase, to legOS-namepoll@gmx.de The last day for your vote is Thursday, 18th. Regards, (...) (22 years ago, 14-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: RCX to RCX communication
|
|
(...) Mark, I was a TA(Teaching Assistant) for a course at Brown University that invovled building robots with the mindstorms kit. Go to the web site: (URL) and click on the link to take you to the normal page. Then go to the "LegOS" section fo the (...) (22 years ago, 14-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | RCX to RCX communication
|
|
I have studied the sources on the WEB for LNP but have not found any examples of C or C++ code for RCX to RCX communication. I have two RCXs and would like to build something that takes advantage of 6 inputs and 6 outputs. Do you have a sample you (...) (22 years ago, 14-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Announcing BricxCC release 3.3.5.6
|
|
(...) I wanted to publicly thank Rob Doucette for reporting the Access Violation bug and for helping me track down where it was occurring. I'd never have fixed it without his help. A big thank you also goes to David Schilling for reported the (...) (22 years ago, 13-Jul-02, to lugnet.robotics.rcx, lugnet.robotics.rcx.nqc, lugnet.robotics.scout)
|
| |
| | Re: detecting memory leaks
|
|
In case anyone attempts to use the mm_defrag() posted previously... you will need the following update to mm_try_join() //! check for free blocks after this one and join them if possible /* \param ptr pointer to size field of current block \return (...) (22 years ago, 13-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: detecting memory leaks
|
|
Jason, Excellent points! I like where this is going. "Jason Clark" wrote <snip> (...) See below. (...) then (...) Yes, it uses mm_try_join() --- here it is: //! defragment free blocks /*! use mm_try_join on each free block of memory */ void (...) (22 years ago, 12-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: detecting memory leaks
|
|
(...) Please, post. (...) I'm guessing you defrag using mm_try_join()? malloc() uses this to defrag the beginning of the pool until it finds a big enough block (which can then be split again if its too big); Defragging during idle would save this (...) (22 years ago, 12-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | Announcing BricxCC release 3.3.5.6
|
|
(...) I was updating the website earlier today which may have caused some disruption. The link worked for me a few minutes ago. This is as good a time as any to post about my new release of BricxCC. Version 3.3.5.6 fixes an Access Violation during (...) (22 years ago, 12-Jul-02, to lugnet.robotics.rcx, lugnet.robotics.rcx.nqc, lugnet.robotics.scout)
|
| |
| | Re: anyone know how to check free space on RCX?
|
|
(...) Thanks for conducting the test... being 200+ miles away from my RCX this was bugging me :). My sources (gcc-2.95.2) have the same #define... but with the following about 120 lines earlier: /* Make int's 32 bits. */ #define TARGET_INT32 (...) (22 years ago, 12-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: anyone know how to check free space on RCX?
|
|
John A. Tamplin, Jason Clark, Jochen Hoenicke and Michael J Ash: Thank you all for addressing these issues! It all make sense after reading the preceeding messages. I appologize for causing confusion. I am glad, however, to get it straight. ??So (...) (22 years ago, 12-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | detecting memory leaks
|
|
In the thread "anyone know how to check free space on RCX?" the issue of checking for memory leaks was raised. I wanted to mention that I have some code that may help in that area. I wrote a function for the memory manager called mm_defrag() It (...) (22 years ago, 12-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | 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)
|
