From: Kim Phillips <kim.phillips@freescale.com>
To: "Vikas Aggarwal" <va824363@albany.edu>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: mpc8248 SEC -- interrupt handler 'is' invoked
Date: Wed, 3 Aug 2005 15:35:40 -0500 [thread overview]
Message-ID: <20050803153540.3530e114.kim.phillips@freescale.com> (raw)
In-Reply-To: <30177.198.22.236.230.1123094006.squirrel@198.22.236.230>
On Wed, 3 Aug 2005 14:33:26 -0400 (EDT)
"Vikas Aggarwal" <va824363@albany.edu> wrote:
> I will try the new BSP but meanwhile like to debug my ported driver.
>
> Is there a way , like kernel level single-stepping to know why the
> "interrupt status register" gets a value of "0x0000000000000040" which
> means TEA , transfer error acknowledge.
afaik, TEA usually means memory was unable to be accessed by the sec (somewhat along the same lines as a SIGBUS or SIGSEGV).
It's a long shot, but you may want to increase the 4-byte alignment of the rng buffer (0x009ffc5c in your trace?) to at least 8-byte.
as for debugging, you can printk sec status registers every time you write one, e.g. in a sec register write wrapper fn. Be sure to check the RNG interrupt status register, and the RNG status register, and the RNG interrupt control register.
and if all else fails, you can bypass the channel infrastructure altogether, and use the RNG EU in slave mode. Reset the SEC, write the RNG Reset Control Register SR bit, write <anyvalue> to the RNG Data size register, and pull data off the RNG FIFO at will.
Kim
next prev parent reply other threads:[~2005-08-03 20:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-29 15:40 mpc8248 SEC -- interrupt handler not invoked Vikas Aggarwal
2005-07-29 20:33 ` Kim Phillips
2005-07-30 3:39 ` Vikas Aggarwal
2005-07-30 23:32 ` Kim Phillips
2005-08-01 0:48 ` mpc8248 SEC -- interrupt handler "is" invoked Vikas Aggarwal
2005-08-01 17:37 ` Kim Phillips
2005-08-01 18:50 ` mpc8248 SEC -- interrupt handler 'is' invoked Vikas Aggarwal
2005-08-02 15:45 ` Vikas Aggarwal
2005-08-03 16:47 ` Kim Phillips
2005-08-03 18:33 ` Vikas Aggarwal
2005-08-03 20:35 ` Kim Phillips [this message]
2005-08-09 13:38 ` Vikas Aggarwal
2005-08-09 15:13 ` Kim Phillips
2005-08-09 20:52 ` Vikas Aggarwal
2005-08-10 15:37 ` Kim Phillips
2005-08-11 18:48 ` Vikas Aggarwal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050803153540.3530e114.kim.phillips@freescale.com \
--to=kim.phillips@freescale.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=va824363@albany.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).