TDA4VM: Move encode from mcu2_1 to mcu2_0

Hi xianogang liu,

Sure, i will provide you patches, but this FAQ demonstrates how to move DMPAC from mcu2_1 to mcu2_0.. For encoder, it could require additional changes, like more local heap memory.

Before that, any specific reason for moving coded to mcu2_0? 

Also please note that starting from SDK8.0, encoder is no longer supported on R5F code.. 

Regards,

Brijesh

Hi Brijesh Jadav:

We are developing in sdk 7.03 now. We try to implement secure functionality in mcu2_1 and immigrant autosar cp to it. Because we dont know how to use tiovx in autosar , so we have to immigrant the origin functionality out of mcu2_1 such as encode/decode.

By the way, why encode/decode is moved out of sdk8.0? Which new version encode can be supported again? 

Hi Brijesh Jadav:

Right now CAN and 4G are runing in muc1_0. If security function is implemented in mcu1_0, the start up speed and cpu load will be affected obviously.

Additionally, Vendors help us immigrant autosar to mcu2_1, and camera/display can be accessed from main domain directly, so we consider to do security in mcu2_1.  

Hi xiaogang liu,

Can you consider using mcu3_0 or mcu3_1 for security management? 

The reason for asking this is, if we move codec to mcu2_0, it can increase load one mcu2_0. So if you are using CSIRX, VPAC, DSS on mcu2_0, codec will further add load to the mcu2_0. 

Also Starting from SDK8.0, codec is anyway moved to A72.

Regards,

Brijesh

Hi Brijesh Jadav:

Yes, we can use mcu3_1 for security management.

We are using sdk7.03 now, could you please  give me a demo or patch to show how to immigrant the encode module.

As we get the new version sdk, it is hard to extract the encode update from the source code. 

Hi xiaogang liu,

encode is not supported in the SDK8.0, i think it is supported in sdk8.1.. Could you please refer to the PSDKLA documentation? 

Regards,

Brijesh