AM263P4-Q1: CCM Example

Hi,

As stated in the Readme here (AM263x MCU+ SDK: SDL CCM), "CCM example should only be tested in QSPI boot mode and should not be tested in no boot mode with debugger connected."

Also see the below excerpt from the TRM explaining the behavior of CCM in Debug mode, and hence you wouldn't be able to debug with breakpoints.

7.1.3.13.2.4 Operation During CPU Debug Mode Certain debug operations place the CPU in a halting debug state where the code execution is halted. Because halting debug events are asynchronous, there is a possibility for the debug requests to cause loss of lockstep. CCM-R5F will disable all functional diagnostics upon detection of halting debug requests. Core compare error will not be generated and flags will not update. A CPU reset is needed to ensure the CPUs are again in lockstep and will also re-enable the CCM-R5F.

Rapeti Sravanthi said:

And change the inputs applied for the test.

Could you please elaborate what inputs you plan to change?

Thanks,

Sahana

Hii Sahana,

Thanks for the reply,

Sahana H G said:

Could you please elaborate what inputs you plan to change?

By “inputs,” I was referring to the test patterns or data values that are provided to both cores (which are in lockstep) during the CCM self-test example. I wanted to understand if these patterns can be modified (for example, changing the operand values or operations being compared between Core0 and Core1) to check how the CCM detects mismatches.

Thanks for the reply Sahana,

I understood the test cases. Is there any other way to test the safety feature of lockstep mode. 

Regards

Sravanthi R.

Hii Sahana,

Thanks for the reply,

So we can test Lockstep feature using CCM only. And the test cases for CCM is also fixed right?

Regards

Sravanthi R.