McBSP EDMA example?

Great, I'll look forward to seeing that.

Thanks for your response!

Aaron

Is this available now for McBSP? 2.0.xx?

As mentioned it's supposed to be released in 2.0.10, currently we've released up to 2.0.9.  You can find the latest release version here.

http://software-dl.ti.com/sdoemb/sdoemb_public_sw/bios_mcsdk/latest/index_FDS.html

Just thought I'd bump this, as it's August and I still don't see the 2.0.10 release. Is there any kind of ETA on it?

Thanks,
Aaron 

Aaron,

I checked with the development team, some things were shuffled around and the current plan now has the McBSP LLD being released in MCSDK 2.1.1.  The timeframe for this release is towards the end of September.

Regards,

Travis

Aaron,

The MCSDK 2.1.1 has been released...

Regards,

Travis

BIOS MCSDK 2.1.1 is available for download; this is a maintenance update for the production R2.1.0 release. This update can be manually downloaded or automatically downloaded directly from CCS using Eclipse Update Manager; see the BIOS MCSDK User's Guide for details on setting up automatic software updates.

The major updates from the production release, BIOS MCSDK 2.1.0, are:

• Production quality software for TMS320C6657
• McBSP LLD for TMS320C6657
• Bug fixes (see the Release Notes for full list)

The BIOS Multicore Software Development Kit (MCSDK) provides the core foundational building blocks that facilitate application software development on TI's high performance and multicore DSPs. This software release gives developers the ability to evaluate major software capabilities of KeyStone family devices TMS320C6657, TMS320C6678, and TMS320C6670 and quickly begin application development. Support is provided for the TMDXEVM6657L/LE, TMDSEVM6678L/LE/LXE, and TMDSEVM6670L/LE/LXE evaluation boards and C66x simulators.

The foundational components include:

• SYS/BIOS which is a light-weight real-time embedded operating system for TI devices
• Chip support libraries, drivers, and basic platform utilities
• Interprocessor communication for communication across cores and devices
• Basic networking stack and protocols
• Optimized application-specific and application non-specific algorithm libraries
• Debug and instrumentation
• Bootloader and boot utilities
• Demonstrations and examples

See the following wiki pages for more information:

• Getting Started Guide
• User's Guide
• Out-of-Box Demo Guide
• Image Processing Demo Guide

Note that C66x device queries should be posted to the C66x Multicore E2E forum, while development tool queries should be posted to the CCS or Compiler forums as appropriate.  MCSDK related queries should be posted to the BIOS forum. See the support section of the User's Guide for more information.

Great, thanks!

What is MCBSP_LOOPJOB mode. In the case where McBSP should run continuously and earlier versions had EDMA linked so that ping pong buffers can be used. But this driver design unless mcbspSubmitChan() request goes, the ioBuf is not tied to EDMA and this submitchan has to be done for every access. Pl. can you provide some details on how to make it ping/pong buffer continuous (we normally disable hwfifo to avoid any delay etc..). I read loopjob buffer is only to replace if the buffer is not available. Pl. advise how to proceed for Ping-pong buffer scheme. 

Regards,

Hari

I've been through the mcbsp loopjob example and feel like I mostly understand it.

One significant difference I'm noticing in this driver compared to the previous IOM driver is that this does not tie directly into the BIOS at all. The example uses BIOS only to create a single task and there doesnt' seem to be any interaction of the driver with BIOS at all, only a callback function.

Am I understanding that correctly?

If this is the new model to code against, would I be correct in assuming that the simplest use case would be to just have the callback function trigger some BIOS task to handle frames of received samples?

Is this considered to be the most efficient way to handle mcbsp/edma sample processing in SYSBIOS?

Thanks,

Aaron

Hello,

Please refer http://e2e.ti.com/support/embedded/bios/f/355/t/224918.aspx

Thanks!