[ECOS] Mbx Test

[ECOS] Mbx Test

[amassa]

I have run the tests through the ecos configuration tool and I consistently
see the intr0.exe test failing.  The message I see is:

FAIL:<Intr tr 0 Failed.> Line: 147, Fi File:
//D/PROGRA~1/REDHAT~1/eCos/packages/hal/powerpc/mpc8xx/v1_3_1/tests/intr0.c

Can anyone help me out with this?

Thanks,
Anthony

Re: [ECOS] Mbx Test

[Jesper Skov]

>>>>> "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

RE: [ECOS] Mbx Test

[Anthony Massa]

What clock speed do your boards run at?

How is the PTA period derived for the TB_PERIOD value?

-----Original Message-----
From: jskov@redhat.com [ mailto:jskov@redhat.com ]
Sent: Friday, June 23, 2000 7:37 AM
To: amassa@cts.com
Cc: ecos-discuss@sourceware.cygnus.com; jlarmour@redhat.co.uk
Subject: Re: [ECOS] Mbx Test


>>>>> "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

Re: [ECOS] Mbx Test

[amassa]

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