Hi. NXP Team.
I am struggling with Index 11(m4_scst_exception_test_handler_thread) of the SCST Test.
The m4_scst_exception_test_handler_thread will throw a hardFault_Handler as shown in Figure 1 when tested with the trace32 debugger attached.
<Figure 1>
But if I remove the debugger it works fine.
(The expected Test Reference Signature is output.)
So I removed the debugger and did m4_scst_execute_core_tests(0,43).
But the test result is failure.
(If core_test is performed one by one without a debugger, normal signatures are output.)
In my opinion, the single test works fine.
But when I run the tests consecutively, Index 11 of the m4_scst_execute_core_tests seems to fail.
Please refer to Figure 2.
<Firgure 2>
I don't know how to test.
I would like to ask for your help.
Hello,
first, please, what product version do you use? Most probably, it is 1.0.4 version which is relatively old. The newest version is 1.0.10, would it possible to migrate to it?
The described behavior might be because the FORCED flag is tied down by the debugger. Unfortunately, this feature complicates debugging of M4 SCST Library. The only possibility for debugging is to set the breakpoint just after the HFSR register is read.
Thanks for your reply.
Currently using the old version, and ordering the new version.
The debugger issue you described has now been resolved.
But I have another problem.
Core test fails as global variable is added.
Can you give me some advice on this?
Hello,
Could you, please, be more specific what global variable do you mean?
Note, that SCST provides 4 global variables, please see SCST User Manual for more details:
Thank you for your reply.
The answers to your questions are summarized below.
Could you, please, be more specific what global variable do you mean?
A : Could this be related to the manual's customSection guide?
Thank you for the additional information.
Please, provide us more information about how SCST fails:
Could this be related to the manual's customSection guide?
- Maybe yes. User application shall not place its global variables into SCST custom sections. Please check your .map file for possible conflicts.