LP-MSPM0G3519: debug CSC failure to verify application image

Crane Shao

Intellectual 910 points

Part Number: LP-MSPM0G3519

Tool/software:

Hi,

I am testing CSC example.

When testing CSC with customer_secure_simple_image, everything works fine.

When testing CSC with my own application, it doesn't work. The reason looks like that it goes directly to start the application without executing the first part of validating the images in two slots. Obviously it failed.

When further debugging the issue, just flash CSC and then check SYSCTL and BCR configuration in flash, INITDONE in SYSCTL register is already set without verifying the images. But the BCR configuration shows that CSC is enabled. Here is the screenshot:

Here is the big But. Although seeing this, it still works fine for CSC + sample image later one. I realize it properly is not the correct way to debug the CSC and I assume that the register value shown here is not the correct value.

So my questions is, if my assumption is true that this way to check the SYSCTL value is not correct?

And then I am wondering if the only way to debug where CSC fails to verify my main application is to check the information printed to Trace module, right? Any other way to do that?

Thanks!

Crane

4 months ago

0 Crane Shao 4 months ago

Intellectual 910 points

I displayed the intermedia results on UART console. Indeed, seeing the same result as single step debugging, the program goes directly to start the application without verifying the image at all.

This debugging shows the result that CSC is considered as "not existing". But it is not what's configured in BCR as posted in the question (not changed in CSC code).

This happens in below two scenarios:

1. When the size of the main application is changed. This size is changed in .json file accordingly.

2. When the offset of the main application is changed. I go back to use the example project "custome_secure_sample_image". As the size of CSC is changed . The offset of the main application in .json file is changed accordingly.

When both CSC and the main application use the sample project, it works fine.

I can understand if it fails to verify the image because the image is changed. But now, it doesn't verify the images at all but goes directly to try to start the app.

So the question: what might cause CSC the status is changed to "non-existence" while it is configured as "existence" in BCR_Config?

Thanks!

Crane