Capture Engine questions

[Chris Johns]

On 27/04/11 1:54 AM, Robert S. Grimes wrote:
> What is the status of the Capture Engine?
>
> I ask because of two issues I've discovered.
>
> 1. If I am using the RTEMS shell, I don't want to use the rtems_monitor,
> right? The shell supercedes the monitor in this case, is that correct?
> It seems to work, though no mention is made of that usage on the Wiki...
>
> 2. The task name is not being reported correctly. Using RTEMS 4.9 and
> the rtems_monitor, I get the following from ctlist:
>
> 1-rtems $ ctlist
> total 13
> 0a01000a 90 90 90 DELAY a--- 0% 0% (15)
> 0a010007 30 30 30 Wevnt a--- 0% 0% (5)
> 0a01000c 80 80 80 Wmsg a--- 0% 0% (3)
> 0a010014 11 11 11 WRATE a--- 0% 0% (9542)
> 0a010004 100 100 100 Wevnt a--- 0% 0% (17)
> 0a010018 10 10 10 WRATE a--- 0% 0% (1983)
> 0a010010 80 80 80 READY a--- 0% 0% (2)
> 0a010002 100 100 100 Wevnt a--- 0% 0% (64)
> 0a010019 100 100 100 DELAY a--- 0% 0% (9809)
> 09010001 255 255 255 READY a--- 0% 0% (172135)
> 0a010001 120 120 120 READY a--- 0% 0% (5)
> 0a010011 80 80 80 READY a--- 0% 0% (233)
> 0a01000b 1 1 1 READY a--- 0% 0% (68596)
>
> Using RTEMS 4.10 and the shell, I get the following output (different
> sets of tasks, of course, and different BSPs, virtex and leon3,
> respectively):
>
> SHLL [/] # ctlist
> total 5
> 0a010003 @G� 10 10 10 Wmsg a--g 0% 0% (0)
> 0a010002 @G� 10 10 10 Wmsg a--g 0% 0% (0)
> 09010001 @G� 255 255 255 READY a--g 0% 0% (12332)
> 0a010005 @G�@
> �(@G� 1 1 1 Wmsg a--g 0% 0% (0)
> 0a010006 @G�@
> �(@G� 100 100 100 READY a--g % `

>
> Am I missing something here?
>

No nothing. It looks to me you found a bug. Please raise a PR and assign 
to me and I will take a look.

Thanks
Chris