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.

TMS320F28377D: What is the difference between MICRO and FULL in the testing diagnostic library?

Part Number: TMS320F28377D
Other Parts Discussed in Thread: C2000WARE

I am asking this for our customer.

In the diagnostic library

C:\ti\c2000\C2000Ware_1_00_01_00\libraries\diagnostic\f2837xd\examples\cpu1\test_application

sta_tests.c

What is the difference between MICRO and FULL?

    STA_HWBIST_MICRO,

    STA_HWBIST_FULL

They look simiar. Shoud the user use either or both?

Likewise, What is the difference between MICRO and FULL? Shoud the user use either or both?

    STA_CLA_MICRO,

    STA_CLA_FULL,

  • Hi champs,

    Do you have any update?

  • The STL_HWBIST_runFull() function runs hundreds of micro runs until HWBIST completes. This is the function to use if you want to test the full CPU at start up.

    STL_HWBIST_runMicro() only runs a single micro run. This function is intended to be used if you want to test the CPU periodically. Since each micro run is short, you can call it periodically without disrupting your application, unlike STL_HWBIST_runFull() which can take a long time. After calling it enough times, it will eventually return a "STL_HWBIST_BIST_DONE" value, letting you know that full coverage has been reached. You can then reinitialize the HWBIST and start the process again.

    Note that the STA does not show how to use STL_HWBIST_runMicro() realistically. Since we are running both micro and full in the same loop, the HWBIST gets reinitialized every time, but like I mentioned above, if you're doing a periodic micro runs, you only need to initialize it once, call STL_HWBIST_runMicro() until BIST_DONE is returned, then reinitialize to restart the process.

    Whitney