This is the mail archive of the
ecos-discuss@sourceware.cygnus.com
mailing list for the eCos project.
Re: Mbx Test
- To: jskov at redhat dot com, ecos-discuss at sourceware dot cygnus dot com, jlarmour at redhat dot co dot uk, Jesper Skov <jskov at redhat dot com>
- Subject: Re: [ECOS] Mbx Test
- From: "amassa at cts dot com" <amassa at cts dot com>
- Date: Fri, 23 Jun 2000 10:22:31 -0700 (PDT)
Thanks for the reply, I'll step through that code when I get a chance.
Are CPM interrupts typically enabled?
What happens when they are not enabled?
I see in the note in the ecos configuration tool that arbitration and
handling must be done by the application code. Is this handled by the ecos
kernel?
Thanks.
Jesper Skov <jskov@redhat.com> writes:
>>>>>> "amassa@cts" == amassa@cts com <amassa@cts.com> writes:
>
>amassa@cts> I have run the tests through the ecos configuration tool
>amassa@cts> and I consistently see the intr0.exe test failing. The
>amassa@cts> message I see is:
>
>amassa@cts> FAIL:<Intr tr 0 Failed.> Line: 147, Fi File:
>amassa@cts>
//D/PROGRA~1/REDHAT~1/eCos/packages/hal/powerpc/mpc8xx/v1_3_1/tests/intr0.c
>
>amassa@cts> Can anyone help me out with this?
>
>Look at the code, my man. Try enabling DEBUG_PRINTFS, see how the
>output compares to the more or less helpful table:
>
>// Time/PERIOD 0 1 2 3 4 5 6 7 8 9 10
>// Interrupt PIT TBA PIT PIT TBB PIT PIT
>// pit_count 0 0 0 1 1 2 2 3 3 4 4
>// count 0 0 1 3 4 4 5 40 41 42
>
>
>Also, there's some hardwired definitions:
>
>#ifdef CYGPKG_HAL_POWERPC_MBX
>#define TB_PERIOD (PIT_PERIOD*384) // PTA period is 15.36 uS
>#else
>#define TB_PERIOD (PIT_PERIOD*32) // assuming 512/16 divisors
>#endif
>
>If your board runs at a different speed than the ones we have, that
>may explain it.
>
>If you figure out what the problem is, I'd be happy to accept a patch :)
>
>Jesper