• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 147 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: Project-related problems encountered while I was using TDA4 EVM PSDK

Katherine Wang
Intellectual 2210 points
Part Number: TDA4VM

Hi Team,

Recently, I am doing mcal development based on the demo of MCUSW in PSDK-rtos. The psdk version is ti-processor-sdk-rtos-j721e-evm-08-04-00-06. The mcu2_1 and mcu1_0 in the demo use the same source file, and only their app functions are different. Recently, I need to do IPC function and need to use mcu2_0 and mcu1_1 cores. Could you please tell me whether I should add the code part of mcu2_0 to the original project or create a new project related only to mcu2_0? When developing mcu2_0, can it be modified on the basis of mcu2_1? Why mcu1_0 and mcu2_1 can use the same set of source files? Is one set of source files suitable for all R5Fs?

Kind regards,

Katherine

  • 0
    TI__Mastermind 36307 points

    Hello,

    Yes, to clarify, the MCAL drivers are identical for the different cores. In your case the IPC driver will be the same, but at the application level they are configured for the different cores. Configuration changes that change between the cores are interrupts, interrupt routing, some initialization code, etc.

    Some of the changes are in the Configurator (EB Tresos) that generates new headers.

    The other changes are in the application code. You could use the same application code and use the defines BUILD_MCU1_0 (or similar) to separate the R5 specific code.

    Regards,

    Erick