• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 186 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Original question:

PCM5142: no sound at output at different sample rates

PCM5142: What is the difference between "Int4xoutROM" and "INT4xOutROMsl"

UA&A_CodyDowling
Intellectual 986 points
Part Number: PCM5142

In a recent project using the PCM5142, we noticed that we ran out of resources when using the Int4xOutROM. But, when we switched over to Int4xOutROMsl it compiled with no issues. What does the "SL" designation mean? The help files are the same for both with no explanation.

Thanks for your help!

  • 0
    TI__Mastermind 24330 points

    Hello,

    Let me look into it and will get back to you by Wednesday afternoon.

    Regards,

    Arash

  • 0 in reply to Arash Loloee
    TI__Mastermind 24330 points

    Hello, I looked for some documentation for this mature device and i could not find anything specific to tell me what SL stands for. However  in PCM5142 datasheet you can see several  different  filters in table 7- Rom preset programs

    Some of the x4 filters require more cycles and some require less cycles. It maybe that the filter they are using, is causing out of resources because it takes more cycles. And when  it uses the other filter it is taking less cycles and thus  compiling ok. 

    Regards,

    Arash

  • +1
    Intellectual 986 points

    Hi Arash, 

    Thank you for the help, but actually I spend quite a bit of time on e2e and found an old post from Patrick Galvin that explained that the "sl" stood for "short latency". That would make sense, since reducing latency can be accomplished by simply reducing the amount of computations which are executed- with the tradeoff being a less aggressive/less accurate filter.

    Thanks for looking into this- I think we may have figured out a work-around so you can close this issue now.