 | | Re: Debugging
|
|
(...) However, last night, I wrote a brute force (spin loop) msleep which works fine in the scheduler. I found that 800 iterations of an empty for loop with a 16 bit index comes pretty close to 1ms. Granted, I cheated a little, knowing that the (...) (26 years ago, 17-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Debugging
|
|
(...) Oh, you're doing stuff inside the scheduler. Yeah, msleep doesn't work too well there :-) Yes, the pauses were only so I could see what was going on. Another thing you could do is print messages out the IR port; but I'm not sure how it would (...) (26 years ago, 17-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Debugging
|
|
(...) I don't think it does. Of course, the source would answer definitively, but I also know that until I remembered to put the refreshes in there, I didn't get useful output. (...) I did that too. In my case, the lower byte was the priority (...) (26 years ago, 16-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Debugging
|
|
(...) That's the method I've used. Just be sure to put an lcd_refresh() after the cputw() call - I can't remember if cputw() does the lcd_refresh() or not. Another thing I've done is write out a number where the upper byte indicates a position in (...) (26 years ago, 16-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | RE: H8300 Stack and SLEEP
|
|
Kekoa wrote: <<snipped original description of problem>> (...) <<snipped description of tests>> Once again, Kekoa goes the extra mile and proves what many of us are happy to be merely confident about. Someday, I'd like to be reincarnated as a grad (...) (26 years ago, 16-Mar-99, to lugnet.robotics.rcx.legos, lugnet.robotics.rcx.pbforth, lugnet.robotics)
|
| |
| | Re: FW: H8300 Stack and SLEEP
|
|
(...) To be more precise, it applies to sleep mode and software standby mode as long as you set port 5 bit 2 to high before activating either mode. It does not apply to hardware standby mode, since that does not save registers or end with an (...) (26 years ago, 16-Mar-99, to lugnet.robotics.rcx.legos, lugnet.robotics, lugnet.robotics.rcx.pbforth)
|
| |
| | Re: H8300 Stack and SLEEP
|
|
(...) After talking with Ralph over the weekend, I suggested a test he might do to figure out if port 5 bit 2 really does what he suggested it might. I don't think he did this test, so I fired up my RCX and hacked it together. I verified that port 5 (...) (26 years ago, 16-Mar-99, to lugnet.robotics.rcx.legos, lugnet.robotics.rcx.pbforth, lugnet.robotics)
|
| |
| | Debugging
|
|
Do you guys have an established mechanism for debugging? I'm thinking of writing certain numbers to the display using cputw(). The idea being that the number frozen forever on the display will be the (approximately) last place the code was ok before (...) (26 years ago, 15-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Program Wanted
|
|
Does anyone have a program for the Recycler robot? Please help! Adamski _______ <adamski2000@adamski...rve.co.uk> (26 years ago, 15-Mar-99, to lugnet.robotics, lugnet.robotics.rcx.legos)
|
| |
| | FW: H8300 Stack and SLEEP
|
|
(...) Markus, (and anyone else listening) I think it applies to the RCX power_shutdown() function as described in Kekoa's reference. The key is that this function puts the external RAM into low-power mode. If you are not calling power_shutdown() or (...) (26 years ago, 15-Mar-99, to lugnet.robotics.rcx.legos, lugnet.robotics, lugnet.robotics.rcx.pbforth)
|
| |
| | H8300 Stack and SLEEP
|
|
Hi All, If this is old news, ignore it... I just figured out this weekend (thanks Kekoa) that the H8/300 stack pointer (r7) and the power-down function in the RCX have a close relationship. The stack pointer MUST be in the on-chip RAM area (0xFD80 (...) (26 years ago, 15-Mar-99, to lugnet.robotics.rcx.legos, lugnet.robotics.rcx.pbforth, lugnet.robotics)
|
| |
| | Re: Idle process
|
|
I guess my earlier posting got out after all. I got the message from the NNTP server telling me to register. That is why a slightly different version of my message appears later in the group. (...) I plan to keep the idle task, now that I understand (...) (26 years ago, 11-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Idle process
|
|
(...) The idle task actually has the lowest priority in my scheme, but there was some efficiency gained in making the task list loop around. If the idle task is always there, it makes for simplified code in multitasking startup if you rely on that. (...) (26 years ago, 11-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Idle process
|
|
Sorry this message is so late, I had to get registered for posting from my work address. (...) I, too, consider power saving to be a valuable (indispensible) feature. That is precisely the sort of thing that I feared I might be overlooking. Up 'till (...) (26 years ago, 11-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Idle process
|
|
(...) I, too, consider power saving to be a valuable (indispensible) feature. That is precisely the sort of thing that I feared I might be overlooking. Up 'till now, I had not worked on an embedded project which would benefit from using (...) (26 years ago, 9-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Idle process
|
|
Hi Lou, the sleep instruction effectively shuts down the CPU until the next interrupt occurs. Thus, the idle process conserves battery power if no task wishes to run. I consider this a worthwile feature. If you can do this without a dedicated idle (...) (26 years ago, 8-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Idle process
|
|
I am reworking parts of the task scheduler in tm.c, tm.h, et al. I notice, reading the code, that there is an idle process which runs all of the time. There is a note in tm.c; "execi needs pd_idle". It appears to use it to locate the head of the (...) (26 years ago, 7-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Scheduler
|
|
Is anybody doing work on the scheduler (tm.c et al)? I've got some ideas for a minor rewrite and don't want to collide with anybody else's efforts. -- No honest business is promoted by spam with the possible exception of Hormel. (26 years ago, 2-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | A few notes...
|
|
Ha! Just completed my first LegOS program - and it only took a month! (off and on :) ) I'm going to note some things which stalled me, in the hope that they won't stall anyone else.. (1) I was trying to count how long the sensor was being pressed (...) (26 years ago, 28-Feb-99, to lugnet.robotics.rcx.legos)
|
| |
| | enhancing the motor driver
|
|
Hi all, I couldn't resist the urge to do something productive after taking the exam today. Dan sent me some code offering 256 levels of power, and I hacked away at it. I played around with the assembler, and here's my new version. It adheres to the (...) (26 years ago, 24-Feb-99, to lugnet.robotics.rcx.legos)
|
