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.

TMS320F280025: HWBIST lib issue in understaing the source

Part Number: TMS320F280025
Other Parts Discussed in Thread: C2000WARE

Hi everybody 

I'm doing hwbist. When I try to inject the following case error, the return values of NO_ERROR, STL_HWBIST_FINAL_COMPARE and STL_HWBIST_NMI_TRAP are the same 0x02.   So how can I distinguish them?

    //

    // Run a micro-run of HWBIST.

    //

returnVal = STL_HWBIST_runMicro();

 

any  idea ? suggestion ? 

thank you very much 

best regards

Carlo

  • Carlo,

    Can you please provide the C2000Ware path of the example project you are having the problem?

    Regards,

    Manoj

  • Hi MAnoj

    C:\ti\c2000\C2000Ware_3_03_00_00\libraries\diagnostic\f28002x\examples\test_application

     best regards

    Carlo

  • Hi Carlo,

    There are some additional flags set in global error flag that provide more detail (the STA calls STL_Util_getErrorFlag() to get its status). For example, when you inject NMI_TRAP, you'll see the STL_UTIL_HWBIST_NMI_INT flag set.

    There's a little more about the errors in this document. Note that the document is focused on F2837xD, so not all of it applies to F28002x (which supports a lower coverage level--90%), but the error injection and the debugging sections may still be helpful.

    Whitney

  • HI Whiteny ,

    still th eissue ..

    I tried to get the flag you said . If returnValue is the same, the errorFlag is the same. They still could not be distinguished .  I got the following results:

    STL_Util_getErrorFlag()  with Errorflag =0 in  more than one case ( see attached ) 

    can you help ? where am I wrong ?

    thank you 

    best regards

    Carlo

  • If you look at the document I mentioned in my previous post, it notes the the FINAL_COMPARE error doesn't actually generate any NMI or fail status, so it's expected that it would look the same as NO_ERROR.

    For LOGIC_FAULT, it doesn't generate an error status for that micro-run, but if you look at the STL_HWBIST_runFull result when that error is injected, you'll see that that both the return value and the global flag will indicate an error.

    Whitney