• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 99 subscribers
  • Views 424 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.

TDA4VM: CDD IPC question(differenc e between SDK7.3 and SDK8.1)

TS L
Intellectual 911 points

Part Number: TDA4VM

Hi expert

I am transplanting my program from SDK7.3 to SDK8.1,I found that,CDD IPC driver source code change,like this.

 --> static code from TI SDK.

 --> configuration code whih is generated by EB Tool.

Question:

1). Why TI chagne the buffer length? bug fixing ? or IPC driver in PDK change which lead to CDD IPC change?

2). Is that means I have to update EB Tool?

  • 0
    TI__Guru*** 125245 points

    Hi TS L,

    1. Yes, the change was made as part of a bug fix and maintaining compatibility with corresponding changes in PDK IPC. 

    A RPMessage IPC transport buffer is of 512 bytes with 496 bytes of data payload and 16-bytes of rpmsg header.  The PDK IPC code pre-allocates the buffers needed for storing the incoming messages onto an end-point in RPMessage_create(). The same buffer is also used as a linked list for queueing all the buffers, this required additional bytes that the 16-bytes of rpmsg header couldn't support. This was fixing a bug when messages with maximum payload of 496 bytes were resulting in list corruption.

    2. I will let Erick answer #2.

    regards

    Suman

  • 0 in reply to Suman Anna
    Intellectual 911 points

    Hi Suman

    Thanks for your answer for 1st question.

    and

    Look forward to the 2nd question's answer.

    regards.

    TSL.

  • 0 in reply to TS L
    TI__Mastermind 36307 points

    Hi TS L,

    You will need to update your configuration in the EB tool to see this update reflected. The following MCUSW Configuration packages are delivered for these SDKs:

    SDK 7.3 - MCUSW_01_03_02_04_CONFIG-windows-installer.exe

    SDK 8.1 - MCUSW_01_03_04_01_CONFIG-windows-installer.exe

    The generated files you referenced in your second picture should be generated by the corresponding CONFIG release. Please let me know if you need help with accessing this, or if you have any other questions.

    Regards,

    Erick