Alden, We have only limited benchmarking information so far, but for MSGQ on DM6446 (which is the most common and popular DSPLink protocol), DSPLink 1.60 takes around 170 micro-seconds for a round-trip message, i.e. GPP->DSP->GPP. This includes OS process switching time etc. on a lightly loaded system. The message buffer size does not matter, since the protocol is zero-copy, i.e. we only send across the address of the message buffer and do not copy contents across.
Regards, Mugdha ________________________________ From: Alden Fuchs [mailto:[email protected]] Sent: Wednesday, January 07, 2009 8:35 PM To: Kamoolkar, Mugdha; [email protected] Cc: '[email protected]'; Abhijit Navalekar; John Roberts Subject: RE: SFFSDR DSPLink Hello world Hi Mugdha Thank you, for the response, I will have John look into the build to see if he used PROC only mode... PS have you benchmarked the performance of DSPlink especially in the shared buffer mode? Cheers Alden Cell (603) 275 9328 ________________________________ From: Kamoolkar, Mugdha [mailto:[email protected]] Sent: Wednesday, January 07, 2009 1:19 AM To: Alden Fuchs; [email protected] Cc: '[email protected]'; Abhijit Navalekar; John Roberts Subject: RE: SFFSDR DSPLink Hello world Alden, Which version of DSPLink are you using? The DSPLink build mechanism does not use CCS, but that does not mean that the IDE cannot be used for debugging purposes.That's still possible to do by loading symbols on the DSP-side CCS once you connect CCS to the DSP after it's running. I would suggest that you use DSPLink 1.60 in PROC-only mode (i.e. when running dsplinkcfg.pl script for build configuration, choose only PROC module. Then rebuild the GPP-side.). That would basically give you a simple loader without anything else in DSPLink, i.e. DSPLink on ARM-side would not bother with anything happening on the DSP. All it will do, is, load the DSP with the executable you give, and start it running. If your DSP executable blinks the LEDs, it will do so even without you having to attach CCS. With this, you would be able to use any CCS-built DSP executable (even non-DSPLink ones) along with DSPLink on ARM being used as a loader. If you want to use DSPLink for inter-processor communication also, then that's a different story, and you'll need some more work. Do you need IPC, or are you just looking for a loader? If you want to attach CCS to the DSP, you can do so once the DSP is running. I don't think there should be any issue with that. You may want to just glance through these once: Building DSPLink: http://tiexpressdsp.com/wiki/index.php?title=Building_DSPLink If you run into any issues during build: http://tiexpressdsp.com/wiki/index.php?title=Troubleshooting_DSPLink_build_issues Building DSPLink on Linux (including DSP-side) is really pretty simple if you want to try it out. Regards, Mugdha ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Alden Fuchs Sent: Wednesday, January 07, 2009 1:34 PM To: [email protected] Cc: '[email protected]'; Abhijit Navalekar; John Roberts Subject: SFFSDR DSPLink Hello world Hi All Sorry to bother you all but I was wondering if any of you have ever written a hello world for the DM6446 on the SFFSDR or other platform... I am a long time CCS3.3 user, and also of Linux, but for some reason I can't get my head around the development environment for DSPlink. Reading the user manuals and the install manuals it seems that the whole CCS IDE is out the window and we are back to Perl scripts and Make files... Just to test that the installs went right (my Linux kernel guru built the ARM side of things) I would love a CCS3.3 project that builds a DSP.out file and the matching executable file for the ARM. My guru built the DSPlink ARM side program using DSPlink sources for me to load any DSP.out file and start the DSP, but for whatever reason I can't get the CCS3.3 to crate a DSP.out file that blinks a silly LED connected to the FPGA on the SFFSDR.. when I don't have the ARM running (Uboot and then go and halt the ARM, and connect to the DSP using CCS and a USB JTAG pod it loads the program fine and blinks the LED) using the loader from DSPlink does not produce the same results i.e. no blinking LED :( I assume that there is some DSPbios configuration I am missing,, or do I have to drop the whole IDE and learn how to use the scripts? If someone can email me a DSP.out and an ARM DSPlink executable that can simply verify the workings of my board that would be greatly appreciated (the source files come with ample sample code but I have not had time to wrap my head around it yet and it is not clear you can use CCS & DSPBIOs to build them :( )... (Source and CSSproject for the supplied executables would be even more fantastic) PS has anyone ever connected to the DSP using CCS3.3 while Linux is running? Cheers Alden Cell (603) 275 9328
_______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
