• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 98 subscribers
  • Views 535 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 configuration issue in EB

Fan_Zhang
Expert 4260 points
Part Number: TDA4VM

Hi,

My customer encountered an issue while configuring Cdd_Ipc in EB.

When setting VertIoRingAddr to address other than 0xaa000000, error is reported. Detailed message is "[C:\EB\tresos\plugins\CddIpc_TI_J721E/generate/src/Cdd_IpcCfg.c (signed):274]: "VertIoRingAddr Address should be = 2852126720 " (node )"

It is shown that possible address could be "VertIoRingddr (0x1 -> 0xffffffffffffffff)", Why can not set to other address?

Please help to explain and guide the right way to change this address.

Thanks!

  • 0
    TI__Guru 50611 points

    Felix,

    You want to change address for Ring Buffer, then it must be changed:

    • Linux/Qnx  -> You need to reserve the address range, same way it is done for 0xAA000000 with size of 0x1C00000
    • Change in the application -> Probably you are doing it.
    • Also, need to modify mmu table for A72(bios), C7x (Bios)
    • Change the Cache setup for C66x accordingly.

  • 0 in reply to Santosh Jha
    TI__Expert 4260 points

    Hi, Santosh,

    I agree that related address settings should be modified accordingly to make the IPC work properly.

    To the EB issue while changing VertIoRingAddr to other value, customer is asking for the reason, and whether this address is configurable. Should customer change this address manually with EB generated code in EB output folder?

    Thanks! 

  • 0 in reply to Fan_Zhang
    TI__Guru 50611 points

    Felix,

    Let me loop in Sujith. HE is owner of Cdd_IpcCfg. 

  • 0 in reply to Santosh Jha
    TI__Genius 12455 points

    Hi Felix,

    This check was added to ensure the CDD IPC is compatible / can work with default config of TI RTOS IPC. I agree this check in EB should be removed. I have created a defect to track this (internal reference number MCAL-4469)

    For now, please update the generated Cdd_IpcCfg.c to require address manually.

    Regards, Sujith

    MCAL-4469

  • 0 in reply to Sujith
    TI__Genius 12455 points

    Also, can i know who is the customer and what is the envisioned usecase for CDD IPC?

    Regards, Sujith

  • 0 in reply to Sujith
    TI__Genius 12455 points

    Hi Felix,

    As i understand after you changed the "VertIoRingAddr " an crash is seen. Can you please check on the following.

    1. If the crash is in MCU R5F
      1. Check if the MPU is configured to allow read/write access to VertIoRingAddr
      2. i.e. consider the MCAL CDD IPC Example 
      3. The MPU is configured in mcusw\mcal_drv\mcal\examples\CddIpc\soc\j721e\mcu1_0\CddIpcR5Mpu.c
      4. Will have to update  0xAA000000 with new value
    2. If the crash is in other cores R5F cores
      1. Check on MPU config for VertIoRingAddr

    Regards, Sujith

  • 0 in reply to Sujith
    TI__Expert 4260 points

    Hi, Sujith,

    Thanks for the further information.

    Customer has modified this address TWICE during the development process.

    In the first modification, the address was changed from 0xAA000000(which is used in the SDK example) to 0xBA000000, and it worked well.

    Then in the second modification, the address was changed from 0xBA000000 to 0xBE000000, and encountered the crash issue.

    Is there any limitation or attention should be paid to while setting this address?

    Thanks.

  • 0 in reply to Fan_Zhang
    TI__Genius 12455 points

    Hi Felix,

    Presuming that 0xBE000000 is being used as address.

    I hope you have the CCS connectivity to the board, if so, after the R5F crashes. Please connect to MCU R5F, open a memory browser and type address 0xBE000000, check if it's accessible. Also, check if the complete rage is accessible i.e. in memory window type 0xBE000000 + <size allocated in hexadecimal value>

    If the MCU R5F is not crashing, please let me know which MCU is crashing

    Regards, Sujith