|
Jeff Brower wrote: > Gustl- >>>> I was talking about the example in spra633. IIRC DX is feed >>>> into DR and FSR. So there is no external UART and therefore >>>> it's syncronous. >>> >>> >>> Where is the clock line? It's not synchronous. >> >> It's inside the DSP. It's syncrounous! spru190d Figure 12-36: >> CLKXM=CLKRM=1 > SPRU190D is the 'C6000 Peripherals Guide. Figure 12-36 depicts the > internal architecture of the McBSP and shows the McBSP connected > to.... nothing. But it shows a clock line from TX to RX when CLKXM=CLKRM=1 > >> From Spra633 abstract: "The McBSP is not capable of supporting >> UART standards > natively." The A in UART means asynchronous. > > So I ask with all due respect, why do you think that feeding DX (Tx > data) into DR (Rx data) and FSR (Rx framesync) is an example of > "synchronous" communication? The whole point of a 42 page article by > TI engineers Hiers, Ma, Malleth, and Chen is how to use the McBSP to > handle asyn comm, not sync. I think McBSP can handle a async communication. But when you use a loop back (DX -> DR,FSR) and CLKXM=CLKRM=1 this is in my opinion not a true async environment because of the internal clock line. And with such a test application you can not cover all caveats of a async communication that uses 2 different DSPs/UARTs. I have had such a situation. The code worked fine with the loop back. But it didn't work when communicating with a PC. Because I'm not a native english speaker I have problems to express my opinion. I think Mike Dunn explained our differences. If you want to continue this discussion I think we should take it from the list. Gustl |
|
|
Re: Asynchronous communication with C6711
Started by ●August 13, 2004
Reply by ●August 13, 20042004-08-13
|
Gustl- On Fri, 13 Aug 2004 10:14:19 +0200, Bernhard Gustl Bauer <> wrote: > Jeff Brower wrote: > > > Gustl- > > > > > >>>> I was talking about the example in spra633. IIRC DX is feed > >>>> into DR and FSR. So there is no external UART and therefore > >>>> it's syncronous. > >>> > >>> > >>> Where is the clock line? It's not synchronous. > >> > >> It's inside the DSP. It's syncrounous! spru190d Figure 12-36: > >> CLKXM=CLKRM=1 > > > > > > SPRU190D is the 'C6000 Peripherals Guide. Figure 12-36 depicts the > > internal architecture of the McBSP and shows the McBSP connected > > to.... nothing. > > But it shows a clock line from TX to RX when CLKXM=CLKRM=1 > > > > >> From Spra633 abstract: "The McBSP is not capable of supporting > >> UART standards > > natively." The A in UART means asynchronous. > > > > So I ask with all due respect, why do you think that feeding DX (Tx > > data) into DR (Rx data) and FSR (Rx framesync) is an example of > > "synchronous" communication? The whole point of a 42 page article by > > TI engineers Hiers, Ma, Malleth, and Chen is how to use the McBSP to > > handle asyn comm, not sync. > > I think McBSP can handle a async communication. > > But when you use a loop back (DX -> DR,FSR) and CLKXM=CLKRM=1 this is in > my opinion not a true async environment because of the internal clock > line. If it has to be synchronous then it should accept clock from external source i.e. CLKRM = 0. But CLKRM = 1 means it uses internal clock for timing and hence I think its async. No clock from outside. > And with such a test application you can not cover all caveats of > a async communication that uses 2 different DSPs/UARTs. > > I have had such a situation. The code worked fine with the loop back. > But it didn't work when communicating with a PC. I have implemented the same application on two different DSP and currently am taking measurements for my thesis on those DSK boards. They are communicating very well with UART's, although, I agree, it took a little longer to tame them. -Tarang > > Because I'm not a native english speaker I have problems to express my > opinion. I think Mike Dunn explained our differences. If you want to > continue this discussion I think we should take it from the list. > > Gustl > > > _____________________________________ > 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 > > Yahoo! Groups Links |
