TMS320F280039: call CPU1BROM_calculateCMAC() in customer bootloader

Hello,

? ? said:

I donot enable the secure boot.

Is there a reason you're not enabling secure boot given you want to calculate the CMAC status? Are you calculating a golden CMAC tag to compare against? If the CMAC calculation fails, this function either halts debugger or enables watchdog to reset device.

Here's the secure boot flow if you'd like to reference.

Best,

Matt 

1、In my understanding, if I enable the security boot mode, then the ROMboot will authentication customer bootloader after power on. Is this correct?

2、Actually, I donot know how to enable security boot mode. and how to disable the security boot mode in 280039.

So I only use the  API function CPU1BROM_calculateCMAC() in customer bootloader to authentication the application.

Could you tell me how to  control security boot mode?

2、Because the ZONE1 Header area can only changed once.

If I want to change CMAC key and not enable security boot mode，what should I set the configuration?

If I want to change CMAC key and enable security boot mode，what should I set the configuration?

3、Another question is when I set the hex format as follow, then cal the CMAC Tag.

Then load the hex image via UniFlash, but warning ocured.

And CMAC tag not download to device.

But when I cancel the configuration: "Output as bytes rather than target addressing (--byte, -byte)" and load hex image, there is no warning. And CMAC tag download to device too. Could you explain this question?

4、I plan to calculate the CMAC tag between the address: 0x84000-0xB0000. My code is located in  address: 0x82000-0xB0000. 

When I add the cmd command:

ROMS
{
FLASH_BANK0_2: o=0x00084000 l=0x0002C000, fill = 0xFFFF /* If fill not specified, then default is all 0s */
}

It seems like the data between 0x82000-0x84000 has been cut in the output hex file after build project.

Hi,

I'm going to forward this to the Secure Boot expert, he's out of office but will be back by 10/21. Please expect a delay in response till then, thank you for your patience.

Best,

Matt