[Dspforum] CIPR question
Jones, Billy
Billy.Jones at thalescomminc.com
Tue Nov 3 08:26:38 MST 2009
The CIPR register can always be changed on the fly with EDMA_RSET(CIPR, n). If the CIPR is being read for indication of transfer completion (like in the waitfordma() function in this week's lab), it needs to be reset/cleared after that read.
Billy Jones
Digital Hardware Engineer
Thales Communications, Inc.
Land & Joint Systems Division
Tel: 240-864-7323
Fax: 240-864-7313
Billy.Jones at Thalescomminc.com
From: dspforum-bounces at echelonembedded.com [mailto:dspforum-bounces at echelonembedded.com] On Behalf Of O'Connor, Sean R.
Sent: Tuesday, November 03, 2009 10:21 AM
To: dspforum at echelonembedded.com
Subject: [Dspforum] CIPR question
Setting the OPT registers for ping and pong to 0x20320002 and 0x20310002 should set CIPR to 2 and 1 when the transfers have completed, I think. CIPR is actually getting set to 6 and 4 respectively, and if I use 6 and 4 as my masks things seem to operate as expected (at least ping and pong get updated and waitfordma() does not hang). To my knowledge the OPT register is the only register that can effect the CIPR... so this discrepancy is confusing to me. Any thoughts?
Thanks,
Sean
This email and any files transmitted with it are confidential and are intended solely for the use of the individual or entity to whom they are addressed. This communication represents the originator's personal views and opinions, which do not necessarily reflect those of Thales Communications, Inc. If you are not the original recipient or the person responsible for delivering the email to the intended recipient, be advised that you have received this email in error, and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. If you received this email in error, please immediately notify Administrator2 at Thalescomminc.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://echelonembedded.com/pipermail/dspforum_echelonembedded.com/attachments/20091103/a6f14588/attachment.html>
More information about the Dspforum
mailing list