• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 240 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

LAUNCHXL2-570LC43: SafeTI Library Expected Results

Christopher Federici
Prodigy 50 points

Part Number: LAUNCHXL2-570LC43
Other Parts Discussed in Thread: TMS570LC4357

Hello

I have opened the SafeTI Diagnostic Library v2.4.0 demo_app and updated per the two forum posts below:

    1. TMS570LC43x SAFETI - Arm-based microcontrollers forum - Arm-based microcontrollers - TI E2E support forums 

    2. LAUNCHXL2-RM57L: Hercules SafeTI Diagnostic Library V2.4.0 demo application stuck at clearing ESM error - Arm-based microcontrollers forum - Arm-based microcontrollers - TI E2E support forums

    3. Enabled FUNCTION_PROFILING_ENABLED to 1

After doing this, following files are generated to debug folder:

      1. ..\SL_TMS570LC4357_NoOS\Debug\Profile_tests.txt
      2. ..\SL_TMS570LC4357_NoOS\Debug\Profile_pbist_tests.txt

I have the following questions about this:

  1. Are there expected failures in this demo? periodicSTFailCount is set to 10 at end.

  2. If I put a breakpoint at first call to _c_int00 within resetEntry function, it will not hit on the first execution - instead the program will stop at entry to main and I can run it from there. However, if I use CCS menu (Run->Reset->CPU Reset) then the PC starts at this line / breakpoint. How come it isn't hit without doing the soft reset?

  3. If I check the result file Profile_pbist_tests.txt, it seems incomplete. THe last two lines are : 
     
    PBIST_RAMGROUP_30_L2RAMW                   PBIST_RAMGROUP_05_AWM1                     0    0    0    0
    PBIST_RAMG

    Is this expected?

  4. If I check Profile_tests.txt it seems not all tests are executed. Following tests show execution count equal to 0. Are more changes required to run all these tests?
    PBIST_EXECUTE
    PBIST_EXECUTE_OVERRIDE
    EFUSE_SELF_TEST_AUTOLOAD
    STC1_RUN
    STC1_COMPARE_SELFCHECK
    STC2_RUN
    STC2_COMPARE_SELFCHECK
    PSCON_PMA_TEST
    MEMINTRCNT_SELFTEST
    PERIPHSEGINTRCNT_UNPRIVELEGED_ACCESS
    ADC_SELFTEST_ALL

Thank you in advance for the support and examples. I have attached the output of my tests below:

Profile_pbist_tests.txt

Profile_tests.txt 

  • 0
    TI__Guru* 78136 points

    Hi Christopher,

    Apologies for the delayed response!

    Christopher Federici said:
    If I put a breakpoint at first call to _c_int00 within resetEntry function, it will not hit on the first execution - instead the program will stop at entry to main and I can run it from there. However, if I use CCS menu (Run->Reset->CPU Reset) then the PC starts at this line / breakpoint. How come it isn't hit without doing the soft reset?

    You can do two things for this,

    One is using of code-based breakpoints, to understand this please refer last comment in below thread:

    (+) TMS570LS1227: HALCOGEN stcSelfCheck breakpoint does not stop on set point - Arm-based microcontrollers - INTERNAL forum - Arm-based microcontrollers - INTERNAL - TI E2E support forums

    Second one is,

    Right click and open project properties:

    Here you can find auto run option that i highlighted here:

    Here change "main" to some other function in "_c_int00", for example you can use "getResetSource"

    Now if you start debugging your code the execution will stop at "getResetSource" itself instead of running till main function:

    Note: I am working on your remaining questions and will provide my updates soon.

    --
    Thanks & regards,
    Jagadish.

  • 0 in reply to jagadish gundavarapu
    TI__Guru* 78136 points

    Hi,

    1. Regarding expected failures:

    Yes, some failures are expected in the demo. The periodicSTFailCount being set to 10 at the end is normal and by design. The demo intentionally injects some faults to demonstrate error detection capabilities. These "failures" are actually successful demonstrations of the diagnostic features working correctly.

    3. Regarding incomplete Profile_pbist_tests.txt:

    The truncated output file is not expected behavior. This suggests the file writing process was interrupted. Possible causes include:

    • Memory constraints during execution
    • Premature termination of the application
    • Buffer overflow in the profiling mechanism

    Try increasing any buffer sizes in the profiling configuration if possible, or check if there's a file size limitation in your implementation.

    4. Regarding unexecuted tests:

    Some tests showing zero execution count is normal for this demo. The demo doesn't necessarily run all available tests by default. The tests you mentioned (PBIST_EXECUTE, STC1_RUN, etc.) may require:

    • Different configuration settings in the application
    • Hardware-specific enablement that might not be applicable for your specific board
    • Manual triggering rather than automatic execution in the demo flow

    To run these specific tests, you may need to:

    • Modify the demo application to explicitly call these test functions
    • Enable specific configuration flags for these tests
    • Check if these tests are compatible with your specific hardware variant

    If you need to run these specific tests, I'd recommend reviewing the SafeTI Diagnostic Library User Guide for configuration options specific to these test functions.

    --
    Thanks & regards,
    Jagadish.