Sign in

Search c55x

Subscribe to c55x

c55x by Keywords

AIC23 | C5509 | CCS | CSL | EMIF | EVM | GEL | GPIO | HPI | Interfacing | JTAG | McBSP | OMAP | Omap15 | OMAP59 | RTDX | SDRAM | TMS320VC5509 | USB | XDS5

Discussion Groups

Discussion Groups | TMS320C55x | RE: code execution sequence

Technical discussions about the TI C55x DSPs (including the c5501, c5502, c5503, c5507, c5509, c5510 and OMAP5910).

Post a new Thread

RE: code execution sequence - liwe...@gmail.com - Mar 7 16:38:00 2006

check McBsp_xrdy() doesn't help. But adding for(*;*;*) loop before close solves this
issue. It might be some pipeline problem. But I am still wondering why no one else mentioned
this before?

(You need to be a member of c55x -- send a blank email to c55x-subscribe@yahoogroups.com )

Re: RE: code execution sequence - Jeff Brower - Mar 8 8:27:00 2006

Li Wei-

> check McBsp_xrdy() doesn't help. But adding for(*;*;*) loop before close
> solves this issue. It might be some pipeline problem. But I am still
> wondering why no one else mentioned this before?

Can you show your code before and after?  I would like to see this
clearly.  Thanks.

-Jeff

(You need to be a member of c55x -- send a blank email to c55x-subscribe@yahoogroups.com )

Re: RE: code execution sequence - Jeff Brower - Mar 8 8:30:00 2006

Li Wei-

> check McBsp_xrdy() doesn't help. But adding for(*;*;*) loop before close
> solves this issue. It might be some pipeline problem. But I am still
> wondering why no one else mentioned this before?

Can you show your code before and after?  I would like to see this
clearly.  Thanks.

-Jeff

(You need to be a member of c55x -- send a blank email to c55x-subscribe@yahoogroups.com )