TMS320F28386D: dcsm.cmd

Hi W Z,

Can you try this in SysConfig instead? Why do you need to create dcsm.cmd and dcsm.asm manually?

Thank you,

Luke

There is no sysconfig of boot_ex1_cpu1_cpu2_cm_secure_flash. Also I need to porting these two example to my customer project which also not have sysconfig.

Is there a application note to show how to add sysconfig to a old existing project?

Or could you please give the solution how to fix the posted question?

Hi W Z,

Could you share your dcsm.asm and dcsm.cmd files so I could test on my side?

I'm assuming you imported this project from c2000ware.

Thank you,

Luke

DSCM.zip

Just copy the dcsm.asm and dcsm.cm into boot_ex1_cpu1_cpu2_cm_secure_flash_cpu1, then you will get my same warning.

Hi W Z,

I will be out of office until the end of June, I will get back to you once I return.

Thank you,

Luke

Could you please help forward this thread to other available security expert? Due to project has urgent time to release. We cannot wait until end of June

This is very easy to reproduce.

Hi W Z,

I've assigned this thread to Vivek Singh, he should be able to assist while I am out of office.

Thank you,

Luke

Hi,

Can you please confirm if you are still having this issue ? 

Vivek Singh

Yes, still having this issue, need TI help.

Ok, let me check this one.

Could please let know if any update?

I have send this to our compiler team. They are looking into it. 

Hi,

These warnings are for not including the DCSM configuration for CMAC calculation which is expected. There is not issue with this.

Vivek Singh

This is not expected, I want build the DCSM configuration in the hex

W Z said:

I want to porting example dcsm_security_tool to boot_ex1_cpu1_cpu2_cm_secure_flash_cpu1.

I add the below two files in the projectspec, dcsm.asm and dcsm.cmd.

Your built has DCSM configuration. Only for golden CMAC tag calculation, it's been excluded which is expected.

Ok, I tried to remove the golden CMAC tag calculation, the DCSM configuration can be build in the hex successfully.

Does this mean that cannot build golden CMAC tag calculation and DCSM configuration together?

The question is how to handle this case for mass production scenario?

What is suggestion way from TI?

Shall burn DCSM configuration with out file? Then burn another hex with application and Golden CMAC Tag?

This may increase the time of burn the software, time is key KPI for mass production scenario.

Hi,

W Z said:

Does this mean that cannot build golden CMAC tag calculation and DCSM configuration together?

What is the observation here ? Are you not seeing the security configuration in hex file when you include the DCSM setting ? As per my understanding the warning msg is saying that USER OTP section is excluded from CMAC calculation which is expected. 

Vivek Singh

Vivek Singh said:

What is the observation here ? Are you not seeing the security configuration in hex file when you include the DCSM setting ?

Yes. Not seeing the security configuration in the hex file when include the DCSM setting.

You got what I am facing now.

The hex which  include the security setting, the address shall start like below from 0x00078000

I think this could be the limitation. I have send this query to out tool team.

I am following this case, if have any update, please let me know. Thanks.

Hi,

I am still waiting for response from our team. Have pinged then again.

Vivek Singh

If any update, please let me know.

Sorry, no update yet. 

Looping in our compiler team to provide their expert comment on this.

Vivek Singh

Just wanted to update that it may take some more time to look into this issue. 

Hello Vivek Singh,

Does Tool team have the feedback?

Ok, Thanks Vivek.