• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 325 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Linux/DRA76P: VIS Radio GPP Loopback

deepthi m
Intellectual 360 points
Part Number: DRA76P

Tool/software: Linux

Hi,

I am trying to route the output of RadioManager to GPP using the setting audioOutputRouting=DSPMGR_AUDIO_OUT_ON_GPP_LOOPBACK.

According to my understanding, if I use this option, the IOA component running on TI-RTOS-DSP side will write the audio data to a RingIO instance and an OutputManager component running on the Linux-ARM-A15 side.

For this I am configuring the following way:
OutputSampleRate = 44100
BoardType = 3
McaspInstance = 3

AudioOutputRouting = VIS_AUDIO_OUT_ON_GPP_LOOPBACK

I have implemented an application similar to Output_Mgr in VIS SDK which will read data from RingIO and write the data to ALSA driver.

The RingIO I am trying to read data from is "dsproc_audio_out". But I am failing to get data because of an assertion failure in "List_empty" function called within RingIO_system_setup().

Please let me know if there is something wrong in my configuration or understanding.

Also, there is a parameter called extFmEnable. Can you tell me the significance of this parameter in terms of Audio routing?

Thanks in advance,

Deepthi

Please guide us

  • 0
    TI__Prodigy 605 points
    Hi Deepthi,

    You can enable output the data to the J6 CPU board by starting RadioApp with the -o ARM option. It will set the "audioOutputRouting=DSPMGR_AUDIO_OUT_ON_GPP_LOOPBACK" as you indicated. If you really want to implement your own output manager, you should reference the output_mgr. The correct RingIO name should be ioaInRioName[0], not "dsproc_audio_out".

    The extFmEnable flag is for third party external analog input. You should leave it as 0 for JAMR3 use cases. The mcasp instance is not used when outputting audio to the CPU board. This is because the McASP on the CPU board should be configured by the ARM OS (Linux in your case).