• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 100 subscribers
  • Views 501 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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: The problem of image space partition in CCM matrix debugging

TDA4VM: When the EE parameter is compiled into the firmware, other modules take effect but EE does not.

chenzhe
Prodigy 190 points
Part Number: TDA4VM

Dear TI Expert,

EE does not take effect, import the bin or compile the firmware does not take effect, generate contains this XML, generate compile parameters, DCC export parameters will be more, how to take effect? Can I import the XML with DCC_TOOL_PATH as well? If some module code is not imported, then the corresponding module parameter in the firmware is the default parameter? The primary problem is that we compile the EE parameters into the firmware just like other modules, other modules can take effect but EE can't.