DSPRelated.com
Forums

McBsp-simple question

Started by silver_sparrow May 13, 2003
I'm now down to just getting a McBSP0 to tx data[tx on peripheral
interface is not connected, and
yes JP1 is shorted out] by CPU interrupts method.

Everything is setup in CSL, and I follow the outline in
'SPRA488B-McBSP Init.'

In 'main', I enable interrupt then McBSP for trasmit and frame
synch generator.

Okay-- I get first interrupt, as I had mapped onto HWI_9 and
MCBSP_xrdy tell me i'm ready to write to it, and so
data is written to it in the interrupt func.

Now I'm in main in a forever while loop waiting for next interrupt.
It never happens -- MCBSP_xrdy always read 0 if I poll it.

So why does it[McBSP0] end with more no interrupts after
being enabled and once written to?? =(

Thanks!
Chiko



You can get details of mcbsp from spru190d.pdf.

In csl of ccs2.1 the address of XCR is wrong with 0x01840010 (it should
be 0x18c0010), i.e.:

#define _MCBSP_XCR0_ADDR 0x018 4?(c) 0010u

Check if this the problem.

Tao Wang
R&D Engineer
ShangHai Orda Opto-electronics Co.

----- Original Message -----
From: "silver_sparrow" <>
Date: Tue, 13 May 2003 18:56:42 -0000
To:
Subject: [c6x] McBsp-simple question

Re: I'm now down to just getting a McBSP0 to tx data[tx on peripheral
Re: interface is not connected, and
Re: yes JP1 is shorted out] by CPU interrupts method.
Re:
Re: Everything is setup in CSL, and I follow the outline in
Re: 'SPRA488B-McBSP Init.'
Re:
Re: In 'main', I enable interrupt then McBSP for trasmit and frame
Re: synch generator.
Re:
Re: Okay-- I get first interrupt, as I had mapped onto HWI_9 and
Re: MCBSP_xrdy tell me i'm ready to write to it, and so
Re: data is written to it in the interrupt func.
Re:
Re: Now I'm in main in a forever while loop waiting for next interrupt.
Re: It never happens -- MCBSP_xrdy always read 0 if I poll it.
Re:
Re: So why does it[McBSP0] end with more no interrupts after
Re: being enabled and once written to?? =(
Re:
Re: Thanks!
Re: Chiko
Re:
Re:
Re:
Re:
Re:
Re: _____________________________________
Re: Note: If you do a simple "reply" with your email client, only the author of
this message will receive your answer. You need to do a "reply all" if you want
your answer to be distributed to the entire group.
Re:
Re: _____________________________________
Re: About this discussion group:
Re:
Re: To Join: Send an email to
Re:
Re: To Post: Send an email to
Re:
Re: To Leave: Send an email to
Re:
Re: Archives: http://www.yahoogroups.com/group/c6x
Re:
Re: Other Groups: http://www.dsprelated.com
Re:
Re:
Re: ">http://docs.yahoo.com/info/terms/
Re:
Re:

--
_______________________________________________
Sign-up for your own FREE Personalized E-mail at Mail.com
http://www.mail.com/?sr=signup



Thanks Tao!

However according to the bug list:

http://www.ti.com/sc/docs/dsps/hotline/techbits/c6bug.htm#SDSsq25431

The address is correct @ 0x01840010 and spru190d.pdf
is wrong. Check URL for details...

******************************************************
****I did get the interrupts going for a DLB config
**** for just the McBSP0, in CPU interrupt config
****if anyone wants to files, let me know
****************************************************** Chiko

--- Tao Wang <> wrote:
> You can get details of mcbsp from spru190d.pdf.
>
> In csl of ccs2.1 the address of XCR is wrong with
> 0x01840010 (it should
> be 0x18c0010), i.e.:
>
> #define _MCBSP_XCR0_ADDR 0x018 4?(c) 0010u
>
> Check if this the problem.
>
> Tao Wang
> R&D Engineer
> ShangHai Orda Opto-electronics Co.
>
> ----- Original Message -----
> From: "silver_sparrow" <>
> Date: Tue, 13 May 2003 18:56:42 -0000
> To:
> Subject: [c6x] McBsp-simple question
>
> Re: I'm now down to just getting a McBSP0 to tx data[tx
> on peripheral
> Re: interface is not connected, and
> Re: yes JP1 is shorted out] by CPU interrupts method.
> Re:
> Re: Everything is setup in CSL, and I follow the outline
> in
> Re: 'SPRA488B-McBSP Init.'
> Re:
> Re: In 'main', I enable interrupt then McBSP for trasmit
> and frame
> Re: synch generator.
> Re:
> Re: Okay-- I get first interrupt, as I had mapped onto
> HWI_9 and
> Re: MCBSP_xrdy tell me i'm ready to write to it,
> and so
> Re: data is written to it in the interrupt func.
> Re:
> Re: Now I'm in main in a forever while loop waiting for
> next interrupt.
> Re: It never happens -- MCBSP_xrdy always read 0 if I
> poll it.
> Re:
> Re: So why does it[McBSP0] end with more no interrupts
> after
> Re: being enabled and once written to?? =(
> Re:
> Re: Thanks!
> Re: Chiko
> Re:
> Re:
> Re:
> Re:
> Re:
> Re: _____________________________________




Now I wish to config, McBSP0 in DLB
with EDMA channels 12 & 13 servicing the port.
***************************************************
First:
The EDMA interrupts are hooked up to HWI 8 in CSL.

Second:
After setting up the EDMA channels in CSL, 'main'
initializes everything and McBSP is started; similar to
how its done in spra488b.

When I run the program, right after starting McBSP0 there
are no interrupts from the EDMA to HWI #8, we just sit
in a while loop.
I am guessing its a setup prob here, and now in 'hack
mode',
trying to fix it. :(

Can anyone point out anything that may help?

Chiko
--- Tao Wang <> wrote:
> You can get details of mcbsp from spru190d.pdf.
>
> In csl of ccs2.1 the address of XCR is wrong with
> 0x01840010 (it should
> be 0x18c0010), i.e.:
>
> #define _MCBSP_XCR0_ADDR 0x018 4?(c) 0010u
>
> Check if this the problem.
>
> Tao Wang
> R&D Engineer
> ShangHai Orda Opto-electronics Co.
>
> ----- Original Message -----
> From: "silver_sparrow" <>
> Date: Tue, 13 May 2003 18:56:42 -0000
> To:
> Subject: [c6x] McBsp-simple question
>
> Re: I'm now down to just getting a McBSP0 to tx data[tx
> on peripheral
> Re: interface is not connected, and
> Re: yes JP1 is shorted out] by CPU interrupts method.
> Re:
> Re: Everything is setup in CSL, and I follow the outline
> in
> Re: 'SPRA488B-McBSP Init.'
> Re:
> Re: In 'main', I enable interrupt then McBSP for trasmit
> and frame
> Re: synch generator.
> Re:
> Re: Okay-- I get first interrupt, as I had mapped onto
> HWI_9 and
> Re: MCBSP_xrdy tell me i'm ready to write to it,
> and so
> Re: data is written to it in the interrupt func.
> Re:
> Re: Now I'm in main in a forever while loop waiting for
> next interrupt.
> Re: It never happens -- MCBSP_xrdy always read 0 if I
> poll it.
> Re:
> Re: So why does it[McBSP0] end with more no interrupts
> after
> Re: being enabled and once written to?? =(
> Re:
> Re: Thanks!
> Re: Chiko
> Re:
> Re:
> Re:
> Re:
> Re:
> Re: _____________________________________
> Re: Note: If you do a simple "reply" with your email
> client, only the author of this message will receive your
> answer. You need to do a "reply all" if you want your
> answer to be distributed to the entire group.
> Re:
> Re: _____________________________________
> Re: About this discussion group:
> Re:
> Re: To Join: Send an email to
>
> Re:
> Re: To Post: Send an email to
> Re:
> Re: To Leave: Send an email to
>
> Re:
> Re: Archives: http://www.yahoogroups.com/group/c6x
> Re:
> Re: Other Groups: http://www.dsprelated.com
> Re:
> Re:
> Re: ">http://docs.yahoo.com/info/terms/
> Re:
> Re:
>
> --
> _______________________________________________
> Sign-up for your own FREE Personalized E-mail at Mail.com
> http://www.mail.com/?sr=signup >
> _____________________________________
> Note: If you do a simple "reply" with your email client,
> only the author of this message will receive your answer.
> You need to do a "reply all" if you want your answer to
> be distributed to the entire group.
>
> _____________________________________
> About this discussion group:
>
> To Join: Send an email to
>
> To Post: Send an email to
>
> To Leave: Send an email to > Archives: http://www.yahoogroups.com/group/c6x
>
> Other Groups: http://www.dsprelated.com > ">http://docs.yahoo.com/info/terms/


__________________________________