• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 31 subscribers
  • Views 933 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.

SAFETI_DIAG_LIB: What are the known issues with SafeTI v2.4.0?

1138
Expert 1226 points

Part Number: SAFETI_DIAG_LIB
Other Parts Discussed in Thread: TMS570LC4357

What are the known issues with TI's SafeTI Hercules Diagnostic Library, version 2.4.0?

Note that I am looking for more recent information than is present in the release notes from late 2017.

--thx

  • 0
    TI__Guru**** 200276 points

    Hello,

    Which device do you use? Did you get any problem with the library?

  • 0 in reply to QJ Wang
    Expert 1226 points

    We're using the TMS570LC4357, silicon revision B.

    We did have some problems with the library, but we were able to successfully fix them.  When we're past our release cycle I'll have some more time available to document them for your review.

    I am not aware of any additional issues with version 2.4.0 of the SafeTI library.  That is why I am inquiring.  We would like to know about any and all known issues with the SafeTI library so that we can evaluate their impact before we encounter them (and, in particular, before our customers do).

    --thx

  • 0 in reply to 1138
    TI__Guru**** 200276 points

    Thanks for sharing the your information with us. We will take a look at if there is any known issue, then talk to you later. 

  • 0 in reply to QJ Wang
    Expert 1226 points

    Hello QJ,

    Can you please provide an update on our query?

    --thx

  • 0
    Intellectual 325 points

    Part Number: TMS570LC4357

    Hi,

    I am using the SafeTI Hercules Diagnostics Library (V.2.4.0) in my project, according to your last Release Note from 28.Nov.2017, the Safety Library (V.2.4.0) still has opened issues, listed in Paragraph 4.

    is some of these issues are closed? or if there is any new issues added to the list of Known issues?

    Thank you.

  • 0
    TI__Mastermind 21425 points

    Hello,

    I'll join this thread to a similar one that is still opened.

    Best regards,
    Miro

  • 0 in reply to Miro
    TI__Guru**** 200276 points

    Hello,

    Apologies for the delay. I will check tomorrow and reply you as soon as I can.

  • 0 in reply to QJ Wang
    TI__Guru**** 200276 points

    Hello,

    Except for the known issues listed in the release notes (v2.4.0), there are two open issues.

    1. Line 1936 in app_main_NoOS.c:  for(i = 0;i < (sizeof(all2portmemories));i++)

       sizeof(all2portmemories) is 4x the number of memory groups for PBIST.

       the wrorkaround is  for(i = 0; i < (sizeof(all2portmemories))/8; i++)

    2. Line 1106 in sl_selftest.c


    The loop variable "content" should not be used outside the for() loop.

    The workaround is to use a counter:

    unsigned int counter = 0;

    for(content = 0U; content<32U; content++) {

    counter ++;

    if((volatile uint32 )(sl_epcREG1->CAM_CONTENT[content] & EPC_CAM_CONTENT_ADDR) == (*volatile uint32 *)(flashBadECC1 & EPC_CAM_CONTENT_ADDR)) {

    break;

    }

    /* Calculate the index location */

    index = counter/4;

    index = counter - index*4;

    counter = counter/4;