This is the mail archive of the
mailing list for the eCos project.
RE: Mbx Test
- To: <jskov at redhat dot com>
- Subject: RE: [ECOS] Mbx Test
- From: "Anthony Massa" <amassa at cts dot com>
- Date: Sun, 25 Jun 2000 14:09:21 -0700
- Cc: <ecos-discuss at sourceware dot cygnus dot com>, <jlarmour at redhat dot co dot uk>
- Reply-To: <amassa at cts dot com>
What clock speed do your boards run at?
How is the PTA period derived for the TB_PERIOD value?
From: email@example.com [mailto:firstname.lastname@example.org]
Sent: Friday, June 23, 2000 7:37 AM
Cc: email@example.com; firstname.lastname@example.org
Subject: Re: [ECOS] Mbx Test
>>>>> "amassa@cts" == amassa@cts com <email@example.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> 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:
#define TB_PERIOD (PIT_PERIOD*384) // PTA period is 15.36 uS
#define TB_PERIOD (PIT_PERIOD*32) // assuming 512/16 divisors
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 :)