• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 98 subscribers
  • Views 332 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.

Original question:

TDA4VM: Link error with CSL_c7xSetBR0()

TDA4VM: the distribution method

Tsurumoto
Genius 15945 points

Part Number: TDA4VM

Hi

Related to http://e2e.ti.com/support/processors/f/791/t/970739.

Will the distribution method be changed in the future?
For example, do you have a plan to support it in a coherent CSL in the future？ In that case, please let me know the schedule for it.

I ask it because, if you change distribution method to something different from the current method in the future then it will cause conflict with current our implementation.

Thanks and Best regards,

HaTa.

  • 0
    TI__Guru** 113810 points

    Hi HaTa,

    Can you please explain your question a little more in detail?

    What do you mean by coherent CSL and where is this terminology coming from?

    Regards

    Karthik

  • 0 in reply to Karthik Ramanan
    TI__Genius 15945 points

    Hi Karthk

    What I'd like to know is if you have a plan to change the SW structure in the future.

    We believe that the CSL should be gathered in the appropriate place such like "pdk_jacinto_07_01_00_45\packages\ti\csl".

    However, for example, the actual codes for CSL_c7xSetTBR0() is located at the folder for TIDL (psdk_rtos_auto_j7_07_00_00_11/tidl_j7_01_02_00_09/common/c7x_mmu/) and not for CSL.

    We describe this situation as CSL is not coherent.

    Thanks and Best regards,

    HaTa.

  • 0 in reply to Tsurumoto
    TI__Guru** 113810 points

    Hi HaTa,

    Ok, I understand your question better now, thank you for the explanation.

    From what I know, no change is planned in the near future. However, you bring an interesting point that may need an investigation to make this "coherent".

    After the investigation if anything changes I will respond on this thread.

    Regards

    Karthik

  • 0 in reply to Karthik Ramanan
    TI__Genius 15945 points

    Hi Karthik,

    Ok, I understand.

    I appreciate if you keep in your mind for about this thread, and let me know it your strategy is changed.

  • 0 in reply to Tsurumoto
    TI__Guru** 113810 points

    Hi HaTa,

    We investigated a bit further and the reasons seem to be coming from some legacy convention, we are considering to remove the CSL from the TIDL folder. But first the investigation must be completed on the impact. So this will be done very soon, you can track TIDL-1271 on the internal JIRA.

    Regards

    Karthik