This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hi Team,
The intent is to use the TI TMS320C5515 DSP + TI TLV320AIC3204 audio codec to sample audio and apply Acoustic Echo Cancellation using TI AEC libraries.
Initially using the TMS320C5515 eZdsp USB stick as a demonstrator to prove the audio performance. We are currently having issues with the C5515 architecture in regards to the CPU data accesses been 16bit addressed and the CPU program access been byte addresses. This is causing some confusion with our dataflow to/from the serial port. This coupled with that CSL routines provide by TI don't seem to work in interrupt mode.
Could we get some details on how this can be addressed and some help with this issue.
King regards,
Jack
Hi John,
Please take a look at this thread regarding 8-bit accesses.
https://e2e.ti.com/support/dsp/c5000/f/109/p/371863/1308065
Are you looking for a generic .cmd file like the attached?
/cfs-file/__key/communityserver-discussions-components-files/791/7418.5460.C5515.cmd
I don't think there's any readily available code to share at this time, but looking further into it. Will post back here with any updates.
Lali
Hi Lali,
Thanks for the link regarding 8-bit accesses. I was misled into thinking 8-bit accesses were allowed by the presence of the type Uint8. Seems like maybe that should be deprecated (or at least heavily commented) for platforms where it's meaningless.
I have a generic command file, I was looking for a command file which would work on the C5515 and which met all the requirements of the AER integration guide. By the way, it seems in many of the example linker files that the various sections are allocated to different DARAM and SARAM blocks - is there a resource somewhere that details the rationale behind this approach? Is it bad just to lump all the DARAM into a single named location and allocate the relevant sections into that?
It's a shame there isn't a more user-friendly example app utilising the AER. The only app available in the distributable is the test app and this is very hard to unpick as it has lots of simulation code layered on top of the actual AER usage. The ideal would be a CCS project with linker files for the various processor types, a simple example AER configuration (e.g. 1 mic in one mode only) and stubs for data input / output which could then plug into arbitrary data paths. This would be a much easier place to start from!
Ho hum, I'll carry on.
John