|
i want to network four C6713-DSPs via the McBSP as a TDM-Highway. i found at TI only transceiver for McBSP<->SPI. can anybody recommend me a transceiver (2-6 channels, min. 4 Mbps, 5 meters distance) between McBSPs ? sincerely, olaf |
|
|
McBSP as TDM : which Transceiver for network ??
Started by ●July 2, 2003
Reply by ●July 5, 20032003-07-05
|
olaf, Since your application is "multidrop", an RS485 compatible interface [IMHO] is likely to be your best choice. You may not be able to achieve your desired data rate. Also, with your speed and cabling arrangement I do not know if you will need a "dummy" time slot between valid data time slots [I am not familiar with TI's TDM implementation]. mikedunn SLLA142 - Extending SPI and McBSP With DIfferential Interface Products olaf636 <> wrote:i want to network four C6713-DSPs via the McBSP as a TDM-Highway. i found at TI only transceiver for McBSP<->SPI. can anybody recommend me a transceiver (2-6 channels, min. 4 Mbps, 5 meters distance) between McBSPs ? sincerely, olaf _____________________________________ 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/ |
|
|
Reply by ●July 6, 20032003-07-06
|
Hello. I'm developing a simple program with a DMA to the McBSP1 in my
TI EVM6201 with CCS 2.20.00. Everything seems fine in debug mode, the interrupts are executed rightly correct and the program doesn't crash, except that the instructions are executed slowly (because of the extra information of the debug mode, I suppose) so when I test the time to execute a simple loop one thousand times toggling a general purpose I/O before and after the loop I obtain a time as big as 50 microseconds (with my oscilloscope). Now I know that I need to use the Release mode in order to change this condition, the problem is that when I change to Release mode and I enable the -o3 option (maximum optimization level) at the same time, the interruptions simple don't work, actually I need to use NONE as opt. level or the interrupts don't work. The problem is that in opt. level "NONE" in release mode the time to execute every instruction is the same than in debug mode (with General Debug Info: "NO DEBUG"). Also I made a test with a simple loop with no interruptions, just a loop. And the result was that in release mode with Opt. level to maximum (-o3) the time of the instructions is really (and I mean really) smaller than with opt. level to NONE. Actually in opt. level to NONE I obtained the same results than in my original project. Does any body could tell me how to use opt. level to maximum level and still have my interruptions running? Why the interruptions are running in DEBUG mode but not in RELEASE mode? Thanks. |
Reply by ●July 7, 20032003-07-07
|
dear mike, thx4 reply, but i believe the speed will be the critical factor.... SLLU016B describes the SN65LVDM31 for mcbsp-multipoint application, but i can use it for multidrop, too ?? -olaf --- In , Mike Dunn <mike-dunn@s...> wrote: > olaf, > > Since your application is "multidrop", an RS485 compatible interface [IMHO] is likely to be your best choice. You may not be able to achieve your desired data rate. Also, with your speed and cabling arrangement I do not know if you will need a "dummy" time slot between valid data time slots [I am not familiar with TI's TDM implementation]. > > mikedunn |
|
|
Reply by ●July 9, 20032003-07-09
|
Hello Olaf, The terms "multipoint", "multidrop" and "bussed" are often used interchangably. In my experience, multidrop is "single master - multiple slaves" while multipoint and bussed can be either single or multiple master. The 65LVDM31 should work well for your app. I just looked at the spec and it appears to be a pretty slick part. The biggest challenge will probably be the overall enable/disable time [device TPZH, TPZL, TPHZ, TPLZ + "control timing]. Even though you should have plenty of headroom, pay close attention to proper termination and use quality cabling. regards, mikedunn olaf636 <> wrote: dear mike, thx4 reply, but i believe the speed will be the critical factor.... SLLU016B describes the SN65LVDM31 for mcbsp-multipoint application, but i can use it for multidrop, too ?? -olaf --- In , Mike Dunn wrote: > olaf, > > Since your application is "multidrop", an RS485 compatible interface [IMHO] is likely to be your best choice. You may not be able to achieve your desired data rate. Also, with your speed and cabling arrangement I do not know if you will need a "dummy" time slot between valid data time slots [I am not familiar with TI's TDM implementation]. > > mikedunn _____________________________________ 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/ |
