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.

SPNU511b Safety Manual and HALCoGen 3.06

Other Parts Discussed in Thread: HALCOGEN

Hello,

HALCoGen 3.06 contains new self-test routines for detecting latent failures.

1) Many of these routines are not called.  Are there any hints on where to add a call in sys_startup.c, sys_selftest.c, or system.c, or would this have to be analyzed on a case-by-case basis?

2) Are these currently being rolled into HALCoGen 3.07?  If so, what is the expected release date?

3) Many of these mechanisms are not mentioned in the Safety Manual.  Are they currently being rolled into SPNU511c?  If so, what is the expected release date?

Thanks, Charlie Johnston

  • Hi Charlie,

    Apologize for the delay.  We just assigned this ticket and hopefully you'll get a reply soon.

    -Anthony

  • Hi Anthony,

    No need to apologize.  You folks are still much more responsive with product support than most companies.

    Thanks, Charlie

  • Hi Anthony,

    Any updates on this?

    Thanks, Charlie Johnston

  • Charlie,

    There's a new HalCoGen 3.08.01 and there's a safety lib now.  I think I routed this post to our safety lead but the software team owners for Hcg and the Safety Lib might be better at answering so we'll try that.

  • Hi Anthony,

    HALCoGen 3.08.01 does not call the new routines; I haven't checked the Safety Lib yet.  I guess the bottom line is: Will an updated Safety Manual refer to the new self-tests (no matter how they are supplied) and when is an update expected.

    Thanks, Charlie

  • Hi Charlie,

    Help me understand little more. Could you please let me know the list of API's that you are mentioning that Safety manual does not have reference. These functions may not be direct reference but I belive Safety Manual covers it all.

    There are few new API's ( I think this is what you are refering)  which are not called as part of startup by default because of user compatibilty reasons, but user can call these routines either in main or using the "User code section in sys_startup.c.

  • Hi Prathap,

    Yes, I am refering to the new APIs: 

    checkClockMonitor(), checkFlashEEPROMECC(), checkPLL1Slip(), checkPLL2Slip(), checkRAMAddrParity(), checkRAMUERRTest(), fmcBus1ParityCheck()

    As one example, checkPLL1Slip() is not mentioned in the Safety Manual Section 5.3.2.  That section says to to use PLL Slip Detection, but has no mention of self-check.  Can I then assume that the authors of the Safety Manual have no opinion on the use of the new APIs?

    Thanks, Charlie Johnston

     

  • Hi Charlie,

    Because the safety manual for hardware is independent of the software library, you will not see references to the software library in the hardware safety manual.  We have a number of customers who require that we keep this isolation as they do not want to implement TI software.  To date I haven't seen anything in the software lib which goes beyond the recommendations in the hardware documentation.

    Note that there is a planned update for the hardware safety manuals this year to coincide with each device's certification activity.  Schedules are available on the SafeTI private E2E forum or via your TI sales rep under NDA.

    Regards,

    Karl