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.

TDA4VM: PBIST test failed

Part Number: TDA4VM


RamTst.zip

Hi, TI

We used SDL PBSIT interfaces(not directly) to perform the PBIST test, the test failed.

Could you help check the function fsRamTst_PBSITTst() in FS_RamTst.c? Is there anything wrong?

And refer to "SDL_RLS_01.00.00\sdl\sdl_docs\userguide\j721e\_sources\modules\pbist.rst.txt", we shall initialize the OSAL, but if we do it accordingly, MCU1 can't start. 

1. Is OSAL initialization essestial?

2. Why it affect MCU1 start?

Thank you very much!

Zhihua

  • Hi TI

    Any update?

    Zhihua

  • Hi Zhihua,

    The SDL requires the application to provide an OSAL implementation for various functionalities in order to keep SDL as OS-agnostic. Primarily, the SDL requires OSAL implementations for interrupt registration and enable/disable, and also for a delay mechanism needed for POK programming.  If the OSAL APIs are not required by your application then no need to call/implement SDL_OSAL_init().

    PBIST is an instrusive test, and it may be that you're testing/impacting the memory your code is running in.   If the provided test code is modified to test only the NAVSS PBIST, does it work?

    Regards,

    kb 

  • Hi KB

    We try test only for NAVSS PBIST

    Here is some issue summarized.

    1.  We did the test after MCAL_Init(), is it a correct place to run the test?

    2.  Interrupt Vector number of NAVSS PBIST is different in SDL and user manual

      - SDL (308)

      - user manual (297)

    3. if we use 308, interrupt register is failed, SW can't run

    if we use 297,  SW run away after PBIST test Done

    Do you have some advise for it?

    Thank you!

    Zhihua

  • Hi Zhihua,

    Is support still required on this topic?

    Regards,

    kb